Session 6

GGOS Portal and Metadata Flow(second draft)
prepared by RICHTER B. and NOLL C.,

with contributions by SOUDARIN L. and NIELL, A.

1. Metadata standards for products and data
1.1. What are metadata and why they should be used
Metadata are data about data.
•

Metadata describe what, where, when and by whom a particular set of data werecollected, and how the data are formatted.

•

Metadata are used to facilitate the understanding, use and management of data. The
metadata required for effective data management varies with the type of data andcontext of use.

•

Metadata are essential for understanding information stored in data warehouses andhave become increasingly important in XML-based Web applications.

Metadata do not contain the actual data nor do they replace a database.

1.2. Why interoperability is important••

The IEEE Standard Computer Dictionary describes interoperability as follows: Abilityof two or more systems or components to exchange information and to use theinformation that has been exchanged.
ISO /IEC 2382-01, Information Technology Vocabulary, Fundamental Terms, definesinteroperability as follows: "The capability to communicate, execute programs, ortransfer data among various functional units in a manner that requires the user tohave little or no knowledge of the unique characteristics of those units".

Products / applications achieve interoperability with other products / applications using either
or both of two approaches:• By adhering to published interface standards• By making use of a "broker" of services that can convert one product's interface intoanother product's interface "on the fly".
Both methods will be used in GGOS applications to achieve the interoperability of metadata.
The ISO 19115 standard for geographic metadata is widely used in the GIS world andrecommended e.g., by FGDC, OGC and GEOSS. Presently the WMO will apply an extended
ISO 19115 metadata standard to its datasets. Here it is proposed to follow the same strategy
for the GGOS and the data provided through the services.
Cross mapping allows the use of different metadata standards as long as the necessary
information covers the requested formalities and are based on XML technology. E.g., theNASA proposed Directory Interchange Format (DIF) and ISO 19115 crosswalk is provided intable 11, displaying an example in the field of habit classification which easily can be adapted
to other science fields.

1.3. Different levels of metadata granularity
The ISO 19115 standard defines an extensive set of metadata elements; typically only asubset of the full number of elements is used. However, it is essential that a basic minimum
number of metadata elements be maintained for a dataset.

Core Metadata to be consistent with ISO 19115
The core metadata elements required to identify a dataset are used typically for catalogue
purposes. These core metadata include the Dublin core which is accepted as basis forvarious standards. The list of core metadata contains metadata elements answering thefollowing questions: “Does a dataset on a specific topic exist (‘what’)?”, “For a specific place(‘where’)?”, “For a specific date or period (‘when’)?” and “A point of contact to learn more
about or order the dataset (‘who’)?”. Already these core metadata facilitates interoperability,
because they allow users to understand without ambiguity the geographic data and therelated metadata provided by either the producer or the distributor. The required elements
are listed in table 1.
Table 1 The ISO core-element set with mandatory fields, the core elements contain several subelements
ISO19115 metadata entity set ISO
information
No

Metadata elements

MD_Metadata
8 Metadata point of contact
9 Metadata date stamp
MD_Identification
360 Dataset title
362 Dataset reference date
25 Abstract describing the dataset
39 Dataset language
MD_DataIdentification
41 Dataset topic category
Table 1: The ISO core-element set with mandatory fields

m
m
m
m
m
m
m

Core light metadata set as mandatory metadata for all geodetic datasets
This core light metadata set should be the minimum basis for all geodetic data sets provide
by GGOS and the IAG Services. Using most of the recommended optional elements in thecore metadata set as mandatory in addition to the already mandatory elements result in asmall list of core metadata for geographic datasets which comprises 22 elements (table 2).
The main extensions are the descriptive keywords, the spatial resolution, the reference
system, format information. But also the still as conditional marked elements are worth to be
filled. With these extensions a more detailed information about data within GGOS can beprovided which is accessible by international services outside our community e.g., GEOSS.
Because the core light metadata set is clearly arranged it should be possible to describe
almost all data sets produced by the IAG services in a simple way without too many efforts.
The lists of descriptive keywords and data set categories topics can be set up according the
GCMD list as a beginning and more improved during discussion (table 9). The format
descriptions should follow the table 4 with extensions for gravity and other geodetic fields notcovered here.
To create the core light metadata follow chapter 1.4.

Table 2. A recommended Core light metadata set for all geodetic datasets, an extended
recommended ISO core-element set
ISO19115 metadata entity set ISO
information
No

Metadata elements

IERS
GGOS

2
10
11
3
4
8
9
6
360
361
362
29
25
33
28
37
38
39
40
41
42
43
45
71
79
81
135
137
143
196
271
277
285
286

Metadata file identifier
Metadata standard nameMetadata standard version
Metadata language
Metadata character set
Metadata point of contact
Metadata date stamp
Scope to which the metadata applies
Dataset title
Dataset short title
Dataset reference date
Dataset responsible party
Abstract describing the dataset
Descriptive keywords
StatusSpatial representation typeSpatial resolution of the dataset
Dataset language
Dataset character set
Dataset topic category
Geographic location
bounding box or geographic identifier
Vertical and temporal extent of dataset
Constraints on using the resource
Scope of data
Lineage statement
Value unit for reporting a data quality result
Quantitative value of the evaluation procedure
Maintenance frequency
Reference system
Distribution format
On-line resource
Format nameFormat version

o
o
o
c
c
m
m
c
m
o
m
m
m
m
o
o
m
m
c
m
m
m
m
o
m
m
o
o
o
m
m
m
m
m

MD_MetadataExtensionInformation

14

Information on metadata extensionso

MD_ApplicationSchemaInformation

321 Application schema information

MD_Metadata

MD_Identification

MD_DataIdentification

MD_Constraints

DQ_DataQuality

MD_MaintenanceInformation
MD_ReferenceSystem

MD_Distribution(m = mandatory, c = conditional, o = optional, (o) = not part of core set).

oExtended Metadata sets
The full ISO metadata standard (ISO 19115) might be able to address most IAG service
requirements. This standard is very complex, but it specifies a process (in ISO 19115 Annex
C) where a community can adopt parts of the standard which it feels relevant (including the"Core Elements") and also extend the elements, keywords and code table instances to suitthat community. As an example, the WMO Core Metadata Profile has been adapted to thegeodetic requirements in a first step and is named GGOS Core Metadata Profile. In principle
each IAG service can develop its own profile based on GGOS Core Metadata Profile(ISO19115 p. 120).
To follow this strategy the following granularity can be developed:• GGOS provides core metadata information for almost all geodetic data sets. Thissolution should be realised fast to comply (e.g., GEOSS). If it is operational thisservice attracts users from other communities and fields of interest and “links” them tothe specific IAG services or components.
• The individual IAG services expand the ISO metadata standard to there
requirements. Based on this specific metadata profile a more detailed response canbe made available.
• An alternative might be that the GGOS metadata profile will include all service
specific specifications. As a consequence the GGOS master profile might be notclearly arranged and will confuse the user by e.g., much extended code lists.
A first draft to create a Geodetic Metadata Profile is given in the (table 3). This profile isbased on the discussion and the result which took place at WMO for several years. The
extended code list can be complemented to the need of the IAG service or product. As an
example to describe the SINEX file in addition to the core light elements for search in
GEOSS: What, Where, When, Who extensions of core elements for search in GGOS:-

stations: technique, time period,-

parameter: type, time period, quality, data frequency

is added.

1.4. Tools to create and export metadata sets and to search for
metadata
The ISO 19115 standard provides a general definition for directory searches and exchangethat should be applicable to a wide variety of GGOS datasets. It does not specify how these
metadata should be archived or presented to users. It also does not specify any particular
implementation and could be implemented as a database, a flat file, or any other suitablemechanism.
Here different methods can be applied:-

The information needed is extracted from the data set by scripts and provided
in the required format (XML)-The information can only partly extracted from the data set and must becompleted by the data provider-

The information must be completed by the provider

Scripts should be developed by some institutions and made available for the broad geodetic
community. To add information the use of editors is recommended, e.g. CatMDEdit,
disyPreludio. The later offers a very comfortable user interface and as a special service, user

profiles according to ISO 19115 will be developed on request. As an example the IERS
Bulletin A is described by GGOS core light metadata1.5. Applications
Metadata management within IERS
Based on a decision of the IERS Directing Board the IERS Data and Information Systemshould realize a central access point for all IERS Products and Information related to the fieldof Earth Rotation and Reference Systems. It has been developed in the framework of the“Geotechnologienprojekt” financed by the Federal Ministry of Science and Application andcontributions from BKG.
An important part of the data system is the metadata management. Initially, a metadata
schema (profile) has been developed to describe the characteristics of all IERS products by
one common schema. This metadata schema allows search for specific information, tocompare the various products, to give a descriptive summary of a product, etc. This
metadata profile was designed to describe all characteristics of the IERS products. The
profile comprises metadata fields like Content, Data, Time, Accuracy, Format, Access,Creator, Contact, Documentation, etc. The metadata are the basis for the dynamic IERS
Web site.
The process to collect the metadata consists of two steps. A general metadata class is being
assigned to each product. As soon as a new product version is being archived the metadataof the superior class is being attached complemented by information extracted from theindividual product version.
To be compliant to the international metadata standard for geographic information (ISO19115) the IERS metadata schema has been extended. In table 10 the elements in column 2
are indicated by “yes” to align the IERS metadata to the metadata set of “GeoPortal.Bund”
the German Geoportal. This applied standard is widely used by metadata catalogues

allowing for interdisciplinary searches by so called catalogue service web interfaces (CSW).
By this extension and inclusion in the “GeoPortal.Bund” the IERS data are interoperable andmade available for the GEOSS pilot project.

2.

Standardised data formats

A preliminary list of known formats within selected IAG services has been compiled andprovided in the annex as table 4.

3.

List of relevant information common to all Services

The Inter-Service Data Integration for Geodetic Operations (INDIGO) (http://indigo.nasa.gov)
provides support for the central offices of the International GNSS Service (IGS, formerly theInternational GPS Service), International Laser Ranging Service (ILRS), and International
VLBI Service for Geodesy and Astrometry (IVS), International DORIS Service as well as the
Crustal Dynamics Data Information System (CDDIS) data archive system, to develop
information systems which enable the simultaneous use of multiple space geodetic
techniques for earth science. Development activities for INDIGO continue.
The data and products from these services are made possible by the many worldwide
agencies that utilize their own resources to collaboratively create them.
INDIGO works closely with the International Earth Rotation and Reference Systems Service(IERS) and the Global Geodetic Observing System (GGOS), and intends to develop systems
which are extensible, to allow other space geodetic techniques to participate.
The tables 5 to 8 IAG Geometric Services Comparison Charts: Data, Products, Service
Information, Site Information (s. annex) give an overview of the geometrical services; otherservices are not yet included and should be added.

4.

GGOS & Service Portals

Introduction
The GGOS Portal will be a unique access point for all GGOS products. The portal will also
provide a route to the heterogeneous IAG service/technique specific information systems.
The portal will be equipped with a database of relevant metadata and WEB services
established according to international standards, which will enable searches for relevant dataand products in a most effective way.

Background
The IAG services, as components of GGOS, provide very important and valuable data,
information, and products, which are indispensable for Earth sciences and their applications.
The GGOS portal will give access to these data and products as well as general information
about geodesy. The portal will contribute to GGOS objectives to promote and improve thevisibility of scientific research in geodesy and to achieve maximum benefit for the scientificcommunity and in society in general. Behind the GGOS portal, each contributing service willcontinue its own visibility and responsibility to maintain and manage its supporting data andinformation system.
The IAG services produce important and valuable products that cannot only be promoted by
GGOS but are critical to the generation of GGOS products. These products and data are
only available at the data centres of the individual components of GGOS. It is clear that for a
future GGOS, all the relevant products for Earth sciences and applications have to be madeaccessible through the GGOS portal, that leads the user – including the non-specialists
working in neighbouring or different fields – to the individual products and theircharacteristics, as shown in Figure 1 below. The products and data themselves will remain
physically located at many different data and product centres and will be promoted by theindividual IAG services as well. As a draw for newcomers or scientists that are not familiar
with space geodesy, the initial web pages of the GGOS portal will present the “burningquestions” of society and lead the way from there to the products relevant for thecorresponding topic, their characteristics, location, availability, latency, accuracy, etc. The
expert user will have the ability to skip these introductory pages and immediately proceed tothe databases themselves. General information about the GGOS project will also be
available through the portal, providing a valuable resource for both the external and internal
GGOS communities.

GGOS Portal Architecture
The success of the GGOS portal will depend on data and information providers accepting
and implementing a set of interoperability arrangements, including technical specifications forcollecting, processing, storing, and disseminating shared data, metadata and products.
GGOS interoperability will be based on non-proprietary standards, with preference given toformal international standards. The eXtensible Markup Language (XML) has become a quasi
standard to facilitate the sharing of data across different information systems, particularly via
the Internet. Moreover, Web services for the support of interoperable Machine to Machinecommunication over a network are built on XML based standards (SOAP, WSDL).

Figure 1. GGOS system design, directing users through the portal to underlying data, products andinformation.

Data, products, and information from contributing IAG services will be catalogued in a
publicly accessible clearinghouse maintained collectively under the GGOS portal. The
catalogue including thesauri will itself be subject to GGOS interoperability specifications,
including the standard search and portrayal services.
The functions of the GGOS portal (e.g., search capabilities for stations, satellites, data,
products, institutions, data mining tools, visualization, Web services, connections to othercatalogues, etc.) are supported by the GGOS Clearinghouse (Figure 2). The GGOS
Clearinghouse will be an facility that collects and distributes information concerning the datacatalogues and services.

user
applications

GGOS portal&
Clearinghouse

Clients

WEB
WEB
WEB
services
services
services

catalogues

other
meta
data

meta
data
metadata

meta data
metadata

meta data

IAG services
data

ISDC
geo
data

CDDIS
geo
data

IERS
geo
data

data

data

data

Servers

Figure 2. GGOS portal architecture

The GGOS Clearinghouse provides access to a distributed network of catalogue services
that support the interoperability agreements of GGOS. Contributing IAG services may
nominate catalogues containing structured, standards-based metadata and other Web
services for access by the GGOS Clearinghouse. The clearinghouse provides searchcapability across the catalogues and their registered resources by mapping thesecatalogues. The GGOS portal will search the GGOS Clearinghouse but will also provide
access to other GGOS resources e.g., calendar functions, bulletin boards, etc. Through theuse of interoperability standards, additional portals may be established for national or
professional communities to access the GGOS Clearinghouse.
The metadata to be held by the clearinghouse is dependent upon the approach used forsearching. Two anticipated capabilities for access to remote catalogues (see Figure 3) may
include:••Distributed search approach: search requests are sent in parallel to registered
distributed catalogues of the IAG services.
Harvested approach: The clearinghouse periodically harvests all metadata fromregistered distributed catalogues. A user search request is executed against the
metadata harvested from the remote catalogues and the results are managed andportrayed in the GGOS Clearinghouse.

Client

GGOS

Figure 3. GGOS Clearinghouse architecture – engineering viewpoint (according to D. Nebert).

GGOS Portal Goals and Objectives
The GGOS Portal will provide a Web site that:
•
•
•
•
•
•

represents a single Web access point (door of entry) for all geodetic products relevantin the framework of GGOS,
access to general information about GGOS,
help in answering the “burning questions of society” and leads the way to the
products, their characteristics, location, availability, latency, and accuracy,
an information resource for GGOS participants (e.g., working group resources,
calendar, meeting summaries, presentation archive, etc.),
access the GGOS clearinghouse to search data catalogues, products and data sets
generated by GGOS components,
allows searching and information retrieval of descriptive metadata from multiple,
diverse target resources, databases, web pages, and library catalogues.

Later the GGOS portal should offer a set of tools for organized knowledge discovery
including visualisation to assist identification and selection of appropriate resources(information, data, products).
Tasks to be addressed by the GGOS Portal:
1. Installation of a GGOS Web siteo Basic functionalities, hot spot information, news, tutorials, quick links,
announcements, etc.
o General information on and explanations of data, products, and geodetic
techniques, with direction to service-specific resourceso Facilitate GGOS communication
 Calendars
 User forums on relevant topics
 Bibliography
 Presentations
 Meeting summaries
 Working group activities
2. Installation of a clearinghouseo host catalogues for metadata for all “products” of the IAG services relevant to
GGOS based on GGOS standards

o

o
o

ensure interoperability within the GGOS community and to other systems e.g.
GEOSS:
 Data Products Organizational components (e.g., infrastructure, supporting institutions,personnel, services) Networks and their stations
Search (temporal, spatial, multi-technique, keywords, etc.) of metadata, data,and product databases
Web services (Catalogue Service Web, Web Map Service (Portrayal), etc…

3. Distributed applications for data mining of the GGOS products /data files to beprovided through the GGOS Portal include:o Data location tools (parse and merge data)o Data visualization toolso Data analysis tools
The Web portal applications allowing users to download, install and customize theportal services in their own environment.
Based on modern architecture, standards and Web services the requested tasks to build up
the GGOS portal can be realized not only by single institutions but also by consortia with
distributed server architecture. The portal should be designed and implemented in such afashion to permit mirroring/installation at alternate physical locations.

Table 3

Version 0.1 of GGOS Core Metadata Profile of the ISO Metadata Standard- November 2007 Notes: The GGOS Core Meta Data Profile is developed based on the WMO Core Metadata Profile of the ISO Metadata Standard andrecommendations of the GEO Architecture and Data Committee.
The following table provides an overview of the GGOS Core Metadata Profile suitable for use by decision makers and users. To implement
this standard the International Standard ISO 19115: 2003 and its corrigendum 1, which describe the complete ISO standard, must be
consulted.
Of the core elements listed, those in bold are mandatory and those in italic are optional with all others being conditional.
This Metadata Profile is a core set as a basic profile to collect the metadata for GGOS data sets. The ISO Standard in general provide morefeatures to descript the data sets in more details.
Deviations from the ISO 19115 are marked in red, information marked in green are lists which have to be complemented by GGOS or the IAG
services. The lists of descriptive keywords and data set categories topics can be set up according the GCMD list as a beginning and more
improved during discussion (table 7). The format descriptions should follow the table 2 with extensions for gravity and other geodetic fields notcovered here.
Generic Name

ISO Name/Role nameand Reference Lines

Definition

Information about the metadata - Basic information of GGOS Core Metadata Profile version 0.1[Metadata entity]
Root entity which defines metadata about a resource or resources
MD_Metadata (1)File ID
Unique identifier for this metadata file
fileIdentifier (2)language (3)Language
Language of this metadata item (ISO639-2, other parts may be used)characterSet (4)Character set
Full name of the character coding standard used for this metadata set
MD_CharacterSetCode (B.5.10)
parentIdentifier (5)File identifier
File identifier of the metadata to which this metadata is a subset (child)hierarchyLevel (6)Scope of metadata
Scope to which the metadata applies
MD_ScopeCode (B.5.25)
hierarchyLevelName (7)Number of hierarchy
Name of the hierarchy levels for which the metadata is provided
Contact
Party responsible for the metadata information
contact (8)CI_ResponsibleParty (see
374)
Date
Date that the metadata was created (ISO8601)
dateStamp (9)Standard nameName of the metadata standard (including profile name) used
metadataStandardName (10)

Standard version
URI
Localized character
stringSpatial information

Reference system
Metadata extension

Dataset identification
Content

Distribution Information
Data quality

metadataStandardVersion (11)dataSetURI (11.1)
locale (11.2)
PT_Locale (ISO19139)
languageCode
LanguageCode (ISO639)
countryCountryCode (ISO3166)characterEncoding
MD_characterSetCode(B.5.10)
spatialRepresentationInfo (12)
MD_SpatialRepresentation(see 156)
referenceSystemInfo (13)MD_ReferenceSystem (see 186)
metadataExtensionInfo (14)MD_MetadataExtensionInform
ation (see 303)
extensionOnlineResource(304)
CI_OnlineResource (see396)
extendedElementInformation(305)
MD_ExtendedElementInf
ormation(see 306)
identificationInfo (15)
MD_Indentification (see 36)
contentInfo (16)
MD_ContentInformation (see232)
distributionInfo (17)MD_Distribution (see 270)
dataQualityInfo (18)
DQ_DataQuality (see 78)

Version of the metadata standard (version of the profile) used
Uniformed Resource Identifier (URI) of the dataset to which the metadata applies
Provides information about an alternatively used localized character string for alinguistic extension

Digital representation of spatial information in the dataset

Description of the spatial and temporal reference systems used in the dataset
I
Information describing metadata extensions

Basic information about the resource(s) to which the metadata applies
Content of the dataset in more detail than the keywords.
Information about the distributor of and options for obtaining the resource(s)Overall assessment of quality of resource(s)Information about the catalogue of rules defined for the portrayal of resource(s)Catalogues

Restriction

Conceptual schema

Frequency of update

Aggregation of dataset
Dataset
Property type

[Identification]

portrayalCatalogueInfo (19)
MD_PortrayalCatalogueReference (see 268)
metadataConstraints (20)
MD_Constraints (see 67)

applicationSchemaInfo (21)
MD_ApplicationSchemaInform
ation (see 320)
metadataMaintenance (22)
MD_MaintenanceInformation(see 142)
seriesDS_Aggregate
describes
DS_DataSet
propertyType
GF_PropertyType (ISO19109)
featureType
GF_FeartureType (ISO19109)
featureAttribute
GF_AttributeType (ISO19109)

MD_Identification (23)
MD_ServiceIdentification (47)
MD_DataIdentification (36)citation (24)
CI_Citation (see 359)
abstract (25)
purpose (26)credit (27)status (28)

Restrictions on the access and use of the dataset (Could specify GGOS additional
Data as free text ) Note: At present the GGOS Core Metadata will not contain the
ISO parameters that describe access constraints to the metadata, but
implementers should be aware that the ISO parameters exist and might berequired in later versions of the GGOS Core. Any metadata “published” through asystem developed for the GGOS Core is therefore likely to be disclosed
regardless of privacy markings on the metadata.
Information about the conceptual schema of a dataset

Information about the frequency of metadata updates, and the scope of those
updates
Aggregation of dataset
DatasetTextual information related to the feature typeTextual information describing the concept of a feature typeClass of attribute definitions of a feature type

Basic information required to uniquely identify resource(s)See ISO19119 for further information
Citation data for the dataset
Brief narrative summary of the content of the dataset
Summary of the intentions with which the dataset was developed
Recognition of those who contributed to the dataset
Status of the dataset

MD_ProgressCode (B.5.23)
pointOfContact (29)
CI_ResponsibleParty (see 374)
resourceMaintenance(30)MD_MaintenanceInformation(see 142)
graphicOverview (31)
MD_BrowseGraphic (see 48)
resourceFormat (32)
MD_Format (see 284)
descriptiveKeywords (33)
MD_Keywords (see 52)
resourceSpecificUsage (34)
MD_Usage (see 62)
resourceConstraints (35)
MD_Constraints (see 67)
aggregationInfo (35.1)
MD_AggregateInformation (see66.1)

[Browse graphic]

Identification of, and means of communication with, person(s) and organizations(s)associated with the dataset
Information about the frequency of resource updates, and the scope of those
updates
A graphic that illustrates the dataset
A description of the format of the dataset
Commonly used words or formalised words or phrases used to describe the subject
Basic information about specific applications for which the dataset have been or
being used by different users
Restrictions on the access and use of the resource or metadata (could specify
GGOS additional data as free text)
Aggregate dataset information(MD_DataIdentification (36))
Method used to spatially represent geographic information
spatialRepresentationType (37)MD_spatialRepresentationType
Code (B.5.26)
Spatial density of the data in the dataset (e.g. grid spacing)spatialResolution (38)
MD_Resolution (see 59)
Language(s) used in the dataset (ISO639-2, other parts may be used)language (39)characterSet (40)Full name of the character coding standard used for the dataset
MD_CharacterSetCode (B.5.10)
topicCategory (41)Discipline covered by this dataset [ISO code list B.5.27] - Note this field is of limited
MD_TopicCategoryCode (B.5.27) use for GGOS purposes but is a required field within the ISO standard and isincluded to ensure conformity
Description of the dataset in the producer's processing environment
environmentDescription (44)extent (45)
Extent information including the bounding box, bounding polygon, vertical andtemporal extent of dataset
EX_Extent (see 334)
Any other descriptive information about the dataset
supplementalInformation (46)
MD_BrowseGraphic (48)

fileName (49)
fileDescription (50)
fileType (51)[Keywords][Representative
fraction][Resolution][Usage]

MD_Keywords (52)keyword (53)

GGOS_Keyword (GGOS)
type (54)
MD_KeywordTypeCode (B.5.17)
thesaurusName (55)
CI_Citation (see 359)
MD_RepresentativeFraction (56)
denominator (57)
MD_Resolution (59)equivalentScale (60)
MD_RepresentativeFraction (56)distance (61)
MD_Usage (62)specificUsage (63)usageDateTime (64)userDeterminedLimitations (65)

[Aggregation]

userContactInfo (66)
CI_ResponsibleParty (see374)
MD_AggregateInformation (66.1)
aggregateDataSetName (66.2)
CI_Citation (see 359)
aggregateDataSetIdentifier (66.3)
MD_Identifier (see 205)
associationType (66.4)
DS_AssociationTypeCode

Name of the file that contains a graphic that provides an illustration of the dataset
Text description of the illustration
Format in which the illustration is encoded, e.g. CGM, EPS, GIF, JPEG, PBM, PS,
TIFF, XWD
List of predefined and other keywords used to describe the dataset. Keywords
should be taken from a standard thesaurus (the URI for this thesaurus should begiven – this, for example, would facilitate searching in different languages), or
other defined list but free form keywords are permitted as well.
Subject matter used to group similar keywords
Name of the formally registered thesaurus or a similar authoritative source of
keywords
The number below the line in a vulgar fraction
Level of detail expressed as the scale of a comparable hardcopy map or chart
Ground sample distance
Brief description of the resource and/or resource series usage
Date and time of the first use or range of uses of the resource and/or resource
seriesApplications, determined by the user for which the resource and/or resource series
is not suitable
Identification of and means of communicating with person(s) and organization(s)using the resource(s)Citation information about the aggregate dataset
Identification information about aggregate dataset
Association type of the aggregate dataset

[Constraint (includes
legal and security](B.5.7)
initiativeType (66.5)
DS_InitiativeTypeCode (B.5.8)
MD_Constraints (67)
useLimitation (68)

Legal Constraint MD_LegalConstraints (69)
useLimitation (68)
accessConstraints (70)
MD_RestrictionCode (B.5.24)
useConstraints (71)
MD_RestrictionCode (B.5.24)
otherConstraints (72)Type of initiative under which the aggregate dataset was produced

Limitation affecting the fitness for use of the resource.
Restrictions and legal prerequisites for accessing and using the dataset
Limitation affecting the fitness for use of the resource.
Any special restrictions or limitations on obtaining the dataset
Any special restrictions or limitations or warnings on using the dataset
Other restrictions and legal prerequisites for accessing and using the dataset

Handling restrictions imposed on the dataset for security reasons
Security Constraint MD_SecurityConstraints (73)
Limitation affecting the fitness for use of the resource.
useLimitation (68)Name of the handling restrictions on the dataset
classification (74)
MD_ClassificationCode (B.5.11)
Explanation of the application of the legal constraints or other restrictions and legal
userNote (75)prerequisites for obtaining and using the dataset
Name of the classification systemclassificationSystem (76)Additional information about the restrictions on handling the dataset
handlingDescription (77)
[Data quality]
DQ_DataQuality (78)
scope (79)
The specific data to which the data quality information applies
DQ_Scope (see 138)
report (80)
Quantitative quality information for the data specified by the scope
DQ_Element (see 99)
lineage (81)Non-quantitative quality information about the lineage of the data specified by the
LI_Lineage (see 82)
scope
Information about the level of processing applied to the dataset. This field should[Lineage]
LI_Lineage (82)be used to indicate whether the data are observations, analyses (re-analyses),
forecast (based on initial states including observations), simulations or othersources of data. Could also be used to include the platform/mission in the sourceof data (e.g. Ship, aircraft, satellite, satellite id).
May need to use pairs of [source, processing step] to provide additional
information. May contain references (e.g. URI) to external information on the[Process step][Source][Data quality element]

statement (83)processStep (84)
LI_ProcessStep (see 86)
source (85)
LI_Source (see 92)
LI_ProcessStep (86)description (87)rationale (88)dateTime (89)processor (90)CI_ResponsibleParty (see 374)
source (91)
LI_Source (see 92)
LI_source (92)description (93)scaleDenominator (94)
MD_RepresentativeFraction(see 56)
sourceReferenceSystem (95)
MD_ReferenceSystem (see 186)
sourceCitation (96)
CI_Citation (see 359)
sourceExtent (97)
EX_Extent (see 334)
DQ_Element (99)
DQ_Completeness (108)
DQ_CompletenessCommission (109)
DQ_CompletenessOmission (110)
DQ_LogicalConsistency (111)
DQ_ConceptualConsistency (112)
DQ_DomainConsistency (113)
DQ_FormatConsistency (114)

processing and source.
Information about the events or source data used in constructing the dataset
Information about an event in the creation process for the dataset
Information about the source data used in creating the dataset

Description of the event, including related parameters or tolerances
Requirement or purpose for the process step
Date and time or range of date and time on or over which the process step
occurred
Identification of, and means of communication with, person(s) and organization(s)associated with the process step
Information about the source data used in creating the data specified by the scope

Detailed description of the level of the source data
Denominator of the representative fraction on a source map

Spatial reference system used by the source data
Recommended reference to be used for the source data
Information about the spatial, vertical and temporal extent of the source data

Aspect of quantitative quality information
Presence and absence of features, their attributes and their relationship
Excess data present in the dataset, as described by the scope
Data absent from the dataset, as described by the scope
Degree of adherence to logical rules of data structure, attribution and relationships
Adherence to rules of the conceptual schema
Adherence of values to the value domains
Degree to which data is stored in accordance with the physical structure of thedataset, as described by the scope

DQ_TopologicalConsistency (115)
DQ_PositionalAccuracy (116)
DQ_AbsoluteExternalPositionalAccuracy (117)
DQ_GriddedDataPositionalAccuracy(118)
DQ_RelativeInternalPositionalAccuracy (119)
DQ_TemporalAccuracy (120)
DQ_AccuracyOfATimeMeasurement(121)
DQ_TemporalConsistency (122)
DQ_TemporalValidity (123)
DQ_ThematicAccuracy (124)
DQ_ThematicClassificationCorrectne
ss (125)
DQ_NonQuantitativeAttributeAccuracy (126)
DQ_QuantitativeAttributeAccuracy(127)
nameOfMeasure (100)measureIdentification (101)
MD_Identifier (see 205)
measureDescription (102)evaluationMethodType (103)
DQ_EvaluationMethodTypeCode (B.5.6)
evaluationMethodDescription (104)evaluationProcedure (105)
CI_Citation (see 359)
dateTime (106)result (107)
DQ_Result (see 128)
[Result]
DQ_Result (128)
Conformance result DQ_ConformanceResult (129)Correctness of the explicitly encoded topological characteristics of the dataset as
described by the scope
Accuracy of the position of features
Closeness of reported coordinate values to values accepted as or being true
Closeness of gridded data position values to values accepted as or being true
Closeness of the relative positions of features in the scope to their respective
relative positions accepted as or being true
Accuracy of the temporal attributes and temporal relationships of features
Correctness of the temporal references of an item (reporting of error in timemeasurement
Correctness of ordered events or sequences, if reported
Validity of data specified by the scope with respect to time
Accuracy of quantitative attributes and the correctness of non-quantitative attributes
and of the classifications of features and their relationships
Compassion of the classes assigned to features or their attributes to a universe of
discourse
Accuracy of non-quantitative attributes
Accuracy of quantitative attributes
Name of the test applied to the data
Code identifying a registered standard procedure
Description of the measure
Type of method used to evaluate quality of the dataset

Description of the evaluation method
Reference to the procedure information
Date or range of dates on which a data quality measure was applied
Value obtained from applying a data quality measure or the outcome of evaluating
the obtained value against a specified acceptable conformance quality level
Information about the outcome of evaluating the obtained value against a specifiedspecification (130)
CI_Citation (see 359)
explanation (131)pass (132)
Quantitative result DQ_QuantitativeResult (133)[Scope][Maintenance][Scope description]

valueType (134)valueUnit (135)errorStatistic (136)value (137)
DQ_Scope (138)level (139)
MD_ScopeCode (B.5.25)
extent (140)
EX_Extent (see 334)
levelDescription (141)
MD_ScopeDescription (see 149)
MD_MaintenanceInformation (142)maintenanceAndUpdateFrequency (143)
MD_MaintenanceFrequencyC
ode (B.5.18)
dateOfNextUpdate (144)
userDefinedMaintenanceFrequency (145)
updateScope (146)
MD_ScopeCode (B.5.25)
updateScopeDescription (147)
MD_ScopeDescription (see 149)
maintenanceNote (148)contact (148.1)
CI_ResponsibleParty (see 374)
MD_ScopeDescription (149)
attribute (150)feature (151)

acceptable conformance quality level
Citation of products specification or user requirement against which data is being
evaluated
Explanation of the meaning of conformance for this result
Indication of the conformance result where 0= fail and 1=pass
The values or information about the value(s) obtained from applying a data quality
level
Value type for reporting a data quality result
Value unit for reporting a data quality result
Statistical method used to determine the value
Quantitative value or values, content determined by the evaluation procedure used
Hierarchical level of the data specified by the scope
Information about the horizontal, vertical and temporal extent of the data specified
by the scope
Detailed description about the level of the data specified by the scope

Frequency with which changes and additions are made to the resource after the
initial resource is completed

Scheduled revision date for resource
Maintenance period other than those defined
Scope of data to which maintenance is applied
Additional information about the range or extent of the resource
Information regarding specific requirements for maintenance the resource
Identification of, and means of communicating with, person(s) and organizations
with responsible party for maintaining the metadata
Attributes to which the information applies
Features to which the information applies

featureInstances (152)
attributeInstances (153)
dataset (154)other (155)[Spatial representation] MD_SpatialRepresentation (156)
Grid spatial rep. MD_GridSpatialRepresentation (157)
MD_Georectified (162)
numberOfDimensions (158)axisDimensionsProperties (159)
MD_Dimension (see 179)
cellGeometry (160)
MD_CellGeometryCode (B.5.9)
transformationParameterAvaila
bility (161)
Regularly spaced (MD_Georectified)
checkPointAvailability (163)checkPointDescription (164)
cornerPoints (165)

centerPoint( 166)

pointInPixel (167)
MD_PixelOrientationCode(B.5.22)transformationDimensionDescription (168)transformationDimensionMapping(169)
Irregularly Spaced MD_Georeferenceable (170)numberOfDimensions (158)

Feature instances to which the information applies
Attribute instances to which the information applies
Dataset to which the information applies
Class of information that does not fall into the other categories to which theinformation applies

Number of independent spatial-temporal axes
Information about spatial-temporal axis properties
Identification of grid data as point or cell
Identification of whether or not parameters for transformation between image
coordinates and geographic or map coordinates exist (are available)
Indication of whether or not geographic position points are available to test theaccuracy of the georeferenced grid data
Description of geographic position points used to test the accuracy of thegeoreferenced grid data
Earth location in the coordinate system defined by the Spatial Reference Systemand the grid coordinate of the cells at opposite ends of grid coverage along two
diagonals in the grid spatial dimensions. There are four corner points in ageorectified grid; at least two corner points along one diagonal are required.
Earth location in the coordinate system defined by the Spatial Reference Systemand the grid coordinate of the cell halfway between opposite ends of the grid in
the spatial dimensions
Point in a pixel corresponding to the Earth location of the pixel

General description of the transformation
Information about which grid axes are the spatial map axes

Number of independent spatial-temporal axes

axisDimensionsProperties (159)
MD_Dimension (see 179)
cellGeometry (160)
MD_CellGeometryCode (B.5.9)
transformationParameterAvaila
bility (161)
controlPointAvailability (171)orientationParameterAvailability(172)
orientationParameterDescription(173)
georeferencedParameters (174)parameterCitation (175)
CI_Citation (see 359)

Information about spatial-temporal axis properties
Identification of grid data as point or cell
Identification of whether or not parameters for transformation between image
coordinates and geographic or map coordinates exist (are available)
Indication of whether or not control point(s) exists
Indication of whether or not orientation parameters are available
Description of parameters used to describe sensor orientation
Terms which support grid data georeferencing
Reference providing description of the parameters

Vector spatial rep. MD_VectorSpatialPresentation (176)
Code which identifies the degree of complexity of the spatial relationshiptopologyLevel (177)
MD_TopologyLevelCode (B.5.28)
Information about the geometric objects used in the dataset
geometricObjects (178)
MD_GeometricObjects (see 18
3)[Dimension]
MD_Dimension (179)Name of the axis
dimensionName (180)
MD_DimensionNameTypeCode (B.5.14)
Number of elements along the axis
dimensionSize (181)
Degree of detail in the grid dataset
resolution (182)[Geometric objects]
MD_GeometricObjects (183)Name of point or vector objects used to locate zero-, one-, two-, or threegeometricObjectType (184)dimensional spatial locations in the dataset
MD_GeometricObjectTypeCode (B.5.15)
Total number of the point or vector object type occurring in the dataset
geometricObjectCount (185)
Information about the reference systems used (temporal, coordinate and
MD_ReferenceSystem (186)[Reference System]
geographic)
Name of reference systemreferenceSystemIdentifier (187)
RS_Identifier (see 208)

Spacial and temporal RS_ReferenceSystem (195)referencename (196)
RS_Identifier (see 208)
domainOfValidity (197)
EX_Extent (see 334)
MD_Identifier (205)[Identifier]authority (206)
CI_Citation (see 359)
code (207)
Identifier for reference RS_Identifier (208)systemauthority (206)
CI_Ciation (see 359)
code (207)codeSpace (208.1)
version (208.2)
MD_ContentInformation (232)[Content Information]
MD_FeatureCatalogueDescription
FeatureCatalogue(233)

complianceCode (234)language (235)includeWithDataset (236)featureTypes (237)featureCatalogueCitation(238)
CI_Citation (see 359)
Grid data cell

MD_CoverageDescription (239)Name of reference system used
Range which is valid for the reference system

Person or party responsible for maintenance of the namespace
Alphanumeric value identifying an instance in the namespace

Person or party responsible for maintenance of the namespace
Alphanumeric value identifying an instance in the namespace
Name or identifier of the person or organization responsible for namespace
Version identifier for the namespace
The ISO standard provides both “feature catalogues” and “Coverage” to describe
the attributes of the data held in the dataset. This GGOS Core Metadata chooses
to use “feature” to describe all aspects of these attributes, including those relating
to grids of data.
Identification of whether or no the cited feature catalogue complies with [ISO19110. Value 1 if feature catalogue is compliant with ISO19110. Default is 0 (notcompliant)Language(s) used in the Catalogue (ISO639-2, other parts can be used)
Indication of whether or not the feature catalogue is included with the dataset.
Required if feature Catalogue is used. Value 1 in feature catalogue is included indataset, 0 if not.
Subset of feature types from the cited feature catalogue occurring in the dataset.
Note: the physical variables described by the data are attributes of a feature (which
could be an observed profile or a field of data, for example).
Complete bibliographic reference to one or more external feature catalogue.
Required if feature Catalogue is used. Bibliographic reference to the featurecatalogue(s) used.

[Range dimension]

MD_ImageDescription (243)
attributeDescription (240)contentType (241)
MD_CoverageContentType
Code (B.5.12)
dimension (242)
MD_RangeDimension (256)(MD_ImageDescription)
illuminationElevationAngle (244)
illuminationAzimuthAngle (245)imagingCondition (246)
MD_ImagingConditionCode(B.5.16)
imageQualityCode (247)
MD_Identifier (see 205)
cloudCoverPercentage (248)processingLevelCode (249)
MD_Identifier (see 205)
compressionGenerationQuantity (250)triangulationIndicator (251)radiometricCalibrationDataavail
ability (252)cameraCalibrationInformationA
vailability (253)filmDistortionInformationAvaila
bility (254)
lensDistortionInformationAvaila
bility (255)
MD_RangeDimension (256)
MD_Band (259)
sequenceIdentifier (257)

descriptor (258)Range of wavelengths (MD_Band)
maxValue (260)

Description of the attribute described by the measurement value
Type of information represented by the cell value

Information on the attribute described by the measurement value

Illumination elevation measured in degrees clockwise
Illumination azimuth measured in degrees clockwise
Conditions affected the image

Specifies the image quality
Area of the dataset obscured by clouds, expressed as percentage of spatial extent
Image distributor's code that identifies the level of radiometric and geometric
processing that has been applied
Count of the number of lossy compression cycles performed on the image
Indication of whether or not triangulation has been performed upon the image
Indication of whether or not the radiometric calibration information for generating
the radiometrically calibrated standard data product is available
Indication of whether or not constants are available which allow for camera
calibration corrections
Indication of whether or not Calibration Reseau information is available
Indication of whether or not lens aberration correction information is available

Number that uniquely identifies instances of bands of wavelength on which asensor operates
Description of the range of a cell measurement value
Longest wavelength that the sensor is capable of collecting within a designatedband

minValue (261)units (262)peakResponse (263)bitsPerValue (264)[Portrayal catalogue][Distribution]

toneGradation (265)scaleFactor (266)
offset (267)
MD_PortrayalCatalogueReference(268)
portrayalCatalogueCitation (269)
CI_Citation (see 359)
MD_Distribution (270)
distributionFormat (271)
MD_Format (see 284)
distributor (272)
MD_Distributor (see 279)transferOptions (273)
MD_DigitalTransferOptions(see 274)

Shortest wavelength that the sensor is capable of collecting within a designatedband
Units in which sensor wavelengths are expressed
Wavelength at which the response is the highest
Maximum number of significant bits in the uncompressed representation for thevalue in each and of each pixel
Number of discrete numerical values in the grid data
Scale factor which has been applied to the cell value
The physical value corresponding to a cell value of zero

Bibliographic reference to the portrayal catalogue cited

A description of the format of the data to be distributed
Information about the distributor
Information about technical means and media by which a resource is obtained fromthe distributor[Digital transfer options] MD_DigitalTransferOptions (274)
Tiles, layers, geographic areas, etc., in which data is available
unitsOfDistribution (275)
Estimated size of a unit in the specified transfer format, expressed in megabytes.
transferSize (276)
Information about online sources from which the resource can be obtained
onLine (277)
CI_OnlineResource (see 396)
Information about offline media on which the resource can be obtained
offLine (278)
MD_Medium (see 291)
[Distributor information] MD_Distributor (279)Party from whom the resource may be obtained. This list need not be exhaustive
distributorContact (280)
CI_ResponsibleParty (see 374)
Information about how the resource may be obtained, and related instructions anddistributionOrderProcess (281)
fee information
MD_StandardOrderProcess(see 298)
Information about the format used by the distributor
distributorFormat (282)
MD_Format (see 284)

[Format][Medium][Standard orderprocess][Extended element]

Information about the technical means and media used by the distributor
distributorTransferOptions (283)
MD_DigitalTransferOptions(see 274)
MD_Format (284)Name of the data transfer format(s)name (285)
Version of the format (date, number, etc.)
version (286)Amendment number of the format version
amendmentNumber (287)Name of a subset, profile, or product specification of the format
specification (288)Recommendations of algorithms or processes that can be applied to read or
fileDecompressionTechniqueexpand resources to which compression techniques have been applied(289)
Information about the distributor’s format
formatDistributor (290)
MD_Distributor (279)
MD_Medium (291)
Name of the medium on which the resource can be received
name (292)
MD_MediumNameCode (B.5.20)
Density at which the data is recorded
density (293)
densityUnits (294)Units of measure for the recording density
Number of items in the media identified
volumes (295)
Method used to write to the medium
mediumFormat (296)
MD_MediumFormatCode(B.5.19)
Description of other limitations or requirements for using the medium
mediumNote (297)
MD_StandardOrderProcess (298)Fees and terms for retrieving the resource. Include monetary units (as specified infees (299)
ISO 4217)
Date and time when the resource will be available
plannedAvailableDateTime (300)
General instructions, terms and services provided by the distributor
orderingInstructions (301)
Typical turnaround time for the filling of an orderturnaround (302)
MD_ExtendedElementInformation (306)Name of the extended metadata element
name (307)
shortName (308)
Short form suitable for use in an implementation method such as XML or SGML.
NOTE other methods may be useddomainCode (309)
Three digit code assigned to the extended element
Definition of the extended element
definition (310)
Obligation of the extended element
obligation (311)
MD_ObligationCode (B.5.21)

condition (312)
dataType (313)
MD_DatatypeCode (B.5.13)
maximumOccurrence (314)domainValue (315)parentEntity (316)[Application schema][Extent]

Condition under which the extended element is mandatory
Code which identifies the kind of value provided in the extended element
Maximum occurrence of the extended element
Valid values that can be assigned to the extended element
Name of the metadata entity(s) under which this extended metadata element may
appear. The name(s) may be standard metadata element(s) or other extended
metadata element(s)Specifies how the extended element relates to other existing elements and entities
Reason for creating the extended element
Name of the person or organization creating the extended element

rule (317)rationale (318)source (319)
CI_ResponsibleParty (see 374)
MD_ApplicationSchemaInformation(320)
Name of the application schema usedname (321)
CI_Citation (see 359)
Identification of the schema language used
schemaLanguage (322)Formal language used in Application SchemaconstraintLanguage (323)Full application schema given as an ASCII file
schemaAscii (324)Full application schema given as a graphics filegraphicsFile (325)Full application schema given as a software development filesoftwareDevelopmentFile (326)Software dependent format used for the application schema software dependent filesoftwareDevelopmentFileFormat(327)
EX_Extent (334)
Spatial and temporal extent for the dataset (in text)
description (335)
GGOS metadata must contain the “bounding box” where relevant – even if global.
geographicElement (336)However, either or both of a geographical name and/or a bounding polygon
and/or an irregular point set should be used as well.
Identification of whether the bounding polygon encompasses an area covered byextentTypeCode (340)the data or an area where data is not present
The polygon is defined as a set of co-ordinate pairs with the last pair the same aspolygon (342)the first. When the points in the polygon are traversed, the interior is to the left ofthe direction of travel. If the region has “holes”, multiple polygons may be used.
The points of the outer polygon will be traversed anti-clockwise, and those of
inner polygons will be traversed clockwise.
NOTE For polar-orbiting satellites, polygon should be used to appropriately
encompass a slant area which is composed by orbits.

westBoundLongitude (344)eastBoundLongitude (345)southBoundLatitude (346)northBoundLatitude (347)

geographicIdentifier (349)
MD_Identifier (205)

temporalElement (337)extent (351)verticalElement (338)minimumValue (355)maximumValue (356)unitOfMeasure (357)verticalDatum (358)[Station]

stationstationDescription (GGOS)InternationalStationId (GGOS)
code (GGOS)
owner (GGOS)
stationName (GGOS)
country (GGOS)GGOSRegion (GGOS)
latitude (GGOS)
longitude (GGOS)
statonHeight (GGOS)

Western-most limit of the dataset, longitude in decimal degrees (positive east)
Eastern-most limit of the dataset, longitude in decimal degrees (positive east)
Southern-most limit of the dataset, latitude in decimal degrees (positive north)
Northern-most, limit of the dataset, latitude in decimal degrees (positive north)
Sets of points defining a bounding polygon.
NOTE This is only an approximate reference so specifying the co-ordinate system
is unnecessary. Using latitude and longitude, for any box surrounding a Pole, thelimits are +/-90 and the southern (northern) most latitude, and the longitude
extent must be +/-180. Bounding box may not be effective when used to searchfor data that cross the international date line or a pole.
Identifier used to represent a geographic area or location. While it is preferable touse names from a well-known Gazetteer (this should be referred to in theidentifier), it is acceptable to use names that are not in a Gazetteer.
NOTE: Each of the Extent fields below is required if applicable
Date and time for the content of the dataset
Vertical domain of the dataset (Note: There is potential ambiguity about verticalextent, particularly in oceanography. This can be resolved by the unitOfMeasure.)
Lowest vertical extent contained in the dataset
Highest vertical extent contained in the dataset
Vertical units used for vertical extent information (E.g.: metres, feet, hectopascals)This must include the sign convention for height (whether values increase upwards
or downwards).
Information about the origin from which the maximum and minimum elevation
values are measured (see ISO 1911).
Description of a geodetic station
Code list for station types; e.g. DOMESName of the station
Name of county
Name of GGOS Region
LatitudeLongitude
Height of the station

[Citation][Responsible party]

referenceHeight (GGOS)
stationContactInfo (GGOS)
CI_Contact (see 387)
prodctList (GGOS)
product (GGOS)
timePeriod (GGOS)
beginDateTime (GGOS)
endDateTime (GGOS)
dataFrequency (GGOS)
accessRights (GGOS)
quality (GGOS)
CI_Citation (359)
title (360)alternateTitle (361)date (362)
CI_Date (see 393)
edition (363)
editionDate (364)identifier (365)
MD_Identifier (see 205)citedResponsibleParty (367)
CI_ResponsibleParty (see 374)
presentationForm (368)
CI_PresentationFormCode(B.5.4)
series (369)
CI_Series (see 403)
otherCitationDetails (370)collectiveTitle (371)ISBN (372)
ISSN (373)
CI_ResponsibleParty (374)individualName (375)

Reference heightContact point of the station
List of products
Time period

Access rights
QualityStandardized resource reference
Name by which the cited resource is known
Short name or other language name by which the cited information is known
Reference date for the cited resource
Version of the cited resource
Date of the edition
Value uniquely identifying an object within a namespace
Name and position information for an individual or organization that is responsible
for the resource
Mode in which the resource is represented

Information about the series, or aggregate dataset, of which the dataset is a part
Other information required to complete the citation that is not recorded elsewhere
Common title with holdings note
NOTE title identifies elements of a series collectively, combined with information
about what volumes are available at the source cited
International Standard Book Number
International Standard Serial Number
Identification of, and means of communication with, person(s) and organizations
associated with the dataset
Name of the responsible person-surname, given name, title, separated by adelimiter[Address][Contact][Date]

Online resources][Series]organisationName (376)
positionName (377)contactInfo (378)
CI_Contact (see 387)role(379)
CI_RoleCode (B.5.5)
CI_Address (380)deliveryPoint (381)city (382)administrativeArea (383)
postalCode (384)country (385)electronicMailAddress (386)
CI_Contact (387)phone (388)
CI_Telephone (see 407)
address (389)
CI_Address (see 380)
onlineResource (390)
CI_OnlineResource (see 396)
hoursOfService (391)contactInstructions (392)
CI_Date (393)date (394)dateType (395)
CI_DateTypeCode (B.5.2)
CI_OnlineResource (396)linkage (397)
protocol (398)applicationProfile (399)name (400)description (401)function (402)
CI_OnlineFunctionCode (B.5.3)
CI_Series (403)

Name of the responsible organizationRole or position of the responsible person
Address of the responsible party
NOTE: Either a phone number or address is required
Function performed by the responsible party

Address line for the location (as described in ISO11180, Annex A)
City of the location
State, province of the location
Postal code (Zip or other)
Country (ISO3166-3, other parts may be used)
Electronic mail address of the responsible party
Telephone numbers at which the organization or individual may be contacted
Physical and email address at which the organization or individual may becontacted
On-line information that can be used to contact the individual or organization
Time period (including time zone) when individuals can contact the organization orindividual
Supplemental instructions on how or when to contact the organization or individual
Reference date for the dataset
Type of date [code list: creation, publication or revision date]

Location for on-line access using Uniform Resource Locator (URL) etc.
Connection protocol to be used
Name of an application profile that can be used with the online resource
Name of the online resource
Detailed text description of what the online resource is/does
Code for function performed by the online resource[Telephone]name (404)issueIdentification (405)page (406)
CI_Telephone (407)voice (408)facsimile (409)

Name of the series, or aggregate dataset, of which the dataset is a part
Information identifying the issue of the series
Details on which pages of the publication the article was published
Telephone numbers by which individuals can speak to the responsible organization
or individual
Telephone numbers of a facsimile machine for the responsible organization orindividual

Extensions to ISO Code Lists

B.5.2 CI_DateTypeCode <<CodeList>>
1.
2.
3.
4.

Name
CI_DateTypeCodecreationpublication
revision

Additional entries
5.
reference

Domain code
DateTypCd
001
002
003

Definition
identification of when a given event occurred
date identifies when the resource was brought into existencedate identifies when the resource was issued
date identifies when the resource was examined or re-examined andimproved or amended

004

B.5.5 CI_RoleCode <<CodeList>>
6.
7.
8.

Name
CI_RoleCoderesourceProvider
custodian

Domain code
RoleCd
001
002

9.
10.
11.
12.
13.

owner
user
distributor
originator
pointOfContact

003
004
005
006
007

14. principalInvestigator
15. processor

008
009

16. publisher
17. author

010
011

Definition
function performed by the responsible party
party that supplies the resource
party that accepts accountability and responsibility for the data andensures appropriate care and maintenance of the resource
party that owns the resource
party who uses the resource
party who distributes the resource
party who created the resource
party who can be contacted for acquiring knowledge about or acquisitionof the resource
key party responsible for gathering information and conducting research
party who has processed the data in a manner such that the resource has
been modified
party who published the resource
party who authored the resource

B.5.10 MD_CharacterSetCode <<CodeList>>
Name
18. MD_CharacterSetC
ode
19. ucs2
20. ucs4
21. utf7
22. utf8
23. utf16
24. 8859part1

Domain code
CharSetCd
001
002
003
004
005
006

25. 8859part2

007

26. 8859part3008

27. 8859part4009

28. 8859part5010

29. 8859part6011

30. 8859part7012

31. 8859part8013

32. 8859part9

014

Definition
name of the character coding standard used for the resource
16-bit fixed size Universal Character Set, based on ISO/IEC 10646
32-bit fixed size Universal Character Set, based on ISO/IEC 10646
7-bit variable size UCS Transfer Format, based on ISO/IEC 10646
8-bit variable size UCS Transfer Format, based on ISO/IEC 10646
16-bit variable size UCS Transfer Format, based on ISO/IEC 10646
ISO/IEC 8859-1, Information technology – 8-bit single-byte coded graphic
character sets – Part 1: Latin alphabet No. 1
ISO/IEC 8859-2, Information technology – 8-bit single-byte coded graphic
character sets – Part 2: Latin alphabet No. 2
ISO/IEC 8859-3, Information technology – 8-bit single-byte coded graphic
character sets – Part 3: Latin alphabet No. 3
ISO/IEC 8859-4, Information technology – 8-bit single-byte coded graphic
character sets – Part 4: Latin alphabet No. 4
ISO/IEC 8859-51, Information technology – 8-bit single-byte codedgraphic character sets – Part 5: Latin/Cyrillic alphabet
ISO/IEC 8859-6, Information technology – 8-bit single-byte coded graphic
character sets – Part 6: Latin/Arabic alphabet
ISO/IEC 8859-7, Information technology – 8-bit single-byte coded graphic
character sets – Part 7: Latin/Greek alphabet
ISO/IEC 8859-8, Information technology – 8-bit single-byte coded graphic
character sets – Part 8: Latin/Hebrew alphabet
ISO/IEC8859-9, Information technology – 8-bit single-byte coded graphic
character sets – Part 9: Latin alphabet No. 5

10

Name
33. 8859part10

Domain code015

34. 8859part11016

35. (reserved for futureuse)
36. 8859part13

017
018

37. 8859part14019

38. 8859part15020

39. 8859part16

021

40.
41.
42.
43.
44.
45.
46.

jis
shiftJIS
eucJP
usAscii
ebcdic
eucKR
big5

022
023
024
025
026
027
028

47. GB2312
Additional entries
48. CP1251

029

Definition
ISO/IEC 8859-10, Information technology – 8-bit single-byte codedgraphic character sets – Part 10: Latin alphabet No. 6
ISO/IEC 8859-11, Information technology – 8-bit single-byte codedgraphic character sets – Part 11: Latin/Thai alphabet
a future ISO/IEC 8-bit single-byte coded graphic character set (e.g.
possibly ISO/IEC 8859-12
ISO/IEC 8859-13, Information technology – 8-bit single-byte codedgraphic character sets – Part 13: Latin alphabet No. 7
ISO/IEC 8859-14, Information technology – 8-bit single-byte codedgraphic character sets – Part 14: Latin alphabet No. 8 (Celtic)
ISO/IEC 8859-15, Information technology – 8-bit single-byte codedgraphic character sets – Part 15: Latin alphabet No. 9
ISO/IEC 8859-16, Information technology – 8-bit single-byte codedgraphic character sets – Part 16: Latin alphabet No. 10
japanese code set used for electronic transmission
japanese code set used on MS-DOS based machines
japanese code set used on UNIX based machinesunited states ASCII code set (ISO 646 US)
ibm mainframe code set
korean code set
traditional Chinese code set used in Taiwan, Hong Kong of China andother areas
simplified Chinese code set

030

B.5.11 MD_ClassificationCode <<CodeList>>
Name
49. MD_ClassificationCode
50. unclassified
51. restricted
52. confidential
53. secret
54. topsecret

Domain code
ClassificationCd
001
002
003
004
005

Definition
name of the handling restrictions on the dataset
available for general disclosure
not for general disclosure
available for someone who can be entrusted with information
kept or meant to be kept private, unknown, or hidden from all but a selectgroup of peopleof the highest secrecy

B.5.18 MD_MaintenanceFrequencyCode <<CodeList>>
Name
55. MD_MaintenanceFr
equencyCode
56. continual
57. daily
58. weekly
59. fortnightly
60. monthly
61. quarterly
62. biannually
63. annually
64. asNeeded
65. irregular
66. notPlanned
67. unknown
Additional entries
68. hourly
69. 3-hourly
70. 6-hourly
71. 12-hourly

Domain code
MaintFreqCd
001
002
003
004
005
006
007
008
009
010
011
012

Definition
frequency with which modifications and deletions are madeto the data
after it is first produced
data is repeatedly and frequently updated
data is updated each day
data is updated on a weekly basis
data is updated every two weeks
data is updated each month
data is updated every three months
data is updated twice each year
data is updated every year
data is updated as deemed necessary
data is updated intervals that are uneven in duration
there are no plans to update the data
frequency of maintenance for the data is not known

013
014
015
016

11

B.5.20 MD_MediumNameCode <<CodeList>>
Name
72. MD_MediumNameC
ode
73. cdRom
74. dvd
75. dvdRom
76. 3halfInchFloppy
77. 5quarterInchFloppy
78. 7trackTape
79. 9trackTape
80. 3480Cartridge
81. 3490Cartridge
82. 3580Cartridge
83. 4mmCartridgeTape
84. 8mmCartridgeTape
85. 1quarterInchCartridg
eTape
86. digitalLinearTape
87. onLine
88. satellite
89. telephoneLink
90. hardcopy

Domain code
MedNameCd

Definition
name of the medium

001
002
003
004
005
006
007
008
009
010
011
012
013

read-only optical disk
digital versatile disk
digital versatile disk, read only
3.5 inch magnetic disk
5.25 inch magnetic disk
7 track magnetic tape
9 track magnetic tape3480 cartridge tape drive3490 cartridge tape drive3580 cartridge tape drive
4 millimetre magnetic tape
8 millimetre magnetic tape0.25 inch magnetic tape

014
015
016
017
018

half inch cartridge streaming tape drive
direct computer linkage
linkage through a satellite communication systemcommunication through a telephone network
pamphlet or leaflet giving descriptive information

B.5.23 MD_ProgressCode <<CodeList>>
91.
92.
93.
94.
95.
96.

Name
MD_ProgressCodecompletedhistoricalArchive
obsoleteonGoingplanned97. required
98. underDevelopment
Additional entries
99. owner

Domain code
ProgCd
001
002
003
004
005
006
007

Definition
status of the dataset or progress of a review
production of the data has been completed
data has been stored in an offline storage facility
data is not longer relevant
data is continually being updated
fixed date has been established upon or by which the data will be createdor updated
data needs to be generated or updated
data is currently in the process of being created008

B.5.24 MD_RestrictionCode <<CodeList>>Name100. MD_RestrictionCode101. copyright

Domain code
RestrictCd001

102. patent

002

103. patentPending
104. trademark

003
004

105. license
106. intellectualProperty
Rights107. restricted108. otherRestrictions

005
006
007
008

Definition
limitation(s)placed upon the access or use of the data
exclusive right to the publication, production, or sale of the rights to aliterary, dramatic, musical, or artistic work, or to the use of a commercial
print or label, granted by law for a specified period of time to an author,
composer, artist, distributor
government has granted exclusive right to make, sell, use or license an
invention or discovery
produced or sold information awaiting a patenta name, symbol, or other device identifying a product, officially registered
and legally restricted to the use of the owner or manufacturer
formal permission to do somethingrights to financial benefit from and control of distribution of non-tangible
property that is a result of creativity
withheld from general circulation or disclosure
limitation not listed

12

B.5.25 MD_ScopeCode <<CodeList>>
Name
109. MD_ScopeCode110. attribute111. attributeType112. collectionHardware
113. collectionSession
114. dataset
115. series

Domain code
ScopeCd
001
002
003
004
005
006

116. nonGeographicData
set
117. dimensionGroup
118. feature
119. featureType120. propertyType
121. fieldSession
122. software
123. service

007
008
009
010
011
012
013
014

124. model

015

125. tile

016

Definition
class of information to which the referencing entity applies
information applies to the attribute value
information applies to the characteristic of a feature
information applies to the collection hardware class
information applies to the collection session
information applies to the dataset
information applies to the series
Note: "series" applies to any DS_Aggregate
information applies to non-geographic data
information applies to a dimension group
information applies to a feature
information applies to a feature type
information applies to a property type
information applies to a field session
information applies to a computer program or routine
information applies to a capability which a service provider entity makes
available to a service user entity through a set of interfaces that define abehaviour, such as a use caseinformation applies to a copy or limitation of an existing or hypotheticalobjectinformation applies to a tile, a spatial subset of geographic data

B.5.26 MD_SpatialRepresentationTypeCode <<CodeList>>
Name
126. MD_SpatialRepresentationTypeCode127. vector
128. grid
129. textTable
130. tin131. stereoModel

Domain code
SpatRepTypCd
001
002
003
004
005

132. video
Additional entries
133. bitmap
134. irregularPoints

Definition
method used to represent geographic information in the dataset

006

vector data is used to represent geographic data
grid data is used to represent geographic data
textual or tabular data is used to represent geographic data
triangulated irregular network
three-dimensional view formed by the intersecting homologous rays of an
overlapping pair of images
scene from a video recording

007
008

Irregularly-spaced points, such as meteorological stations

B.5.27 MD_TopicCategoryCode <<CodeList>>
Name
135. MD_TopicCategory
Code

Domain code
TopicCatCd

136. farming

001

137. biota

002

138. boundaries

003

Definition
high-level geographic data thematic classification to assist in the grouping
and search of available geographic data sets. Can be used to group
keywords as well.
Listed examples are not exhaustive.
NOTE It is understood there are overlaps between general categories andthe user is encouraged to select the one most appropriate.
rearing of animals and/or cultivation of plants
Examples: agriculture, irrigation, aquaculture, plantations, herding, pests
and diseases affecting crops and livestock
flora and/or fauna in natural environment
Examples: wildlife, vegetation, biological sciences, ecology, wilderness,sealife, wetlands, habitat
legal land descriptions
Examples: political and administrative boundaries

13

Name
Domain code
139. climatologyMeteorol 004
ogyAtmosphere140. economy

005

141. elevation006

142. environment

007

143. geoscientificInformat 008
ion

144. health009

145. imageryBaseMapsE 010
arthCover146. intelligenceMilitary011

147. inlandWaters

012

148. location

013

149. oceans

014150. planningCadastre

015

151. society016152. structure017

153. transportation

018

154. utilitiesCommunicati 019
on

Additional entries
155. ITRF
156. ICRF
157. EOP
158. hydrology
159. climatology
160. Mapping function
161. GPS
162. DORIS
163. LASERDefinition
processes and phenomena of the atmosphere
Examples: cloud cover, weather, climate, atmospheric conditions, climatechange, precipitation
economic activities, conditions and employment
Examples: production, labour, revenue, commerce, industry, tourism andecotourism, forestry, fisheries, commercial or subsistence hunting,
exploration and exploitation of resources such as minerals, oil and gas
height above or below sea level
Examples: altitude, bathymetry, digital elevation models, slope, derived
products
environmental resources, protection and conservation
Examples: environmental pollution, waste storage and treatment,
environmental impact assessment, monitoring environmental risk, nature
reserves, landscapeinformation pertaining to earth sciences
Examples: geophysical features and processes, geology, minerals,sciences dealing with the composition, structure and origin of the earth’s
rocks, risks of earthquakes, volcanic activity, landslides, gravity
information, soils, permafrost, hydrogeology, erosion
health, health services, human ecology, and safety
Examples: disease and illness, factors affecting health, hygiene,
substance abuse, mental and physical health, health services
base maps
Examples: land cover, topographic maps, imagery, unclassified images,
annotations
military bases, structures, activities
Examples: barracks, training grounds, military transportation, informationcollection
inland water features, drainage systems and their characteristics
Examples: rivers and glaciers, salt lakes, water utilization plans, dams,
currents, floods, water quality, hydrographic charts
positional information and services
Examples: addresses, geodetic networks, control points, postal zones
and services, place names
features and characteristics of salt water bodies (excluding inland waters)
Examples: tides, tidal waves, coastal information, reefs
information used for appropriate actions for future use of the land
Examples: land use maps, zoning maps, cadastral surveys, landownershipcharacteristics of society and cultures
Examples: settlements, anthropology, archaeology, education, traditional
beliefs, manners and customs, demographic data, recreational areas andactivities, social impact assessments, crime and justice, census
information
man-made construction
Examples: buildings, museums, churches, factories, housing,monuments, shops, towers
means and aids for conveying persons and/or goods
Examples: roads, airports/airstrips, shipping routes, tunnels, nauticalcharts, vehicle or vessel location, aeronautical charts, railways
energy, water and waste systems and communications infrastructure andservices
Examples: hydroelectricity, geothermal, solar and nuclear sources ofenergy, water purification and distribution, sewage collection anddisposal, electricity and gas distribution, data communication,
telecommunication, radio, communication networks

020
021
022
023
024
025
026
027
028

14

Name
164. VLBI
165. Gravity
166. Gravity models
167. Absolute gravity
168.
169.
170.
171.
172.
173.
174.
175.
176.
177.
178.
179.

Domain code
029
030
031
032

Definition

GGOS_DataFrequencyCode <<CodeList>> (GGOS)Name
1.

GGOS_DataFrequencyCod
e

2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.

continuous
1-minute
5-minute
10-minute15-minute30-minutehourly3-hourly
6-hourly
8-hourly
12-hourly
daily
weekly10-daily
fortnightly
monthly
quarterly
biannuallyannually
decadallyirregularly

Domain code
DataFreqCd
001
002
003
004
005
006
007
008
009
010
011
012
013
014
015
016
017
018
019
020
021

Definition
Temporal sampling frequency of the data
within the dataset
More than once per minute

Decade or longer

15

Table 4

Standardized Data Formats
FormatRINEX

Hatanaka
NPT

FR

CRD

CPF

SINEX

SP

Description

VersionReceiver Independent Exchange format that can accommodate GNSS data (GPS, GLONASS,
2.10, 2.11
3.0 (F)future Galileo). Seven main file types: C (satellite and receiver clock), D (Hatanaka compressed
GNSS observation data) G (GLONASS broadcast ephemeris), H (GEO broadcast ephemeris) M(meteorological), N (GPS broadcast ephemeris), O (GNSS observation data). Each file typeconsists of a header and data section which contains information for the entire file. Each filecontains the data from one receiver and one session (e.g., day, hour, sub-hour). Observables are:time, pseudo-range, phase, and Doppler.
ftp://igscb.jpl.nasa.gov/pub/data/format/rinex210.txt
ftp://igscb.jpl.nasa.gov/pub/data/format/rinex211.txt
ftp://igscb.jpl.nasa.gov/pub/data/format/rinex300.txt
Compression format used with RINEX observation data files
4.0.
ftp://terras.gsi.go.jp/software
Normal point format. Data are sampled over time based upon the presence of some minimum
2
number of data points in the sampling interval Data record contains data from one station and one
pass segment. Pass segment consists of a header record followed by data records.
http://ilrs.gsfc.nasa.gov/products_formats_procedures/normal_point/np_format.html
Full-rate format. he full-rate data are sorted by satellite and time and are available in daily and3monthly increments.
http://ilrs.gsfc.nasa.gov/products_formats_procedures/fullrate/fr_format_v3.html
Consolidated Laser Ranging Data format under development. An integrated, flexible, extensible
0.26
format for the ILRS full-rate, sampled engineering, and normal point data. Will accommodate
transponder data and to handle high repetition rate laser data without unnecessary redundancy. Fileconsists of header, configuration, and data records from one satellite and one session (hourly,
daily, monthly).
http://ilrs.gsfc.nasa.gov/products_formats_procedures/crd.html
Consolidated Prediction Format. The CPF information accurately predicts positions and ranges for
1.01
a much wider variety of laser ranging targets than had been previously possible. CPF files include
daily tables of X, Y, and Z positions for each target which can then be interpolated for very
accurate predictions. CPF provides an expanded format capability and greatly improves tracking
on low satellites because the full modeling potential of the orbit computation at the prediction
center will be passed on to the stations.
http://ilrs.gsfc.nasa.gov/products_formats_procedures/predictions/cpf.html
Software Independent Exchange Format. General-purpose solution exchange format for space
2.01
geodesy that facilitates the task of combining solutions. SINEX was designed to be modular andgeneral enough to handle multiple techniques. It provides complete information on a priori
information that can be removed when required, making it unnecessary to submit or distributemultiple SINEX solution files, e.g. constrained and unconstrained (free) solution files. Also used
for VLBI experiment data.
http://ilrs.gsfc.nasa.gov/products_formats_procedures/predictions/cpf.html
Standard Product (for orbits) for all satellite types. The basic format is a position and clock record; SP3c, SP1
a second, optional, record contains velocities and clock rates-of-change. Also includes satellite
clock corrections, orbit accuracy exponents, comment lines, as many as three different sets of

ASCII/
Type
Binary
A
D

IGS

ILRS

IDS

X

X

X

A

D

A

D

X

A

D

X

X

A

X

A

P

A

P

A

IVS

X

X

X

X

X (F)

X

satellite position accuracy indicators.
ftp://igscb.jpl.nasa.gov/pub/data/format/sp1.pdf
ftp://igscb.jpl.nasa.gov/pub/data/format/sp3c.txt
IONEX
Ionosphere Exchange format. A common data format to exchange, compare, or combine TEC
maps. Supports the exchange of 2- and 3-dimensional TEC maps given in a geographic grid.
ftp://igscb.jpl.nasa.gov/pub/data/format/ionex1.pdf
Site log
Information organized by section describing sites used by analysts in reducing data. Information
includes site IDs, location, coordinates/eccentricities, surveys, co-location, instrument
information, site ownership, etc.
ftp://igscb.jpl.nasa.gov/pub/station/general/blank.log
ftp://cddis.gsfc.nasa.gov/reports/slrlog/slr_blank.txt
ftp://ivscc.gsfc.nasa.gov/pub/config/ns-config.txt
ANTEX
Contain information for GNSS satellite and receiver antennas, including phase center offsets.
ftp://igscb.jpl.nasa.gov/pub/station/general/antex13.txt
Tropo SINEX
Format based on SINEX for the series of total zenith path delay transformed to precipitable water
vapor.
ftp://igscb.jpl.nasa.gov/pub/data/format/sinex_tropo.txt
ERP
ftp://igscb.jpl.nasa.gov/pub/data/format/erp.txt
GSFC DB
Goddard VLBI database format. The VLBI database is a binary format for archiving and handlinggeodetic/astrometric observables delay and delay rate generated by fringe-fitting algorithms fromraw correlator output. Developed for the CALC/SOLVE data analysis system, the files also
contain other generated outputs such as correlation coefficients, fringe amplitudes and total
phases; cable calibration and station weather information; theoretical observables and parameterpartial derivatives (from CALC); and editing and ambiguities (from SOLVE).
http://gemini.gsfc.nasa.gov/solve/
NGS Card
NGS format for VLBI data transfer. Partial ASCII transcription of a Goddard database file. This
format is being used by VLBI analysis packages such as Modest, Occam, and SteelBreeze.
http://lacerta.gsfc.nasa.gov/mk5/help/dbngs_format.txt
Baseline length Time series of baseline lengths consisting of downloadable baseline length results, including
graphs and statistics, for a chosen baseline. An automatic script computes the information onlinefrom the submissions of six participating Analysis Centers as well as a combined solution. The
data, residual, and plot files for all seven time series can be downloaded for further analysis.
http://vlbi.geod.uni-bonn.de/baseline-project/
DORIS data
Standard exchange format for range-rate observations; DORIS-specific.
ftp://ftp.cls.fr/pub/ids/data/doris21.fmt
STCD
Station Coordinate Difference format for time series of coordinates expressed at a reference epoch.
Provides coordinate time-series results in both Cartesian and ellipsoidal coordinates. Coordinate
time-series consist of residuals relative to a reference position. Each coordinate of the series isassumed to be expressed in the same reference system as at the observation epoch.
http://ids.cls.fr/documents/report/CB_STCD_format_v1.0.pdf
A=ASCII
B=Binary
D=DataP=Product
O=Other
F=Future

1

A

P

X

A

O

X

1.3

A

O

X

0.01

A

P

X

2
8.8.89

A
B

P
D

X

A

D

X

A

P

X

2.1

A

D

X

1.0

A

D

X

X

X

X

X

Table 5

IAG Geometric Services Comparison Chart– Data –Item
Data Storage at
Primary (Global) Data Centers
Regional Data Centers
Data Availability
Data File Organization

Format of Data Files

IGS
Global, Regional, and Local Data
Centers
CDDIS (USA), SIO (USA), IGN(France), KASI (Korea)
BKG (Germany), GA (Australia),
NRCan (Canada), NGS (USA),
JPL (USA)
1990 to today
Sub-hourly, hourly, and daily
files per station (grouped by year
and day-of-year)
RINEX (obs, nav, met)

ILRS
Global, Regional, andOperational Data Centers

IVS

IDS

Data Centers

Data Centers

CDDIS (USA), EDC (Germany)

CDDIS (USA), BKG (Germany),
OPAR (France)

CDDIS (USA), IGN (France)

Shanghai (China)

CNR (Italy), GeoDAF (Italy),
NICT (Japan)–

1979 to today

1990 to today

Session-wise (grouped by year
and session)

10-day “cycle” files per satellite

Goddard data base format(binary), NGS card format(ASCII)DORIS format

Observing schedules, session
logs, met data, notes

Satellite information

Z compressed format–
FTP

Z compressed format–
FTP

1976 to today
Hourly, daily, and monthly files
per satellite and station (groupedby year and satellite)
NP Format (quick-look), Full-rate
Formatofficial abbrev. for rcvr, ant,
radomes (rcvr_ant.tab); ant. phase Satellite orbit prediction files (byAuxiliary Data Files
email or ftp)
center (igs_01.pcv); reference pt
info (antenna.gra)Standard compression software
Z compressed format
Z compressed format
Special compression software
Hatanaka–
Data Transfer Mechanism
FTP
FTP– non-existent; n/a not applicableTable 6

IAG Geometric Services Comparison Chart– Products –ItemAnalysis Centers (AC)SoftwareCombined Solution

Products Overview
Product Types:
Satellite Orbit Prediction

IGS

ILRS

IVS

IDS

about 10 ACs, additional
AACs

8 ACs, additional AACs

about 20 ACs

6 ACs, additional AACs

Geodyn, Solve, UTOPIA,
DOGS, EPOS, SATAN,
GINS/MATLO

Calc/Solve, Modest,
Occam, Gloria,
SteelBreeze, Geosat

Gipsy/OASIS, Geodyn,
Zoom, GINS, Bernese

VariousAnalysis Coordinator(primary and backup)

Analysis Coordinator

Analysis Coordinator

Combination Centers

Gipsy/OASIS, Bernese,
GAMIT, EPOS, PAGE,
NAPEOS
Analysis Center
Coordinator, & ProductCenters (RF, Time)http://igscb.jpl.nasa.gov/co
mponents/prods.html

IERS
product centers (TRF,
EOP, rapid
service/prediction),convention center

http://ilrs.gsfc.nasa.gov/pro
http://ids.cls.fr/html/analysi
http://ivscc.gsfc.nasa.gov/p
http://www.iers.org/MainD
ducts_formats_procedures/s_coord/documents/struct_roducts-data/products.html
isp.csl?pid=8-10
products.html
dc.html–satellite ephemerides for
GPS (4 types) and
GLONASS (2 types)
GPS clock information

daily

n/a

–

n/a

{satellite ephemerides}

n/a

n/a

n/a

EOP

Polar motion, Polar motion
rates, length-of-day

EOP, length-of-day

TRF

IGS tracking station
coordinates and velocities

TRF solution (station
positions and velocities)

CRF

n/a

n/a

Troposphere

Zenith tropospheric pathdelay estimates–

Ionosphere

Global ionospheric maps–

Satellite Orbit Determination
Satellite Clocks

Station positions, polar
motion, polar motion rates,
Contributions to IERS
length-of-day (weekly
combined solutions)– non-existent; n/a not applicable; { } plannedn/aStation positions, polar
motion, length-of-day(weekly combined
solutions)n/an/asession-wise EOP solution(EOP-S)
Polar motion, length-of-day
1-hour Intensive EOP
solution (EOP-I)
Weekly and monthly timeseries of DORIS station
TRF solution (station
positions, cumulative
positions, velocities,
solutionscorrelations) roughly every (positions/velocities), time
3 months
series of coordinates of the
TRF origin, station
coordinate difference plots
CRF solution at irregularn/atime schedule
troposphere parameters per–session and station
derived vertical total–
electron content (VTEC)
Station positions, polar
EOP & position (DSNX)
motion, length-of-day(combined solutions by(weekly combined
session)solutions)n/aLong term, rapid service,
and predictions for EOP

ITRF

ICRF
–
–

n/a

Table 7

IAG Geometric Services Comparison Chart– Service Information –Item
Service Inauguration
Organization (Chart)
Terms of Reference

Publications
Meetings

Working Groups

Pilot Projects
Mailing Lists
FTP Archives

IGS
ILRS
IVS
IDS
IERS
1994
1998
1999
2003
1988
http://igscb.jpl.nasa.gov/orga http://ilrs.gsfc.nasa.gov/about http://ivscc.gsfc.nasa.gov/abo http://ids.cls.fr/html/organiza http://www.iers.org/MainDis
nization/figure1.html_ilrs/organiza.html
ut/org/index.html
tion/schema.html
p.csl?pid=15-33
http://ivscc.gsfc.nasa.gov/abo
http://ids.cls.fr/html/organiza http://www.iers.org/MainDis
http://igscb.jpl.nasa.gov/orga http://ilrs.gsfc.nasa.gov/about
ut/org/documents/ivsTOR.ht
tion/tor.html
p.csl?pid=14-36
nization/bylaws.html_ilrs/termsref.html
mlAnnual Reports, Technical
Annual Reports,
Annual Reports, Newsletters,
Annual Reports, Workshop
Annual Reports, Bulletins,
Reports, Workshop
Performance Report Cards,
General Meeting
Proceedings
Technical Notes
Proceedings
Special Reports
Proceedings
General Assembly, Technical General Meeting, Technical
WorkshopWorkshopWorkshopWorkshopMeeting, Workshop
GPS Phase Center Mapping,
Site Survey and CoReference Frame, Clock
Analysis, Data Formats and
IVS Product Specification
Location, Combination,
Products, Troposphere,
Procedures, Missions,
Analysis, Site Selection
and Observing Programs,
Prediction, Second
Ionosphere, GNSS, LEO,
Networks and Engineering,
VLBI2010, Second
Realization of the ICRF
Real-Time, Data CenterTransponder
Realization of the ICRF
Tide Gauge Benchmark
Tropospheric parameters–––
Monitoring, GLONASS(closed), Baseline products(closed)http://igscb.jpl.nasa.gov/mail http://ilrs.gsfc.nasa.gov/conta http://ivscc.gsfc.nasa.gov/ma http://ids.cls.fr/html/report/ http://www.iers.org/MainDis/mailindex.html
ct_ilrs/mail_services/
ilman/listinfo
doris_mails.html
p.csl ?pid=45-25788
http://ids.cls.fr/html/data_cen http://www.iers.org/MainDis
ftp://igscb.jpl.nasa.gov/igscb
At data centers
ftp://ivscc.gsfc.nasa.gov/pub/ters.html
p.csl ?pid=34-8– non-existent; n/a not applicableTable 8

IAG Geometric Services Comparison Chart– Site Information –Item
Network Map
Network List
Form of Site Log
Example Site Log (Greenbelt)
Site Identification
Approx. Station Coordinates
Tectonic Plate
Geologic Information
Monument/Marker Description
Local Surveys
Local Ties, Collocation

IGS
ILRS
IVS
IDS
http://igscb.jpl.nasa.gov/network/ http://ilrs.gsfc.nasa.gov/stations/i http://ivscc.gsfc.nasa.gov/stations http://ids.cls.fr/html/doris/sitelog.
maps/allmaps.html
ndex.html/ns-map.html
html
http://igscb.jpl.nasa.gov/network/ http://ilrs.gsfc.nasa.gov/stations/si ftp://ivscc.gsfc.nasa.gov/about/or http://ids.cls.fr/html/doris/sitelog.
list.html
telist/index.html
g/components/ns-list.html
html
HTML document or
ASCII file
ASCII file
ASCII file
ASCII file
http://igscb.jpl.nasa.gov/igscb/stat ftp://cddis.gsfc.nasa.gov/pub/repo http://ivscc.gsfc.nasa.gov/pub/con http://ids.cls.fr/html/doris/stations
ion/log/gode_20030911.log
rts/slrlog
fig/ns/ggao.config.txt/GREB.shtml[Sec 1] site name, 4-character ID, [Sec 1&3] site name, DOMES,[Sec 1] site name, 8-letter code,[Sec 1] site name, DOMES, 4DOMES, CDP number
CDP number, 4-char code
DOMES, CDP number
char code[Sec 2][Sec 2][Sec 2.1][Sec 1&3&4][Sec 2][Sec 2][Sec 2.1][Sec 1][Sec 1][Sec 1]–[Sec 1][Sec 1][Sec 1]–[Sec 2]––[Sec 2.2]–[Sec 13] local vectors between[Sec 5&6&7] local vectors
co-located techniques,
between co-located[Sec 5&7] local vectors between[Sec 10] list of techniques, novectors between collocated SLR
collocated techniques
local difference vectors
techniques,vectors between
systems
collocated DORIS system[Sec 3&4] incl. history of antenna[Sec 4&5&6][Sec 3&4][Sec 2&3]
and receiver changes

Instrument Information (antenna,
receiver, laser)
Local Events (possibly affecting–
position)
Time/Frequency Standards[Sec 6]
Meteorological Instrumentation[Sec 8]Field System Computer–
Aircraft Detection
n/aLocal Contact Information[Sec 11][Sec ?] Section in site log file; – non-existent; n/a not applicable[Sec 14]––[Sec 9][Sec 12]–[Sec 11][Sec 15][Sec 8][Sec 7][Sec 11]n/a[Sec 13]–[Sec 8]–n/a[Sec 9]

Table 10

IERS

GPB (GPB = GeoPortal.Bund)

metaData
metadataFileIdentifier

yes

MD_Metadata Metadata (1)fileIdentifier (2)metadataLanguageyeslanguage (3)metadataCharacterSet

yescharacterSet (4)-?

parentIdentifier (5)-yeshierarchyLevel (6)

-

yes

C
M
O
C Condition
R
O*
E
…
O
not defined byC
encoding?

(6) is not equal to"dataset"(6) is not equal toC"dataset" (default)(6) is not equal toC"dataset"C

CI_ResponsibleParty RespParty (374)(M)

individualName

yes

individualName (375)C

organisationName

yesorganisationName (376)C

positionName

nopositionName (377)C

metadataContact

contact (8)contactInfo
phone

contactInfo (378)

voice

yes

facsimilenoaddress

CI_Contact Contact (387)
CI_Telephone Telephone (407)phone (388)address (389)O

facsimile (409)O

CI_Address Address (380)deliveryPointnodeliveryPoint (381)

O

city

no

O

administrativeArea

nopostalCodecountrynonoelectronicMailAddressyescity (382)administrativeArea(383)
postalCode (384)country (385)electronicMailAddress(386)
CI_OnlineResource OnlineRes (396)…

linkage (397)M-

onlineResource (390)onlineAddress

no

role

yes

role (379)

ISO 19115 B.5.10 Metadata character set

file identifier of the metadata to which
this metadata is a subset (child)

mdParentID

Free text

scope to which the metadata applies

mdHrLv

ISO 19115 B.5.25 Metadata hierarchy level

name of hierarchy levels for which themetadata is applied

mdHrLvName

Free text

Metadata hierarchy level name

Free text

Metadata contact individual name

Free text

Metadata contact organisation name

Free text

Metadata contact position name

Free text

Metadata contact phone voice

Free text

Metadata contact phone facsimile

see ISO11180
Annex AFree text

Metadata contact address city

[ mdContact ]name of responsible person for therpIndName
metadata (surname, given name, title)
name of responsible organization for the
rpOrgName
metadatarole or position of the person responsible
rpPosNamefor the metadata[ rpCntInfo ][ cntPhone ]telephone number of organisation or
voiceNum
individual responsible for the metadatafacsimile number of organisation or
faxNumindividual responsible for the metadata[ cntAddress ]address line for the location of organis.
delPoint
or individ. responsible for the metadata
city of the location of organis. or …
city

Metadata parent identifier

Metadata contact address delivery point

eMail address of organis. or individ. …

eMailAdd

Free text

Metadata contact address electronic maillinkage

URL

Metadata contact address online resource

yes

metadataStandardVersion (11)O

referenceSystemInfo
referenceIdentifier
identificationInfo
citationyes

referenceSystemInfo (13) MD_ReferenceSystem RefSystem (186)referenceSystemIdentifier (187) RS_Identifier RsIdent (208)code (207)
MD_Identification Ident (23)
identificationInfo (15)
CI_Citation Citation (359)citation (24)

…
…
O
…
…

resourceTitle

yestitle (360)-yesalternateTitle (361)individualName

mdCharO

metadataStandardVersion

status (28)pointOfContact (29)Metadata language

Metadata contact address administrative areaO

yes

ISO 639-2

Metadata contact address postal code
Metadata contact address countryM

pointOfContact

mdLangFree text

dateStamp (9)abstract (25)Metadata file identifier

Free text
ISO 3166-3

metadataStandardName (10)yesFree text

postCodecountry

yes

abstract

mdFileID

state, province of the location of org. … adminArea

yes

yes
yes

unique identifier for this metadata filelanguage used for documenting
metadata

ZIP or other postal code of the loc. …
country of the pyhsical address of …

metadataStandardName[ cntOnlineRes ]

O
(M)
M
M
M
O

CI_ResponsibleParty RespParty (374)

(O)

yes

individualName (375)C

organisationName

yesorganisationName (376)C

positionName

nopositionName (377)C

URL for on-line information about theorganisation or individual responsible…
function performed by the party
responsible for the metadata
date that the metadata was createdname of the metadata standard(including profile name) usedversion (profile) of the metadata
standard usedrole

ISO 19115 B.5.5 Metadata contact role

mdDateSt

ISO19115 B.4.2

Metadata date stamp

mdStanName

Free text

Metadata standard namemdStanVer

Free text

Metadata standard version

name of reference system used

[ refSysInfo ][ refSysId ]identCode[ dataIdInfo ][ idCitation ]Free text

Dataset reference system nameresTitle

Free text

Dataset citation title

resAltTitle

Free text

Dataset citation alternate title

resRefDate
refDaterefDateType

ISO19115 B.4.2 Dataset citation dateISO 19115 B.5.2 Dataset citation date typename by which the cited resource is
known
short name or other language name bywhich the cited information is known

M

CI_Date DateRef (393)date (394)dateType (395)

GGOS NameO

M

date (362)DomainOO

metadataDateStamp

auf der Ebene
identificationinfo
eingeordnet! (mehrfach!)(376) and (377) notdocumented(375) and (377) notdocumented(375) and (376) notdocumented…

voice (408)

Short name

ISO/IEC 10646-1 not
full name of the character coding
used and not defined
standard used for the metadata set
by encoding?

ChierarchyLevelName (7)Meaning(376) and (377) notdocumented(375) and (377) notdocumented(375) and (376) notdocumented

reference date for the cited resource
event used for reference datebrief narrative summary of the content of
idAbs
the resource(s)status of the resource(s)idStatus[ idPoC ]name of person responsible for the data
rpIndName(surname, given name, title)
name of organisation responsible for the
rpOrgNamedatarole or position of the person responsible
rpPosNamefor the data

Free text

Dataset abstract

ISO 19115 B.5.23 Dataset status
Free text

Dataset contact individual name

Free text

Dataset contact organisation name

Free text

Dataset contact position name

contactInfo

contactInfo (378)phone

CI_Contact Contact (387)
CI_Telephone
phone (388)Telephone (407)[ rpCntInfo ][ cntPhone ]

voice

yes

voice (408)O

facsimileyesfacsimile (409)
CI_Address Address
(380)

O

address (389)addressdeliveryPoint

Dataset contact address city

Free text

Dataset contact address administrative areaOO

ZIP or other postal code of the loc. …
country of the pyhsical address of …

postCodecountry

Free text
ISO 3166-3

Dataset contact address postal code
Dataset contact address countryO

eMail address of organisation or …

eMailAdd

Free text

Dataset contact address electronic mail

URL

Dataset contact address online resource

city

yes

city (382)O

administrativeArea

noadministrativeArea (383) O

postalCodecountryyes
yeselectronicMailAddress

yes

yes

role

yes

descriptiveKeywords- kein Unterelement

descriptiveKeywords (33)yesspatialRepresentationTypeyesspatialResolution? Leeres Element:
spationResolution!

linkage (397)

M

MD_Keywords Keywords (52)…

MD_DataIdentification DataIdent (36)…
O

MD_Resolution Resol (59)
MD_RepresentativeFraction RepFract (56)equivalentScale (60)(O)

denominator (57)C

dataLanguagenoyeslanguage (39)

dataCharacterSet

yescharacterSet (40)C

topicCategory
dataExtent

yes

topicCategory (41)extent (45)M

description

nogeographicElement
geographicBoundingBox

distance (61)CM

method used to spatially represent
geographic information
either (69) resp. (57)
the number below the line in a vulgaror (61) must be
fraction
documented
ground sample distancelanguage(s) used within the dataset
ISO/IEC 10646-1 not full name of the character codingused?
standard used for the dataset
C (6) equals "dataset" main theme(s) of the dataset

EX_Extent Extent (334)description (335)
geographicElement (336)C

yeswestBoundLongitude
(344)

C

eastBoundLongitude

yeseastBoundLongitude
(345)

C

southBoundLatitude

yessouthBoundLatitude
(346)

C

northBoundLatitude

yes-northBoundLatitude(347)
EX_GeographicDescription GeoDesc (348)
MD_Identifier MdIdent
geographicIdentifier
(349)
(205)
code (207)
EX_TemporalExtent TempExtent (350)C

geographicIdentifier
temporalElement

yes

beginDateTime

yes

extent (351)

endDateTime
verticalElement

yes

extent (351)
TM_Primitive.end (B4.5)
EX_VerticalExtent VertExtent (354)O

minimumValuenominimumValue (355)O

maximumValuenomaximumValue (356)O

temporalElement (337)verticalElement (338)(336), (337) + (338)
not documented

spatial and temporal extent for thereferring object

EX_GeographicExtent GeoExtent (339)
EX_GeographicBoundingBox GeoBndBox (343)westBoundLongitudeC

TM_Primitive.begin (B4.5) O

unitOfMeasurenounitOfMeasure (357)

O

-

no

verticalDatum (358)

O

city

URL for on-line information about thelinkageorganisation or individual responsible…
function performed by the partyrole
responsible for the data
[ descKeys ]commonly used word(s) or formalisedword(s) or phrase(s) used to describe
keywordthe subset

M

spatialRepresentationType (37)delPoint

Dataset contact address delivery point[ cntOnlineRes ]M

role (379)yesaddress line for the location of organis.
or individ. responsible for the data
city of the location of organis. or …

…

keyword (53)spatialResolution (38)

Dataset contact phone voice
Dataset contact phone facsimilestate, province of the location of org. … adminArea

O

onlineAddress

Free text
Free text

see ISO11180
Annex AFree text

deliveryPoint (381)-

voiceNum
faxNum[ cntAddress ]yespostalCode (384)country (385)electronicMailAddress(386)
CI_OnlineResource
onlineResource (390)
OnlineRes (396)

telephone number of organisation orindividual responsible for the data
facsimile number of organisation or …

spatRpType

ISO 19115 B.5.5 Dataset contact role

Free text

Dataset keywords

ISO 19115 B.5.26 Dataset spatial representation type[ dateScale ][ equScale ]rfDenom

Integer > 0

Dataset spatial resolution denominatorscaleDist
dataLang

ISO 19115 B.4.3 Dataset spatial resolution distanceISO 639-2
Dataset language

dataChar

ISO19115 B.5.10 Dataset character set

tpCat[ dataExt ]ISO19115 B.5.27 Dataset topic category

exDescFree text

Dataset extent description

Angle B.4.3[-180, 180]

Dataset extent geographic bb westBL

Angle B.4.3[-180, 180]

Dataset extent geographic bb eastBL

Angle B.4.3[-90, 90]

Dataset extent geographic bb southBL

Angle B.4.3[-90, 90]

Dataset extent geographic bb northBL

Free text

Dataset extent geographic description ident.

[ geoEle ]western most coord. of the limit of thedataset extent, expressed in longitude in westBL
decimal degrees (positive east)
eastern most coord- of the limit of theeastBLdataset extent, expressed in …
if (6) equals "dataset"southern most coord. of the limit of theeither (343) or (348)dataset extent, expressed in longitude in southBLis required
decimal degrees (positive north)
northern most coord. of the limit of thenorthBLdataset extent, expressed in …

identifier to repres. a geographic area
date and time for the content of thedataset (begin)date and time for ... dataset (end)code[ tempEle ]begin

ISO 19108

Dataset extent temporal begin

end[ vertEle ]ISO 19108

Dataset extent temporal end

lowest vertical extent contained in thedatasetvertMinVal

Real

Dataset extent vertical minimum value

highest … contained in the dataset

vertMaxVal

Real

Dataset extent vertical maximum value

vertical units used for vertical extent
vertUoM
information
provides information about the origin
from which the maximum and minimum vertDatum
elevation values are measured

ISO 19115
Dataset extent vertical unit of measure
UomLength B.4.3
ISO 19115
SC_Vert.Datum Dataset extent vertical datum
B.4.9

distributionInfo
distributionFormat
formatName
formatVersion-

distributionInfo (17)
yes
yes

-

yes

-

yes

MD_Distribution Distrib (270)
MD_Format Format (284)distributionFormat (271)name (285)version (286)
MD_Distributor Distributor (279)
distributor (272)
CI_ResponsibleParty RespParty (374)
distributorContact (280)organisationName
(376)

yes

onLineSourceyes…

linkage (397)O

yesdataQualityInfo (18)

DQ_DataQuality DataQual (78)
DQ_Scope DQScope (138)
scope (79)yes-report (80)yeslineageStatement

location (address) for on-line accessusing a URL

lineage (81)

useConstraints

yes

useConstraints (71)hierarchy level of the data specified by
the scope…
…

resFees

Free text

Dataset fees

medNameISO 19115 B.5.20 Dataset off-line resource namelinkage

IETF RFC
1738/2056

Dataset on-line resource namescpLvlISO 19115 B.5.25 Dataset scope level[ dqReport ][ measResult ]LI_Lineage Lineage (82)…

statement (83)O C

metadataConstraints (20) MD_LegalConstraints LegConsts (69)

legalConstraints

ISO 19115 B.5.5 Dataset distributor role

[ dqInfo ][ dqScope ]value (137)yes

Dataset distributor organisation name[ distTranOps ][ onLineSrc ]valueUnit (135)yesname of the medium on which theresource can be received

M

DQ_Element DQElement (99)
DQ_QuantitativeResult QuanResult (133)result (107)Free text[ offLineMed ]…
…

level (139)

Dataset distribution format name
Dataset distribution format verson[ distorTran ]C-fees and terms for retreiving theresourceO

MD_DigitalTransferOptions DigTranOps (274)
CI_OnlineResource OnlineRes (396)
onLine (277)Free text
Free text[ distorOrdPrc ]O

name (292)transferOptions (273)dataQualityInfo-…

distributorTransferOptions
MD_DigitalTransferOptions DigTranOps (274) …
(283)
MD_Medium Medium
offLine (278)
…
(291)

-

[ distInfo ][ distFormat ]formatName
formatVer[ distributor ][ distorCont ]name of the organisation responsible forrpOrgName
distributionfunction performed by the partyrole
responsible for distributionO

MD_StandardOrderProcess StanOrdProc(298)
fees (299)-

offLineMedium (unterhalb
von transferOptions!)transferOptions-

name of the data transfer format(s)version of the formatOrole (379)
distributionOrderProcess
(281)

-

…
…
O
O
…
…

either (135) and(137) or (83)quantitative value(s)quanValUnit

value unit for reporting a data quality
resultquanValgeneral explan. of the data producer's
knowl. about the lineage of a dataset

statement

ISO 19115
Record B.4.3
UnitOfMeasure
B.4.3

Dataset completeness value
Dataset completeness value unit

[ dataLineage ]…

if scope equals"dataset" or "series"

Free text

Dataset lineage statement[ mdConst ]O

constraints applied to assure theprotection of privacy or intellectual
property, and any special restrictions or useConsts
limitations or warnings on using theresource or metadata

ISO 19115 B.5.24 Metadata use constraints

DIF

Table 11table 11 Metadata XMAP(1), 10.12.2007

ISO 11915 Core metadata components
ISO 11915 Other (comprehensive) metadata components
GCMD DIF Required Fields (Req.)
GCMD DIF Recommended Fields (Rec.)
GCMD DIF Optional Fields (O)FGDC Content Standard for Digital Geospatial Metadata
OBIS metadata

Description

ISO 19115 Metadata for
geographic datasets

obligation UML hierarchy

Database nameName or title (may include
acronyms)

360 Dataset title

(M)

(O)

Version - would recommend be 363 Dataset edition
part of a citation group

Citation

Entry_Title (this field may be
duplicated under
Data_Set_Citation >Data_Set_Title)(Req.)

8,4

Title

(M)

The name by which thedata set is known.

Include(MD_Metadata >MD_DataIdentification.citati
on > CI_Citation.edition)(MD_Metadata >MD_DataIdentification.citati
on > CI_Citation.date)"Version of the citedresource"

Data_Set_Citation > Version(Rec.)"Title of DIF";
descriptive enough sothat a user candetermine the generalcontent of the data set"Version is the versionof the data set"

8,5

Edition(MIA)

The version of the title.

Include within
citation"Reference date for the cited Data_Set_Citation >resource"
Data_Set_Release_Date(Rec.)"The date when thedata set was madeavailable for release"

8,2

Publication Date (M)"The production status 1.4.1of the data set
regarding its
completeness"; Options:
Planned, In Work, orComplete"Restrictions, limitations 1,7
and legal prerequisites
for accessing the data
set" - free-text field(MD_Metadata >MD_Identification.Status )"Status of the resource(s)"Data_Set_Progress

(O)

70

Access constraints fordataset(O)(MD_Metadata >"Access constraints applied
MD_Constraints.accessCons to assure the protection oftraints )privacy or intellectual
property, and any special
restrictions or limitations on
obtaining the resource ormetadata" ISO list:
copyright, patent,
patentPending, trademark,license,intellectualPropertyRights,
restricted, otherRestrictions

Access_Constraints(Rec.)

Dataset Citation(M) - Only
Dataset Title
and Dataset
Reference
Date as partof thecitation aremandatory(MD_Metadata >Citation data for the
MD_Identification.Citation ) - resource(s)Citation (359):
MD_Metadata >MD_Identification.Citation> CI_Citation.title
MD_Metadata >MD_Identification.Citation> CI_Citation.date"Data_Set_Citation" Group:
Dataset_Creator:
Dataset_Title:
Dataset_Series _Name
Dataset_Release_Date:
Dataset_Release_Place:
Dataset_Publisher: Version:
Issue_Identification:
Data_Presentation_Form:
Other_Citation_Details:
Online_Resource:
Science Keywords
Auxillary Keywords"A citation for the data 8(Rec.)
Entry_Title (// set to properly credit
Dataset_Title) the data set producer.
is a required
This fields indicates how
DIF field
the data set should becited in the professional
scientific literature."

the dataset (by four
coordinates or bygeographic identifier)

Yes(MD_Metadata >"Name by which the cited
MD_DataIdentification.citati resource is known"
on > CI_Citation.title)(O)east Atlantic)

The geographic name of Include
a location covered by adata set.

Proposed
OBIS usage

Status of dataset

Geographic scope Common place name (e.g. North- 343 Geographic location of Mandatory

Use
IOBIS
Taxonomi
c ListDescription

28

No Match

Yes

FGDC Content
Obligation
Standard for Digital
Geospatial Metadata

Status (e.g. Final version or Data
continus to be added)

taxonomic hierarchy, add others
where appropriate.

IncludeDescription

362 Dataset reference date (M)Taxonomic scope Include names in informal OBIS

Other
Comment

obligation

Date released - would
recommend be part of acitation group

Follow bibliographic standards,
24
e.g. Author, year, title, publisher,place of publication, whereappropriate. This will duplicate
some other fields. Name or title,
Date Released, Version will be
duplicated

Query
From
from
DiGIR
IOBIS
Entry
database

GCMD DIF metadata

Description(MD_Metadata >"Geographic position of the Location
under certain MD_DataIdentification.exte dataset; (Note: This is only
an approximate reference soconditions - nt > EX_Extent >specifying the coordinate(C)
EX_GeographicExtent >EX_GeographicBoundingBox reference system isorunnecessary)"
EX_GeographicDescription)

Progress(M)

AccessConstraints

(M)

(MIA)
“Citation”
compound item:
8.1 Originator:
8.2 Publication
Date: 8.4 Title:
8.7.1 Series Name:
8.8.2 Publisher:
8.8.1 Publication
Place(Req.)(O)"Science keywords
allows the specificationof keywords that are
representative of thedata set being
described" - controlled
vocabulary used fordata discovery"Auxillary Keywords any words or phrases
used to further
describe data sets."(Rec.)"names of places which 1.6.2. Place Keyword
may be used for2
searching" - controlled
vocabulary

Page 1 of 3

(MIA)

The date when the data Include within
set is published or
citationotherwise made available
for release.
The state of the data set. Omit (onlyDomain: "Complete" "In posting online
work" "Planned".
data0

Restrictions and legal
Omit (onlyprerequisites forposting publicaccessing the data set.
data)
These include any accessconstraints applied toassure the protection ofprivacy or intellectual
property, and any special
restrictions or limitations
on obtaining the data
set. Domain “None”, freetext.
The recommended reference Include
to be used for the data set.

Latitude-longitude box (Min Lat,
Min Long, Max Lat, Max Long)344- see above (+347 westBoundLongitude,
eastBoundLongitude,
southBoundLatitude,
northBoundLatitude)

Geographical resolution (seeguidelines)

38

Spatial Resolution(O)

Number of locations

No Match
350- Additional extent
351 information for the(O)

Date of first record
Temporalcoverage
Date of last record
Habitat coverage Major environment such as

53

marine, brackish, freshwater,
coast-land (seal haulouts, bird
nesting).
Depth zone (e.g. littoral,
sublittoral, coastal, continental
slope, deep-sea, abyssal)
Seascape features (e.g. estuary,
seamounts, bay, lagoon, canyon)
Species habitats (sediment, rocky,
front,
Community association (e.g. coral
reef, kelp forest, sea grass bed,
oyster bed)
Total distribution Insert number

No Exact Match
Dataset keywords"Spatial_Coverage" group:
Southernmost_Latitude:
Northernmost_Latitude:
Westernmost_Longitude:
Easternmost_Longitude:
Minimum_Altitude:
Maximum_Altitude:
Minimum_Depth:
Maximum_Depth:(Rec.)(MD_Metadata >"Factor which provides a"Data_Resolution" group:(Rec.)
MD_DataIdentification.spati general understanding of the Latitude_Resolution:
alResolution)
density of spatial data in the Longitude_Resolution:
dataset"Horizontal_Resolution_Range:
Vertical_Resolution:
Vertical_Resolution_Range:
Temporal_Resolution:
Temporal_Resolution_Range:(MD_Metadata >MD_DataIdentification.exte(MD_Metadata >(O) - the
MD_Keywords.keyword);
free-text
also seecharacter
MD_KeywordTypeCodestring"keyword" CodeList (B.5.17)
is the only
mandatory
field in the"MD_Keyw
ord"
optional
field"Time period covered by thecontent of the dataset" or"Commonly used word(s) orformalised word(s) orphrase(s) used to describe
the subject - free-text

No Match"Temporal_Coverage" group: (Rec.)
Start_Date: [yyyy-mm-dd](Req.)
Science Keywords(O)
Auxillary Keywords(user can choose from acontrolled vocabulary list
or enter habitat-related
keyword(s) as "free-text")"Geographic coverage(horizontal/vertical) of
the data described)"

1.5"The difference
4
between two adjacentgeographic, vertical, or
time values." Keyword
list can be viewed at
http://gcmd.nasa.gov/Resources/valids/keywor
d_list.html“Temporal Coverage” in 1.3
DIF – start and stop
Some “science
keywords” pertaining tohabitat classification:
Benthic Habitat; Coastal
Habitat; Demersal
Habitat; Estuarine
Habitat; Pelagic
Habitat; Reef Habitat;
Rivers/Stream Habitat;
Lakes; Saline Lakes.
Keyword list can beviewed at
http://gcmd.nasa.gov/Resources/valids/keywor

Spatial Domaon: (M)1.5.1 Bounding
Coordinate:s1.5.1.1 WestBounding
Coordinate:
1.5.1.2 East
Bounding
Coordinate:
1.5.1.3 North
Bounding
Coordinate:1.5.1.4 SouthSpatial(M)
Reference
Information: 4.1
Horizontal
Coordinate
SystemDefinition: 4.1.1
Geographic:
4.1.1.1 Latitude
Resolution:
4.1.1.2
Longitude
Resolution:

the geographic areal domain Include
table 11 Metadata XMAP(1), 10.12.2007of the data set.

Time Period ofContent: 9.3.1

Time period of thecontent
Same as GCMD

(M)

The description of thereference frame for, andthe means to encode,
coordinates in the data
setIncludeIncludeIncludeIncludeInclude

Yes
Yes
Yes
Need toreview
avaiable
keywords

IncludeIncludeIncludeIncludeNo Match

IncludeYes

IncludeYes

records provided
to OBIS

Total number of Insert number
taxaCollection method Sampling method (e.g. trawl,

No Match

No Match

No Matchgrab, visual observation, video)

Data sourcee.g. field observation, specimen incollection, image.

Abstract

Short description of dataset forpotential users. Mention any
quality control issues.

Publications from Provide citation (e.g. author,
year, title, journal, volume,
this data

pages). Typically paper, but canbe CD or diskette publications.

Instrument (i.e sensor)
Sensor_Name: [SHORTNAME] > [Long Name](Rec.)

Platform (i.e Source)
Source_Name: [SHORTNAME] > [Long Name](Rec.)(MD_Metadata >"Brief narrative summary of
MD_DataIdentification.abstr the content of theact)
resource(s)Summary(Req.)

some ISO profiles uses
MD_PortrayalCatalogue
Reference (B.2.9)

Reference(O)

see MD_KeywordTypeCode
CodeList (B.5.17)<KeyTypCdvalue="instrument"/>

No Match

25

Abstract describing the (M)dataset359 Citation (359)(O)

Page 2 of 3

"Instrument or
1.2.3
hardware used toacquire the data."
Keyword list can beviewed at
http://gcmd.nasa.gov/Resources/valids/keywor
1.2.3"The platform of datacollection, as in aspacecraft, ship or
ground station housing
the sensor(s) used toacquire the data; or as
in a map from which thedata were digitized; oras in a model fromwhich the data weregenerated.""A brief description of 1.2.1
the data set, descriptive
enough to allow
potential users of thedata set to determine if
the data set is useful for
their needs.""key bibliographic
references pertaining to
the data set"

Supplementary
Information(O)other descriptive
Includeinformation about the data
set.

Supplementary
Information(O)other descriptive
Includeinformation about the data
set.

Abstract(M)a brief narrative
Includesummary of the data set.

IncludeScientific Contact Scientist responsible for thequality and content of the data
(e.g. Principal Investigator).

Technical contact OBIS contact to ensure

374 Dataset responsible
party

(O)

(MD_Metadata >"Identification of, and means Data_Center_Name:(Rec.)
MD_DataIdentification.point of communication with,[SHORT NAME] > [Long
OfContact >person(s) and organizations Name] Data_Center_URL:
CI_ResponsibleParty)
associated with the dataset" Data_Set_ID:
ISO list: resourceProvider,"Personnel" Group:
custodian, owner, user,
Role:
First_Name:
distributor, originator,
Middle_Name:pointOf Contact,
Last_Name:
principalInvestigator,
Email:
processor, publisher, author Phone:
FAX"Contact_Address" Group:
Address:
City:
Province_Or_State:
Postal_Code:Country:

1.9
INVESTIGATOR –person who headed theinvestigation or
experiment that
resulted in theacquisition of the data.
TECHNICALCONTACT– person who
is knowledgeable about
the technical content of
the data (quality,
processing methods,
units…etc).
DIF
AUTHOR – person who
is responsible for thecontent of the DIF(metadata contact);

29

Metadata point ofcontact(M)(MD_Metadata.contact >CI_ResponsibleParty)

DATA CENTER
1.9
CONTACT (Required
field in “DATA CENTER”
Group) –Identifies thedata center point ofcontact responsible forthe distribution of thedata; Or someone who
knows about the data
(see definition above for
TECHNICAL CONTACT)

396 - On-line resource
397

(O)

(MD_Metadata >"Information about on-line
MD_Distribution >sources from which the
MD_DigitalTransferOption.o dataset, specification, or
nLine > CI_OnlineResource) community profile name andextended metadata
elements can be obtained.""Related_URL"(Rec.)URL Type keywords can befound athttp://gcmd.nasa.gov/Resourc
es/valids/url_type.html& "Project"[SHORT NAME] > [LongName]This field provides
8.10
hypertext URL links toInternet sites that
contain information
related to the subject ofthe data, as well asother useful Internet
sites such as projecthome pages, related
data archives/servers,
metadata extensions,
online software
packages, web mapping
services, andOnline Linkage

292 Name of medium(O)(MD_Metadata >MD_Distribution>MD_Medium.name )"Distribution" group:
Distribution_Media:
Distribution_Size:
Distribution_Format:
Fees:"Distribution - The
6.4.2
medium, size, scientific
data format, and fees
involved in distributing
the data set";Distribution_Media: themedia options for theuser receiving the data.

Digital Form
(O)
6.4.2.1.1 Format
Name : 'OBIS' :6.4.2.2.1.1 :Network
Resource Name(?/digir.php):6.4.2.2.1.1.1.1
Network
Resource Name(DiGIR eso ce
Supplementary (O)Information

The description of options Omitfor obtaining the data set on
computer-compatible media.

Metadata(M)
Reference
Information : 7.1
Metadata Date

information on the
Includecurrentness of themetadata information, andthe responsible party.

interoperability.

WebsiteOne or more website url wheremore information on the data set
is available. Indicate relationshipof site to dataset, e.g. Original
project description, museum
collection catalogue, data centre,
host organization.

"Identification of, and means "Data_Center" Group:[Req.]of communication with,
Personnel Role: TECHNICAL
person(s) and organizations CONTACT and/or DIF Author
associated with theresource(s)" ISO list:
resourceProvider, custodian,owner, user, distributor,
originator, pointOf Contact,principalInvestigator,
processor, publisher, author"Name of the medium on
which the resource can bereceived"

Comment

Optional

46

Supplemental info on
dataset(O)(MD_Metadata >"Any other descriptive
MD_DataIdentification.supp information about thelementalInformation)
dataset"Date this entry
completed

Date this metadata form
completed

9

Metadata date stamp(M)(MD_Metadata.dateStamp)(Rec.)No Match"Date that the metadata was DIF_Creation_Date
created"Such comments could
1.2.3
also be recorded in the
abstract/summary,
and/or auxillary
keyword metadata field.
(O) however
automaticallyfilled inPage 3 of 3

"The date the DIF was 7.
created" [yyyy-mm-dd]

Point of Contact (O): 10.1 Contact
Person Primary(Group) :10.1.1
Contact Person :10.3 Contact
Position (title ofindividual) : 10.4
Contact Address: 10.4.2 Address(Group) 10.4.3
City: 10.4.4
State or Province: 10.4.6 Country: 10.5 Contact
Voice Telephone: 10.6 Contact
TDD/TTY
Telephone : 10.7
Contact
Facsimile
Telephone : 10 8
As above(O)(O)

contact information for an Include
table 11 Metadata XMAP(1), 10.12.2007
individual or organizationthat is knowledgeable
about the data set. Where
Position Title like
'Investigator'

Where Position Title like
'Technical Contact'

Includethe name of an online
Includecomputer resource that
contains the data set.
Entries should follow the
Uniform Resource Locator
convention of the Internet.

other descriptive
Omit
information about the dataset.