| 1 | [[TOC]] |
| 2 | |
| 3 | = GRASS GIS Sample Datasets = |
| 4 | |
| 5 | ''Description and discussion of (future) GRASS GIS 7 data set - an updated and simplified `nc_spm_08`, to be used in manual pages, tutorials, courses, code testing, development and OSGeo Live. |
| 6 | |
| 7 | Contributors: Markus Neteler, Helena Mitasova, Vaclav Petras, Anna Petrasova, Hamish Bowman, [contribute and add yourself] |
| 8 | |
| 9 | == Proposal == |
| 10 | |
| 11 | === Basic NC location with PERMANENT mapset === |
| 12 | |
| 13 | This is practically the gisdemo location with some updates. |
| 14 | |
| 15 | * loc_ncspm_baseline |
| 16 | * PERMANENT |
| 17 | * raster: |
| 18 | * elevation |
| 19 | * elevation_shade |
| 20 | * landuse |
| 21 | * basins |
| 22 | * orthophoto(?) |
| 23 | * soils? |
| 24 | * lakes? |
| 25 | * geology? |
| 26 | * vector: |
| 27 | * boundary_region |
| 28 | * boundary_state |
| 29 | * census |
| 30 | * streams |
| 31 | * streets |
| 32 | * railroads |
| 33 | * schools |
| 34 | * hospitals |
| 35 | * firestations |
| 36 | * points_of_interest |
| 37 | * historical sites |
| 38 | * geonames |
| 39 | * geology |
| 40 | * sqlite |
| 41 | * mymapset1 |
| 42 | |
| 43 | === Specialized mapsets === |
| 44 | |
| 45 | That can be inserted into baseline location - each will need to be distributed with a barebone location/PERMANENT so that it is readable by GRASS without the baseline data set. |
| 46 | |
| 47 | Providing just mapsets did not work, it was very confusing for users. But perhaps the only problem was that that "GRASS welcome screen" cannot unpack (unzip, untar) a mapset and copy it into an existing mapset. |
| 48 | |
| 49 | * mapset_ncspm_dem |
| 50 | * mapset_ncspm_landsat |
| 51 | * mapset_ncspm_networks |
| 52 | * mapset_ncspm_orthoimg |
| 53 | |
| 54 | === Basic world location === |
| 55 | |
| 56 | * loc_world_ll_baseline |
| 57 | * PERMANENT |
| 58 | |
| 59 | * specialized mapsets |
| 60 | * mapset_ll_climate |
| 61 | * mapset_ll_landcover |
| 62 | |
| 63 | == Notes after HVA discussion with Hamish == |
| 64 | |
| 65 | * barebone dataset for OSGeo Live which will include a script to generate the derived data needed for tutorials (?) |
| 66 | * metadata |
| 67 | * maps (layers) |
| 68 | * exclude layers which can be generated |
| 69 | * secref elevation? + orthophoto |
| 70 | * add NC WMS service to GUI |
| 71 | * soils, geology, lakes just vector |
| 72 | * elevation, landuse, orthophoto |
| 73 | * fields - parcel plots - with anonymized names - for secref - planimetry |
| 74 | * SPOT image |
| 75 | * elevation and precipitation points into baseline |
| 76 | * add zipcodes |
| 77 | * powerlines (extended) |
| 78 | * separate layers for state and counties boundaries |
| 79 | * natural earth for latlon dataset |
| 80 | |
| 81 | |
| 82 | == Comments == |
| 83 | |
| 84 | The data sets can be distributed separately or we can have packages with several mapsets or all mapsets, depending on the size. |
| 85 | I found that packaging and distributing mapsets without location is not practical, so I ended up distributing the specialized mapsets with nc_spm_baseline or world_baseline - is this OK?. |
| 86 | We also need to figure out how to include the original metadata that come with the original data - link to the source in history file may be enough. |
| 87 | |
| 88 | The baseline location+mapset should be simple with easy to understand names of map layers, |
| 89 | my only issue is the loc_ncspm_baseline name as I am not able to come up with |
| 90 | a simple name that would say that this is a location with North Carolina data in state plane meters coordinate system - maybe loc_ncarolina would be better, assuming that state plane in meters is the official coordinate system for NC? But I also keep ncspf for feet and ncutm. |
| 91 | |
| 92 | == Notes about data sources == |
| 93 | |
| 94 | There is a lot of data, main challenge now is to select a consistent, meaningful, but not too large data set. |
| 95 | Many data sets are regularly updated and new ones are posted but tutorials and man pages require stable data to work |
| 96 | the history file should include link to the original data source with a note that an updated version of the data map be available from there |
| 97 | |
| 98 | Significant natural heritage areas and natural heritage element occurrences posted on NC one map. |
| 99 | |
| 100 | |
| 101 | == TODO == |
| 102 | |
| 103 | ''List of actionable items.'' |
| 104 | |
| 105 | * replace historical markers with historical places (done?) |