Version | Datum | Release notes |
---|
1.18.1 | 19/09/2024 18/09/2024 | HOTFIX Fixed a rare issue where parts of a multipolygon were not correctly registered—seems they decided to play a little hide and seek! |
1.18.0 | 12/09/2024 27/08/2024 | SUMMARY ADDED CALLS GET /api/v1/public-domain-occupancies/geojson : Search public domain occupancies with GeoJson results. GET /api/v1/mobility-hindrances/geojson : Search mobility hindrances with GeoJson results. GET /api/v1/trench-synergies/geojson : Search trench synergies with GeoJson results.
BUGFIX Fixed an issue in the examples for the swagger api documentation Our geoservice monitoring system used to think “no news is good news” when one specific third-party services went down. Now, it’ll notice and send us a heads-up. Crisis averted!
|
1.17.0 | 01/08/2024 | SUMMARY ADDED CALLS GET /api/v1/annual-signaling-permits/{gipodId} :Returns details of an annual signaling permit GET /api/v1/annual-signaling-permits/{gipodId}/attachments/{attachmentId} :Download attachment of an annual signaling permit GET /api/v1/annual-signaling-permits : Search for annual signaling permits POST /api/v1/annual-signaling-permits : Register an annual signaling permit PUT /api/v1/annual-signaling-permits/{gipodId}/applicant/contactorganisations : Update the contact information for the applicant of the annual signaling permit PUT /api/v1/annual-signaling-permits/{gipodId}/owner/contactorganisations : Update the contact information for the owner (local government) of the annual signaling permit PUT /api/v1/annual-signaling-permits/{gipodId}/approve : As a local government approve the annual signaling permit PUT /api/v1/annual-signaling-permits/{gipodId}/decline : As a local government decline the annual signaling permit PUT /api/v1/annual-signaling-permits/{gipodId}/revoke : As a local government revoke the annual signaling permit
|
1.16.1 | 31/07/2024 30/07/2024 | HOTFIX |
| 30/07/2024 30/07/2024 | SUMMARY After many years of hard work, our staging environment has decided to get its summer body ready and take a permanent vacation. Yes, it’s time for it to hit the beach and relax! But don’t worry, our beta environment has been hitting the gym and is eager to take on your test requests with renewed energy and enthusiasm.
REMOVED RESOURCES |
1.16.0 | 27/06/2024 27/06/2024 | SUMMARY UPDATED CALLS |
1.15.0 | 30/05/2024 12/05/2024 | SUMMARY Added an extra hindrance consequence: “Tijdelijk tweerichtingsverkeer” Added extra validation for invalid PATCH requests. This patch patches the patch endpoints! Migrate GTMF client (GRB-impact) to new URI
UPDATED CALLS “GET /api/v1/organisations”: Added parameter ‘isRootOrganisation’ to filter on root and non-root organisations “GET /api/v1/public-domain-occupancies”: Added parameter ‘rootownerid’ to filter by one or more root organisations. “GET /api/v1/public-domain-occupancies”: Added rootOwner to the items in the resultset “GET /api/v1/public-domain-occupancies”: Added parameter ‘publicdomainadministratorid’ to filter by one or more public domain administrators, on which domain the occupancy lies. “GET /api/v1/public-domain-occupancies”: Added parameter ‘hasGeneralPermitForPublicDomainAdministratorId' to filter the public domain occupancies with a general permit for the specified public domain administrator id. “GET /api/v1/public-domain-occupancies”: Added parameter ‘generalPermitValidity' to filter the general permit validity. This can only be used in combination with the parameter ‘hasGeneralPermitForPublicDomainAdministratorId’. See taxonomy 'taxonomies/general-permit-groundworks/validities' for values for this parameter. “PATCH /api/v1/mobility-hindrances/{gipodId}/signaling-permits/{signalingPermitId}”: Added “StatusReason”, used when declining a signaling permit. “GET /api/v1/mobility-hindrances/{gipodId}/signaling-permits/{signalingPermitId}”: Added “StatusReason”
BUGFIX Signaling permits with a reference exceeding 100 characters will no longer cause a server error, but will now return the correct Bad Request response (400). Our OpenApi specification did not expose the optional if-match header. “GET /api/v1/groundworks/{gipodId}”: The addressRepresentation did not refer to the correct OSLO URI. Groundworks registered as POINT-wkt are saved as POINT-wkt instead of a buffered polygon. “PATCH /api/v1/groundworks/{gipodId}”: patching “IsReadyRequestForGroundwork” with the existing value is ignored from now on, 'cuz it has no added value. The LastModifiedOn-timestamp will not be modified either.
|
/ | 02/04/2024 | SUMMARY The functionality “General Permit Groundworks” is activated in production. See version 1.13.0 and further for more information. |
1.14.3 | 26/03/2024 24/03/2024 | UPDATE |
1.14.2 | 07/03/2024 07/03/2024 | HOTFIX |
1.14.1 | 23/02/2024 23/02/2024 | HOTFIX |
1.14.0 | 18/01/2024 08/01/2024 | 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 19/11/2023 | HOTFIX |
1.13.7 | 02/12/2023 02/11/2023 | HOTFIX |
1.13.6 | 01/12/2023 30/11/2023 | HOTFIX |
1.13.5 | 23/11/2023 23/11/2023 | HOTFIX |
1.13.4 | 23/11/2023 14/11/2023 | SUMMARY |
1.13.3 | 08/11/2023 08/11/2023 | SUMMARY HOTFIX |
/ | 30/10/2023 30/10/2023 | SUMMARY |
1.13.2 | 23/10/2023 19/10/2023 | SUMMARY |
1.13.1 | 10/10/2023 3/10/2023 | 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 |
1.13.0 | 13/09/2023 28/08/2023 17/08/2023 | SUMMARY Info |
---|
The activation date of the “General Permit Groundworks” functionality in PROD is to be decided and confirmed by the GIPOD Business Werkgroep. |
ADDED CALLS: “POST /api/v1/general-permit-groundworks": Register a new general permit groundworks “PUT /api/v1/general-permit-groundworks/{gipodID}/approve”: Approve general permit groundworks “PUT /api/v1/general-permit-groundworks/{gipodID}/decline”: Decline general permit groundworks “PUT /api/v1/general-permit-groundworks/{gipodID}/revoke”: Revoke general permit groundworks “PUT /api/v1/general-permit-groundworks/{gipodID}/applicant/contactorganisations”: Update applicant contact information “PUT /api/v1/general-permit-groundworks/{gipodID}/public-domain-administrator/contactorganisations”: Update domain administrator contact information “GET /api/v1/general-permit-groundworks/{gipodID}": Get the details of a general permit groundworks “GET /api/v1/general-permit-groundworks/{gipodID}/attachments/{attachmentId}": Get an attachment of a general permit groundworks “GET /api/v1/general-permit-groundworks": Search for general permit groundworks
|
1.12.5 | 17/08/2023 16/08/2023 16/08/2023 | HOTFIX |
1.12.4 | 31/07/2023 31/07/2023 | HOTFIX |
1.12.3 | 26/07/2023 26/07/2023 | HOTFIX |
1.12.2 | 10/07/2023 10/07/2023 | HOTFIX |
1.12.1 | 15/05/2023 15/05/2023 11/05/2023 | BUGFIX |
1.12.0 | 27/04/2023 21/04/2023 07/04/2023 | SUMMARY Add data projectors for WMS/WFS databases Add API access to facilitate contractor usecases in GUI Add status “Ingetrokken” on signaling permit, to allow a contractor to retract a signaling permit request
|
1.11.2 | 21/03/2023 21/03/2023 21/03/2023 | SUMMARY |
1.11.1 | 20/03/2023 13/03/2023 09/03/2023 | SUMMARY |
1.11.0 | 16/02/2023 09/02/2023 01/02/2023 | SUMMARY BUGFIX CreatedOn and CreatedBy data was incorrect for new request for groundworks (calculated by GIPOD system) Notification “SV aangevraagd in uw gemeente” didn’t expire when the signaling permit was deleted, this is now fixed
|
1.10.10 1.10.11 | 08/02/2023 08/02/2023 08/02/2023 | HOTFIX |
1.10.9 | 23/12/2022 23/12/2022 22/12/2022 | HOTFIX |
1.10.4 | 1/12/2022 1/12/2022 1/12/2022 | HOTFIX |
1.10.3 | 30/11/2022 30/11/2022 30/11/2022 | HOTFIX |
1.10.2 | 29/11/2022 29/11/2022 29/11/2022 | HOTFIX |
1.10.1 | 24/11/2022 24/11/2022 24/11/2022 | HOTFIX |
1.10.0 | 22/11/2022 17/11/2022 10/11/2022 | SUMMARY 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
|
1.9.1 | 20/09/2022 20/09/2022 19/09/2022 | SUMMARY |
1.9.0 | 16/09/2022 15/09/2022 23/08/2022 | SUMMARY Add ready for request for groundwork Mark contact as “request for groundwork”-contact 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. Search public domain occupancies: You can now search Groundworks that are marked as ready for request for groundwork. 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. Status |
---|
colour | Red |
---|
title | 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!GET notificationtypes taxonomy: the definitions of the notification types have been improved
DEPRECATED CALLS |
1.8.0 | 04/07/2022 30/06/2022 29/06/2022 | SUMMARY Mails and mail subscriptions for notifications OSLO improvements for LDES Added LDES feed for mobility-hindrance Data cleanup for Hinderpremie
ADDED CALLS Mail subscriptions : Create, modify, delete, get and search mail subscriptions LDES: LDES endpoints to get mobility hindrance feed
UPDATED CALLS 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!
|
1.7.1 | 28/03/2022 25/03/2022 25/03/2022 | SUMMARY Improved order of the notification types taxonomy. Improvements to the OSLO context. Etag and Ifmatch support improved.
BUGFIXES The notification for Approved or Rejected signaling permit request would break the notifications in some rare cases. Many bugfixes to De Lijn-impact. Calculations should now run smooth as a bus. Searching for notifications with the full tree or a subtree of notification types now yields results.
|
1.7.0 |