<div dir="ltr"><span style="font-family:arial,sans-serif;font-size:13px">>With the availability of LANDSAT-8 imagery now coming on line[1] it seems a good time to make an accessible common sample</span><div><span style="font-family:arial,sans-serif;font-size:13px"> >dataset available for everyone to play with and adapt+race their various softwares against. More acutely for the OSGeo Live DVD we're </span><div>
<span style="font-family:arial,sans-serif;font-size:13px">>looking for a modern multi- or hyper-spectral imagery standard dataset that we can share between quickstarts. The newly online </span></div><div><span style="font-family:arial,sans-serif;font-size:13px">>MERIS data[2] might be nice for that but the EU is not as gifting as the US gov't wrt copyright redistribution issues (although this new</span></div>
<div><span style="font-family:arial,sans-serif;font-size:13px"> >release is really encouraging!) and the MERIS ground resolution is 10x coarser than that of LANDSAT.</span><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">>The obvious choice for a ground target is to continue with the Raleigh, NC osgeo-edu landsat time-series[3], and on 2013-05-14 there >was a nice image taken:</span><br style="font-family:arial,sans-serif;font-size:13px">
<span style="font-family:arial,sans-serif;font-size:13px">>? </span><a href="http://muck.otago.ac.nz/~hamish/osgeo/screenshots/LC80160352013134LGN03_rgb.jpg" target="_blank" style="font-family:arial,sans-serif;font-size:13px">http://muck.otago.ac.nz/~hamish/osgeo/screenshots/LC80160352013134LGN03_rgb.jpg</a><br style="font-family:arial,sans-serif;font-size:13px">
<br style="font-family:arial,sans-serif;font-size:13px"><span style="font-family:arial,sans-serif;font-size:13px">>In the above link the red box is the bounds of the earlier imagery crop. This time I propose that the earlier scenes were a bit small, and </span><div>
<span style="font-family:arial,sans-serif;font-size:13px">>to increase the image size to 1000x1000 cells. Raleigh-Durham Airport is present in the NW corner of the proposed new bounds for </span></div><div><span style="font-family:arial,sans-serif;font-size:13px">>visual scale and human interest.</span><br clear="all">
<div> I think adding the LANDSAT-8 data is a good idea and I take Hamish's point about the need for coastal data. I also started thinking about data for mountainous areas. </div><div><br></div><div>Hamish's post also got me thinking about making more updated datasets available for the same footprint as the NC dataset. There is 4 band digital aerial imagery ( NAIP , USDA summer 2012 , 1m resolution) and 3 band 6 inch winter imagery ( State of NC 2010 ortho , possibly 4 band for Wake County), etc for the Raleigh/ Wake County area. There may also be higher resolution Lidar data available in the future. </div>
<div><br></div><div>Of course, the more data you add, the bigger the download, or more space needed on the live-demo iso image. </div><div><br></div><div>Would it be a good idea to have a "core" downloadable dataset at <a href="http://www.grassbook.org/data_menu3rd.php">http://www.grassbook.org/data_menu3rd.php</a> and have a supplimentary download link for other, updated higher resolution data sets for the same footprint or other specific distinct geophysical environments?</div>
<div><br></div><div>Doug</div><div><br></div><div><br></div><div><br></div>-- <br><div>Doug Newcomb</div><div>USFWS</div><div>Raleigh, NC</div><div>919-856-4520 ext. 14 <a href="https://mail.google.com/mail/?view=cm&fs=1&tf=1&to=doug_newcomb@fws.gov" target="_blank">doug_newcomb@fws.gov</a></div>
<div>---------------------------------------------------------------------------------------------------------</div><div>The opinions I express are my own and are not representative of the official policy of the U.S.Fish and Wildlife Service or Dept. of the Interior. Life is too short for undocumented, proprietary data formats.</div>
</div></div></div></div>