Difference between revisions of "GRASS Metadata Management"

From GRASS-Wiki
Jump to navigation Jump to search
Line 37: Line 37:




{|class="wikitable sortable"  border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"  
{|class="wikitable sortable"  border="2" cellspacing="0" cellpadding="4" rules="all" style="margin:1em 1em 1em 0; border:solid 1px #AAAAA; border-collapse:collapse; background-color:#edf9c7; font-size:95%; empty-cells:show;"  
!width=50px|''' Reference '''
!width=50px|''' Reference '''
!width=100px|''' Metadata elements '''
!width=100px|''' Metadata elements '''
!width=50px|''' Multiplicity '''
!width=50px|''' Multiplicity '''
!''' Condition '''
!''' Condition '''
!''' Variable(s) '''
!''' Notes '''
!''' Notes '''
|-
|-
Line 56: Line 55:
|1
|1
|  
|  
| abstract
| (+ optional: abstract_URL)
| (+ optional: abstract_URL)
|-
|-
Line 63: Line 61:
|1
|1
|  
|  
| resType
| Spatial data set series (series) | Spatial data set (dataset) | Spatial data services (services)
| Spatial data set series (series) | Spatial data set (dataset) | Spatial data services (services)
|-
|-
Line 70: Line 67:
|0..*
|0..*
|Mandatory if a URL is available to obtain more information on the resource, and/or access related services
|Mandatory if a URL is available to obtain more information on the resource, and/or access related services
|
|  
|  
|-
|-
Line 77: Line 73:
|1..*
|1..*
|  
|  
| fileIdentifier
|  
|  
|-
|-
Line 84: Line 79:
|0..*
|0..*
|Mandatory if the resource include textual information
|Mandatory if the resource include textual information
| language
|  
|  
|-
|-
Line 91: Line 85:
|1..*
|1..*
|  
|  
| topicCategory
| Topic categories in accordance with ISO 19115
| Topic categories in accordance with ISO 19115
|-
|-
Line 97: Line 90:
|Keyword
|Keyword
|1..*
|1..*
|
|  
|  
|  
|  
Line 104: Line 96:
|Geographic bounding box
|Geographic bounding box
|1..*
|1..*
|
|  
|  
|  
|  
Line 111: Line 102:
|Temporal reference
|Temporal reference
|1..*
|1..*
|
|  
|  
|  
|  
Line 118: Line 108:
|Lineage
|Lineage
|1
|1
|
|  
|  
|  
|  
Line 126: Line 115:
|0..*
|0..*
|Mandatory for data sets and data set series if an equivalent scale or a resolution distance can be specified
|Mandatory for data sets and data set series if an equivalent scale or a resolution distance can be specified
|
|  
|  
|-
|-
Line 132: Line 120:
|Conformity
|Conformity
|1..*
|1..*
|
|  
|  
|  
|  
Line 139: Line 126:
|Conditions for access and use
|Conditions for access and use
|1..*
|1..*
|
|  
|  
|  
|  
Line 146: Line 132:
|Limitations on public access
|Limitations on public access
|1..*
|1..*
|
|  
|  
|  
|  
Line 153: Line 138:
|Responsible organisation
|Responsible organisation
|1..*
|1..*
|
|  
|  
|  
|  
Line 160: Line 144:
|Metadata point of contact
|Metadata point of contact
|1..*
|1..*
|
|  
|  
|  
|  
Line 167: Line 150:
|Metadata date
|Metadata date
|1
|1
|
|  
|  
|  
|  
Line 174: Line 156:
|Metadata language
|Metadata language
|1
|1
|
|  
|  
|  
|  

Revision as of 14:10, 13 February 2014

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.

INSPIRE Metadata structure

In order to be INSPIRE compliant, a metadata for spatial data sets or spatial data set series should include at least the information provided in the table reported in the INSPIRE metadata regulation (those are intended as required fields; the user should be able to add more fields).


Reference Metadata elements Multiplicity Condition Notes
1.1 Resource title 1 title
1.2 Resource abstract 1 (+ optional: abstract_URL)
1.3 Resource type 1 Spatial data set (dataset) | Spatial data services (services)
1.4 Resource locator 0..* Mandatory if a URL is available to obtain more information on the resource, and/or access related services
1.5 Unique resource identifier 1..*
1.7 Resource language 0..* Mandatory if the resource include textual information
2.1 Topic category 1..* Topic categories in accordance with ISO 19115
3 Keyword 1..*
4.1 Geographic bounding box 1..*
5 Temporal reference 1..*
6.1 Lineage 1
6.2 Spatial resolution 0..* Mandatory for data sets and data set series if an equivalent scale or a resolution distance can be specified
7 Conformity 1..*
8.1 Conditions for access and use 1..*
8.2 Limitations on public access 1..*
9 Responsible organisation 1..*
10.1 Metadata point of contact 1..*
10.2 Metadata date 1
10.3 Metadata language 1

Links