Resource Information

Please specify general metadata for the data set here. Mandatory fields are: Publication Year, Resource Type, Language of dataset, Title.

By default, GFZ Data Services is the publisher. If this should not be the case, e.g. in some cooperation projects, please contact us for further advice. Note: the publisher will be named in the citation of the dataset as requested by the citation guidelines of DataCite.

DOI

The DOI is a unique string that identifies a resource. Format should be 10.ORGANISATION/ID. GFZ DataServices will register a DOI for your Dataset after submission and curation.

Optional field. Please leave this field empty if your dataset is not published yet.

Publication Year

The year when the data was or will be made publicly available. In the case of datasets, “publish” is understood to mean making the data available on a specific date to the community of researchers. Values between 1901 and 2155 are allowed in the format YYYY.

• If that date cannot be determined, use the date of registration.
• If an embargo period is in effect, use the date when the embargo period ends.
• If there is no standard publication year value, use the date that would be preferred from a citation perspective.

Resource Type

Please specify the type of Dataset here. See DataCite Documentation for definition of the controlled list and examples.

Version

The version number or other identifier of the dataset. If your dataset is published for the first time, this field can be left empty. If it has been updated, specify the version number here. The suggested practice is to use a pair of major_version.minor_version to indicate changes in the dataset. Major changes typically require registration of a new DOI.

Optional field. If unsure, leave blank.

Language of dataset

The primary language of the dataset. Choose from a list of supported languages. Default is English.

Title

The title of the dataset. Please note that the title shall describe the data and not repeat the title of the corresponding article! The first row is reserved for the main title. You can specify up to additional titles if your dataset is known by multiple names or translations.

Title Type

Indicates the type of title being provided, such as an alternative title or translated title. Mandatory for every title except the main title in the first row.

• Alternative Title: You can also add an alternative title if required.
• Translated Title: If the dataset is also to be published with a translated title, this title should have this title type.

Author(s)

Please enter authors of the dataset here by entering their last and first name without any titles. Ideally you provide an ORCID. Entering an ORCID loads data from the corresponding ORCID profile. To add more authors, use the "add" button on the right. The order of the authors can be changed using drag & drop.

Please mark at least one author as contact person. (Person with knowledge of how to access, troubleshoot, or otherwise field issues related to the resource.)

ORCID

Uniquely identifies an individual or legal entity, according to various schemes. Please enter a valid ORCID in the format XXXX-XXXX-XXXX-XXXX (i.e. 0000-0001-5727-2427). If you do not have an ORCID iD yet, you can learn about it and register here. If you enter a valid ORCID, an attempt will be made to fill in the remaining required fields automatically. Results are depending on the information provided in the ORCID profile.

Optional field.

Affiliation

The organisational or institutional affiliation of the creator.

It is recommended to select the affiliation from the list. If the required affiliation is not among the available options, it can be entered manually.

ROR ID

Affiliation data is based on the Research Organization Registry (ROR). The ROR ID uniquely identifies organisations worldwide and ensures clear and consistent attribution. For more information about ROR, visit https://ror.org.

Contact Person(s)

Person with knowledge of how to access, troubleshoot, or otherwise field issues related to the resource. May also be "Point of Contact" in organisation that controls access to the resource. Please enter at least one contact person.

After filling in the list of authors, the Contact Person can be selected by simply clicking the button on the left. The email address of the author, who is labelled as the contact person, must also be provided. The specification of a website is optional.

Website

Professional or specialized website, excluding any private websites. The specification of a website, such as that of your institution, offers further contact options in case of questions.

Author Institution(s)

This optional section allows you to enter an institution or organization as the author. This is useful, for example, when the publication was created by a group, project, or institution rather than by individual persons.

Please provide the organization name in the required field. You may optionally add one or more affiliations (e.g., departments, working groups). As you type, suggestions will appear, but you can also enter custom affiliations manually.

Note on the difference between Organization Name and Affiliation:
The Organization Name refers to the institution or organization listed as the author. An Affiliation, on the other hand, describes a specific connection within or between organizations – for example, a department, institute, or subunit. Multiple organizations can be represented by the same affiliation, and conversely, one organization can have several affiliations.

Originating Laboratory

Please specify the laboratory from which the data originates. This is essential for retrieval of data publications from a laboratory and improving the findability of your data.
You can choose from a list of the EPOS multi-scale laboratories. This list is provided and maintained by Utrecht University.

Name of the originating laboratory

Click on the input field to browse the list of multi-scale laboratories or start typing to filter.

Contributor Persons

A contributor person is a person responsible for collecting, managing, distributing, or otherwise contributing to the development of the resource. To add more than one contributor, use the "add" button on the right.

With Contributing Person(s) you have the possibility to acknowledge additional persons or institutions related to the dataset which you would normally not mention as authors. These are not named in the citation but are always related to the dataset and findable just as all the other metadata fields.

Optional field.

ORCID

Uniquely identifies an individual or legal entity, according to various schemes. Please enter a valid ORCID in form of XXXX-XXXX-XXXX-XXX(X) (i.e. 0000-0001-5727-2427). You can find your colleagues' ORCID on the ORCID search page. If you enter a valid ORCID, an attempt will be made to fill in the remaining required fields automatically. Results are depending on the information provided in the ORCID profile.

Optional field.

Roles

The role of the contributing person(s) in the creation of the resource. Please choose one or more roles from the controlled list provided by DataCite.

• Data Collector: Person responsible for finding or gathering/collecting data under the guidelines of the author(s) or Principal Investigator (PI).
• Data Curator: Person tasked with reviewing, enhancing, cleaning, or standardizing metadata and the associated data submitted for storage, use, and maintenance within a data center or repository; While the "DataManager" is concerned with digital maintenance, the DataCurator's role encompasses quality assurance focused on content and metadata. This includes checking whether the submitted dataset is complete, with all files and components as described by submitter, whether the metadata is standardized to appropriate systems and schema, whether specialized metadata is needed to add value and ensure access across disciplines, and determining how the metadata might map to search engines, database products, and automated feeds.
• Data Manager: Person responsible for maintaining the finished resource. The work done by this person ensures that the resource is periodically "refreshed" in terms of software/hardware support, is kept available or is protected from unauthorized access, is stored in accordance with industry standards, and is handled in accordance with the records management requirements applicable to it.
• Editor: A person who oversees the details related to the publication format of the resource. Note: if the Editor is to be credited in place of multiple authors, the Editor's name may be supplied as Author, with "(Ed.)" appended to the name.
• Producer: Typically a person or organisation responsible for the artistry and form of a media product. In the data industry, this may be a company
• Project Leader: Person officially designated as head of project team or sub-project team instrumental in the work necessary to development of the resource.
• Project Manager: Person officially designated as manager of a project. Project may on consist of one or many project teams and sub-teams. The manager of a project normally has more administrative responsibility than actual work involvement.
• Member: Person on the membership list of a designated project/project team. This vocabulary may or may not indicate the quality, quantity, or substance of the person's involvement.
• Related Person: A person without a specifically defined role in the development of the resource, but who is someone the author wishes to recognize. This person could be an author's intellectual mentor, a person providing intellectual leadership in the discipline or subject domain, etc.
• Researcher: A person involved in analyzing data or the results of an experiment or formal study. May indicate an intern or assistant to one of the authors who helped with research but who was not so “key” as to be listed as an author.
• Rights Holder: Person owning or managing property rights, including intellectual property rights over the resource.
• Sponsor: Person that issued a contract or under the auspices of which a work has been written, printed, published, developed, etc. Includes organisations that provide in-kind support, through donation, provision of people or a facility or instrumentation necessary for the development of the resource, etc.
• Supervisor: Designated administrator over one or more groups/teams working to produce a resource or over one or more steps of a development process.
• WorkPackage Leader: A Work Package is a recognized data product, not all of which is included in publication. The package, instead, may include notes, discarded documents, etc. The Work Package Leader is responsible for ensuring the comprehensive contents, versioning, and availability of the Work Package during the development of the resource.
• Other: Any person making a significant contribution to the development and/or maintenance of the resource, but whose contribution does not

Affiliation

The organisational or institutional affiliation of the person/s.

It is recommended to select the affiliation from the list. If the required affiliation is not among the available options, it can be entered manually.

ROR ID

Affiliation data is based on the Research Organization Registry (ROR). The ROR ID uniquely identifies organisations worldwide and ensures clear and consistent attribution. For more information about ROR, visit https://ror.org.

Contributor Institutions

A contributor institution is an organisation responsible for collecting, managing, distributing, or otherwise contributing to the development of the resource. To add more than one contributor, use the "add" button on the right.

With Contributing Institution(s) you have the possibility to acknowledge additional persons or institutions related to the dataset which you would normally not mention as authors. These are not named in the citation but are always related to the dataset and findable just as all the other metadata fields.

Optional field.

Organisation Name

The name of the institution.

Roles

The role of the contributor organisation/s in the creation of the resource. Please choose one or more roles from the controlled list values provided by DataCite:

• Data Collector: Institution responsible for finding or gathering/collecting data under the guidelines of the author(s) or Principal Investigator (PI).
• Data Manager: Institution responsible for maintaining the finished resource. The work done by this person ensures that the resource is periodically "refreshed" in terms of software/hardware support, is kept available or is protected from unauthorized access, is stored in accordance with industry standards, and is handled in accordance with the records management requirements applicable to it.
• Distributor: Institution tasked with responsibility to generate/disseminate copies of the resource in either electronic or print form. Works stored in more than one archive/repository may credit each as a distributor.
• Hosting Institution: Typically, the organisation allowing the resource to be available on the internet through the provision of its hardware/software/operating support. May also be used for an organisation that stores the data offline. If your data was derived from a laboratory, please include the name of the laboratory (with affiliation) as contributor with the role “HostingInstitution”. There may be two hosting institutions if the data or work is stored in both. Often a data centre.
• Producer: Typically a organisation responsible for the artistry and form of a media product. In the data industry, this may be a company
• Registration Agency: Institution/organisation officially appointed by a Registration Authority to handle specific tasks within a defined area of responsibility. DataCite is a Registration Agency for the International DOI Foundation (IDF). One of Data Cite's tasks is to assign DOI prefixes to the allocating agents who then assign the full, specific character string to data clients, provide metadata back to the Data Cite registry, etc.
• Registration Authority: A standards-setting body from which Registration Agencies obtain official recognition and guidance. The IDF serves as the Registration Authority for the International Standards Organisation (ISO) in the area/domain of Digital Object Identifiers.
• Research Group: Typically refers to a group of individuals with a lab, department, or on division; the group has a particular, defined focus of activity. May operate at a narrower level of scope; may or may not hold less administrative responsibility than a project team.
• Rights Holder: Institution owning or managing property rights, including intellectual property rights over the resource.
• Sponsor: Organisation that issued a contract or under the auspices of which a work has been written, printed, published, developed, etc. Includes organisations that provide in-kind support, through donation, provision of people or a facility or instrumentation necessary for the development of the resource, etc.
• Other: Any institution making a significant contribution to the development and/or maintenance of the resource, but whose contribution does not

Affiliation

The organisational or institutional affiliation of the Institution.

It is recommended to select the affiliation from the list. If the required affiliation is not among the available options, it can be entered manually.

ROR ID

Affiliation data is based on the Research Organization Registry (ROR). The ROR ID uniquely identifies organisations worldwide and ensures clear and consistent attribution. For more information about ROR, visit https://ror.org.

Descriptions

Filling in the description fields greatly improves the discoverability of your data publication.
The abstract is a mandatory field, because it is (just like the abstract of a paper) highly valuable to other scholars in finding your data and then determining whether or not the resource is worth investigating further, re-using, or validating.
Please keep in mind that the descriptions should describe the resource itself and not the corresponding article.

Abstract

A brief description of the resource and the context in which the resource was created. Please keep in mind that this abstract is describing the resource itself and should not simply be the abstract of a corresponding article.
When writing the abstract, please keep in mind:

• The audience is the broader scientific community, not only your own subdomain.
• Although your abstract must be focused on the data, we recommend beginning with the description of the original purpose of data collection and a short introduction to the project or method. Please do not provide the abstract of the paper here.
• Please provide a technical description of the data generation (e.g. sampling method, location, method of analysis, detection limits, data processing steps, conversions, etc.), partners/partner institutions, and a summary of datasets included in this data publication (e.g. “7 boreholes reaching depths from 2-14 m” or “This data set encompasses broadband seismic data from c. 20 stations in Northern Chile, recorded since 2006” or “… paleomagnetic and rock magnetic dataset from two Calypso giant piston cores collected at the crest of the Bellsund (GS191-01PC) and Isfjorden (GS191-02PC) sediment drifts during the Eurofleets-2 PREPARED cruise, on board the R/V G.O. Sars (Lucchi et al., 2014).”).
• Please specify the data formats and form (e.g. do you have several individual datasets or combined files, e.g. as zip folder?). In case of complex (zip)-folder structures, we recommend to provide the file overview in the data description or as additional document “List of files” (e.g. http://doi.org/10.5880/GFZ.4.1.2019.005)

Methods

The methodology employed for the study or research.

Technical Information

Detailed information that may be associated with design, implementation, operation, use, and/or maintenance of a process, system, or instrument.

Other

Other description information that does not fit into an existing category.

EPOS Multi-Scale Laboratories Keywords

Please click on the Thesaurus button to the right to select keywords from the tree or start typing to use the autocomplete function. By adding terms like these, you make it much easier for us to find your data and to make it discoverable in this catalogue and the EPOS data portal.

The selectable keywords are taken from EPOS Multi-Scale Laboratories vocabularies, available on GitHub.

Keyword Viewer

Please try to choose your keywords as specific as possible. Always check if there is a more fitting keyword further down the hierarchy. Definitions of keywords can be read via mouse over, if provided by the thesaurus maintainer.

To open the hierarchy ("tree"), click on the small arrow or double-click the keyword. Choose a keyword by clicking on it and thereby checking the checkbox. The keyword is than automatically added. Selected keywords have a checkmark in their checkbox.

You can also use the search bar on top. It searches the keywords and their definitions or descriptions.

GCMD Platforms Keywords

Please click on the Thesaurus button to the right to select keywords from the tree or start typing to use the autocomplete function.

GCMD Platforms are important for identifying the sources of data collection. We recommend selecting relevant platform keywords to provide context about how your dataset was acquired.

GCMD Instruments Keywords

Please click on the Thesaurus button to the right to select keywords from the tree or start typing to use the autocomplete function.

GCMD Instruments help specify the tools used for data collection. We encourage you to select appropriate instrument keywords to give users a clear understanding of how your data was measured or observed.

GCMD Science Keywords

Please click on the Thesaurus button to the right to select keywords from the tree or start typing to use the autocomplete function.

GCMD Science Keywords are essential for filtering options within the GFZ Metadata Portal. Therefore, we highly recommend selecting at least one GCMD Science Keyword to describe your dataset (you are welcome to add more if relevant).

Keyword Viewer

Please try to choose your keywords as specific as possible. Always check if there is a more fitting keyword further down the hierarchy. Definitions of keywords can be read via mouse over, if provided by the thesaurus maintainer.

To open the hierarchy ("tree"), click on the small arrow or double-click the keyword. Choose a keyword by clicking on it and thereby checking the checkbox. The keyword is than automatically added. Selected keywords have a checkmark in their checkbox.

You can also use the search bar on top. It searches the keywords and their definitions or descriptions.

Dates

This group of fields refers to important data in the life cycle of the data set. Please enter the information as precisely as possible to ensure the chronological classification and availability of the data set.

Date created

The date on which the dataset was created. The date should be between 01.01.1900 and 31.12.2100.

If the dataset is a collection of data from different sources, use the date when the dataset was compiled. If the dataset is a simulation, use the date when the simulation was completed. If the dataset is a reanalysis, use the date when the reanalysis was completed. If the dataset is a combination of data from different sources, use the date when the dataset was compiled.

Embargo until

The date until which the dataset is under embargo. Only by arrangement. If the dataset is not under embargo, leave this field empty.

Spatial and Temporal coverage

Geographic location and time period covered by the dataset. Includes coordinates (latitude/longitude), dates, times, and time zones. Essential for data discovery and relevance assessment. Enables users to search for datasets in specific regions or time frames. Please provide accurate information to enhance the findability and usability of your research data in our repository.

Geographic Coverage

You can add singles coordinates with Latitude Min and Longitude Min or a bounding box with Latitude Min, Latitude Max, Longitude Min and Longitude Max.

You can also use the map to set the coordinates either for rectangles or points. There you can also search for place names to determine the coordinates of the location.

• Latitude Min: Geographic latitude of a single coordinate or the smaller geographic latitude of a rectangle as a floating point number with a dot as the separator. Only positive and negative numbers in the range from -90.00 to +90.00 are allowed.
• Latitude Max: Geographic latitude of a rectangle as a floating point number with a dot as the separator. Optional field. Only positive and negative numbers in the range from -90.00 to +90.00 are allowed.
• Longitude Min: Geographic longitude of a single coordinate or the smaller geographic longitude of a rectangle as a floating point number with a dot as the separator. Only positive and negative numbers in the range from -180.00 to +180.00 are allowed.
• Longitude Max: Geographic longitude of a rectangle as a floating point number with a dot as the separator. Optional field. Only positive and negative numbers in the range from -180.00 to +180.00 are allowed.

Description

Free text field for explaining the geographic and temporal context. Required field without any restrictions.

Temporal Coverage

Both Start and End Date should be between 01.01.1900 and 31.12.2100.

• Start Date: Date of the beginning of the temporal coverage of the dataset. Can be selected via the date picker. Required field.
• Start Time: Time specification in format hh:mm:ss. Can be selected via the time picker.
• End Date: Date of the end of the temporal coverage of the dataset. Can be selected via the date picker. Required field.
• End Time: Time specification in format hh:mm:ss. Can be selected via the time picker.

Timezone

Related Work

Please enter resources related to your data. This helps connecting your data to other work like articles, samples, etc. Identifiers must be globally unique.

Note: related references may always be added to the metadata of a datasets (thus improving the data description and discovery), even after the registration of the DOI. We encourage you to inform us if you want to add new references to the published datasets.

Optional field.

Relation Type

The following different relation types are available for selection:

• IsCitedBy: indicates that B includes A in a citation
• Cites: indicates that A includes B in a citation
• IsSupplementTo: indicates that A is a supplement to B
• IsSupplementedBy: indicates that B is a supplement to A
• IsContinuedBy: indicates A is continued by the work B
• Continues: indicates A is a continuation of the work B
• Describes: indicates A describes B
• IsDescribedBy: indicates A is described by B
• HasMetadata: indicates resource A has additional metadata B
• IsMetadataFor: indicates additional metadata A for a resource B
• HasVersion: indicates A has a version B
• IsVersionOf: indicates A is a version of B
• IsNewVersionOf: indicates A is a new edition of B, where the new edition has been modified or updated
• IsPreviousVersionOf: indicates A is a previous edition of B
• IsPartOf: indicates A is a portion of B; may be used for elements of a series
• HasPart: indicates A includes the part B
• IsPublishedIn: indicates A is published inside B, but is independent of other things published inside of B
• IsReferencedBy: indicates A is used as a source of information by B
• References: indicates B is used as a source of information for A
• IsDocumentedBy: indicates B is documentation about/explaining A (e.g. points to software documentation or a data report)
• Documents: indicates A is documentation about/explaining B (e.g. points to software documentation or a data report)
• IsCompiledBy: indicates B is used to compile or create A
• Compiles: indicates B is the result of a compile or creation event using A
• IsVariantFormOf: indicates A is a variant or different form of B
• IsOriginalFormOf: indicates A is the original form of B
• IsIdenticalTo: indicates that A is identical to B, for use when there is a need to register two separate instances of the same resource
• IsReviewedBy: indicates that A is reviewed by B
• Reviews: indicates that A is a review of B
• IsDerivedFrom: indicates B is a source upon which A is based
• IsSourceOf: indicates A is a source upon which B is based
• IsRequiredBy: Indicates A is required by B
• Requires: Indicates A requires B
• Obsoletes: Indicates A replaces B
• IsObsoletedBy: Indicates A is replaced by B
• IsCollectedBy: Indicates A is collected by B
• Collects: Indicates A collects B

Identifier

Identifiers of related resources. These must be globally unique identifiers.

Identifier Type

The type of the Related Identifier.

• ARK: A URI designed to support long-term access to information objects. In general, ARK syntax is of the form (brackets, []. indicate optional elements).
• arXiv: arXiv.org is a repository of preprints of scientific papers in the fields of mathematics, physics, astronomy, computer science, quantitative biology, statistics, and quantitative financ.
• bibcode: A standardized 19-character identifier according to the syntax yyyyjjjjjvvvvmppppa.
• DOI: A character string used to uniquely identify an object. Format should be 10.ORGANISATION/ID.
• EAN13: A 13-digit barcoding standard that is a superset of the original 12-digit Universal Product Code (UPC) system.
• EISSN: ISSN used to identify periodicals in electronic form (eISSN or e-ISSN).
• Handle: This refers specifically to an ID in the Handle system operated by the Corporation for National Research Initiatives (CNRI).
• IGSN: A code that uniquely identifies samples from our natural environment and related features-of-interest.
• ISBN: A unique numeric book identifier. There are 2 formats: a 10-digit ISBN format and a 13-digit ISBN.
• ISSN: A unique 8-digit number used to identify a print or electronic periodical publication.
• ISTC: A unique “number” assigned to a textual work. An ISTC consists of 16 numbers and/or letters..
• LISSN: The linking ISSN or ISSN-L enables collocation or linking among different media versions of a continuing resource.
• LSID: A unique identifier for data in the Life Science domain. Format: urn:lsid:authority:namespace:identifier:revision.
• PMID: A unique number assigned to each PubMed record.
• PURL: A PURL has three parts: (1) a protocol, (2) a resolver address, and (3) a name.
• UPC: A barcode symbology used for tracking trade items in stores. Its most common form, the UPC-A, consists of 12 numerical digits.
• URL: Also known as web address, a URL is a specific character string that constitutes a reference to a resource. The syntax is: scheme://domain:port/path?query_string#fragment_id.
• URN: A unique and persistent identifier of an electronic document. The syntax is: urn::. The leading urn: sequence is case-insensitive, is the namespace identifier, is the namespace-specific string.
• w3id: Mostly used to publish vocabularies and ontologies. The letters ‘w3’ stand for “World Wide Web”.

Funding Reference

Information about financial support (funding) for the resource being registered. It is a best practice to supply funding information when financial support has been received.

Funder

The name of the funding provider. To receive suggestions, please enter at least the first two letters. If possible, please choose from the controlled list. You can also manually enter the funding provider. Please use the funder name in the corresponding national language (e.g. "Deutsche Forschungsgemein- schaft" for DFG, "Vetenskapsrådet" for the Swedish Research Council). Several grant numbers by the same funder should be entered as individual entries (several lines).

Grant Number

Free text field for entering the grant number assigned by the funding provider.

Grant Name

Free text field for entering the title or name of the grant.

Award URI

Optional link or identifier to detailed information about the award. This can be a URL pointing to the grant on the funder's website or a DOI.

Characteristics of the model

This section defines the essential characteristics of Global Gravitational Models (GGMs) and describes GGMs published via the ICGEM (International Center for Global Earth Models) service.

ICGEM provides the opportunity to publish a Global Gravitational model.

Model publication is a unique effort of scientific work, so ICGEM provides long-term support for the model developers.

The model is published on the ICGEM website and is available for download, calculation, and visualization.

The data file of the model is provided with metadata and published with a DOI via GFZ Data Services. Rich and structured metadata is essential for the model findability and reusability.

This editor is a tool to provide metadata for GGM model publications. It is adapted from GFZ Data Services metadata editor, which connects ICGEM to the data publication workflow in the GFZ.

ICGEM database is an archive and information hub, centered around gravity field models. It collects properties that describe the mathematical and technical specifications of your gravity field model.

Validation Logic: In order to upload the model, we ask you to provide the following information: Model Type, Mathematical Representation, Model Name, and File Format. Please make sure to provide them.

Model Type

A higher level classification of the Global Gravitational Models (GGM). The types are represented on the ICGEM website and include:

• static – models of the gravity field potential computed from satellite-based gravity measurements. The spatial details of the gravity field (short wavelengths or high frequencies) are collected via terrestrial, airborne, and shipborne gravity measurements as well as radar altimetry.
• temporal – models derived from input data covering specific time periods, enabling monitoring of temporal changes in the gravity field.
• topographic – models representing the gravitational potential generated by Earth's topographic masses. Gravity is computed based on very high resolution digital elevation models describing the Earth's shape and mass densities within the topography. These models are not based on actual gravity measurements.
• simulated – models based on simulated data and not on measurements.

Based on Ince et al. (2019): ICGEM – 15 years of successful collection and distribution of global gravitational models, associated services, and future plans. Earth System Science Data, 11, pp. 647–674. DOI: 10.5194/essd-11-647-2019

Mathematical Representation

The mathematical representation of a gravity field model refers to the set of functions used to express the gravitational potential, which are solutions of Laplace’s equation in a given coordinate system. The coordinate system determines the type of harmonics — spherical or ellipsoidal — and thus defines the mathematical form of the model.

Based on STR by Barthelmes (2013): https://doi.org/10.2312/GFZ.b103-0902-26

Note: This field is mandatory because it is not possible to use the model without this information.

Celestial Body

Specify the celestial body for which the gravity field model was computed. The default selection is Earth, but models for other planetary bodies are also supported.

File Format

All models on the ICGEM are published in the ICGEM file format. See description at ICGEM-Format-2023.pdf

This field is mandatory. To support time-limited validity periods for time-varying coefficients, a new parameter has been introduced: format=icgem2.0.

Note: You cannot mix coefficients formatted as icgem1.0 and icgem2.0. Please ensure all model files use the same format version.

Model Name

The unique identifier name for your gravity field model to be represented on the ICGEM website. This should be a concise and descriptive name that follows standard conventions in the gravity field community. No spaces are allowed.

As a title, this name will be displayed on the GFZ Data Services landing page. It will also be the main title from the first formgroup.

Requirements:

• No spaces allowed in the model name
• Use underscores or hyphens to separate words if needed
• Should be unique and descriptive
• Examples: GO_CONS_GCF_2_SPW_R5, Tongji-Grace02s, LUH-GRACE-FO-2020

Product Type

Static and temporal models produced based on direct gravity observations (for instance, from satellite gravity missions) have the product type gravity field.

If the model is topographic and was produced using forward modelling, then the product type is topographic gravity field.

Characteristics of the model

This section defines the essential characteristics of Global Gravitational Models (GGMs). Amd describes GGM published via the ICGEM (International Center for Global Earth Models) service. ICGEM provides opportunity to publish a Global Gravitational model. Model publication is a unique effort of scientific work, so ICGEM provides a long term support for the model developers. The model is published on the ICGEM website and is available for download, calculation visualisation. The data file of the model is provided with metadata and published with a DOI via GFZ Data Services. Rich and structured metadata is essential for the model findability and reusability. This editor is a tool to provide metadata for GGM model publications. It is adapted from GFZ Data Services metadata editor, which connects ICGEM to the data publication workflow in the GFZ. ICGEM database is an archive and information hub, centered around gravity field models. It collects properties that describe the mathematical and technical specifications of your gravity field model.

Validation Logic: In order to upload the model, we ask you to provide the following information: Model Type, Mathematical Representation, Model Name, and File Format. Please make sure to provide them.

Model Type

A higher level classification of the Global Gravitational Models (GGM). The types are represented on the ICGEM website and include:

• static – models of the gravity field potential computed from satellite-based gravity measurements. The spatial details of the gravity field (short wavelengths or high frequencies) are collected via terrestrial, airborne, and shipborne gravity measurements as well as radar altimetry.
• temporal – models derived from input data covering specific time periods, enabling monitoring of temporal changes in the gravity field.
• topographic – models representing the gravitational potential generated by the attraction of Earth's topographic masses. Gravity is computed based on very high resolution digital elevation models describing the Earth's shape and mass densities within the topography. These models are not based on actual gravity measurements.
• simulated – models based on simulated data and not on measurements.

Mathematical Representation

The mathematical representation of a gravity field model refers to the set of functions used to express the gravitational potential, which are solutions of Laplace’s equation in a given coordinate system. The coordinate system determines the type of harmonics — spherical or ellipsoidal — and thus defines the mathematical form of the model. Based on STR by Barthelmes (2013): https://doi.org/10.2312/GFZ.b103-0902-26 This field is mandatory because it is not possible to use the model without this information.

Celestial Body

Specify the celestial body for which the gravity field model was computed. The default selection is Earth, but models for other planetary bodies are also supported.

File Format

All models on the ICGEM are published in the ICGEM file format. See description at https://icgem.gfz-potsdam.de/docs/ICGEM-Format-2023.pdf This field is mandatory. To support time-limited validity periods for time-varying coefficients, a new parameter has been introduced: format=icgem2.0. Note: You cannot mix coefficients formatted as icgem1.0 and icgem2.0. Please ensure all model files use the same format version.

Model Name

The unique identifier name for your gravity field model to be represented on the ICGEM website. This should be a concise and descriptive name that follows standard conventions in the gravity field community. No spaces are allowed. As a title, this name will be displayed on the GFZ Data Services landing page. It will also be the main title from the first formgroup.

Requirements:

• No spaces allowed in the model name
• Use underscores or hyphens to separate words if needed
• Should be unique and descriptive
• Examples: GO_CONS_GCF_2_SPW_R5, Tongji-Grace02s, LUH-GRACE-FO-2020

Product Type

Static and temporal models produced based on direct gravity observations (for instance, from satellite gravity missions) have the product type "gravity field". If the model is topographic and was produced using forward modelling, then the product type is "topographic gravity field".