Open data in intelligent transport systems
summary
Norway publishes production APIs for ITS: the Norwegian Public Roads Administration (NPRA/Statens vegvesen) exposes NVDB: 725,000 road signs, 240,000 km of speed limits, 370 object types and registry extracts, Avinor exposes a case‑sensitive flight XML feed with status codes in Norwegian/English, and traffic uses DATEX2 XML feeds that require credentials, frequent downloads and custom parsing. Real projects combine route planner, DATEX, NVDB and map layers into a browser map beta that pulls webcams, travel times and announcements; builders store history and wrap simpler JSON APIs for clients.
AI-written summary · about
chapters (33)
- 0:00Intro
- 0:46Agenda
- 1:50Definitions
- 3:39Why open data
- 6:58Quality of open data
- 9:58RDF
- 18:12Examples
- 19:42Norwegian
- 20:03Flight information
- 20:55Code lists
- 21:35Documentation
- 22:41Endpoints
- 23:00API calls
- 33:58API
- 34:45API endpoints
- 36:01envdb
- 36:27map
- 36:52tunnel search
- 39:30API call
- 40:17Results in XML
- 40:38API endpoint
- 41:35Dynamic road data
- 41:57Data X2
- 45:36Data X Source
- 46:14Data X Model
- 49:16Making your own API
- 51:46Mapbased traffic information
- 52:47Other moving parts
- 53:50Traditional traffic announcement
- 54:51Service
- 57:07Summary
- 58:11Resources
- 58:33Questions
related talks
16mAccelerating territory’s development through Open Data
54mBuilding an Open Government with Open Code and Open Source
21mThe socio-economic advantages of open data implementations
24mBuilding Open Data Platforms, an Insider's Perspective
48mA Journey to Open Data
31mApidays Virtual Helsinki - Oliver Thamm, Xapix.io
05mUnlocking Real-Time Data
47mPanel: Open Data In Public Use
