Open Taraskin opened 3 years ago
This behaviour is due to the special treatmet of the 580 object in NVDB api LES. The 580 type "Kontraktsområde" is used to index all other features plus the road network ("vegnett/veglenkesekvenser/segmentert") with "kontraktsområde" information. Due to data volume, speed of indexing and the complexity in fully indexing 580 with itself, the 580-objecs have a very simplified representation in NVDB api LES.
I highly doubt a workaround (such as looping over the individual 580 objects in the initial response) will be implemented, but leave it open while we consider it.
Also, please bear in mind that very good workarounds exists for many of the use cases where it feels natural to download the 580 object:
Thank you for the response, @LtGlahn.
As developers of the Brutus system (which is closely integrated with NVDB in both directions), we are very interested in getting some extra details for contracts, especially - dates, to determine if contract is expired - this is very important for us.
So, as a quick solution/workaround, I hope - it is possible to put from/to date attributes among others into <kontraktsområde>
section as part of <lokasjon>
block for bridge information, something like:
<kontraktsområder>
<kontraktsområde>
<id>494270639</id>
<nummer>805</nummer>
<navn>0805 Rjukan 2015-2021</navn>
<datefrom>2015-01-01</datefrom>
<dateto>2021-12-31</dateto>
</kontraktsområde>
Provide attributes for Driftskontraktsområde (Datakatalog code = 580).
AreaClient.getContractAreas()
method returns only limited set of properties - id, type, name, number, counties, municipalities.RoadObjectClient.getRoadObjects()
for featureTypeId = 580 returns only IDs, without a properties. At the same time web endpoint - https://nvdbapiles-v3.utv.atlas.vegvesen.no/vegobjekter/580/114142161: responds with:Interested mostly in next properties: Navn - 5174 Nr - 5175 Type - 8832 Dato fra - 8833 Dato til - 8834
It would be also nice to have possibility receive attributes for multiple driftskontrakt at once, based on IDs in request, for example - it will reduce amount of requests to the service.