User guide for NVDB Eksport
Exports are layered around NVDB API Les, with an almost identical interface. It is integrated into Vegkart, and you can easily retrieve data in the desired format.
There are two different ways to use Export: through Vegkart, or by making a call directly to the Export API.
Export through Vegkart
Once you have performed a search in Vegkart, you can export the data to the CSV or SOSI file formats. How this is done is described in Vegkart documentation.
Export through the API
There are two endpoints used to retrieve data, /vegobjekter og /vegnett. In addition, we have /changelog and /auth.
Road objects
Endpoint: /vegobjekter/<typeid>.<csv|sosi|sos>
Export one or more road objects to either SOSI or CSV format. The endpoint uses the same parameter as API Les . Note that when exporting to SOSI format, it is required to include either the parameter "kartutsnitt" or "sosiutsnitt". The "kartutsnitt" parameter will only retrieve road objects within a given section, while "sosiutsnitt" will only be used in the SOSI head if "kartutsnitt" is not set.
Example: This example will retrieve speed bumps (type 103) in Trondheim municipality (5001), with the given map section as MIN and MAX-NE in the SOSI head.
https://nvdb-eksport.atlas.vegvesen.no/vegobjekter/103.sosi?kommune=5001&inkluder=alle&sosiutsnitt=250339.83,7010675.56,285864.43,7051059.45Road network
Endpoint: /vegnett/veglenkesekvenser/segmentert.csv
Export a set of segmented road link segments to CSV format. Uses the same parameter as API Les, read here for more information.
Example: This example will extract the pavement road network in Skaun municipality (5029) in CSV.
https://nvdb-eksport.atlas.vegvesen.no/vegnett/veglenkesekvenser/segmentert.csv?kommune=5029&typeveg=fortauChange log
Endpoint: /changelog
Retrieves a list of versions of the export application with associated change log in JSON format.
Endpoint: /changelog/latest
Retrieves the version number of the latest release of the export application with associated change log in JSON format.
Pre-authentication
Endpoint: /auth/<request>
Generates a key to pre-authorize the specified export request. This is how you can create a one-time link that allows you to download shielded data. This requires that an id token is included as a bearer token in the Authorization header. Read more about ID Token.
Example: This example will create a key to retrieve pipelines (type 77) in Malvik municipality (5031).
https://nvdb-eksport.atlas.vegvesen.no/auth/vegobjekter/77.csv?kommune=5031&inkluder=alle
Furthermore, you can use the generated key in key parameters in a request.
https://nvdb-eksport.atlas.vegvesen.no/vegobjekter/77.csv?kommune=5031&inkluder=alle&key=YOUR_GENERATED_KEYNote that a key is only valid for the query it was generated for, it can only be used once, and it is only valid for one minute from the point it was generated.
Other parameters
|
Parameter |
Description |
|
api |
Used to select which NVDB Read environment the data should be exported from. Useful if you want to see what data has been published in the development or test environments. Example: api=https://nvdbapiles-v3.atlas.vegvesen.no |
|
opprettet_dato |
Used if you want to include the MET.OPPRETTET_DATE field in the csv. |