Publisher Data Catalogs

AI-generated Key Takeaways

outlined_flag

• Publisher Data Catalogs are public collections of Earth Engine assets curated and managed by the data publishers, not Google.

• To publish a catalog, data must be publicly available at no cost under a minimally restrictive license, and storage costs must be covered.

• Publishers need a technical contact familiar with git pull requests to manage catalog entries.

• A written commitment for dataset maintenance, including fixing errors and providing new versions, is required.

Publisher Data Catalogs are curated by the publisher of the dataset for use by Google Earth Engine users and shared publicly using Earth Engine. Google does not curate these Catalogs and is not responsible for the Catalogs, including whether they will continue to be available or whether their content is accurate and up to date.

Eligibility

Data publishers who meet the following requirements can request to publish a Publisher Data Catalog:

• Data are available publicly at no cost under a minimally restrictive (e.g., an attribution-only) license.
• Earth Engine users must use their own storage for Publisher Data Catalogs.
  • For Earth Engine customers in Public Sector Operations:
    • Must have a mandate & funding to distribute public data.
  • For Earth Engine customers in Private Sector:
    • Citable publication with methodology strongly recommended.

• Must have a technical person on-staff assigned to the upload who is familiar with git pull requests and is willing to spend ~1 day to add the first catalog entry, plus data upload time. If you don't have technical person on-staff familiar with git pull requests, you can work with a Partner Advantage Partner, such as NGIS, who has made datasets available as part of the Preview. See the NGIS program website to understand eligibility and register interest with NGIS.

• Must provide a written intent (i.e. email acknowledgement from supervisor) for maintaining the dataset for at least one year and:

  • Not removing the data without a deprecation announcement at least 180 days in advance.
  • Fixing errors and adding new versions as appropriate.

If you meet these requirements, and want to become a Publisher Data Catalog, fill out this form .