HOTFIX
In some cases, special characters such as %, _, and [ could confuse the search engine, causing unexpected or incomplete search results. The search functionality has been updated to correctly handle these characters and return the expected occupancies.
Special characters are no longer treated as special cases.
GET/api/v1/public-domain-occupancies: Search public domain occupancies by reference now works more reliably.
2.2.0
09/06/2026 PROD
22/05/2026 BETA
SUMMARY
Groundworks are no longer limited to a single point. Except for Cat1, groundworks can now be registered using multiple points, allowing for more flexible and accurate zone definitions.
Our email service also received an upgrade. You may now receive notifications from the new @noreply.athumi.eu domain, so make sure these emails are recognised by your systems.
We also introduced new endpoints to help detect possible conflicts earlier and more efficiently.
ADDED CALLS
GET/api/v1/entities/{gipodId}/conflicts/geojson: Find possible conflicts based on an existing GipodId
GET/api/v1/entities/conflicts/geojson: Find possible conflicts based on specific parameters
UPDATED CALLS
POST /api/v1/groundworks: Groundworks, except for Cat1, can now be registered using a zone of type MultiPoint.
PATCH/api/v1/groundworks/{gipodId}: Groundworks, except for Cat1, can now be edited using a zone of type MultiPoint.
2.1.1
10/03/2026 PROD
09/03/2026 BETA
HOTFIX
On some endpoints the scope gipod_org_read was secretly required. In our ongoing effort to improve the documentation, we aligned the application with the documentation. The hidden requirements are removed.
Archiving notifications had a brief moment of rebellion after the last release and stopped doing its job. Order has now been restored.
Resolved an issue where some mail servers and our notifications were no longer on speaking terms. They have now talked it out and are communicating again. Your mailboxes won’t be empty anymore!
Fixed a problem where contractors could not access the signaling permit functionality
We like to keep things simple, but some zones insist on being complex. Fixed an issue where Groundworks with complex zones refused to launch TrenchSynergyRequests.
2.1.0
02/03/2026 PROD
26/02/2026 BETA
SUMMARY
Groundworks registered by address are getting a brain upgrade. Instead of dropping a pin on a building, GIPOD now automatically calculates a proper groundwork zone right on the border between the parcel and the public domain. More accurate, more logical, less guesswork.
We added a messaging system to push information to the web application, like always this API call is available to everyone.
Once more we focused on technical improvements to keep our platform running smooth.
ADDED CALLS
GET/api/v1/messages/active: Retrieve a list of the current system messages.
BUGFIXES
Some public domain occupancies were living in the past with outdated NIS codes. We fixed the timeline and brought them safely back to the future.
TECHNICAL IMPROVEMENTS
The ‘Hinder in kaart’ link got some updates to support the changes by Geopunt
We reorganised several services to group them more logically. The result? Clearer structure and improved stability for some workers behind the scenes.
2.0.0
19/01/2026 BETA
SUMMARY
Added support for permit-exempt zones. New functionality to query, create and manage zones where permits are not required.
Squashed a number of annoying issues to make things smoother
Behind the scenes, we’ve made several solid upgrades
ADDED CALLS
GET/api/v1/permit-exempt-zones/{gipodId}: Retrieve a specific permit-exempt zone by its identifier.
GET/api/v1/permit-exempt-zones/{gipodId}/attachments/{attachmentId}: Download a specific attachment related to a permit-exempt zone.
GET/api/v1/permit-exempt-zones: Search for permit-exempt zones
GET/api/v1/permit-exempt-zones/geojson: GeoJson info on permit-exempt zones
POST /api/v1/permit-exempt-zones: Create a new permit-exempt zone.
PATCH/api/v1/permit-exempt-zones/{gipodId}: Update an existing permit-exempt zone.
DELETE /api/v1/permit-exempt-zones/{gipodId}: Delete a permit-exempt zone.
GET/api/v1/permit-exempt-zones/{gipodId}/history: changelog for a specific permit-exempt zone
GET/api/v1/permit-exempt-zones/{gipodId}/history/{position}: historic view of a specific version
UPDATED CALLS
GET/api/v1/entities: Added support for permit-exempt zone
BUGFIXES
Fixed an incorrect date filter in Request for Groundwork searches, time now behaves as expected ⏱️
Status/period notifications are now properly cleaned up when period is still ongoing.
Put an end to double notifications. Got 99 notifications but the duplicate ain’t one.
Searching on reference did not always yield results
TECHNICAL IMPROVEMENTS
Improved our build and deployment pipelines for harder, better, faster, stronger releases
Updated the authentication flow, removing Azure AD dependencies
Gave our health checks and monitoring systems new glasses
Turbocharged geographical searches for faster results where it counts
Added contact organisations property to request for groundworks and the possibility to add, modify and delete this property from a request for groundworks
Added taxonomy for permit exempt zones
ADDED CALLS
GET/api/v1/taxonomies/permit-exempt-zones/types: Potential types for a permit exempt zone
GET/api/v1/taxonomies/permit-exempt-zones/types/{typeId}: Get a specific type for a permit exempt zone
GET/api/v1/taxonomies/permit-exempt-zones/purposes: Get the purposes for a permit exempt zone
GET/api/v1/taxonomies/permit-exempt-zones/purposes/{purposeId}: Get a specific purpose for a permit exempt zone
GET/api/v1/request-for-groundworks/{gipodId}/contactorganisations/{contactId} : Get a specific contact for a request for groundworks
POST /api/v1/request-for-groundworks/{gipodId}/contactorganisations : Add a contact to a request for groundworks as PDA
PUT /api/v1/request-for-groundworks/{gipodId}/contactorganisations/{contactId} : Modify a specific contact for a request for groundworks as PDA
DELETE /api/v1/request-for-groundworks/{gipodId}/contactorganisations/{contactId} : Delete a specific contact for a request for groundworks as PDA
UPDATED CALLS
GET/api/v1/taxonomies/entitytypes: Added a new entitytype 'Uitzonderingszone'
GET/api/v1/taxonomies/zonetypes: Added a new zonetype 'UitzonderingsZone'
GET/api/v1/request-for-groundworks/{gipodId}: Added new field 'ContactOrganisation’
1.25.0
23/07/2025 PROD
27/06/2025 BETA
SUMMARY
Technical improvements to the Api gateway
Slight performance improvement
Monitoring service reworked
Healthcheck system reworked
Improvements for Request For Groundwork
Add 2 notifications for Request For Groundwork
Request For Groundwork revoked by Local Governments
Request For Groundwork revoked by Applicant
Performance improvement to DeLijn import process
ADDED CALLS
GET/api/v1/taxonomies/request-for-groundworks/reasontypes: Potential reasons for the withdrawal of a request for groundwork
PATCH /api/v2/request-for-groundworks/{gipodId}:
New validation rules for statusses ‘Ingetrokken door aanvrager’ & ‘Ingetrokken door domeinbeheerder’.
Added 'ReasonTypeId' to the status patchitem.
Added support to update 'ApplicantReference'
Renamed field ‘ReasonStatus’ to ‘Reason’
UPDATED CALLS
GET/api/v1/taxonomies/statuses: Altered labels and added extra status 'Ingetrokken door domeinbeheerder'
GET/api/v1/request-for-groundworks: Extended search functionality for new fields ‘RevocationDate', ‘DecisionDate’ and 'ApplicantReference’
GET/api/v1/request-for-groundworks/{gipodId}: Added new fields ‘RevocationDate', 'DecisionDate’ and 'ApplicantReference’
Use the new endpoint:/api/v2/request-for-groundworks/{gipodId}
POST /api/v1/groundworks/{gipodId}/request-for-groundworks: Added optional 'ApplicantReference' field
POST /api/v1/trench-synergies/{gipodId}/request-for-groundworks: Added optional 'ApplicantReference' field
BUGFIX
We've updated our geojson endpoints: even if you forget the geojson request header, you'll still get valid GeoJSON. Call it a bugfix, call it an improvement — either way, you will get GeoJson back. 🗺️
1.24.1
23/06/2025 PROD
23/06/2025 BETA
HOTFIX
SOS a missing S! In the detail of a synergy, we renamed ContactOrganisations to ContactOrganisation. This tiny change caused an unintended breaking change. Apologies for the unexpected S-stress!
UPDATED CALLS
GET/api/v1/trench-synergies/{gipodId}:
Both properties are now available: ContactOrganisationsdeprecated and ContactOrganisation.
They return the same data, so you can keep going without any code changes.
1.24.0
18/06/2025 PROD
14/05/2025 BETA
SUMMARY
We’ve added a detailed changelog so you can track what changed, when, and by whom (organisation). On top of that you can now view specific historical versions of Gipod entities. Whether you're investigating changes or just curious about the past, it’s all at your fingertips. Time travel has never been easier.
Technical rework for the notification ‘VGW termijn bijna verstreken’.
Technical improvements to our heathcheck systems
ADDED CALLS
GET/api/v1/mobility-hindrances/{gipodId}/history: changelog for a specific mobility hindrance
GET/api/v1/mobility-hindrances/{gipodId}/history/{position}: historic view of a specific version
GET/api/v1/trench-synergies/{gipodId}/history: changelog for a specific trench synergy
GET/api/v1/trench-synergies/{gipodId}/history/{position}: historic view of a specific version
GET/api/v1/trench-synergy-requests/{gipodId}/history: changelog for a specific trench synergyrequest
GET/api/v1/trench-synergy-requests/{gipodId}/history/{position}: historic view of a specific version
GET/api/v1/events/{gipodId}/history/{position}: historic view of a specific version
GET/api/v1/works/{gipodId}/history/{position}: historic view of a specific version
GET/api/v1/groundworks/{gipodId}/history/{position}: historic view of a specific version
UPDATED CALLS
GET/api/v1/events/{gipodId}/history: changelog for a specific event, updated response format
GET/api/v1/works/{gipodId}/history: changelog for a specific work, updated response format
GET/api/v1/groundworks/{gipodId}/history: changelog for a specific groundwork, updated response format
BUGFIX
Updates to an identical geographical location but with a different coordinate order will no longer register an irrelevant change.
1.23.1
25/04/2025 PROD
25/04/2025 BETA
HOTFIX
A change in the .NET 8 framework had an impact on the performance of the public domain occupancy search when looking for specific types. That issue has now been resolved.
Some users were receiving incorrect notifications for status/period. From now on you’ll once again get the right notifications.
1.23.0
10/04/2025 PROD
01/04/2025 BETA
SUMMARY
Our API jumped from .NET 6 to .NET 9, and our Gateway took the leap from .NET 8 to .NET 9
Even more changes under the hood: We improved our release process
BUGFIX
The gateway was acting like a picky bouncer—occasionally turning away guests with valid invites. We've fixed a rare issue to ensure that valid tokens always get you in.
1.22.1
01/04/2025 PROD
31/03/2025 BETA
HOTFIX
Fixed a rare issue where the calculation of the public domain owner interfered with other processes
Added Diversions-functionality to MobilityHindrance
Performance improvements to MobilityHindrance search
Added extra information about who triggered a notification
Added functionality to determine the public domain administrators
ADDED CALLS
POST /api/v1/mobility-hindrances/{gipodId}/diversions: Register a diversion for a mobilityhindrance
GET/api/v1/mobility-hindrances/{gipodId}/diversions/{diversionId}: Get the details of a diversion
PATCH /api/v1/mobility-hindrances/{gipodId}/diversions/{zoneId}: Modify a diversion
DELETE /api/v1/mobility-hindrances/{gipodId}/diversions/{zoneId}: Delete a diversion
GET/api/v1/mobility-hindrances/zones/geojson: GeoJson info on mobilityhindrances zones
GET/api/v1/mobility-hindrances/diversions/geojson: GeoJson info on mobilityhindrances diversions
GET/api/v1/public-domain-occupancies/{gipodId}/public-domain-administrators: Get information on the public domain administrators and their generalpermits for a given groundwork
UPDATED CALLS
GET/api/v1/notifications: Added TriggeringOrganisation to the response
GET/api/v1/notifications/{notificationId}: Added TriggeringOrganisation to the response
GET/api/v1/taxonomies/mobility-hindrance/consequencetypes: Altered the tree structure and added consequencetypes for diversions
GET/api/v1/mobility-hindrances/{gipodId}: Added diversions to the response
GET/api/v1/mobility-hindrances: Added diversions to the response
POST /api/v1/mobility-hindrances: Added MobilityHindranceDiversion to the request
GET/api/v1/public-domain-occupancies: Added search filter for public domain administrators
DEPRECATED CALLS
Friendly reminder: Our deprecated API endpoints will be gradually phased out. To ensure uninterrupted service, please update your integrations to the latest endpoints. Below is a list of all affected endpoints and their deprecation dates.
GET/api/v1/mobility-hindrances/geojson: deprecated
Use the new endpoints:
GET/api/v1/mobility-hindrances/zones/geojson
GET/api/v1/mobility-hindrances/diversions/geojson
POST /api/v1/groundworks/{gipodId}/attachments: deprecatedsince 9/2022
Our notifications were a little too quick, instantly alerting you the moment a status/period combo went wrong—like an overenthusiastic alarm clock. We have hit the snooze button and added a 3-hour grace period, giving you a fair chance to fix things before the notifications start nagging! ⏰
The notification “TrenchSynergyRequest increased by 50m²” was a bit too enthusiastic since release 1.20.0. Turns out, our notification system had a habit of rounding up - just like gentlemen - when discussing size. We've recalibrated it to ensure that 50m² actually means 50m². No more unnecessary exaggerations! 📏
The notification 'Synergy Pilot transferred' did not mention the correct triggering organisation in the data. Thanks to the new TriggeringOrganisation property we can now clearly state who this was.
The notifications “Add groundworks before deadline 2” could disappear for all participants when an organisation added their groundwork. It’s unclear whether they were misplaced, or simply abducted by aliens. Either way, they’re back and here to stay … till you resolve them!
1.21.1
05/02/2025 PROD
05/02/2025 BETA
HOTFIX
Fixed a rare bug where the operational tools stubbornly refused to update the signaling permit URI setting
1.21.0
02/01/2025 PROD
15/12/2024 BETA
SUMMARY
Municipal mergers 2025
Merging organisations
Remark: The 'CreatedBy' values will not be updated. The original CreatedBy organisation will remain unchanged.
Ownership transfer functionality to ensure a smooth transition
Adjustments to municipality boundaries
Enhancements to operational tools for improved management
BUGFIX
Some data in Hinder in Kaart wasn’t mapped correctly, causing unexpected hindrances. We've corrected the data.
1.20.2
16/12/2024 PROD
13/12/2024 BETA
HOTFIX
Refined calculation of the publicdomainadministrators in the area of Stad Antwerpen & Port of Antwerp-Bruges
1.20.1
10/12/2024 PROD
04/12/2024 BETA
HOTFIX
Requests for groundwork can no longer be moved to ‘In behandeling’ after the response period has expired.
Our system got a bit confused when duplicate attachments were submitted for the General Permit. We’ve added extra validation to ensure every attachment is unique.
Resolved an issue where new GeneralPermits were not displayed. This was caused by a processing error in areas with a high volume of public domain occupancies. Updates should now be visible as expected.
1.20.0
21/11/2024 PROD
20/11/2024 BETA
SUMMARY
Reworked the backend of the notification system (with focus on notifications for TrenchSynergy, TrenchSynergyRequest and SignalingPermit).
Added an extra hindrance consequence: “Parkeerverbod”
BUGFIX
We taught our API & documentation to remember its own name! The API & documentation sometimes referred itself with the wrong hostname URL. Now, it’s displaying the correct URL every time.
A slight deviation was identified in the contours of the shapefile that outlines the public domain administrators. We’re pleased to share that this has now been fully resolved, ensuring the shapefile is once again perfectly accurate.
GIPOD serves as a crucial data broker for various external systems (ex. ‘Hinder in Kaart'). Previously, when these external systems operated slower than expected, the health check inaccurately flagged GIPOD as unhealthy. To address this, we have introduced a higher threshold for communication with non-essential systems, ensuring that health checks now provide a more accurate and reliable status report.
We’ve reworked the notifications for incorrect status/period in release 1.19.0. This had unintentionally generated additional alerts for "niet-concreet gepland" and "voorontwerp." These extra notifications have now been removed, and we’ve ensured they won’t appear again.
Oops! It seems two endpoints introduced in 1.18.0 decided to play hide-and-seek and weren’t accessible for integrations. But don’t worry, the game is over! /api/v1/mobility-hindrances/geojson and /api/v1/trench-synergies/geojson are now back in action and ready for all integrators to use.
Size does matter! Creating or updating collaboration zones with large areas wasn’t possible since release 1.13.1. We’ve fixed the issue because we believe in big collaborations for big impact. So go ahead, maximize your collaborative spirit, and take up all the space you need.
1.19.1
06/11/2024 PROD
05/11/2024 BETA
HOTFIX
In version 1.18.2 we encountered a hiccup with uploading files to the /api/v2/groundworks/{gipodId}/attachments endpoint, which temporarily disrupted attachment uploads. We're happy to report that everything is back to normal. Thanks for your patience, and happy uploading!
1.19.0
29/10/2024 PROD
09/10/2024 BETA
SUMMARY
Add 2 notifications for Annual Signaling Permit
Annual Signaling Permit requested for Local Governments
Annual Signaling Permit updated for Applicant
We've flipped the switch on the old PublicAPI and some other legacy systems. Yes, this was announced ages ago. So, if you're still using them, now's the time to panic!
Improvement to DeLijn impact search. Added the option to search by municipality.
BUGFIX
Reworked the notification for incorrect status/period.
1.18.2
21/10/2024 PROD
01/10/2024 BETA
As part of our ongoing efforts to reduce costs, we have transitioned from the Apigee Gateway to a more cost-efficient gateway solution. Don’t worry, it’s just as fast, but now with extra savings!
1.18.1
19/09/2024 PROD
18/09/2024 BETA
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 PROD
27/08/2024 BETA
SUMMARY
Support for GeoJson searches with new search endpoints
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 BETA
SUMMARY
Endpoints for Annual Signaling Permit
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 PROD
30/07/2024 BETA
HOTFIX
Updates to the zone of public domain occupancies were not processed correctly towards Geoselection and Geopunt.
30/07/2024 PROD
30/07/2024 BETA
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
These services have also decided to follow the staging environment’s example:
Geosecure fallback URLs have been discontinued on all environments
Legacy Geoselections services have been discontinued on all environments
Legacy Public api services have been discontinued on the test and beta environments
1.16.0
27/06/2024 PROD
27/06/2024 BETA
SUMMARY
Upgrade internal tools (GIPOD admin only)
Added settings for Annual Signaling Permit in internal tools (GIPOD admin only)
UPDATED CALLS
GET/api/v1/localgovernments: Added properties ‘AnnualSignalingPermitEnabled' and 'AnnualSignalingPermitToolUri’
1.15.0
30/05/2024 PROD
12/05/2024 BETA
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.
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 PROD
SUMMARY
The functionality “General Permit Groundworks” is activated in production. See version 1.13.0 and further for more information.
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)
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.
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!
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.
