EarthCube Resource Registry
Please submit resource descriptions by filling out the form. A submitted resource description will be assigned an ARK identifier, stored in EarthCube registry, and made available for discovery and re-use.

𝘕𝘖𝘛𝘌: 𝘚𝘰𝘮𝘦 𝘧𝘰𝘳𝘮 𝘴𝘦𝘤𝘵𝘪𝘰𝘯𝘴 𝘢𝘳𝘦 𝘰𝘯𝘭𝘺 𝘢𝘱𝘱𝘭𝘪𝘤𝘢𝘣𝘭𝘦 𝘵𝘰 𝘴𝘱𝘦𝘤𝘪𝘧𝘪𝘤 𝘳𝘦𝘴𝘰𝘶𝘳𝘤𝘦 𝘵𝘺𝘱𝘦𝘴, 𝘪𝘯𝘴𝘵𝘳𝘶𝘤𝘵𝘪𝘰𝘯𝘴 𝘴𝘩𝘰𝘶𝘭𝘥 𝘱𝘳𝘰𝘷𝘪𝘥𝘦 𝘨𝘶𝘪𝘥𝘢𝘯𝘤𝘦 (𝘴𝘰 𝘺𝘰𝘶 𝘥𝘰𝘯'𝘵 𝘩𝘢𝘷𝘦 𝘵𝘰 𝘧𝘪𝘭𝘭 𝘰𝘶𝘵 𝘢𝘭𝘭 15 𝘴𝘦𝘤𝘵𝘪𝘰𝘯𝘴).

*ğ™ğ™šğ™¦ğ™ªğ™žğ™§ğ™šğ™™ ğ™›ğ™žğ™šğ™¡ğ™™ğ™¨ 𝙖𝙧𝙚 ğ™žğ™£ğ™™ğ™žğ™˜ğ™–ğ™©ğ™šğ™™ ğ™¬ğ™žğ™©ğ™ 𝙖 𝙧𝙚𝙙 ğ™–ğ™¨ğ™©ğ™šğ™§ğ™žğ™¨ğ™   

NOTE: after populating the required fields, you can submit the form.  When you submit the form, there will be an edit URL provided, labeled "Edit your Response" -- PLEASE save this link so that you can return to editing this form, that way you can do a partial submission and return to add additional information.  If you enter you e-mail address before submitting, you will also receive the edit link in an e-mail message.

If multiple values apply for a given field put each entry on a separate line; hit ENTER to start a new line.
Any web link, e.g. a URL, can have a label string preceding the URL on the same  line. This is useful to help users figure out what the links lead to. Example:
-- search data,  --
-- python code repository, --

Examine sample Resource Registry entries:
Browse and search EC resources with SuAVE:
View and suggest changes to controlled vocabularies:
Preview form fields and descriptions:

Please post suggestions and feedback in the GitHub issue tracker at

Form Version 2. Updated 2021-01-05

<CODE:RED> We sincerely apologize for any annoyance you may experience at the depth of information we ask from you combined with the clumsiness of the form !!! </CODE:RED>. You'll feel happy at the end.
Sign in to Google to save your progress. Learn more
Section 1. Required Resource Information
Resource name, description, citation, license,  registrant, resource type,
Short name by which the resource can be identified
Description *
Please provide as much detail as possible, so that we can automatically extract additional information, and search engine text indexing will provide useful results. Feel free to copy and paste from respective web sites, papers, reports, etc. (100  characters minimum)
Citation *
Please provide a recommended citation to reference this resource in publications, using a standard bibliographic format (50 characters minimum)
License *
Note that a resource may be available under more than one license.
Registry Contributor *
The full name of the person completing this resource registration form.
ORCID of the Contributor
Optional, but highly recommended. A URI that identifies the contributor;  If you don't know if an ORCID is registered, you can search at  If another unique, dereferenceable identifier is available, that will work.
Alternate Resource Name(s)
Alternate names by which the resource might be known or discovered. If names are provided in a non-English language, please suffix a language identifier using the '@' delimiter and an ISO-639-1 two letter language code, e.g. Forme universelle binaire de l'OMM@fr. Please put each name on a separate line; hit ENTER to start a new line.
URL to User-Readable Page
URL to access information about the resource on the Web.  Please provide a label for the URL (e.g. 'home page',  'OGC specification'),  and separate the label from the URL with a comma (no commas in the label!)                                                           e.g.   OGC specification landing page, .  To add multiple links, please put each entry on a separate line; hit ENTER to start a new line.
Date of publication or most recent release
External Identifier(s)
One or more globally-unique URIs, ideally using a scheme that can be dereferenced on the Web.                                                                                                                                                                  HTTP URI's are preferred, but any URI scheme is allowed, e.g. ISSN, DOI, ARK, ISBN, URN:OGC...                                                                                Each identifier should be on a separate line; hit ENTER to start a new line.                                        NOTE FOR INTERCHANGE FORMAT resources,  the string included here should be the token used to associate the data format with either input or output formats for Software, Service endpoint actions, or in API descriptions. This is the value that will be used for data-application matching by GeoCODES.                                                                                                                                 EXAMPLE: (Use namespace uri for XML interchange formats);   application/octet-stream;type=DMSP ;   application/x-netcdf;type=SeaDataNet-CF3D.  See for a current list of recognized formats
Responsible Parties
Persons or organizations with roles in the creation of the resource content, e.g. Creator, Editor, Contributor...   Please Note-- use this special formatting to generate better metadata.                                                                                                                              Each responsible party should be on a separate line (hit ENTER to start a new line).   Each line should indicate the party's role, whether they are a person or organization, their name, and provide an (Optional) identifier. The format is like this:{Creator|Editor|Contributor|Publisher}, {Organization|Person}, Name, Identifier.   NOTE that the parts of each party row are separated by COMMAS (','). The identifier is optional, and can be a ROR (for organizations) or OrcID (for persons).                                                                                                EXAMPLE:  editor, Person, Klaas Deneudt,
Primary Publication
An Identifier (e.g. DOI) or standard academic citation for publication that specifies or describes the resource.                   EXAMPLE:  Barnes, Stanley L., 1980, Report on a Meeting to Establish a Common Doppler Radar Data Exchange Format: Bulletin of the American Meteorological Society, vol. 61, no. 11, pp. 1401–1404. (accessed at
Index items to guide discovery; use words or phrases you would expect searchers to enter into search engines.  Each keyword should be on a separate line; hit ENTER to start a new line. Individual keywords should not contain commas.
Clear form
Never submit passwords through Google Forms.
This content is neither created nor endorsed by Google. Report Abuse - Terms of Service - Privacy Policy