This profile together with the E-ARK CITS GEOSPATIAL document describes the representation METS document for an IP conforming to the E-ARK CITS GEospatial.
An extension schema with the added attributes for use in this profile.
The schema is used with a namespace prefix of sip.
An extension schema with the added attributes for use in this profile.
The schema is identified using the namespace prefix csip.
The filepath must be decoded consistently throughout all file references within the information package.
Describes the type of the alternative record ID.
Describes the type of a note for an agent.
Lists the names of specific E-ARK content information type specifications supported or maintained in this METS profile.
Declares the categorical classification of package content.
Describes the uses of the file group `<fileGrp>` that are supported by the profile.
Own names should be placed in an own extending vocabulary.
All information recorded within the portion of a conforming METS document defined using the Simple DC XML Schema must be employ ISO 639-2 language codes within the 'language' element.
Describes the status of the descriptive metadata section (dmdSec) which is supported by the profile.
Valid values for the mime types of referenced files.
Describes the type of the structural map `<structMap>` that is supported by the profile.
Own types should be placed in an own extending vocabulary.
Describes the label of the structural map that is supported by the profile.
Own labels should be placed in an own extending vocabulary.
The value is set to "https://geospatial.dilcis.eu/profile/E-ARK-GEOSPATIAL-REPRESENTATION.xml".
The `mets/@TYPE` attribute is set to the value "Geospatial Data".
The `mets/@csip:CONTENTINFORMATIONTYPE` attribute is set to the value "GeoData".
The `mets/@csip:OTHERCONTENTINFORMATIONTYPE` attribute is not to be used.
The Geospatial root METS document metsHdr element should comply with metsHdr requirements in the CSIP profile.
The Geospatial root METS document metsHdr element should comply with metsHdr requirements in the SIP profile.
The Geospatial root METS document dmdSecr element should comply with dmdSec requirements in the CSIP profile.
The Geospatial root METS document dmdSec element should comply with dmdSec requirements in the SIP profile.
The Geospatial root METS document amdSec element should comply with amdSec requirements in the CSIP profile.
In Geospatial it is required that any rights or digital provenance metadata that is general to the package can be held within the root metadata folder and that any rights or digital provenance metadata that is specific to the data held in the representation should be held in the representation metadata folder.
The eHEALTH1 root METS document amdSec element should comply with amdSec requirements in the CSIP profile.
In eHEALTH1 it is required that any rights or digital provenance metadata that is general to the package can be held within the root metadata folder and that any rights or digital provenance metadata that is specific to the data held in the representation should be held in the representation metadata folder.
There MUST be a minimum of one mets/fileSec/fileGrp[@USE='Representations']/@csip:CONTENTINFORMATIONTYPE with the value “GeoData” as taken from the CSIP Vocabulary for Detailed Content Type that direct to the representation METS.xml in the representation folder containing geospatial data.
The value of the attribute `mets/fileSec/fileGrp/@csip:CONTENTINFORMATIONTYPE` is set to "GeoData".
There must be a discrete representation `div` element for each representation.
Section not defined or used in CSIP, additional own uses may occur.
Information regarding the structural links is found in the METS Primer
Section not defined or used in CSIP, additional own uses may occur.
Information regarding the behavior section is found in the METS Primer
There MUST be a minimum of one representation and, therefore minimum of one Package METS.xml and a minimum of one Representation METS.xml in a CITS Geospatial compliant package.
If the value in mets/@csip: CONTENTINFORMATIONTYPE is "GeoData", then there MUST exist at least one file in a geospatial format in representations/[RepresentationName]/data
If there are more geospatial records in a representation, each geospatial file MAY be placed or grouped in subfolders in representations/[RepresentationName]/data
The Information Package MUST contain at least one representation of geospatial record in a long-term preservation format, as defined by the Archive or in the Long-term Preservation Format Profile
The Information Package MAY contain a separate representation of the same data, containing geospatial data in its original format
Every geospatial dataset MUST be accompanied with information about its underlying Coordinate Reference System (CRS) in one of two ways:
* Full description of the CRS together with the archived data (within the geospatial file itself or in an accompanying file)
* The geospatial file contains a reference to a CRS registry
The geographies in the geospatial records SHOULD be located within a fixed bounding box defined in the submission agreement between the producer and the archive according to the expected location and extent of the dataset
Every geospatial dataset MUST be accompanied with a metadata file, that describes the dataset with the basic required information
Any geospatial vector datafile in representations/[RepresentationName]/data MUST be a valid vector file compliant with its respective format requirements (must pass the validation with the chosen validator for its format)
Each Vector Feature dataset MUST contain at least one Feature attribute unique to each feature instance
Geospatial vector data in a long-term preservation representation SHOULD comply with the requirements for the respective Long-Term preservation format Profile for Geospatial Vector data
Any raster file in representations/[RepresentationName]/data MUST be a valid raster file compliant with its respective format requirements (must pass the validation with the chosen validator for its format).
Raster data in the long-term preservation representation SHOULD comply with the requirements for the respective Long-Term preservation format Profile for Geospatial Raster data
If raster objects are organised using an external tiling index file, this tiling index MAY be placed in representations/[RepresentationName]/data
Technical documentation specific to one representation SHOULD be placed in representations/[RepresentationName]/documentation
Note tht any documentation pertaining to all representations in the Information package SHOULD be placed in /documentation on package level
A document containing definitions and descriptions of feature types, its feature attributes and feature attributes related to all the geospatial records in the Information Package MUST be provided
A standardised machine-readable feature catalogue SHOULD be provided in the Information Package
If a standardised machine-readable feature catalogue exits it MUST be placed in representations/[RepresentationName]/documentation/structure
Documentation, describing elements of a feature catalogue, not compliant with GEO_27 (a non standardised machine- readable feature catalogue) SHOULD be provided in Documentation/structure folder on the package level
A document describing relationships between multiple geospatial entities or geospatial and non-spatial records SHOULD be provided in the Information Package
If a document describing the logical model exists it MUST be provided in a documentation/structure folder
If a standardised machine-readable version of a document describing the logical model exists it MUST be provided in representations/[RepresentationName]/documentation/structure
A document describing the structure of geospatial records in the GIS System MAY be provided in the Information Package. A standardised machine-readable version is preferred.
An image displaying the overall view or a representative section of any geospatial dataset MUST be provided in the Information Package and placed in a documentation/rendering folder
A standardised machine-readable rendering configuration for one or more geospatial datasets MAY be provided in the Information Package
If a standardised machine-readable rendering configuration for one or more geospatial datasets exists it MUST be provided in representations/[RepresentationName]/documentation/rendering
Information product examples based on geospatial record or records example SHOULD be provided in the Information Package
If information product examples exists they MUST be provided in the Information Package in a documentation/rendering folder
If the CRS definition in a geospatial file is documented only by a reference to a CRS registry a standardised machine-readable format CRS definition compliant with standards for CRS definition SHOULD be provided in the Information Package
If a standardised machine-readable format CRS definition exists it MUST be provided in a documentation/CRS folder
For system using data in multiple CRS systems, standardised machine-readable transformation parameters between those CRS MAY be provided in the Information Package
If standardised machine-readable transformation parameters exists, they MUST be provided in a documentation/CRS folder
Contextual documentation covering only content within a particular representation SHOULD be placed in representations/[RepresentationName]/documentation/other
Descriptive geospatial metadata in the long-term preservation format representation of the Information Package SHOULD be provided in the form of standardized machine-readable format compliant with geospatial metadata standards
If a standardised descriptive geospatial metadata file exists it MUST be provided in representations/[RepresentationName]/metadata/descriptive
If a standardised descriptive geospatial metadata file exits it MUST be accompanied by an XML schema definition placed in a sub-folder called /schemas within the Information Package root folder or the representation folder
Geospatial metadata in non-long-term preservation representations MAY be stored in its original form or as documentation. However, formats need to comply with the archival guidelines (stored in approved long-term preservation formats).
Requirements not stated in CITS Geospatial
Requirements not stated in CITS Geospatial