Merged
Conversation
- Expanded the scope of the dgeo extension in README to include "Assets". - Enhanced the description to clarify the purpose of the dgeo extension. - Updated objectives for improved clarity on queryable CID-based discovery and asset-level metadata. - Revised examples in README to reflect new usage patterns and asset-level fields. - Modified JSON Schema to include required fields for dgeo:cids and dgeo:piece_cids. - Added asset-level fields dgeo:cid and dgeo:cid_profile to support CID-to-asset correlation. - Improved validation patterns for CIDs and Piece CIDs in the schema. - Removed deprecated context fields and clarified the structure for asset definitions.
…n with dgeo specifications; add invalid examples for schema validation
…pdate asset links and metadata for improved clarity and consistency
…breaking changes, new features, and migration steps
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request introduces a major new version (v1.2.0) of the dgeo extension, focused on improving queryability, schema validation, and compatibility with pgstac and the STAC API. The update includes breaking changes to the schema and example files, new fields for CID discovery, asset-level metadata, and improved documentation and migration guidance.
Key highlights:
dgeo:assetsarray is replaced by a flat, queryabledgeo:cidsarray.dgeo:cid,dgeo:cid_profile) are now supported, enabling better CID-to-asset correlation.Most important changes:
Schema and Validation Improvements
dgeo:assetswith a flat, requireddgeo:cidsarray, introduces optionaldgeo:piece_cids, and adds asset-leveldgeo:cidanddgeo:cid_profilefields. Enforces stricter validation with regex patterns for CIDs, uniqueness, and minimum array lengths. [1] [2]item-invalid.jsonto demonstrate schema enforcement for required fields, format validation, uniqueness, and minimum array constraints.Breaking Changes and Asset Model Updates
item.json,item-core.json,collection.json) to use the new flatdgeo:cidsarray and asset-level fields, removing the old nesteddgeo:assetsstructure anddgeo:context. Asset roles, descriptions, and naming now use standard STAC asset keys and fields. [1] [2] [3] [4] [5]Documentation and Migration Guidance
CHANGELOG.mddetailing all breaking changes, new features, migration steps, and schema improvements. References a new migration guide and provides upgrade instructions.General Improvements
These changes are a major step toward making dgeo assets more discoverable, interoperable, and standards-compliant, but require all users to migrate existing data to the new schema.