Check antimeridian bbox #121
Merged
Conversation
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
Collaborator
Author
|
We should probably check to make sure the bbox and the polygon fields match for items |
…ac-check into check-antimeridian
Merged
jonhealy1
added a commit
that referenced
this pull request
Jun 1, 2025
## [v1.7.0] - 2025-06-01 ### Added - Added validation for bounding boxes that cross the antimeridian (180°/-180° longitude) ([#121](#121)) - Checks that bbox coordinates follow the GeoJSON specification for antimeridian crossing - Detects and reports cases where a bbox incorrectly "belts the globe" instead of properly crossing the antimeridian - Provides clear error messages to help users fix incorrectly formatted bboxes - Added sponsors and supporters section with logos ([#122](#122)) - Added check to verify that bbox matches item's polygon geometry ([#123](#123)) - Added configuration documentation to README ([#124](#124)) - Added validation for geometry coordinates order to detect potentially reversed lat/lon coordinates ([#125](#125)) - Checks that coordinates follow the GeoJSON specification with [longitude, latitude] order - Uses heuristics to identify coordinates that may be reversed or contain errors - Provides nuanced error messages acknowledging the uncertainty in coordinate validation - Added validation for definite geometry coordinate errors ([#125](#125)) - Detects coordinates with latitude values exceeding ±90 degrees - Detects coordinates with longitude values exceeding ±180 degrees - Returns detailed information about invalid coordinates - Added dedicated geometry validation configuration section ([#125](#125)) - Created a new `geometry_validation` section in the configuration file - Added a master enable/disable switch for all geometry validation checks - Reorganized geometry validation options into the new section - Separated geometry validation errors in CLI output with a [BETA] label - Added detailed documentation for geometry validation features - Added `--pydantic` option for validating STAC objects using stac-pydantic models, providing enhanced type checking and validation ([#126](#126)) ### Enhanced - Improved bbox validation output to show detailed information about mismatches between bbox and geometry bounds, including which specific coordinates differ and by how much ([#126](#126)) ### Fixed - Fixed collection summaries check incorrectly showing messages for Item assets ([#121](#127))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
stac-utils/stac-validator#246