Geodata Repository - Revision history

Martin: Mspott is now Martin

2021-04-05T10:44:01Z

Mspott is now Martin

Wiki-Brylie: /* TODO */

2013-10-21T12:19:34Z

TODO

Wiki-Brylie: /* How the data gets in */ grammar, wording, structure

2013-10-21T12:19:02Z

How the data gets in: grammar, wording, structure

Neteler: /* See Also */ +http://grasswiki.osgeo.org/wiki/Global_datasets

2013-04-26T21:08:41Z

See Also: +http://grasswiki.osgeo.org/wiki/Global_datasets

Arnulf: /* Metadata */

2011-08-19T15:46:52Z

Metadata

Martin: /* TelaScience / OSGeo / FlightGear Landcover Database Shapefile Download */

2010-04-04T16:34:33Z

TelaScience / OSGeo / FlightGear Landcover Database Shapefile Download

Martin: Update Custom Scenery comment

2010-02-18T13:20:14Z

Update Custom Scenery comment

Martin: Add number of CS layers

2009-07-25T12:41:50Z

Add number of CS layers

Martin: Drop Landsat7, now incorporated into Custom Scenery

2009-07-25T12:38:39Z

Drop Landsat7, now incorporated into Custom Scenery

Martin: Avoid duplicate pointers on the same page

2009-04-26T16:30:53Z

Avoid duplicate pointers on the same page

@@ Line 21: / Line 21: @@
 * Markus Neteler is contributing data processing code and resources as part of the GRASS data packaging effort
 * Norm Vine is providing a point of contact for administering the system and general reality-checking to all involved.
-* [[User:Mspott|Martin Spott]] maintains the content of the [[Geodata_Repository#PostGIS_serving_vector_data|PostGIS-repository]] on 'zuluviz'.
+* [[User:Martin|Martin Spott]] maintains the content of the [[Geodata_Repository#PostGIS_serving_vector_data|PostGIS-repository]] on 'zuluviz'.
 = Interface Design =

@@ Line 152: / Line 152: @@
 The data are stored internally in the respective, geospatially searchable geometry data type.
-=== TODO ===
+=== Timeline ===
 ==== Phase 1 ====

@@ Line 133: / Line 133: @@
 ==== How the data gets in ====
-* Many datasets are readable with the GDAL/OGR(/OGDI) toolbox. Notably these are the VMap datasets, GSHHS, PGS, SWBD and MGRS. The 'ogr2ogr' command is used here, hidden behind a somewhat complex contruct of shell scripts which automates the whole thing. Writing to the DB is accomplished by the PostGIS driver provided by 'ogr2ogr'.
+Many datasets are readable with the GDAL/OGR(/OGDI) toolbox. Notably these are the
-* Some other datasets are automagically or manually (for those sets which are not expected to change often) transformed into OGC-compilant SQL scripts and run through the respective SQL monitor.
+* VMap datasets,
-* Few datasets are being imported right into the DB with Perl/DBI. AptNav for example is parsed from a text file with a home-grown parser in Perl and written to the database table with DBI.
+* GSHHS,
-* Everything that is meant to represent a geometry is stored in the DB using OCG-compilant geometry types POLYGON, LINESTRING and POINT. A POINT for example is written into the DB for example as "INSERT INTO <Tablename> ([...]) VALUES ([...] PointFromText('POINT(<Lon> <Lat>)', 4326) [...])" and stored internally in the respective, geospatially searchable geometry data type.
+* PGS,
 === TODO ===

@@ Line 235: / Line 235: @@
 = See Also =
+* OSGeo's [[Geodata Discovery Working Group]] - half-dormant
-* [[Geodata Discovery Working Group]] - half-dormant
+* http://grasswiki.osgeo.org/wiki/Global_datasets
 * [http://www.mapdex.org/search/ MapDex] offers a metadata search facility
 * [http://www.geonames.org/ GeoNames] is a gazetteer and naming collection

← Older revision		Revision as of 15:46, 19 August 2011
Line 217:		Line 217:

	See http://mapserver.flightgear.org/download.psp		See http://mapserver.flightgear.org/download.psp
		+
		+	== City of Vienna, Austria ==
		+
		+	[http://data.wien.gv.at OGD Wien] offers data under CC-BY. This data can be imported to [[OSM]]. Supported interface standard include:
		+	* WMS
		+	* WFS GML
		+	* JSON
		+	* KML geplant
		+	Contact on IRC at #ogdwien.

	= Metadata =		= Metadata =

@@ Line 214: / Line 214: @@
      TileCache: http://mapserver.flightgear.org/tc (EPSG:900913 !!)
-== SDSU / OSGeo / FlightGear Landcover Database Shapefile Download ==
+== TelaScience / OSGeo / FlightGear Landcover Database Shapefile Download ==
 See http://mapserver.flightgear.org/download.psp

@@ Line 124: / Line 124: @@
 |-
 |Custom Scenery
-|Landuse data at selected areas [http://mapserver.flightgear.org/map/?lon=13.40385&lat=52.50199&zoom=11 (example)] has been auto-classified from Landsat7-images and converted into suitable polygons at the [http://www.custom-scenery.org/Research-Deve.274.0.html World Custom Scenery Project]. More to come.
+|Landuse data at selected areas [http://mapserver.flightgear.org/map/?lon=9.20438&lat=47.63982&zoom=11 (example)] has been auto-classified from Landsat7-images and converted into suitable polygons at the [http://www.custom-scenery.org/Research-Deve.274.0.html World Custom Scenery Project].
-In contrast to the datasets which are listed above, the purpose of this chapter is to serve as a place for developing our future schema layout in collaboration. According to the planning, this will use VMap0 data as a basis, improved by "home grown" landcover data.
+In contrast to the datasets which are listed above, this chapter is the place for our future development. It consists of VMap0 data as a basis and is being improved either by "home grown" landcover data or by imports of "free" (TM) datasets.
-* This import is done manually whenever new data is being mada available, result is supposed to me merged into VMap0.
+|61 [[LandcoverDB_CS_Detail|(DETAIL)]]
 |}
 Many thanks to Norman Vine for running the HCRA, the "Human Communications Relay Agent"  :-)

@@ Line 123: / Line 123: @@
 |1 [[LandcoverDB_FGSODB_Detail|(DETAIL)]]
 |-
-|Landsat7
+|Custom Scenery
 |Landuse data at selected areas [http://mapserver.flightgear.org/map/?lon=13.40385&lat=52.50199&zoom=11 (example)] has been auto-classified from Landsat7-images and converted into suitable polygons at the [http://www.custom-scenery.org/Research-Deve.274.0.html World Custom Scenery Project]. More to come.
-* This import is done manually whenever new data is being mada available.
+In contrast to the datasets which are listed above, the purpose of this chapter is to serve as a place for developing our future schema layout in collaboration. According to the planning, this will use VMap0 data as a basis, improved by "home grown" landcover data.
-|18 [[LandcoverDB_Landsat7_Detail|(DETAIL)]]
+* This import is done manually whenever new data is being mada available, result is supposed to me merged into VMap0.
 |?? [[LandcoverDB_CS_Detail|(DETAIL)]]
 |}

@@ Line 43: / Line 43: @@
 * [http://mapserver.flightgear.org/ Graphical MapServer interface]
 * [http://mapserver.flightgear.org/download.psp Download Shapefiles]
-* [http://mapserver.flightgear.org/ms?Service=WMS&Version=1.1.1&request=GetCapabilities WMS GetCapabilities]
+* [[Geodata_Repository#WMS_.2B_WFS_.2B_TileCache_services|WMS + WFS + TileCache services - see below]]
- The web mapping colour schema has been applied in accordance with the [http://terrestrial.eionet.europa.eu/CLC2000/ Corine Land Cover] project.
+    The web mapping colour schema has been applied in accordance with the [http://etc-lusi.eionet.europa.eu/CLC2000/classes/ Corine Land Cover] project.
 * Direct read access to the database is available to users of the 'geodata.telascience.org' system. Retrieval in SQL syntax as "SELECT asText(wkb_geometry) FROM <Tablename> WHERE <Column> LIKE '<Keyword>'".
@@ Line 177: / Line 175: @@
 * Generation of shapefiles on-the-fly for user-defined region and layer(s). Use 'pgsql2shp' and consider the 2 GByte-per-file limit: [http://mapserver.flightgear.org/download.psp Landcover Database Shapefile Download]
 * Rebuild TIGER layers from 2006se release according to [http://docs.codehaus.org/display/GEOSDOC/Loading+TIGER+data these instructions] - mostly finished.
-* Limit the "viewing angle" of WMS/WFS-services in order to save the DB-servers' life ....  Solved by setting MAXSCALE
+* Limit the "viewing angle" of WMS/WFS-services in order to save the DB-servers' life ....  Solved by setting MAXSCALE for some layers.
 === Old status ===