GRASS Metadata Management: Difference between revisions
Jump to navigation
Jump to search
(url update) |
(+http://wiki.osgeo.org/wiki/Metadata_software) |
||
Line 21: | Line 21: | ||
== Links == | == Links == | ||
* [http://www.eurogeographics.org/eng/documents/draftINSPIREMetadataIRv2_20070202.pdf DT Metadata – Draft Implementing Rules for Metadata] | * [http://www.eurogeographics.org/eng/documents/draftINSPIREMetadataIRv2_20070202.pdf DT Metadata – Draft Implementing Rules for Metadata] | ||
* http://wiki.osgeo.org/wiki/Metadata ( | * http://wiki.osgeo.org/wiki/Metadata and http://wiki.osgeo.org/wiki/Metadata_software (software list) | ||
[[Category:Development]] | [[Category:Development]] |
Revision as of 21:08, 6 January 2009
Metadata support
Raster
- r.support (r.support history="long text" now functional, it does line wrapping)
- Metadata support in GRASS raster library notes
Vector
- 'head' file format
- TODO: tool to edit this head file needed using
v.support
. (Reference: http://lists.osgeo.org/pipermail/grass-user/2007-February/038378.html)
Comments on a vector map can be added manually by editing $MAPSET/vector/$MAPNAME/hist
.
Metadata management ideas for future versions of GRASS
Unified XML-based approach for raster/vector/imagery
- store relevant metadata in an XML-based format, along with creation/modification history
- a new directory '$maspset/metadata/' could house this information
- would probably require major re-write of the raster/vector history mechanism
- generic reading/writing of XML data (don't we already have this functionality somewhere...)