Merge branch 'main' into reverse-coords

Author: jonhealy1

.github/workflows/test-runner.yml

@@ -18,10 +18,10 @@ jobs:
     steps:
       - uses: actions/checkout@v3
 
-      - name: Set up Python 3.10
+      - name: Set up Python 3.12
         uses: actions/setup-python@v4
         with:
-          python-version: "3.10"
+          python-version: "3.12"
 
       - name: Install dependencies
         run: |
@@ -41,7 +41,7 @@ jobs:
     runs-on: ubuntu-latest
     strategy:
       matrix:
-        python-version: ["3.8", "3.9", "3.10", "3.11", "3.12", "3.13"]
+        python-version: ["3.9", "3.10", "3.11", "3.12", "3.13"]
 
     steps:
       - uses: actions/checkout@v3

CHANGELOG.md

@@ -8,18 +8,36 @@ The format is (loosely) based on [Keep a Changelog](http://keepachangelog.com/)
 
 ### Added
 
+- Added validation for bounding boxes that cross the antimeridian (180°/-180° longitude) ([#121](https://github.com/stac-utils/stac-check/pull/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](https://github.com/stac-utils/stac-check/pull/122))
+- Added check to verify that bbox matches item's polygon geometry ([#123](https://github.com/stac-utils/stac-check/pull/123))
 - Added configuration documentation to README ([#124](https://github.com/stac-utils/stac-check/pull/124))
 - Added validation for geometry coordinates order to detect potentially reversed lat/lon coordinates ([#125](https://github.com/stac-utils/stac-check/pull/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 `--pydantic` option for validating STAC objects using stac-pydantic models, providing enhanced type checking and validation ([#126](https://github.com/stac-utils/stac-check/pull/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](https://github.com/stac-utils/stac-check/pull/126))
+
+### Fixed
+
+- Fixed collection summaries check incorrectly showing messages for Item assets ([#121](https://github.com/stac-utils/stac-check/pull/127))
 
 ### Updated
 
 - Improved README with table of contents, better formatting, stac-check logo, and enhanced documentation ([#122](https://github.com/stac-utils/stac-check/pull/122))
 - Enhanced Contributing guidelines with step-by-step instructions ([#122](https://github.com/stac-utils/stac-check/pull/122))
 
+### Removed 
+
+- Support for Python 3.8 ([#121](https://github.com/stac-utils/stac-check/pull/121))
+
 ## [v1.6.0] - 2025-03-14
 
 ### Added

README.md

@@ -86,6 +86,7 @@ Options:
                            (enabled by default).
   --header KEY VALUE       HTTP header to include in the requests. Can be used
                            multiple times.
+  --pydantic               Use stac-pydantic for enhanced validation with Pydantic models.
   --help                   Show this message and exit.
 ```
 
@@ -130,6 +131,8 @@ linting:
   links_self: true
   # check if geometry coordinates are potentially ordered incorrectly (longitude, latitude)
   geometry_coordinates_order: true
+  # check if a bbox that crosses the antimeridian is correctly formatted
+  check_bbox_antimeridian: true
 
 settings:
   # Number of links before the bloated links warning is shown

sample_files/1.0.0/bad-item.json

@@ -8,7 +8,7 @@
     -122.59750209,
     37.48803556,
     -122.2880486,
-    37.613537207
+    37.613531207
   ],
   "geometry": {
     "type": "Polygon",

sample_files/1.0.0/invalid-antimeridian-bbox.json

@@ -0,0 +1,23 @@
+{
+  "stac_version": "1.0.0",
+  "type": "Feature",
+  "id": "invalid-antimeridian-bbox",
+  "bbox": [-170, -10, 170, 10],
+  "geometry": {
+    "type": "Polygon",
+    "coordinates": [
+      [
+        [-170, -10],
+        [170, -10],
+        [170, 10],
+        [-170, 10],
+        [-170, -10]
+      ]
+    ]
+  },
+  "properties": {
+    "datetime": "2023-01-01T00:00:00Z"
+  },
+  "links": [],
+"assets": {}
+}

setup.py

@@ -3,7 +3,7 @@
 
 from setuptools import find_packages, setup
 
-__version__ = "1.6.0"
+__version__ = "1.7.0"
 
 with open("README.md", "r") as fh:
     long_description = fh.read()
@@ -20,7 +20,7 @@
         "requests>=2.32.3",
         "jsonschema>=4.23.0",
         "click>=8.1.8",
-        "stac-validator>=3.6.0",
+        "stac-validator[pydantic]>=3.7.0",
         "PyYAML",
         "python-dotenv",
     ],
@@ -37,6 +37,6 @@
     license="MIT",
     long_description=long_description,
     long_description_content_type="text/markdown",
-    python_requires=">=3.8",
+    python_requires=">=3.9",
     tests_require=["pytest"],
 )

stac_check/cli.py

@@ -91,6 +91,13 @@ def intro_message(linter: Linter) -> None:
         f"Validator: stac-validator {linter.validator_version}", bg="blue", fg="white"
     )
 
+    # Always show validation method
+    validation_method = (
+        "Pydantic" if hasattr(linter, "pydantic") and linter.pydantic else "JSONSchema"
+    )
+    click.secho()
+    click.secho(f"Validation method: {validation_method}", bg="yellow", fg="black")
+
     click.secho()
 
 
@@ -111,7 +118,17 @@ def cli_message(linter: Linter) -> None:
 
     """ schemas validated for core object """
     click.secho()
-    if len(linter.schema) > 0:
+
+    # Determine if we're using Pydantic validation
+    using_pydantic = hasattr(linter, "pydantic") and linter.pydantic
+
+    # For Pydantic validation, always show the appropriate schema model
+    if using_pydantic:
+        click.secho("Schemas validated: ", fg="blue")
+        asset_type = linter.asset_type.capitalize() if linter.asset_type else "Item"
+        click.secho(f"    stac-pydantic {asset_type} model")
+    # For JSONSchema validation or when schemas are available
+    elif len(linter.schema) > 0:
         click.secho("Schemas validated: ", fg="blue")
         for schema in linter.schema:
             click.secho(f"    {schema}")
@@ -194,10 +211,15 @@ def cli_message(linter: Linter) -> None:
     multiple=True,
     help="HTTP header to include in the requests. Can be used multiple times.",
 )
+@click.option(
+    "--pydantic",
+    is_flag=True,
+    help="Use stac-pydantic for enhanced validation with Pydantic models.",
+)
 @click.command()
 @click.argument("file")
 @click.version_option(version=importlib.metadata.distribution("stac-check").version)
-def main(file, recursive, max_depth, assets, links, no_assets_urls, header):
+def main(file, recursive, max_depth, assets, links, no_assets_urls, header, pydantic):
     linter = Linter(
         file,
         assets=assets,
@@ -206,6 +228,7 @@ def main(file, recursive, max_depth, assets, links, no_assets_urls, header):
         max_depth=max_depth,
         assets_open_urls=not no_assets_urls,
         headers=dict(header),
+        pydantic=pydantic,
     )
     intro_message(linter)
     if recursive > 0: