Astral
  • Welcome
  • Astral Litepaper
  • GeoNFT
    • Ecological State
  • Spatial Data Registry
    • On-chain Spatial Data Registry
    • Celo/EVM Anchored Spatial Data Registry
      • Technical Design
        • Ingestion
        • Anchoring
        • Validation
        • List on Ocean Marketplace
      • Summary
    • CosmWasm Anchored Spatial Data Registry
  • Progress
  • ARCHIVE
    • Introduction
    • Spatial Data Primer
    • Background
      • Motivation
      • Value
      • The Stack
        • Data
        • Oracles
        • Spatial Contracts
    • A Web3-Native Geospatial Vision
      • A rationale for GeoDIDs
      • GeoTIFFs and IPLD
        • Encoding the GeoTIFF
        • Decoding the GeoTIFF
    • Spatial.sol
      • Design Considerations
    • Verifiable Spatial Data Registries
    • GeoDIDs
      • DID Primer
      • GeoDID Core
        • GeoDID Core Specification
        • GeoDID Collection Example
        • GeoDID Item Example
      • GeoDID Extensions
        • GeoJSON
        • GeoTIFF
          • IPLD-encoded GeoTIFF
          • Cloud-optimized GeoTIFF
        • STAC
          • STAC Items
          • STAC Catalogs
      • Build with GeoDIDs
        • Getting Started
        • @astralprotocol/core
          • API
          • Types
        • @astralprotocol/contracts
          • API
        • @astralprotocol/subgraph
      • GeoDIDs v0.2
    • Spatial Oracles
    • Universal Location Proofs
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. ARCHIVE
  2. GeoDIDs

GeoDID Extensions

PreviousGeoDID Item ExampleNextGeoJSON

Last updated 3 years ago

Was this helpful?

Spatial data assets identified by GeoDIDs will come in a particular format, likely with information about the spatial reference system, attribution and other metadata. GeoDID extensions will enable the GeoDID Core Spec to expand to support any type of spatial data asset - legacy, current, or future.

Under construction - stay tuned!

@AstralProtocol