-
Notifications
You must be signed in to change notification settings - Fork 2
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
[RS Core DISTRIBUTION] Add GeoFootprint properties #1070
Comments
Tested on Werum testing environment:
|
@w-fsi You asked during kick-off meeting is the new GeoFootprint should
In order to keep backward compatibility, we want to add GeoFootprint next footprint property |
We should point out that this modification is not done within the elastic search index and not requiring a migration within the database. The value is formated when given out via the frontend. Both fields are existing there and provided in the format that was used in the past for backward compatibility. |
User story description: "As a end user, I would like to do GeoFootprint queries so that I can filter query by geoJson footprint."
Note: The current prip field "footprint" fit to geojson [RFC7946]. It would seem that rename this field will cover the PRIP ICD update. To be confirmed by WERUM technical leader.
Definition of ready:
Acceptance criteria:
Note : Tests can be done directly on OPS plateform (see #1071 / #1072)
Definition of Done:
The text was updated successfully, but these errors were encountered: