Difference between revisions of "GRASS Metadata Management"

From GRASS-Wiki
Jump to navigation Jump to search
Line 19: Line 19:
* 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 ===

Revision as of 10:36, 21 November 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...)

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 =
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

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