Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix global crs codes lookup in discovery collections crs tests #255

Merged

Conversation

groldan
Copy link
Contributor

@groldan groldan commented Nov 17, 2024

  • Fix DiscoveryCollectionsStorageCrs look up of global crs
    DiscoveryCollectionsStorageCrs asserts that a /collections document complies with

    Abstract Test 3: /conf/crs/storageCrs
    Test Purpose: Verify that the storage CRS identifier is a valid value
    
    Test Method: For each collection object that includes a storageCrs property in the paths /collections and
    /collections/{collectionId}, validate that the string is also found in the crs property of the collection or, in case
    the crs property includes a value #/crs, in the global list of CRSs.
    

    but doesn't expand the collection's #/crs JSON pointer to the collections document crs list.
    This patch fixes it and adds unit tests to cover all possible cases.

  • Fix DiscoveryCollectionsDefaultCrs look up of codes in the global crs

    DiscoveryCollectionsDefaultCrs asserts that a /collections document complies with

     Abstract Test 2: /conf/crs/default-crs
     Test Purpose: Verify that the list of supported CRSs includes the default CRS.
     Requirement: /req/crs/fc-md-crs-list B
    

    but doesn't expand the collection's #/crs JSON pointer to the collections document crs list.

    This patch fixes it and adds unit tests to cover all possible cases.


Fixes #251

DiscoveryCollectionsDefaultCrs asserts that a `/collections` document
complies with

```
 Abstract Test 2: /conf/crs/default-crs
 Test Purpose: Verify that the list of supported CRSs includes the default CRS.
 Requirement: /req/crs/fc-md-crs-list B
```

but doesn't expand the collection's `#/crs` JSON pointer to the collections
document crs list.

This patch fixes it and adds unit tests to cover all possible cases.
DiscoveryCollectionsStorageCrs asserts that a `/collections` document
complies with

```
Abstract Test 3: /conf/crs/storageCrs
Test Purpose: Verify that the storage CRS identifier is a valid value

Test Method: For each collection object that includes a storageCrs property in the paths /collections and
/collections/{collectionId}, validate that the string is also found in the crs property of the collection or, in case
the crs property includes a value #/crs, in the global list of CRSs.
```

but doesn't expand the collection's `#/crs` JSON pointer to the collections
document crs list.

This patch fixes it and adds unit tests to cover all possible cases.
groldan added a commit to groldan/geoserver that referenced this pull request Nov 17, 2024
…nal fixes

Use a patched version of `ogccite/ets-ogcapi-features10:1.8-SNAPSHOT-teamengine-5.4.1`.

Currently, we require the following pull request to be applied:
[Fix global crs codes lookup in discovery collections crs tests](opengeospatial/ets-ogcapi-features10#255)
to the test suite.

This may happen again, hence we're introducing a build step to generate
the required `ogccite/ets-ogcapi-features10` image out of the
`geoserver/ets-ogcapi-features10` fork, using a branch named `geoserver/integration`.

The procedure to maintain that branch is to rebase on top of the upstream
master branch as required, and apply the additional branches with `git merge --no-ff`.
groldan added a commit to groldan/geoserver that referenced this pull request Nov 17, 2024
…nal fixes

Use a patched version of `ogccite/ets-ogcapi-features10:1.8-SNAPSHOT-teamengine-5.4.1`.

Currently, we require the following pull request to be applied:
[Fix global crs codes lookup in discovery collections crs tests](opengeospatial/ets-ogcapi-features10#255)
to the test suite.

This may happen again, hence we're introducing a build step to generate
the required `ogccite/ets-ogcapi-features10` image out of the
`geoserver/ets-ogcapi-features10` fork, using a branch named `geoserver/integration`.

The procedure to maintain that branch is to rebase on top of the upstream
master branch as required, and apply the additional branches with `git merge --no-ff`.
@groldan
Copy link
Contributor Author

groldan commented Nov 27, 2024

@bpross-52n I can't merge pull requests on this repo. Would you merge it for me please?

@dstenger
Copy link
Contributor

@groldan Sure, don't worry, we are taking care of it. This is usually done when we prepare the next Beta release.

@dstenger dstenger merged commit 70bb3e8 into opengeospatial:master Nov 27, 2024
@dstenger dstenger added this to the 1.8 milestone Nov 27, 2024
@groldan
Copy link
Contributor Author

groldan commented Nov 27, 2024

Thanks a lot, I wasn't sure what the procedure was.

groldan added a commit to groldan/geoserver that referenced this pull request Nov 27, 2024
Revert to build the
`ogccite/ets-ogcapi-features10:1.8-SNAPSHOT-teamengine-5.4.1` docker
image for ogcapi-features CITE testing from the official repository's
`master` branch now that the [requried fix](opengeospatial/ets-ogcapi-features10#255)
is merged.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
3 participants