Edu Data Package North Carolina

This page is an ideas collection for a new educational/training data set. We want to create a new data set similar to the GRASS Spearfish dataset. This page is being worked on by Helena Mitasova and Markus Neteler.

NC related Data Sources

• http://nationalmap.gov/ and http://seamless.usgs.gov/
• http://gisdata.usgs.net/website/NC_OneMap/viewer.asp
• http://nmviewogc.cr.usgs.gov/viewer.htm (NC One map, Johnston county and others)
• Additional links are here: http://skagit.meas.ncsu.edu/~helena/classwork/hon297webgis.html
• General list: Geodata Packaging Working_Group#Public_Datasets_for_Possible_Mirroring_or_Distribution

• Additional, specialized data can be obtained here:
  • Coastal lidar: http://www.csc.noaa.gov/crs/tcm/about_ldart.html
  • Flood maps:http://www.ncfloodmaps.com/default_swf.asp
  • Real-time streamflow data (these should be available through the national map too): http://water.usgs.gov/waterwatch/
  • Climate data: http://www.nc-climate.ncsu.edu/cronos/map.php
  • USDA should have the soil data or http://www.ncgc.nrcs.usda.gov/products/datasets/ssurgo/
  • Very detailed county data (parcels, building footprints, etc.) can be viewed here: http://imaps.co.wake.nc.us/imaps/main.htm?msize=525 (no downloading - that should be handled by the National map)

Proposed new data set North Carolina

Wake county (that is Raleigh, Cary etc., around here) would be pretty good. It has everything mentioned below and a lot more and one has both the USGS data and the local county data, EPA, State Climate Office, NCFlood maps are finished here too. There is a big enough city, but also some rural areas that still have some agriculture. SE of it is Johnston county that has FOSS-based county GIS, running mapserver and PostGIS on-line. But it has only small towns and rather flat topography.

Suggested region (should be slightly more than Spearfish, around 20x20miles):

• LL(SW) corner: -78.7854 (78:47:06), 35.5897 (35:35:23)
• UR(NE) corner: -78.4466 (78:26:46), 35.8689 (35:52:08)

We should have a latlong location and a state plane in meters - that is official for NC, but many organizations (counties, NC Flood) use feet...

We suggest to package the data set in sections (aka GRASS Mapsets concept).

RASTER

Original data:

• elevation (NC One map USGS NED, lidar based)
• landuse/landcover (NC One map EPA 1998, check for newer)
• aerial images (raw stereo pair + orthophotos)
• raw geocoded satellite data, derived vegetation indices and land surface temperatures
• raw SRTM V2
• HydroSHEDS data (check if resolution is high enough)

Derived data (from vector maps, maybe not needed?):

• DEM from Lidar vector points
• streams from DEM
• derived satellite indices
• hydrological sound SRTM V2

VECTOR

• point data:
  • climate stations: temp., precip., frost, wind, cloud cover, ...
  • diseases incident data
  • hydrological data
  • Lidar point clouds
  • placenames (gazetteer data)
  • pollution and contamination data
  • results of elections
  • soils (Wake County Soil data)
• line data:
  • railroads
  • roads (TIGER and simplified)
  • streams
• area data:
  • countyboundaries
  • geology
  • landowners (should cover owners, fields)
  • landuse/landcover
  • parcels (land owners, fields)
  • quadrangles
  • soils
  • urban areas
  • ZIP codes

Packaging issues

• convert feet to meters if needed
• File Naming convention
• Metadata management
• provide in common GIS formats as well as GRASS location

... see Geodata Packaging Working_Group#Tasks.

Proposed NC themes for education

1. Coast
2. Urban
3. Atmospheric 3D
4. Hydrology and earth surface processes
5. Vegetation, land use (image processing, multitemporal)
6. Note for example the NCOne hydrography, it has the old USGS streams but also the high resolution streams (they call it flowlines) derived from the lidar data using the methodology developed for EDNA, so one can nicely demonstrate how the small scale (in cartographic sense) national data are inaccurate when one would try to use it a local scale (also how you would damage your DEM if you would have tried to use them

for stream enforcement).