Difference between revisions of "Edu Data Package North Carolina"

From OSGeo
Jump to navigation Jump to search
Line 30: Line 30:
  
  
We should have a latlong location and a location in state plane coordinate system in meters - that is official for NC, but many organizations (counties, NC Flood) use feet...
+
Coordinate systems:
 +
*Geographic Coordinate System in decimal degrees WGS84 (or NAD83?)  horizontal datum: EPSG:4326 SRS/CRS
 +
that all the OGC compliant software tends to use
 +
*NC State Plane Coordinate System, NAD 83 datum, units of meters
 +
*lot of local data and NCFlood mapping lidar come in US Survey feet
 +
*xy for scanned historical maps and other non-georeferenced data
 +
 
  
 
We suggest to package the data set in thematic sets (aka GRASS Mapsets concept).
 
We suggest to package the data set in thematic sets (aka GRASS Mapsets concept).
  
The below list needs to be organized into thematic sets, such as baseline data, imagery, census, terrain, ... it is too messy now
+
The below list needs to be further organized into thematic sets, Ramona GIS inventory http://nc.gisinventory.net/
 +
is used in the updated sections.
 +
 
 
=== RASTER ===
 
=== RASTER ===
====Basic data set (minimum needed to replace Spearfish) - put into PERMANENT====
+
====Framework (minimum needed to replace Spearfish) - put into PERMANENT====
 
**elevation
 
**elevation
 
**landcover
 
**landcover
**satelite imagery
+
**orthoimagery
 
***all other rasters can be derived from elevation and vector data: put them into user1?
 
***all other rasters can be derived from elevation and vector data: put them into user1?
 
***derived from DEM:
 
***derived from DEM:
 
**slope, aspect
 
**slope, aspect
**upslope area, streams (derived from DEM)
+
**contributingarea, streams (derived from DEM)
 
**erosion
 
**erosion
 
***derived from vector data
 
***derived from vector data
 
**climate stations (to replace bugsites)
 
**climate stations (to replace bugsites)
**fields, owner, soils, geology, landuse, landcover (vegetation)
+
**fields (replace by parcels?), soils, geology, landuse
**rairoads, roads, streams
+
**rairoads, roads
 +
**hydrography (note Ramona does not use terms streams, lakes, rivers, should we?)
  
 
====Additional data that can go into the basic/general data set====
 
====Additional data that can go into the basic/general data set====

Revision as of 18:36, 21 August 2006

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

Proposed new data set North Carolina

Area in and around Wake county (eastern section of the Triangle) has public data for all basic data layers that were in Spearfish and there is an easy access to USGS data, local county data, EPA, State Climate Office, NCFlood maps and others through the above listed web sites. There is a big enough city, but also some rural areas that still have some agriculture with rolling topography . SE of it is Johnston county that has FOSS-based county GIS, running mapserver and PostGIS on-line.

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)


Coordinate systems:

  • Geographic Coordinate System in decimal degrees WGS84 (or NAD83?) horizontal datum: EPSG:4326 SRS/CRS

that all the OGC compliant software tends to use

  • NC State Plane Coordinate System, NAD 83 datum, units of meters
  • lot of local data and NCFlood mapping lidar come in US Survey feet
  • xy for scanned historical maps and other non-georeferenced data


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

The below list needs to be further organized into thematic sets, Ramona GIS inventory http://nc.gisinventory.net/ is used in the updated sections.

RASTER

Framework (minimum needed to replace Spearfish) - put into PERMANENT

    • elevation
    • landcover
    • orthoimagery
      • all other rasters can be derived from elevation and vector data: put them into user1?
      • derived from DEM:
    • slope, aspect
    • contributingarea, streams (derived from DEM)
    • erosion
      • derived from vector data
    • climate stations (to replace bugsites)
    • fields (replace by parcels?), soils, geology, landuse
    • rairoads, roads
    • hydrography (note Ramona does not use terms streams, lakes, rivers, should we?)

Additional data that can go into the basic/general data set

  • 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
    • DRG topo sheets
    • Historical maps, e.g. Schools situation North Carolina 1871 to 1876
    • HydroSHEDS data (check if resolution is high enough) URL, but only non-commercial use
  • Derived data (from vector maps, maybe not needed? - this should go into specialized packages - e.eg. terrain analysis, image processing):
    • DEM from Lidar vector points
    • complete set of topographic parameters (slope, aspect, different types of curvature)
    • streams from DEM
    • landforms
    • derived satellite indices
    • hydrologically conditioned SRTM V2

VECTOR

  • point 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
    • US Census 2000 maps
    • ZIP codes

Packaging issues

  • convert feet to meters if needed
  • File Naming convention
  • Metadata management (most data include standard FGDC metadata)
  • provide in common GIS formats as well as GRASS location

... see Geodata Packaging Working_Group#Tasks.

Additional proposed themes for data sets

  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, has the old USGS streams but also the high resolution streams 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).