Page Comparison

1.20.1

10/12/2024

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

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

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

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

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

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

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

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

HOTFIX

• Updates to the zone of public domain occupancies were not processed correctly towards Geoselection and Geopunt.

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

• 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

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

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

UPDATE

• Update dependencies on http://basisregisters.vlaanderen.be V1 → V2

1.14.2

07/03/2024

HOTFIX

• Improved reliability of the geoservices projector

1.14.1

23/02/2024

HOTFIX

• Technical fix concerning ovo-code for organisations

1.14.0

18/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

HOTFIX

• Ignore unknown organisations in GIPOD organisations when calling OSLO API public-domain-administrators

1.13.7

02/12/2023

HOTFIX

• Fix scheduled task to clean up geoservices

1.13.6

01/12/2023

HOTFIX

• Fix permissions for eventstore in support API (GIPOD admin only)

1.13.5

23/11/2023

HOTFIX

• Hotfix OSLO scheme for MetaDataLd: Changed AgentLd to OrganisationLd

1.13.4

23/11/2023

SUMMARY

• Migrate GTMF client (GRB-impact) to ACM/IDM

• Added task to rename Telenet organisation to Wyre

1.13.3

08/11/2023

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

SUMMARY

• Improvement on governance of (sub)organisations - GIPOD admin only

1.13.2

23/10/2023

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

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

1.13.0

13/09/2023

SUMMARY

• Upgrade .NET version

• Added general permit groundworks functionality

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

HOTFIX

• Fix calculation of domain administrators for AWV roads

1.12.4

31/07/2023

HOTFIX

• Problem solved concerning processing of changed entities

1.12.3

26/07/2023

HOTFIX

• Remove null values from url’s array from works and events response

1.12.2

10/07/2023

HOTFIX

• Remove null values from url’s array from groundwork response

1.12.1

15/05/2023

BUGFIX

• Bugfix calculation of public domain administrators for port areas

1.12.0

27/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

SUMMARY

• Fix in healthcheck

1.11.1

20/03/2023

SUMMARY

• Improvement in calculation of public domain administrators to allow zones like port area’s.

1.11.0

16/

02/

2023

09/

02/

2023

2023

SUMMARY

• Improve stability of several notifications:

  • “VGW ingediend voor uw OD”

  • “VGW akkoord”

  • “VGW beantwoord”

  • “VGW termijn verstreken”

  • “VGW termijn bijna verstreken“

  • “Periode GW valt buiten periode VGW”

  • “GW met VGW gewijzigd”

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

• An issue with duplicate contacts on trench synergy, causing a delay on the oslo read api, was fixed

1.10.9

23/12/2022

HOTFIX

• Fix calculation of domain administrators for multi-polygon zones

1.10.4

1/12/2022

HOTFIX

• Fix calculation of domain administrators for point zones

1.10.3

30/11/2022

HOTFIX

• Fix error when calling GRB to calculate road segment

1.10.2

29/11/2022

HOTFIX

• Fix calculation of domain administrators for point zones

• Fix notifications request for groundwork accepted & answered

1.10.1

24/11/2022

HOTFIX

• Fix authorization on endpoints with multiple allowed scopes

1.10.0

22/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

SUMMARY

• Improve performance of update operations

1.9.0

16/09/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

• Upload groundwork attachment : “POST /api/v1/groundworks/{gipodId}/attachments” is deprecated. Please use v2 version “POST /api/v2/groundworks/{gipodId}/attachments“.

1.8.0

04/07/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

• Search public domain occupancies: You can now search Groundworks with or without a request for groundwork.

• 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!

1.7.1

28/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

10/02/2022

SUMMARY

• New notifications for request for groundworks (see notification taxonomy)

• New notification for new signaling permit request (see notification taxonomy)

• New notifications for request to be added to synergy (see notification taxonomy)

• Add API for request to be added to synergy

• Preview: Add API for registering and reading general permits. Api’s for searching and updating will be added in a future release.

• Improved De Lijn impact calculation and data import

• Performance improvements on databases

ADDED CALLS

• Request to be added/removed from synergy

• Requests for registering and reading general permits

UPDATED CALLS

• Public domain administrators search: now includes information about the general permit situation of the domain administrator. (generalPermitForGroundworksEnabled and generalPermitForGroundworksConditionsUri)

1.6.1

16/12/2021

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/2021

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.

• Search Entities / Search public domain occupancies (GET): Added CreatedBy & CreatedOn search parameters and search results

• Search Entities / Search public domain occupancies / Search Signaling Permits / Search TrenchSynergies / … (GET): All search endpoints now support the ‘If-Match’ header

• Search Local Governments (GET): This endpoint reached the final stage and is now ready for your production environment.

• Find Domain Administrators (GET): Result is now split into organisations who use GIPOD and those who haven’t seen the light yet.

• GetNotificationTypes / GetNotifications (GET): New notification types added:

  • Inname: status en periode komen niet overeen

  • Synergie: status en periode komen niet overeen

BUGFIXES

• 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/2021

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/2021

SUMMARY

• Add functionality to request and manage for Signaling Permits

• Add notifications for Signaling Permits

• Upgrade infrastructure code for better error detecting

CHANGED CALLS

• Detail Work / Detail Event / Detail Groundwork / Detail MobilityHindrance (GET): Added niscode to zone. This property indicates the niscod-areas the zone overlaps.

• Detail Work zone / Detail Event zone / Detail Groundwork zone / Detail MobilityHindrance zone (GET): Added niscode to zone. This property indicates the niscod-areas the zone overlaps.

• Search Signaling Permits (GET): Extended search options and search results

• Upload application attachement (POST): New endpoint where an applicant can upload attachements for his signaling permit.

• GetNotificationTypes / GetNotifications (GET): Notification types for signaling permits added

• Register Request for groundwork (POST): Endpoint removed while we work on the new requirements for this feature.

BUGFIXES

• GW cat1 min. 30 dagen zonder hinder (hinderpremie) notification still had some issues to work through. It’s back on the right track.

1.4.2

02/09/2021

HOTFIX

• Notifications for Trenchsynergies & TrenchsynergyRequests contained the wrong data since last release. This release corrects all notifications to contain the correct data.

1.4.1

01/09/2021

HOTFIX

• 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

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.

CHANGED CALLS

• Delete Event / Delete Groundwork / Delete Work (DELETE): Extra business rules are added.

• Delete MobilityHindrance (DELETE): Extra business rules are added.

• Search TrenchSynergyRequests to be answered before deadline 1 (GET): Search by zone is added.

• Search TrenchSynergyRequests with groundworks to be added (GET): Search by zone is added.

• Modify TrenchSynergy (PATCH): New validation rules for status and period are added.

• 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.

• TransferPilot (PUT) / Close TrenchSynergyRequest (POST): Set description of the synergy to the description of the (new) pilot’s groundwork.

BUGFIXES

• DeLijn auto-updates did not run. System now auto-updates.

• Create SignalingPermit (POST): Fix een issue where the applicant could not register the SignalingPermit. Improved the OpenAPI documentation.

• Search public domain occupancies / Search TrenchSynergies / Search MobilityHindrances (GET): Performance improvement when filtering on large search zone

• You can now once again upload attachements without issues.

1.3.1

25/06/2021

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.

1.3.0

16/06/2021

SUMMARY

• 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).

1.2.0

16/04/2021

SUMMARY

New functionality to automatically update the status of a work or an event to follow the timing.

CHANGED CALLS

• Register event / Register work (POST): An additional parameter status follows timing has been added

  • 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

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

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

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.

1.1.0

01/03/2021

SUMMARY

In this release we focused on performance improvements for the various search endpoints.
We added a new notification for ‘Hinderpremie’.

CHANGED CALLS

• GetNotificationTypes / GetNotifications(GET): Notification type ‘GW cat1 min. 30 dagen zonder hinder (hinderpremie)’ added

• Entities / SearchMobilityHindrances / SearchPublicDomainOccupancies / SearchTrenchSynergies (GET): Performance improvements search, extra improvements on geographic searches

BUGFIXES

• 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

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

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

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

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

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.

1.0.0

21/01/2021

New GIPOD API launched.
You can view the changes prio to 1.0.0 in the Release notes 0.x.x Archive.