GRASS Metadata Management: Difference between revisions

From GRASS-Wiki
Jump to navigation Jump to search
 
(21 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Metadata support ==
== Metadata support ==
See [[ISO/INSPIRE Metadata Support]] and related [http://trac.osgeo.org/grass/wiki/GSoC/2014/MetadataForGRASS GSoC project] (g.gui.metadata)


=== Raster ===
=== Raster ===
Line 19: Line 21:
* would probably require major re-write of the raster/vector history mechanism
* 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...)
* generic reading/writing of XML data (don't we already have this functionality somewhere...)
==== Here's a list of the variables extracted from a compliant xml metadata ====
A_fileIdentifier
: fileIdentifier =
B_language
: languageCode =
C_characterSet
: characterSetCodeValue =
: characterSetCodeList =
D_hierarchyLevel
: MDscopeCodeValue =
: MDscopeCodeList =
E_contact
: responsiblePartyOrgName =
: contactAddress =
: roleCodeValue =
: roleCodeList =
F_dateStamp
: dateTime =
G_metadataStandardName
: MDstandardName =
J_metadataStandardVersion
: MDstandardVersion =
K_referenceSystemInfo
: CRSidentifierCode =
: CRSidentifierCodeSpace =
: TRSidentifierCode =
: TRSidentifierCodeSpace =
L_identificationInfo
: title =
: creationDate =
: creationDateTypeCodeListValue =
: creationDateTypeCodeList =
: publicationDate =
: publicationDateTypeCodeListValue =
: publicationDateTypeCodeList =
: revDate =
: revDateTypeCodeListValue =
: revDateTypeCodeList =
: MDidentifCode =
: RSidentifCode =
: RScodeSpace =
: abstract =
: ownerOrgName =
: ownerEmail =
: roleCodeListValue = "owner"
: roleCodeList =
: resourceProviderOrgName =
: resourceProviderEmail =
: roleCodeListValue = "resourceProvider"
: roleCodeList =
: authorOrgName =
: authorIndividualName =
: authorEmail =
: roleCodeListValue = "author"
: roleCodeList =
<!--Although not foreseen by ISO 19115, for the sake of simplicity, if all individuals have the same role and organization we can group them in a single element following the convention used in aritcles-->
: MDcustodian =
: MDcustodianOrg =
: MDcustodianEmail =
: GEMET_INSPIRE_keyword =
: GEMET_Concepts_keyword1 =
: GEMET_Concepts_keyword2 =
: GEMET_Concepts_keyword3 =
: GEMET_Concepts_keyword4 =
: GEMET_Concepts_keyword5 =
: GEMET_Concepts_keyword6 =
: GEMET_Concepts_keyword7 =
: GEMET_Concepts_keyword8 =
: GEMET_Concepts_keyword9 =
: useLimitation =
: otherConstraints =
: spatialRepresentationType =
: distanceUnit =
: distanceLanguage =
: westBoundLongitude =
: eastBoundLongitude =
: southBoundLatitude =
: northBoundLatitude =
: beginTemporalExtent =
: endTemporalExtent =
M_distributionInfo
: MDformatName =
: MDformatVersion =
: MDformatSpecification =
: viewServiceURL =
: viewServiceName =
: viewServiceDescription =
: viewServiceFunctionCodeListValue =
: viewServiceFunctionCodeList =
: licenseURL =
: licenseName =
: licenseDescription =
: inputDataURL =
: inputDataName =
: inputDataDescription =
N_dataQualityInfo
: MDscopeCodeListValue =
: MDscopeCodeList =
: DQdomainConsistency =
: DQconformanceResult
: DQspecification =
: DQcitation =
: DQdate =
: DQdateTypeCodeListValue =
: DQdateTypeCodeList =
: lineage =


=== Creating an INSPIRE compliant version of {v,r}.support ===
=== Creating an INSPIRE compliant version of {v,r}.support ===
Line 179: Line 33:


The GRASS module could call the [http://inspire-geoportal.ec.europa.eu/validator2/ validator]'s API and return the check result.
The GRASS module could call the [http://inspire-geoportal.ec.europa.eu/validator2/ 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 [http://eur-lex.europa.eu/legal-content/EN/TXT/PDF/?uri=CELEX:32008R1205&from=EN INSPIRE metadata regulation] (those are intended as required fields; the user should be able to add more fields).
{|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=100px|''' Metadata elements '''
!width=50px|''' 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 series (series) | 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 ==
== Links ==
Line 187: Line 170:
* https://www.ngdc.noaa.gov/wiki/index.php?title=ISO_Metadata_Standard
* https://www.ngdc.noaa.gov/wiki/index.php?title=ISO_Metadata_Standard
* [http://inspire-geoportal.ec.europa.eu/validator2/ INSPIRE Geoportal's metadata validator]
* [http://inspire-geoportal.ec.europa.eu/validator2/ INSPIRE Geoportal's metadata validator]


[[Category:Development]]
[[Category:Development]]
[[Category:Metadata]]
[[Category:Metadata]]
[[Category:INSPIRE]]

Latest revision as of 14:03, 11 January 2018

Metadata support

See ISO/INSPIRE Metadata Support and related GSoC project (g.gui.metadata)

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

Retrieved from "https://grasswiki.osgeo.org/w/index.php?title=GRASS_Metadata_Management&oldid=24976"