OSGeodata: Unterschied zwischen den Versionen

Aus Geoinformation HSR
Wechseln zu: Navigation, Suche
(Weblinks)
(Weblinks)
 
(36 dazwischenliegende Versionen von 4 Benutzern werden nicht angezeigt)
Zeile 1: Zeile 1:
 
== Overview ==
 
== Overview ==
  
These are experimental pages originated from OSGeodata Mailing List on [https://geodata.osgeo.org/servlets/BrowseList?listName=geodata&by=date&paged=false OSGeo.org].
+
These are experimental pages ([[OSGeodata Discovery|1]],[[OSGeodata metadata exchange model|2]],[[OSGeodata metadata exchange protocol|3]],[[OAI-PMH|4]]) originated from OSGeodata Mailing List on [https://geodata.osgeo.org/servlets/BrowseList?listName=geodata&by=date&paged=false OSGeo.org].
  
Let's finally unleash geographic information through open access and dissemination of geographic data and (metadata) search appliances!
+
Let's unleash geographic information through open access and dissemination of geographic data and (metadata) search appliances!
  
:''Managing metadata well is the key to making a repository of open geographic data really useful and re-usable. Creating metadata can be a dull chore. Part of the problem is over-focus on production, rather than consumption; on standards, rather than on usage. The Geodata Committee at OSGeo has been working on a "simplest useful thing" approach to geographic metadata...''. (Citation from Jo Walsh)
+
Allow to '''[[OSGeodata Discovery| discover geodata]]'''! Let's make metadata 'sexy' again.
 
'''Therefore we urgently need a [[OSGeodataMetadataModel| metadata information model]] as well as a [[OSGeodataMetadataProtocol| metadata exchange protocol]] (see below).'''
 
  
Keywords: ''Open access to and dissemination of geographic data (geodata) and information; Metadata; Finding, harvesting or discovery of geodata and web map services; Interoperability; Integration; Service binding; Spatial data infrastructure; Standards''.
+
For the '''[[OSGeodata Discovery| discovery of geodata]]''' we need a
 +
* '''[[OSGeodataMetadataModel| Geographic metadata exchange model]]''' as well as a
 +
* '''[[OSGeodataMetadataProtocol| Geographic metadata exchange protocol]]''' (catalog service).  
  
== Need for a metadata information model ==
+
For '''documentation''' an internal geodata management model is needed. For the '''metadata metadata exchange model''' a proposal was made called  '''[http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Information_model_for_metadata_exchange Dublin Core lite for Geo (DClite4G)]'''.
  
We definitively need first a metadata information model. Geographic catalog is rather data provider centric name for a system and a model, so we prefer a user centric 'metadata (information) model'. See [[OSGeodataMetadataModel]] for further discussion.
+
Remarks: '''Metadata''' is just data about data. There is nothing special regarding its modeling and encoding. Metadata according to metadata exchange model should be strictly free (LGPL?).
  
== Need for a metadata exchange protocol ==
+
== Pleadings for metadata (models) and adequate protocols ==
 +
* ''Managing metadata well is the key to making a repository of open geographic data really useful and re-usable. Creating metadata can be a dull chore. Part of the problem is over-focus on production, rather than consumption; on standards, rather than on usage. The Geodata Committee at OSGeo has been working on a "simplest useful thing" approach to geographic metadata...''. (Citation from Jo Walsh)
 +
* [http://www.digitalearth.com.au/2006/06/23/lightweight-web-resource-catalogue/ Blog 1] - "Leight Weight Web Resource Catalogue"
 +
* [http://geotips.blogspot.com/2006/02/more-simple-web-services-catalogues.html Blog 2] - More Simple Web Services Catalogues...", and
 +
* [http://www.kralidis.ca/blog/2006/08/04/geospatial-catalog-development-brewing/ Blog 3] - geospatial-catalog-development-brewing.
 +
* [http://home.badc.rl.ac.uk/lawrence/blog/all Bryan's Blog]: "To extend or not to extend ..." ("In practice, we can exchange any derivative of the ISO19139 profiles using OAI and store them in xml databases.").
 +
* Paper "Are Geospatial Catalogues Reaching their Goals?" from [http://www.agile2006.hu/papers/Larson_Siliceo_etal.pdf Larson et al.].
  
For general '''protocol requirements''' read [[OSGeodataMetadataProtocol]]. For proposals around the '''metadata information model''' requirements see [[OSGeodataMetadataModel]]. After having agreed on a better protocol there is also a need for a better name than 'Geographic Catalog Service or Protocol', like 'Geographic Metadata Harvesting Protocol'.
+
== Building blocks for metadata management ==
 +
Building blocks are:
 +
# A geometadata '''management model''' (e.g. internal to each organisation)
 +
# '''Tools''' to manage the geometadata
 +
# A geometadata '''[[OSGeodata metadata exchange model| exchange model]]'''
 +
# An '''encoding''' of the geometadata exchange model (probably XML)
 +
# Geometadata '''[[OSGeodata metadata exchange protocol| exchange protocols]]''' (like [[OAI-PMH]], see [[OSGeodata_Discovery]])
  
 
== Weblinks ==
 
== Weblinks ==
Zeile 24: Zeile 36:
 
* [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Discovery Wiki at osgeo.org] for requirements
 
* [http://wiki.osgeo.org/index.php/Geodata_Metadata_Requirements#Discovery Wiki at osgeo.org] for requirements
 
* [https://geodata.osgeo.org/servlets/BrowseList?listName=geodata Geodata mailing list at osgeo.org] for discussions
 
* [https://geodata.osgeo.org/servlets/BrowseList?listName=geodata Geodata mailing list at osgeo.org] for discussions
* Pleadings... [http://www.digitalearth.com.au/2006/06/23/lightweight-web-resource-catalogue/ Blog 1] - "Leight Weight Web Resource Catalogue",  [http://geotips.blogspot.com/2006/02/more-simple-web-services-catalogues.html Blog 2] - More Simple Web Services Catalogues...", and [http://www.kralidis.ca/blog/2006/08/04/geospatial-catalog-development-brewing/ Blog 3].
 
  
Geographic information search services:
 
* Catalogs:
 
** [http://www.mapdex.org mapdex.org]
 
** [http://www.geographynetwork.com ESRI's geography network]
 
** National Portals: [http://www.geodata.gov US], [http://geodiscover.cgdi.ca CA], [http://eu-geoportal.jrc.it EU], [http://www.gogeo.ac.uk UK], [http://www.geocatalogue.fr FR], [http://www.geoportal.bund.de DE], [http://www.geoland.at AT], [http://www.geocat.ch CH]
 
* Search engines:
 
** General: [http://maps.google.com/ Google Maps], MSN live, Yahoo!
 
** Specialized: [http://www.geometa.info geometa.info] (still german only for linguistic processing reasons)
 
* GIS with catalog and search components:
 
** [http://udig.refractions.net uDig], ArcGIS, ...?
 
  
 
<!-- Kategorien und ev. Koordinaten -->
 
<!-- Kategorien und ev. Koordinaten -->
[[Kategorie: Geodaten]]
+
[[Kategorie: Geodaten]] [[Kategorie: Metadaten]] [[Kategorie: English]]
[[English]]
 

Aktuelle Version vom 29. Oktober 2006, 12:15 Uhr

Overview

These are experimental pages (1,2,3,4) originated from OSGeodata Mailing List on OSGeo.org.

Let's unleash geographic information through open access and dissemination of geographic data and (metadata) search appliances!

Allow to discover geodata! Let's make metadata 'sexy' again.

For the discovery of geodata we need a

For documentation an internal geodata management model is needed. For the metadata metadata exchange model a proposal was made called Dublin Core lite for Geo (DClite4G).

Remarks: Metadata is just data about data. There is nothing special regarding its modeling and encoding. Metadata according to metadata exchange model should be strictly free (LGPL?).

Pleadings for metadata (models) and adequate protocols

  • Managing metadata well is the key to making a repository of open geographic data really useful and re-usable. Creating metadata can be a dull chore. Part of the problem is over-focus on production, rather than consumption; on standards, rather than on usage. The Geodata Committee at OSGeo has been working on a "simplest useful thing" approach to geographic metadata.... (Citation from Jo Walsh)
  • Blog 1 - "Leight Weight Web Resource Catalogue"
  • Blog 2 - More Simple Web Services Catalogues...", and
  • Blog 3 - geospatial-catalog-development-brewing.
  • Bryan's Blog: "To extend or not to extend ..." ("In practice, we can exchange any derivative of the ISO19139 profiles using OAI and store them in xml databases.").
  • Paper "Are Geospatial Catalogues Reaching their Goals?" from Larson et al..

Building blocks for metadata management

Building blocks are:

  1. A geometadata management model (e.g. internal to each organisation)
  2. Tools to manage the geometadata
  3. A geometadata exchange model
  4. An encoding of the geometadata exchange model (probably XML)
  5. Geometadata exchange protocols (like OAI-PMH, see OSGeodata_Discovery)

Weblinks

Information: