Technical fix concerning ovo-code for organisations
1.14.0
18/01/2024 PROD 08/01/2024 BETA
SUMMARY
Add Permit Reference to a Request For Groundwork
Add 2 notifications for general permit (requested for public domain administrator, status updated for applicant)
Various small improvements for migration to ACM/IDM
1.13.8
19/12/2023 PROD 19/11/2023 BETA
HOTFIX
Ignore unknown organisations in GIPOD organisations when calling OSLO API public-domain-administrators
1.13.7
02/12/2023 PROD 02/11/2023 BETA
HOTFIX
Fix scheduled task to clean up geoservices
1.13.6
01/12/2023 PROD 30/11/2023 BETA
HOTFIX
Fix permissions for eventstore in support API (GIPOD admin only)
1.13.5
23/11/2023 PROD 23/11/2023 BETA
HOTFIX
Hotfix OSLO scheme for MetaDataLd: Changed AgentLd to OrganisationLd
1.13.4
23/11/2023 PROD 14/11/2023 BETA
SUMMARY
Migrate GTMF client (GRB-impact) to ACM/IDM
Added task to rename Telenet organisation to Wyre
1.13.3
08/11/2023 PROD 08/11/2023 BETA
SUMMARY
Improvements in performance of geographical search of mobility hindrance
HOTFIX
Reduced geometry validations: a feature should intersect with the Bbox of Flanders instead of being completely inside the Bbox of Flanders,
/
30/10/2023 PROD 30/10/2023 BETA
SUMMARY
Improvement on governance of (sub)organisations - GIPOD admin only
1.13.2
23/10/2023 PROD 19/10/2023 BETA
SUMMARY
Adapted data schema used by geowebservices (WMS/WFS) to improve performance
Added extra information to geowebservices needed for Geopunt/Hinder in kaart
1.13.1
10/10/2023 PROD 3/10/2023 BETA
SUMMARY
Improve performance of search API: bad performance when requesting bbox bigger than flanders, or combined bbox and niscode is now improved
Add validation on geometry write endpoints: from now on invalid WKT’s, coördinates outside Flanders and areas bigger than 100km² will no longer be accepted by the system
Add call that allows the GIPOD support team to delete an (empty) organisation
Connect to Wegenregister via WFS instead of sync trough download service
HOTFIX
Fixed bug causing multiple request for groundworks to be sent out for a single request
Added History endpoints for Groundwork, Work and Events
Internal preparations for migrating away from Geosecure
Block request for groundworks for groundworks with no attachments
Calculation of domain administrators for request for groundworks is now based on GRB and Wegenregister, fixing an issue that groundworks on the side of regional roads weren’t correctly dispatched to the domain administrator (AWV).
Added caching to mobility hindrance LDES endpoint
Improved stability to authentication mechanism
ADDED CALLS
“GET /api/v1/events/{gipodId}/history": Get the history of changes to an event
“GET /api/v1/groundworks/{gipodId}/history": Get the history of changes to a groundwork
“GET /api/v1/works/{gipodId}/history": Get the history of changes to work
UPDATED CALLS
“POST /api/v1/groundworks/{gipodId}/request-for-groundworks”: validation added, this call will now fail if there are no attachments on the groundwork
“POST /api/v1/trench-synergies/{gipodId}/request-for-groundworks”: validation added, this call will now fail if there are no attachments on any groundwork in the synergy
Mark attachment as “request for groundweork”-attachment
Rename property “reasonStatusNoAgreement” to “reasonStatus” on request for groundworks
Improve definitions in notifications type taxonomy
ADDED CALLS
“GET /api/v1/taxonomies/context-tags“: Taxonomy for context-tags.
“POST /api/v2/groundworks/{gipodId}/attachments”: Version 2 endpoint to upload groundwork attachments. This endpoint allows to add context-tags to an attachment.
“PUT /api/v1/groundworks/{gipodId}/attachments/{attachmentId}/context-tags”: Add or update context-tags of an existing groundwork attachment. Only this context-tag is possible for the moment GET /api/v1/taxonomies/context-tags/17709a38-2019-4172-b77f-dfbc3509928e.
UPDATED CALLS
GET / POST / PATCH groundworks now includes an element “IsReadyRequestForGroundwork” indicating that the groundwork is ready to be sent out to domain administrators.
When adding or updating a contactorganisation for groundworks, there is now the possibility to add context-tags to the contactinformation. This context-tag is possible for the moment “GET /api/v1/taxonomies/context-tags/17709a38-2019-4172-b77f-dfbc3509928e". This context-tag is indicating the contactinformation is relevant for request for groundworks. For a contactorganisation with role “Verantwoordelijke vraag voor grondwerken“ this context-tag is set automatically, all old contact data have been updated.
breaking change “GET, PATCH /api/v1/request-for-groundworks/{gipodId}”: The element “reasonStatusNoAgreement” has been removed and replaced by element “reasonStatus”. Warning, this is a breaking change!
Upload groundwork attachment : “POST /api/v1/groundworks/{gipodId}/attachments” is deprecated. Please use v2 version “POST /api/v2/groundworks/{gipodId}/attachments“.
Signaling Permit Application Attachment: Not only the applicant, but also the owner of the application can now upload an attachment. You now have a licence to … upload!
OSLO context: The provided context contained some errors. We also added some missing terms.
BUGFIXES
In some rare timezone related cases create and edit of a groundwork, a work or an event could result in an invalid status/period combination. We improved the validation.
Related to this invalid status/period combination, users could receive an incorrect notification
Related to this invalid status/period combination, some notifications never disappeared after resolving the status or period/timeschedule.
During the initial Gipod release, some data of the old platform was mapped to an unsatisfactory state. This caused issues for VLAIO Hinderpremie. No new data was harmed during this operation!
Public domain administrators search: now includes information about the general permit situation of the domain administrator. (generalPermitForGroundworksEnabled and generalPermitForGroundworksConditionsUri)
1.6.1
16/12/2021PROD 15/12/2021 Staging 14/12/2021 BETA
SUMMARY
Add missing functionality to manage permit-attachments and permit-urls for Requests for Groundwork
Added the option to withdraw a Requests for Groundwork
Trying to update Signaling Permits or Mobility Hindrance properties with the current value, will no longer cause an update. No errors will be thrown, the action will just be ignored. Server says no, to unnecessary work.
1.6.0
06/12/2021PROD 29/11/2021 Staging 25/11/2021 BETA
SUMMARY
Add functionality to read, request, update, search and automatically close Requests for Groundwork
Integration with GRB
Enhancements to Entities Search endpoint
All endpoints will cap the precision of WKT-coordinates to 2 decimals
CHANGED CALLS
Search Entities (GET): Added new types: Signaling Permits and Request for Groundwork.
Some requests result in an incorrect Not Found (404). Improved logging and reworked code in an attempt to catch this volatile bug.
Last modified info was not set on some endpoints when the resource was never changed. For consistency this property is now always set.
1.5.1
05/11/2021PROD 04/11/2021 Staging 04/11/2021 BETA
HOTFIX
When using a specific combination of fields to update a Trenchsynergy, some fields were not updated. All patchkeys are once again processed correctly.
In some situations when modifying the reference of Event, Groundwork or Work, the reference was not updated but added. This resulted in 2 references. Just like the Highlander, there can be only one!
1.5.0
06/10/2021PROD 05/10/2021 Staging 01/10/2021 BETA
SUMMARY
Add functionality to request and manage for Signaling Permits
Add notifications for Signaling Permits
Upgrade infrastructure code for better error detecting
Notifications for Trenchsynergies & TrenchsynergyRequests contained the wrong data since last release. This release corrects all notifications to contain the correct data.
Search MobilityHindrances (GET): Release 1.4.0 removed sorting from this endpoint. Results are sorted once again!
Detail Work / Detail Event (GET): Fixed an error in the documentation. statusFollowsTiming no longer starts with a capital S.
GW cat1 min. 30 dagen zonder hinder (hinderpremie) notification never did appear after the introduction in release 1.1.0. This notification has been notified, its vacation is over.
1.4.0
19/08/2021 Staging 12/08/2021 BETA
SUMMARY
Improvement in data quality through better data validation when deleting items
Extend search functionality with more parameters and extra details in responses
Add security for contractors (Signaling permits)
Now the grace period of one month has long ended, we will stop supporting urls not mentioned in this announcement. Please make sure you are using the correct urls.
Search TrenchSynergies (GET): Search on reference selects all items which contain the keyword, used to be only items starting with the keyword.
Search public domain occupancies (GET): Search on reference selects all items which contain the keyword, used to be only items starting with the keyword; Response contains period when period is not recurring.
You can now once again upload attachements without issues.
1.3.1
25/06/2021 PROD 25/06/2021 Staging
HOTFIX
WKT-geometries created or updated since the 1.3.0 release were not showing up in geographic searches. Search by zone and search by bbox have been vaccinated on all affected endpoints.
DeLijn routes & stops are now automaticly updated. Impact calculation will now be up-to-date with the data provided by DeLijn.
Frameworks & dependencies updated to latest stable version
BUGFIXES
WKT-geometries with a lot of vertices will no longer cause a server error
Validation of WKT-geometries was improved: Invalid zones or zones with x,y,z-coordinates were accepted by the service and will now get the correct Bad Request response (400).
When providing the value “true” the status will be changed by the Gipod system according to the provided timeschedule/periods.
When the parameters is not provided or “null” the system will assume the value to be “true”
Modify event / Modify work (PATCH):The value for status follows period can be adjusted using the patch item with key “StatusFollowsTiming”. Contrary to registering the allowed values are “true” or “false”.
BUGFIXES
When registering with an addressId some addresses could not be used. In this release the impacted addressIds are valid again.
Improved api documentation for the detail response when Work, Event, Groundwork or Hindrance are deleted.
1.1.3
26/03/2021 PROD 25/03/2021 STAGING
HOTFIX
We needed to enable the new backend system for hindrance search. The system we prepared in release 1.1.0 is now ready to be enabled. There are no new functionalities, only improvements in performance.
1.1.2
24/03/2021 PROD 23/03/2021 STAGING
HOTFIX
During the move from the legacy system to the new Gipod, Trenchsynergies did not contain the launching groundwork. This hotfix will check all data and add the missing groundwork where needed. Due to the missing groundwork, the initial trenchsynergy-zone was not correct. This fix will remediate this as well. Any updates to the trenchsynergy-zone after the initial create will not be impacted.
1.1.1
12/03/2021 PROD 12/03/2021 STAGING
HOTFIX
Searching with a combination of boundingbox, zone and/or niscode caused an error when the provided boundingbox, zone and/or niscode didn’t describe a common area. Searching with a boundingbox or zone outside Flanders could trigger this same error.
Search endpoints did not filter correct on period.
A work with period starting on 20/12/2020 00:00 and ending on 21/12/2020 00:00 was returned when querying for public domain occupancies between 21/12/2020 00:00 and 31/12/2020 00:00. As a period is defined as a half-open interval (start moment included, end moment not included) this was not correct and consistent with the other parts of the API.
1.0.5
04/02/2021 PROD 04/02/2021 STAGING
HOTFIX
When logged in with a sub-organisation the endpoint could update the main organisation details with data of the sub-organisation. The endpoint will now only update the main organisation with the correct data of the main organisation.
1.0.4
29/01/2021 PROD 29/01/2021 STAGING
HOTFIX
Modifying the zone or adding an attachment to a Work made the timeschedule disappear. Modifying the zone of an Event made the timeschedule disappear. We resolved this issue and reset missing timeschedules to the correct value No data was lost.
1.0.3
27/01/2021 PROD 27/01/2021 STAGING
HOTFIX
Modify the period of a groudwork imported from legacy in the status ‘Uitgevoerd’ will no longer cause an issue where you need to supply the GrbImpact while this is already set to ‘No Impact’
1.0.2
26/01/2021 PROD 26/01/2021 STAGING
HOTFIX
Modify contact information on a trenchsynergy imported from the legacy system, will no longer cause an incorrect ‘NotFound’ error.
Remove contact organisation on a trenchsynergy imported from the legacy system, will no longer cause an incorrect ‘NotFound’ error.
1.0.1
25/01/2021 PROD 25/01/2021 STAGING
HOTFIX
Resolved bug during removal of a mobility-hindrance zone when the same zone was tried to be removed multiple times.
Temporary fix to allow police zones Brugge and Leuven to validate mobility-hindrance.