-
Notifications
You must be signed in to change notification settings - Fork 2
Standat to Stancode
It is planned that DKJord and its related systems must change from using Standat to instead using Stancode for pollutant component parameters.
This conversion will happen in four stages:
Stage 1 of this process will be the change of DKJord to support both Standat and Stancode for all endpoints. I.e. for all input objects, where user can specify a Standat pollution parameter code, it should also be possible to instead specify a Stancode parameter code. For all output objects, the system will offer systems a choice between Standat and Stancode value.
Stage 2 should be that third party systems (JAR) change from using Standat to using Stancode.
Stage 3 will be that Grundrisk/Screening change from using Standat to using Stancode.
Stage 4 will be that DKJord removes Standat from all methods.
Stage 1 is currently planned to be released with DKJord version 24.2 (May 20, 2024).
This may although be postponed if the development team before this date are not sent a complete mapping list between all currently used Standat values to distinct Stancode values. No 'one-to-many' conversions - either way - can exist in the mapping file. If external data providers plan to merge parameters, this must happen in the source system and not as part of the mapping file definition. If such a situation arises, the data provider should map duplicates to custom Stancode values and then have the cleanup process executed during a later version within its own database.
DKJord has already prepared the endpoint changes even if it has yet to receive the mapping file. This should enable external system developers to prepare the code on their end in connection with Stage 2 and 3.
The existing REST methods that have been updated in connection with these changes can be found on the TEST environment already. Please refer to the following page for the TEST endpoints: https://github.com/danmarksmiljoeportal/DkJord/wiki
The methods and objects that have been changed are:
| Method | Object | Change |
|---|---|---|
| POST / api / locations | "pollutants":[] | Now contains attribute "pollutantComponentSc1008" both at root level and within projectPhases |
| GET / api / locations / {locationReference} | "pollutants":[] | Now contains attribute "pollutantComponentSc1008" both at root level and within projectPhases |
| GET / api / locations / landfills / pollutants | "pollutants":[] | Now contains attribute "pollutantComponentSc1008" both at root level and within projectPhases |
| PUT / api / locations / {id} | "pollutants":[] | Now contains attribute "pollutantComponentSc1008" both at root level and within projectPhases |
We have also prepared a number of public functions that external systems can call in order to map from Standat to Stancode or Stancode to Standat as well as return Stancode values. Please go this page to read more: https://github.com/danmarksmiljoeportal/DkJord/wiki/Public-API-Guideline The functions to look at are:
- Get Stancode1008
- Convert Standat to Stancode
- Convert Stancode to Standat