Release notes API

1.6.0

??/1?/2021PROD
29/11/2021 STAGING
25/11/2021 BETA

SUMMARY

• Add functionality to read, request, update, search and automaticly 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 environnement.

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

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 PROD
02/09/2021 STAGING
02/09/2021 BETA

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 PROD
19/08/2021 STAGING
19/08/2021 BETA

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

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

1.3.0

16/06/2021 PROD
07/06/2021 STAGING
26/05/2021 BETA

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 PROD
16/04/2021 STAGING
16/04/2021 BETA

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

1.1.0

01/03/2021 PROD
01/03/2021 STAGING
24/02/2021 BETA

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

1.0.0

21/01/2021 PROD

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