Norwegian National SensorHub - sharing IoT data with open standards and technology
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
| Title |
| |
| Title of Series | ||
| Number of Parts | 351 | |
| Author | ||
| License | CC Attribution 3.0 Unported: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
| Identifiers | 10.5446/69006 (DOI) | |
| Publisher | ||
| Release Date | ||
| Language | ||
| Production Year | 2022 |
Content Metadata
| Subject Area | ||
| Genre | ||
| Abstract |
| |
| Keywords |
FOSS4G Firenze 2022238 / 351
1
7
13
22
25
31
33
36
39
41
43
44
46
52
53
55
58
59
60
76
80
93
98
104
108
127
128
133
135
141
142
143
150
151
168
173
176
178
190
196
200
201
202
204
211
219
225
226
236
242
251
258
263
270
284
285
292
00:00
James Waddell Alexander IIProjective planeSheaf (mathematics)Proof theoryCollaborationismSystem administratorComputer animation
00:29
Open setDomain nameStandard deviationReal numberCASE <Informatik>Physical systemFrequencyCommunications protocolVolumeDigital filterData modelLibrary catalogRegular graphComputer architectureStreaming mediaGeometryDifferent (Kate Ryan album)Internet service providerDenial-of-service attackoutputWater vaporStandard deviationPhysical systemElectric generatorDiallyl disulfideCollaborationismHypothesisOpen setMultiplicationReal numberCommunications protocolMusical ensemblePurchasingShared memoryProof theorySoftware testingComputer architectureSimilarity (geometry)QuicksortConnectivity (graph theory)PredictabilityDomain nameVolume (thermodynamics)FrequencyCASE <Informatik>GeometryRepresentational state transferFunction (mathematics)Channel capacityExterior algebraComputer animationEngineering drawingDiagram
04:12
Different (Kate Ryan album)System administratorLevel (video gaming)Water vaporMathematicsComputer architectureDemo (music)Graph coloringBuildingComputer architectureComputer animation
04:52
EmailStandard deviationoutputLatent heatJSONUML
Transcript: English(auto-generated)
00:00
Thank you. I'm Alexander Nossum. I work for a GIS IT company in Norway and I'm here to tell you about the proof of concept project that we have done this last year with the collaboration between a lot from the government section, the public administration section. And the title of the project was From
00:27
Sensor to Society. And the main question that we sort of tried ourselves on is how can the society in general leverage sensor data from multiple sensor providers and
00:42
solutions. Which is a huge question so I'm not going to solve that now. But we're inspired by the way we in Norway share a lot of geo data, GIS data. We have a fair amount of success standardizing across the public private
01:02
sector and also the public public sector. Which is forming an ecosystem of data sharing with GIS data. We use a lot of open standards in Norway so we build upon those open standards like VFS and using rest APIs and similar. But
01:21
we have done this in other domains not sort of geo geo domains but also in port data and more sea like data. Which works successfully when there's a high geospatial component for the data. But with sensor data the sort of
01:42
the I know that there's exists of standards and everything but but the real situation at least in Norway for sensor data is that it's a lot of unstandardized data. There's obviously unpredictable volumes of data and predictable frequencies from sensors. And also a lot of different protocols
02:02
used and a lot of different proprietary protocols not some de facto proprietary as well. And that makes the public sector in particularly very worried and scared to use or purchase sensor technology in general. So a lot of
02:22
smaller municipalities, smaller cities in Norway don't have the capacity to sort of get vendor locked in with a certain kind of sensor provider. And that is also the case for the sensor vendors and not that they want to be
02:40
proprietary but they don't have really a good alternative to be open. So they are also in search of so more open ecosystem of sharing sensor data. So that led us to sort of define a high-level architecture which is sort of all-inclusive. But we focused a lot on the API sides of it. The
03:05
input and the output of making a sort of a sensor hub. And we have been using a lot of open standards so some proof of concept this and test it in in proof of concept on real data in Azure. But the main idea is to
03:25
generate or to make open standards for data sharing with the sensor vendors. We were lucky to have a lot of collaborators, a lot of sensor providers, everything from building sensors to ocean water level
03:43
sensors to flood level sensors and water and sewage systems in Norway. So we had a lot of real data to work with, a lot of different data and we were lucky to have our hypothesis concluded that
04:02
there are a lot of different protocols, a lot of different standards, a lot of data hassling even though they should be standardized. And that led us to this is in Norwegian but you can bear with me. This led us to a demo which is really successful for public administration because showing
04:22
them a high-level architecture is so mind-blowing for them. So we made this 3D demo which shows the climate of the using colors on the different buildings with live sensor data comparing that with the water level and the temperature level.
04:43
Everything from very different sensor vendors. So it shows the usefulness of having a successful data change. And that's all. What we are doing further now is to investigate further on the OTC standards if that could be something to extend into this project. We're hoping that we get more
05:04
funding from the public sector to work with this and to standardize between the public sector so they can get the de-facto standard at least in the public sector in Norway for this. I'm really, really interested in experience from others, hopefully internationally because I
05:20
think this problem is not Norwegian specific. So other input from this is really appreciated. So just reach out. That's my email. Yeah. Thanks.