PB-987: Add item-search to conformance endpoint

[LukasJoss]

There are multiple issues with item-search confomance (e.g. timestamps) so for now only feature conformance has been added

[hansmannj]

Would we also need to add conformance to https://api.stacspec.org/v1.0.0/collections/?

[benschs]

If I remember correctly we don't fully comply with the "item-search".
We use content-type header application/json instead of application/geo+json, this is to optimize cloudfront.
If we don't care about this we could probably also add "https://api.stacspec.org/v1.0.0/ogcapi-features".

I found https://github.com/stac-utils/stac-api-validator useful to help test our conformance.

[LukasJoss]

@hansmannj there are more problems with conformance for item-search than just the json/geojson stuff so it is probably better to not add that for now

[benschs]

I ran the conformance validator again with the item-search which returned the following errors. I already removed any geojson issues as we decided to ignore them.

The issues are mainly around input validation.
The limit issues seem to be because we only support a max limit of 100, but the spec allows up to 10000. For the datetime parameter I guess we don't parse all input correctly. For the search with bbox and intersects I don't know what the issues are.

- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'limit': 10000} body= had unexpected status code 400 instead of 200: 
- [Item Search] : POST http://localhost:8000/api/stac/v1/search params=None body={"limit": 10000} had unexpected status code 400 instead of 200: 
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'limit': 100000} body= had unexpected status code 400 instead of 200: 
- [Item Search] : POST http://localhost:8000/api/stac/v1/search params=None body={"limit": 100000} had unexpected status code 400 instead of 200: 
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'limit': 1000000} body= had unexpected status code 400 instead of 200: 
- [Item Search] : POST http://localhost:8000/api/stac/v1/search params=None body={"limit": 1000000} had unexpected status code 400 instead of 200: 

- [Item Search] : POST http://localhost:8000/api/stac/v1/search params=None body={"bbox": [0, 0, 1, 1], "intersects": {"type": "Polygon", "coordinates": [[[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0]]]}} had unexpected status code 200 instead of 400: Search with bbox and intersects
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'bbox': '100.0,0.0,0.0,105.0,1.0,1.0'} body= had unexpected status code 400 instead of 200: 
- [Item Search] : POST http://localhost:8000/api/stac/v1/search params=None body={"bbox": [100.0, 0.0, 0.0, 105.0, 1.0, 1.0]} had unexpected status code 400 instead of 200: 
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'bbox': '100.0, 1.0, 105.0, 0.0'} body= had unexpected status code 200 instead of 400: bbox (lat 1 > lat 2)
- [Item Search] : POST http://localhost:8000/api/stac/v1/search params=None body={"bbox": [100.0, 1.0, 105.0, 0.0]} had unexpected status code 200 instead of 400: bbox (lat 1 > lat 2)

- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'datetime': '/1985-04-12T23:20:50.52Z'} body= had unexpected status code 400 instead of 200: with datetime=/1985-04-12T23:20:50.52Z extracted from an Item
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'datetime': '1985-04-12t23:20:50.000z'} body= had unexpected status code 400 instead of 200: with datetime=1985-04-12t23:20:50.000z extracted from an Item
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'datetime': '1985-04-12'} body= had unexpected status code 200 instead of 400: invalid datetime returned non-400 status code
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'datetime': '1937-01-01T12:00:27.87+0100'} body= had unexpected status code 200 instead of 400: invalid datetime returned non-400 status code
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'datetime': '1985-12-12T23:20:50.52'} body= had unexpected status code 200 instead of 400: invalid datetime returned non-400 status code
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'datetime': '1985-04-12T23:20:50.Z'} body= had unexpected status code 200 instead of 400: invalid datetime returned non-400 status code
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'datetime': '1985-04-12T23:20:50,Z'} body= had unexpected status code 200 instead of 400: invalid datetime returned non-400 status code
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'datetime': '1986-04-12T23:20:50.52Z/1985-04-12T23:20:50.52Z'} body= had unexpected status code 200 instead of 400: invalid datetime returned non-400 status code
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'datetime': '1985-04-12T23:20:50,52Z'} body= had unexpected status code 200 instead of 400: invalid datetime returned non-400 status code

- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'intersects': '{"type": "Point", "coordinates": [100.0, 0.0]}'} body= had unexpected status code 400 instead of 200: 
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'intersects': '{"type": "LineString", "coordinates": [[100.0, 0.0], [101.0, 1.0]]}'} body= had unexpected status code 400 instead of 200: 
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'intersects': '{"type": "Polygon", "coordinates": [[[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0]]]}'} body= had unexpected status code 400 instead of 200: 
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'intersects': '{"type": "Polygon", "coordinates": [[[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0]], [[100.8, 0.8], [100.8, 0.2], [100.2, 0.2], [100.2, 0.8], [100.8, 0.8]]]}'} body= had unexpected status code 400 instead of 200: 
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'intersects': '{"type": "MultiPoint", "coordinates": [[100.0, 0.0], [101.0, 1.0]]}'} body= had unexpected status code 400 instead of 200: 
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'intersects': '{"type": "MultiLineString", "coordinates": [[[100.0, 0.0], [101.0, 1.0]], [[102.0, 2.0], [103.0, 3.0]]]}'} body= had unexpected status code 400 instead of 200: 
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'intersects': '{"type": "MultiPolygon", "coordinates": [[[[102.0, 2.0], [103.0, 2.0], [103.0, 3.0], [102.0, 3.0], [102.0, 2.0]]], [[[100.0, 0.0], [101.0, 0.0], [101.0, 1.0], [100.0, 1.0], [100.0, 0.0]], [[100.2, 0.2], [100.2, 0.8], [100.8, 0.8], [100.8, 0.2], [100.2, 0.2]]]]}'} body= had unexpected status code 400 instead of 200: 
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'intersects': '{"type": "GeometryCollection", "geometries": [{"type": "Point", "coordinates": [100.0, 0.0]}, {"type": "LineString", "coordinates": [[101.0, 0.0], [102.0, 1.0]]}]}'} body= had unexpected status code 400 instead of 200: 
- [Item Search] : GET http://localhost:8000/api/stac/v1/search params={'collections': 'ch.swisstopo.swissalti3d', 'intersects': '{"type": "Polygon", "coordinates": [[[0, 0], [90, 0], [90, 90], [0, 90], [0, 0]]]}'} body= had unexpected status code 400 instead of 200: 

[hansmannj]

Thanks for checking!
Fine for me, if we drop it for the moment. What about the https://api.stacspec.org/v1.0.0/collections/ conformance class? Are we conform here and should list it?

[benschs]

@hansmannj yes, we are conform with https://api.stacspec.org/v1.0.0/collections, and it is already set.
Currently the following conformance classes are already set on stac v1:

https://api.stacspec.org/v1.0.0/core
https://api.stacspec.org/v1.0.0/collections
http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/core
http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/oas30
http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/geojson

[hansmannj]

@hansmannj yes, we are conform with https://api.stacspec.org/v1.0.0/collections, and it is already set. Currently the following conformance classes are already set on stac v1:

https://api.stacspec.org/v1.0.0/core
https://api.stacspec.org/v1.0.0/collections
http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/core
http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/oas30
http://www.opengis.net/spec/ogcapi-features-1/1.0/conf/geojson

Thanks for checking.
Sorry, misunderstanding, I was thinking of the currently productive v0.9, where it is not yet listed in the conformance endpoint.
But since we will be on v1.0 soon anyways, no need to adapt the old version's conformance endpoint.

[hansmannj]

Thanks a lot 🚀