You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
NOTE: The GeoJSON above is indeed invalid, as links although it can be empty, it is mandatory, but the catalogue should not accept it, or tolerate it and assume it empty "links": []. With the current behavior instead, a bad GeoJSON pushed by mistake can make the entire catalogue query fail.
Description
If you POST a GeoJSON to the new transaction endpoint
/collections/{collectionId}/items
which does not contain alinks
field, likethe product will be correctly ingested (call returns
201 created
) but the catalogue will then fail to retreive items, failing with the error:NOTE: The GeoJSON above is indeed invalid, as
links
although it can be empty, it is mandatory, but the catalogue should not accept it, or tolerate it and assume it empty"links": []
. With the current behavior instead, a bad GeoJSON pushed by mistake can make the entire catalogue query fail.Environment
geopython/pycsw:eoepca-2.0.0-beta1
Steps to Reproduce
POST to
/collections/{collectionId}/items
the following GeoJSON:then try to perform a GET items from the catalogue. An
Internal Server Error
will appear.If you then delete the item, the errors disappears
Additional Information
Catalogue should check the validity of the GeoJSON before ingesting it, and check
links
fields exists or assume it emptyThe text was updated successfully, but these errors were encountered: