Geodata Metadata Requirements

= Why this document exists =

One goal of the Public Geospatial Data Project is to offer, in the future, a repository of reusable public geographic data that can support open source geospatial software projects, both inside and outside the foundation.

One big requirement for a potential Geodata Repository is that there be a well-defined baseline for metadata. This can be seen as a quality assurance effort - data won't be accepted without a certain amount of metadata.

The |US Federal Geographic Data Committee metadata standard emphasises conformance, but doesn't emphasise exchangeability / reusability. FDGC is standard for "Spatial Data Infrastucture" efforts, but doesn't have much of a "geospatial web" orientation.

There are some properties in addition to FGDC which it would be really useful to have - different distribution channels like WFS, bittorrent which have come into existence since FGDC was originally defined. For many elements, FGDC asks for full-text descriptions. More structure in descriptions would help with automating discovery or re-use.

This is a "straw-person" set of suggestions, and comment / additional references would be gratefully received.

= Draft Metadata model =

Graph illustrating a basic metadata model generated from an RDF model of what OSGeo Geodata Committee participants have identified as their core needs for metadata.

This picks an arbitrary namespace for an OWL schema that maps to most, if not all, of the FGDC mandatory properties and provides some extra ones.



title
Title of the data set. Corresponds to Dublin Core title

description
Text description of the data set. Corresponds to Dublin Core description element.

Person
A person responsible for publication of the data set - name and contact email address. These properties are well-defined in the FOAF vocabulary.

Organization
A organization responsible for publication of the data set - name and contact email address. These properties are well-defined in the FOAF vocabulary.

Spatial Data Organization
Vector, Raster or Point data, as described in FGDC. (cf http://biology.usgs.gov/fgdc.metadata/version2/sdorg.htm )

datasource
URL from which the data can be downloaded via different protocols

WFS
For Vector data in GML

WMS
For Raster data described in GML

BitTorrent
URL of bittorrent .torrent tracker file.

Other Web API
For example, OpenStreetmap API ( http://wiki.openstreetmap.org/index.php/REST )

License information
Emphasis on public geographic data licenses: PGL, possible LPGL, Public Domain, Creative Commons-type licenses. These can be represented by URLs.

Publication date
Corresponds to Dublin Core date: ISO compliant date of publication.

Spatial Domain
A lot of this can be inferred either using GDAL/OGR or collected from a WMS/WFS GetCapabilities. It would be nice to bypass human error on collecting this kind of metadata.

bounding coordinates
FGDC specifies north, east, west, south bounding co-ordinates. It doesn't specify a projection in which these should be described. For reasons of simplicity it could make sense to require these be in WGS84 (EPSG:4236) - for the same reasons GeoRSS decided to mandate WGS84, rather than complicate matters by dictating that people also specify an SRS.

Projection (Raster, Vector)
Original projection of the data (reference to an ?)

Horizontal and vertical datum;

Horizontal and vertical units.

Taxonomy/Ontology
Currently undecided; would be good to refer this to current well-known thesauri for data themes.

= References =

Geospatial

 * FGDC geospatial metadata model


 * GEON geospatial metadata model


 * DIF geospatial metadata model


 * GeoRSS


 * WFS

RDF

 * Resource Description Framework


 * RDF Primer


 * OWL Web Ontology Language Guide


 * Semantic Web for Earth and Environmental Terminology OWL Ontologies at NASA


 * Dublin Core metadata model for documents


 * FOAF metadata model for people and organisations


 * DOAP metadata model for open source software projects and code repositories

From Geodata Packaging Working Group:

 * Specifications of a data set
 * Creator
 * Date
 * License
 * Data Type
 * Topic
 * Spatial Extent
 * Coordinate System/Projection
 * Target Scale/Precision
 * Attribute Data