Difference between revisions of "GRASS Metadata Management"

From GRASS-Wiki
Jump to navigation Jump to search
Line 53: Line 53:
|-
|-
|1.1
|1.1
|Resource Title
|Resource title
|1
|1
|  
|  
|
|
|-
|1.2
|Resource abstract
|1
|
|
|
|-
|1.3
|Resource type
|1
|
|
|
|-
|1.4
|Resource locator
|0..*
|Mandatory if a URL is available to obtain more information on the resource, and/or access related services
|  
|  
|  
|  

Revision as of 08:31, 18 December 2013

Metadata support

Raster

Vector

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...)

Creating an INSPIRE compliant version of {v,r}.support

One idea would be to develop an INSPIRE compliant version of {v,r}.support. The module would ensure that all fields required for INSPIRE would be completed. It should be possible to write the Metadata out as XML (see above section). The European Union Open Source Metadata Editor (EUOSME) is a Web-based INSPIRE module that is published under the European Union Public Licence [1,2].

[1] EUOSME

[2] Required Fields

Validation

The GRASS module could call the validator's API and return the check result.

Links

Metadata structure

In order to be INSPIRE compliant, a metadata should include at least the following information (required fields; the user should be able to add more fields):

Reference Metadata elements Multiplicity Condition Variable Notes
1.1 Resource title 1
1.2 Resource abstract 1
1.3 Resource type 1
1.4 Resource locator 0..* Mandatory if a URL is available to obtain more information on the resource, and/or access related services