Application Domain Extensions definition for crowd source and Volunteer Geographic Information for smart-cities services deployment. F. Prandi, R. de Amicis, P. Parslow, M. Ford, E. D Hondt
Outlook Introduction to i-scope project; Motivations; The crowd source approach; Noise measurement modelling; Disabled routing data modelling; Conclusion.
i-scope project Context The latest generation of 3D Urban Information Models (UIM), created from accurate urban-scale geospatial information, can be used to deploy smart web services based on geometric, semantic, morphological and structural information at urban scale level.
i-scope project The consortium
i-scope project: Goal i-scope aim to deliver an open source toolkit for 3D smart city services based on 3D Urban Information Models (UIM), created from accurate urban-scale geospatial information.
i-scope project: The adressed scenario 1) Improved inclusion and personal mobility of aging people and diversely able citizens; 2) Energy dispersion & solar energy potential assessment; 3) Noise mapping & simulation.
Motivation: standard approach to city models CityGML as a standard CityGML is designed as an open data model and XMLbased format for the storage and exchange of virtual 3D city models. CityGML is an application schema of the Geography Markup Language 3 (GML3) CityGML is based on a number of standards from the ISO 191xx family, the Open Geospatial Consortium, the W3C Consortium, the Web 3D Consortium, and the Organisation for the Advancement of Structured Information Standards (OASIS) 14th of March 2012: the members of the OGC have adopted version 2.0.0 of CityGML as an official OGC Standard.
Motivation: Use of ADEs to model the services Extensions to the CityGML data model applying to specific application fields can be implemented using the Application Domain Extensions (ADE).
The crowd source approach Noise mapping and simulation. To do so i-scope delivers smart services that: Calculate, in an interoperable manner, noise levels both through simulation and through mapping based on accurate UIMs. Create real-time and accumulated noise maps through data collected by citizens, who are involved as prosumers (producers and consumers) of environmental data, through the use of their mobile phones as noise sensors, measuring city-wide noise levels
The crowd source approach Issues How to ensure the significance of the measurements? How to verify the accuracy? How to relate the noise to the city features?
The crowd source approach Crowd source noise Data collection: GOAL: Collect initial set of Noise data by pilot partners. Campaigns using NoiseTube. Coordinated grassroot/istitutional campaign. Multiple user Unstructured data Single user Unstructured data Avoid unstructured individual campaign. Better using know and calibrated devices. Multiple user Averaged data
The crowd source approach Crowd source noise Data collection i-cscope pilot examples: Zagreb Baia Mare
Profiling ISO19156 Observations and Measurements ISO 19156 Observations and measurements provides a generic framework for describing both the observing event and the results of the observation. It is applicable to a wide range of scientific and technical domains. The generic nature of this standard means that it requires further specialisation to constrain aspects of the model
Profiling ISO19156 Observations and Measurements INSPIRE Specialised Observations Defines 3 types of Specialised Observation based on the Result Type. These extend the example ISO 19156 specialised observations: Gridded Observation Trajectory or Profile Observations Point Observations INSPIRE Specialised Observations constrain the result, featureofinterest and phenomenontime
Proposed Noise Measurements Model Two data exchange requirements: Source noise exposure measurements Aggregated/modelled noise exposure measurements 1. Source noise exposure measurements: Time series collected at mobile locations (NoiseTube) Recommendation 1 Use INSPIRE Specialised Observation Trajectory Observation Need to extend to include summary statistics
Proposed Noise Measurements Model Constraints for INSPIRE Specialised Observation - Trajectory Observation 1. result must be a TimeSeries 2. each point in the result must be a TimeLocationValueTriple 3. phenomenontime must be a TM_Period 4. featureofinterest must be a SF_SamplingCurve SamplingCoverageObservation «featuretype» Trajectory and Profile Observations:: TrajectoryObservation TimeSeries Result for Trajectory Observation CVT_DiscreteTimeInstantCoverage «Type» Timeseries::Timeseries + temporalextent :TM_Period +collection 0..* «featuretype» NoiseTrajectoryObservation +point 0..* CVT_TimeInstantValuePair «DataType» Timeseries:: AnnotatedTimeValuePair + geometry :TM_Position + value :Record «DataType» NoiseTubeStatistics + count :Integer + lengthoftrack :Length + maxlaeq :Measure + meanlaeq :Measure + minlaeq :Measure +summarystatistics 0..1 «DataType» SummaryStatistics «datatype» Trajectory and Profile Observations:: TimeLocationValueTriple constraints {UoM of maxlaeq shall be given in dba} {UoM of minlaeq shall be given in dba} {UoM of meanlaeq shall be given in dba} + location :GM_Position For an aggregated/modelled trajectory observation the INSPIRE TrajectoryObservation should be used
Proposed Noise Measurements Model 2. Aggregated/modelled noise exposure measurements Post-processing modelling may generate generalised noise exposure measurements for an area of interest: Regular gridded data overlay over terrain model or city model Recommendation 1 Use INSPIRE Specialised Observation Grid Observation Around Road, Rail, Airport, Industry (see Noise Mapping Model)
GridObservation «FeatureType» observation::om_observation Grid Observation Result - INSPIRE RectifiedGridCoverage «featuretype» Coverages (Base)::Coverage + metadata :Any [0..*] + rangetype :RecordType «FeatureType» coverageobservation:: OM_DiscreteCoverageObservation «featuretype» Coverages (Domain and Range):: CoverageByDomainAndRange + coveragefunction :CoverageFunction [0..1] + domainset :Any + rangeset :Any [0..*] {ordered} «union» Coverages (Domain and Range):: Cov eragefunction + ruledefinition :CharacterString + rulereference :URI + gridfunction :GridFunction «FeatureType» Sampling Coverage Observation:: SamplingCov erageobserv ation «datatype» Coverages (Domain and Range)::GridFunction + sequencerule :CV_SequenceRule [0..1] + startpoint :Integer [0..*] {ordered} «featuretype» Coverages (Domain and Range):: RectifiedGridCoverage «featuretype» Gridded Observations:: GridObservation constraints {domainisrectifiedgrid} {grid points shall coincide with grid cell centres} Constraints for INSPIRE Grid Observation: 1. The Result shall be a RectifiedGridCoverage 2. phenomenontime must be a TM_Instant 3. featureofinterest must be a SF_SamplingSolid or SF_SamplingSurface NOTE: The GridObservation shall be directly imported from the INSPIRE Coverage Model without any addition extensions for Noise.
Routing services Pilots have very few data of their own available for the task of Inclusive Routing Solution: Leverage on OpenStreetMap data. Survey missing elements on a pilot area: Other Graph Survey Optional elements Mandatory elements OSM data Data preparation Manual (JOSM) Pg routing OpenLS Interface
Routing services Mobile application for barriers Data collection: Architectural Barriers Survey App offers a system of data collection that allow crowdsourcing in the field of the urban architectural features evaluation. Thanks to this application and the NoiseTube App, the user will become active part of the project, letting the data collected in the urban area be accessible to everybody through a dedicated web portal. Architectural Barriers Survey App is available from Apple Store for free
Routing services Best practice: GSH NGO Cles A good example of involvment of the final users is the collaboration with GSH: GSH was already involved into architectural barriers survey, but the data (in analogic format) are not usable and difficult to update. i-scope involves the NGO into the definitions of the data model of the application. GSH performs an already planned survey substituting the traditional analogic survey with a first beta version of the app. Thanks to their feedback many improvements have been done. i-scope provide the collected data into an open reusable (.csv) format to GSH. The data acquired became the base for the OSM data enrichment (to be completed). JOSM editor The new surveyed featurs have to be used to edit and enrich the existing OSM dataset (in green the new sidewalks features) Dedicated Web Portal Data Export The data are listed in a table view and the photos are visible in a preview popup.
Routing services
Application Domain Definition
Conclusion Crowd source approach is growing with location services enabled smart-phones; Issues are still open about accuracy and quality; Definition of very strong constrains into survey rules and procedures can improve the situation; A well defined data model is mandatory; Very difficult to instantiate a direct pipeline: collectionservices.