OGC Intro, update and what’s new - Paikkatietoikkuna

®

®

© 2015 Open Geospatial Consortium

OGC

Intro, update and what’s new

Bart De Lathouwer

OGC Director, Interoperability Programs

10th December, 2015

Finnish Geospatial Forum

Helsinki, Finland

OGC®


Topics

• Quick Intro and overview of the OGC

• Update and Trends

– InfraGML

– CityGML

– SmartCity

– LinkedData

– Point Cloud DWG

– TJS

Source: MIT

OGC®

What most people think about standards work!


OGC®


OGC

• The Open Geospatial

Consortium (OGC)

– Not-for-profit, international

consortium of 515 industry,

government, and university

members

• Founded in 1994

• Work is based on

collaboration and

consensus!

OGC Mission

Our core mission is to deliver interface specificationsthat are openly available for global use, and which are used by Geospatial data producers and software transparently to the users.

OGC®

OGC at a Glance

Not-for-profit, international voluntary consensus standards

organization; leading development of geospatial standards

• Founded in 1994.

• 515 members and growing

• 38 standards

• Hundreds of product

implementations

• Broad user community

implementation worldwide

• Alliances and collaborative

activities with ISO and many other

SDO’s

Commercial41%

Government18 %

NGO10 %

Research7 %

University24%

© 2015, Open Geospatial Consortium5

OGC®

6

OGC at a Glance

Not-for-profit, international voluntary consensus standards

organization; leading development of geospatial standards

• Founded in 1994.

• 515 members and growing

• 38 standards

• Hundreds of product

implementations

• Broad user community

implementation worldwide

• Alliances and collaborative

activities with ISO and many other

SDO’s

© 2015, Open Geospatial Consortium

Africa; 4

Asia Pacific; 59

Europe 203

Middle East7

North America 163

South America 2

OGC®


OGC Programs

OGC®

An OGC Update

• New working groups, experiments and initiatives


OGC®

Smart City


OGC®

Location Services for Smart Cities

• Citizen Services

– Location-aware municipal services

using open data and standards

• Infrastructure management

– LandInfra

– Smart Energy

– Smart Water Management

• Disaster and Emergency Response

– Common Operational Picture

• Urban Maps

– 3D City Models

– Indoor Venue Maps

– Interoperability with BIM

• Sensor Webs

– Situational awareness from

fusion of sensor observationsSource; Thomas Kolbe, Berlin TU

OGC®

An OGC Framework for Smart Cities

• “OGC Smart Cities Spatial

Information Framework” – https://portal.opengeospatial.org/files/?artifact_id=61188

• Influenced by:– OGC’s geospatial, sensor, processing,

mobile standards work

– Survey of Smart City Standards Activities:

• JTC 1, ITU, ISO, BSI, DIN, others

– Survey of OGC CityGML implementations

• Goals:

– Pilot Smart Cities Spatial Framework in

select cities (http://www.opengeospatial.org/blog/1886)

– Advance an OGC Best Practice for Location

Enabled Smart Cities

OGC Smart Cities Spatial Information

Framework

https://portal.opengeospatial.org/files/?artifact_id=61188

http://www.opengeospatial.org/blog/1886

OGC®

FutureCities Pilot

• Coordinated effort between OGC and buildingSMART International

• Seeking sponsors, most of work is intended to occur in Europe

• Pilot will demonstrate and enhance the ability of cities to use diverse,

interoperating spatial technologies to deliver improved quality of life,

civic initiatives, and resilience

Copyright © 2015 Open Geospatial Consortium

http://www.opengeospatial.org/pressroom/pressreleases/2290

http://www.opengeospatial.org/pressroom/pressreleases/2290

OGC®

City Geography Markup Language – CityGML

Application independent Geospatial Information Modelfor semantic 3D city and landscape models

• comprises different thematic areas(buildings, vegetation, water, terrain, traffic, tunnels, bridges etc.)

• Internat‘l Standard of the Open Geospatial Consortium

– V1.0.0 adopted in 08/2008; V2.0.0 adopted in 3/2012

• Data model (UML) + Exchange format (based on GML3)

CityGML represents

• 3D geometry, 3D topology, semantics, and appearance

• in 5 discrete scales (Levels of Detail, LOD)

T. H. Kolbe – City System Modeling based on Semantic 3D

City Models

2025. 6. 2014

OGC®

And todays 3D Visualization World


GTA V Samet Konuksal

OGC®

CityGML, next steps

• CityGML 3.0 is being developed in 14 work packages

• New work includes design changes including revision and

improvement of the UML model and improvements to

metadata

• CityGML editors to develop a method to keep synchronized

with GML

• Model is being extended to include new features (land

administration, non-building structures, utilities)

• Model is being extended to include new concepts

(volumetric construction, texturing, stories, time series,

revised LOD)


OGC®

IndoorGML

• The aim of IndoorGML is to represent and exchange the

geoinformation that is required to build and operate indoor

navigation systems.

• Not just geometry but a model of the indoor space!


OGC®

LandInfra


• Addresses Civil Engineering space

– Follow on to LandXML

– Fully defined conceptual model

– Common UML model synchronized

between OGC and bSI

– For encoding in GML, other

encodings

• Public review completed in early

2015

• To Sydney TC Dec 2015 for

discussion to proceed to vote

• Bentley at Lead as Editor and DWG

/ SWG chair

OGC®

OGC Candidate 3D Portrayal Standard

Copyright © 2015 Open Geospatial Consortium 25

OGC®

3D Portrayal Interoperability Experiment


OGC®

The OGC Work does not happen in isolation

• The OGC and OGC Members collaborate and participate in

numerous other standards organizations and communities

that have requirements for 3D/4D/5D encoding, modeling,

analysis, and visualization


OGC®

Linked (Open) Data


OGC®

OGC & W3C Workshop


OGC®

Semantic 101

• Current web:

– Human interpret the hyperlinks – by clicking on the link, you ‘jump’ to

the next.

• How to get from “Adele” to “Zaz” in a minimal number of clicks

– Semantic web:

• Same thing as above, but by machines

• Machines are able to “interpret” the links!


OGC®

5 Stars for open data

* make your stuff available on the web (whatever format)

** Make it available as structured data

*** whatever format, using open standards

**** use URLs to identify things, so that people can point at your stuff

***** link your data to other people's data to provide context


OGC®

Linked Data

Triple:

<Subject><Predicate><Object>

RDF extends the linking structure of the Web to use URIs to

name the relationship between things as well as the two

ends of the link (this is usually referred to as a “triple”)

<Uri><Uri><Uri>

Make up an example Bart!


OGC®

Linked Data

RDFS (RDF Schema)

set van klassen met bepaalde

eigenschappen v RDF

a set of classes with certain properties using the RDF extensible knowledge

representation data model, providing basic elements for the description of

ontologies, otherwise called RDF vocabularies, intended to structure RDF

resources. These resources can be saved in a triplestore to reach them with the

query language SPARQL.


OGC®

(Geo)SPARQL

• SPARQL: SPARQL Protocol and RDF Query Language

PREFIX foaf: <http://xmlns.com/foaf/0.1/>

SELECT ?name ?email

WHERE {

?person a foaf:Person.

?person foaf:name ?name.

?person foaf:mbox ?email.

}

(browse foaf vocabulary)


http://xmlns.com/foaf/0.1/

OGC®

Ontologies

• Foaf, …

• LOD Repository

– http://lov.okfn.org/dataset/lov/

• Do not create your own one!

– Reuse!!!


http://lov.okfn.org/dataset/lov/

OGC®

OGC & W3C Working Group

• Use Cases and Requirement

• Spatial Data on the Web Best Practices

– an agreed spatial ontology conformant to the ISO 19107

– advice on use of URIs as identifiers in GI systems

– advice on providing different levels of metadata for different usage

scenarios

– develop advice on, or possibly define, RESTful APIs to return data in

a variety of formats including those defined elsewhere, such as

GeoJSON, GeoJSON-LD and TopoJSON

• OWL Time Ontology

• Semantic Sensor Network Ontology

• Coverage's in Linked Data


https://portal.opengeospatial.org/files/?artifact_id=66381&version=1

OGC®

Point Cloud DWG


®

®

Reporting after OGC Point Cloud DWG

(prepared with Bart De Lathouwer)

After 97th OGC Technical Committee, Sydney, Australia

(Stan Tillman, Jan Boehm, Peter van Oosterom,

Point cloud DWG co-chairs), 3 December 2015


OGC®

Contents

• Some background (Point Clouds)

• History of the Point Cloud DWG

• Point Cloud survey


OGC®

Standardization of point clouds?

• ISO/OGC spatial data:

– at abstract/generic level, 2 types of spatial representations:

features and coverages

– at next level (ADT level), 2 types: vector and raster, but

perhaps points clouds should be added

– at implementation/ encoding level, many different formats

(for all three data types)

• nD point cloud:

– points in nD space and not per se limited to x,y,z

(n ordinates of point which may also have m attributes)

– make fit in new ISO 19107 (recently revised).

– note: nD point clouds are very generic;

e.g. also cover moving object point data: x,y,z,t (id) series.

OGC®

Standardization actions

• Within OGC establish a point cloud DWG

• Probably better not try to standardize point clouds at

database level, but rather focus on webservices level

(more support/ partners expected)

• A lot of overlap between WMS, WFS and WCS

• Proposed OGC point cloud DWG should explore if

WCS is good start for point cloud services:

– If so, then analyse if it needs extension

– If not good starting point, consider a specific WPCS, web point

cloud service standards (and perhaps further increase the

overlapping family of WMS, WFS, WCS,... )

OGC®

Contents





OGC®

Agenda Boulder, Colorado USAPoint Cloud ad hoc, 1 June 2015

• Scott Simmons, OGC: Introduction to Point Cloud discussion and

summary of standards efforts

• Jeff Young, ASPRS: ASPRS activities with LiDAR data

• Chris Little, UK Met Office: What (where and when) is the Point in

Meteorology

• Keith Ryden, Esri: Enterprise community requirements for point

clouds

• Jason Smith, Exelis (NGA): Sensor Independent Point Cloud (SIPC)

data format, a profile of HDF5

• Michael Gerlek, RadiantBlue: Current situation and future work for

point clouds

• Peter Baumann: Point clouds in coverages

• Martin Isenburg, OSGeo: Open Source community drivers for point

cloud standards

• Doug O’Brien, IDON Technologies: ISO and point cloud standards


OGC®

Agenda Nottingham, UKPoint Cloud DWG, 15 September 2015

• Stan Tillman, Intergraph: Review the Charter

• Election of Chair(s)

• Scott Pakula, Pixia: Serving LiDAR thru existing OGC services

• Barry Gleeson, RICS: Point Cloud Usage in a Railway Context and

rules/issues related to extraction and sharing

• Gene Roe, Lidar News: The ASTM E57 Data Interoperability Standard

• Jan Boehm, University College London: IQmulus - Cloud Platform

for Point Cloud Processing

• Peter Baumann, Jacobs University: OGC WCS: fomat-independent

point cloud services

• Jean-Baptiste Henry, Thales: Point Cloud from Photogrammetry

• Edward Verbree, Delft University of Technology: Management and

direct use of massive point clouds


OGC®

Agenda Sydney, AustraliaPoint Cloud DWG, 3 December 2015

• Stan Tillman, Intergraph: Point Cloud Survey Overview

• Martin Isenburg, rapidlasso GmbH: The LASzip LiDAR

compressor: past choices, current rewards, and future

directions

• Nathan Quadros, CRC for Spatial Information:

Bathymetric LiDAR Specifications and LAS Classification

Standards


OGC®

Domain Working Group charter

• https://portal.opengeospatial.org/?m=projects&a=view&proj

ect_id=489 (initial date 23 july 2015, updated 30 oct 2015)

• DWG= discussion/documentation platform, change request

exiting standards (not work on new standards)

• Problem Statement OGC Point Cloud DWG:

– point cloud data has often been overlooked

– stored in many formats

– many domains such as .. LiDAR, Elevation, Seismic, Bathymetric,

Meteorological, and Fixed/Mobile consumer sensors

• Examples de facto standards: ASPRS LAS,

Sensor Independent Point Cloud (SIPC) based on HDF5

• greater interoperability between point cloud datasets and

… interoperate with other OGC standards

https://portal.opengeospatial.org/?m=projects&a=view&project_id=489

OGC®

Contents





OGC®

Motivation for the Survey

• With contributions provided in Nottingham, it was apparent

there are many facets to point clouds

• When trying to determine what should be a focus of the

DWG, it was decided that we needed to get a better

understanding of the community. We should not approach

this topic based on biases.

• We have put together a short survey that we feel will give

us a general overview. If more details are needed on

specific topics, we will plan a more directed survey on

given topics.


OGC®

A Look at the Survey

• https://portal.opengeospatial.org/files/?artifact_id=66239

• Opening remarks survey:

– You can pick multiple options as well as add your own options

– For each option you pick please rate its importance high or low

– If you wish please leave a comment in the last section

• Total of 14 questions


https://portal.opengeospatial.org/files/?artifact_id=66239

OGC®

1. What are your major sources for surface scan point clouds?

a. Airborne LiDAR

b. Terrestrial Lidar (including Mobile Mapping)

c. Indoor Laser Scanning

d. Photogrammetry

e. SONAR (single and multi-beam echo’s)

f. Subsurface Point Cloud from Seismic

g. RADAR (PS-InSAR)

h. Other (please specify):

OGC®

2. What formats do you use to store point clouds?

a. LAS (ASPRS)

b. LAZ

c. ZLAS

d. E57

e. PCD

f. POD

g. ASCII

h. PLY

i. SPD

j. Other (please specify):

OGC®

3. What formats do you use to transfer point clouds (both internally and to external entities)?

a. LAS (ASPRS)

b. LAZ

c. ZLAS

d. E57

e. PCD

f. POD

g. ASCII

h. PLY

i. SPD

j. Other (please specify):

OGC®

4. What are your most common use cases for point clouds?

a. Visualization

b. Digital Terrain Modelling

c. Feature Extraction

d. Forestry

e. GIS

f. Other (please specify):

OGC®

5. How do you store point clouds?

a. In a file on a computer

b. In a file on a network drive

c. In a database

d. In the cloud

e. Other (please specify):

OGC®

6. What attributes do your point clouds contain besides XYZ coordinates?

a. Timestamp

b. Intensity

c. Colour

d. Classification

e. Pulse Form

f. Pulse Count

g. Direction and Length of Scanline


OGC®

7. What conversion do you apply to the point clouds in order to use them?

a. To regular grid (raster)

b. To TIN

c. To features (vector object after detection/recognition)

d. None, direct use of point clouds


OGC®

8. Which temporal aspect of point clouds are relevant for you?

a. Temporal granularity at point level

b. Temporal granularity at data set (a ‘point cloud’) level

c. Temporal resolution / update frequency years

d. Temporal resolution / update frequency months

e. Temporal resolution / update frequency days

f. Temporal resolution / update frequency seconds

g. Monitoring applications, change detection


OGC®

9. During what phase do you encounter interoperability challenges?

a. Data Acquisition

b. Storage / Management

c. Combining Data from multiple source

d. Change Reference System

e. Analysis / Simulation

f. Dissemination

g. Visualization / Interaction


OGC®

10. What do you consider the most important area of point cloud standardization?

a. Data Model

b. File Format / Encoding

c. DBMS / SQL

d. Web Service (WxxS) protocol,


OGC®

11. What volume of point clouds have you managed/processed/stored/etc. in the last 12 month?

a. Less than 100 million (106) points

b. More than 100 million (106) points

c. More than 1 billion (109) points

d. More than 1 trillion (1012) points

OGC®

12. What tools do you use?

a. PDAL

b. Potree

c. LAStools

d. GRASS

e. Esri ArcGIS

f. Bentley Pointools

g. Leica CloudWorx

h. GeoMedia

i. Oracle SDO_PC

j. PosgreSQL/PostGIS

k. Other (please specify):

OGC®

Last 2 questions:

13.Do you use point clouds that are generated from moving

objects / trajectories? (Yes/No)

14.Comments:

OGC®

Next Steps Survey

• Work with OGC Staff to create the survey

• Work with OGC Staff to advertise and promote the survey

• Execute the survey and capture results

• Report the survey results at the next TC meeting

(7-11 March 2016, Washington D.C.)


OGC®

Table Join Service

• From the European Location Framework project


OGC®

Agenda

1. Introduction; OGC Table Joining Service

2. Health statistics data tables (Eurostat)

3. Demo

4. Architecture and final deployment

5. Euroboundarymap

6. Upcoming work

7. TJS software (Geoserver) repository

OGC®

1. Introduction of the OGC Table Joining Service

tabulair data

boundary data

applications

http://stage.gis.si/casper/


OGC®

Tabellen joinen met gebiedsindelingen

tabulair data

boundary data

applications

TJS



OGC®

Table joining (service) and unique id’s (keys)

tabular data

boundary data

OGC TJS

Unique id’s

(keys)

OGC®

TJS and the GDAS (XML) data format

tabular data

boundary data

data transformation

Geo data

OGC TJS

OGC®

Client application and TJS operations

tabular data

boundary data

OGC®

OGC TJS operations

OGC®

2. Health statistics data tables (Eurostat)

OGC®

Eurostat’s health statistics (>300 tables)

OGC®

Input and output formats of TJS

OGC®

3. Demo

• Demo

http://213.136.91.254/tjs

OGC®


Architecture for development (and demo client)

OGC®


data tables

(SDMX)

Download

Service

SDMX

to

GDASEuroSTAT

E.L.F. - Oskari Platform

Euroboundarymap

Health statistics

Cached

data

Casper

(GINST)

Geographic

data

Download

Service

WFS

TJS demonstrator

(Kadaster)

TJS join

Download

ServiceDownload

Service

Download

Service

WFS

(GeoJSON, GML)WMS

Join

Service

TJSGeopackage,

jsonLD,RDF

Other

clients

Transformation

Service

SDMX

REST

Architecture final deployment

OGC®

5. Euroboundarymap

We are using EuroBoundaryMap. However, I did not yet have informed if EuroBoundaryMap is available for E.L.F. or that that have to use the administrative boundaries from the EuroGlobalMap are not compatible with the Euros (because of missing NUTS codes) which is available as open data.

(see mail d.d. 7-4-2014 MG -> JH)

OGC®

6. Upcoming work

1. Finalizing data transformation Eurostat data

2. Develop data transformation for ODATA format (CBS)

3. Implementation output formats: Geopackage, jsonLD,

RDF

4. Testing TJS with CASPER client

5. Deployment OSKARI platform

6. Documentation

OGC®

7. TJS software (Geoserver) repository

TJS en GeoServer implementation

Open source project: GeoServer TJS plugin

Code public available on GitHub:

https://github.com/thijsbrentjens/geoserver/tree/2.6.0.x

https://github.com/thijsbrentjens/geoserver/tree/tjs_2.2.x/

OGC®

Questions?

Blijf op de hoogte via:

http://www.geonovum.nl/onderwerpen/services/table-joining-services

[email protected] | www.geonovum.nl | @geonovum

http://www.geonovum.nl/onderwerpen/services/table-joining-services

OGC®

Concluding

• Intro OGC

• We looked at:

– OGC - W3C

– OGC – bSI

– CityGML and Smart Cities

– Table Join Services

– Point Cloud DWG


OGC®

Thank you

• [email protected]


OGC®

Vragen?

OGC®


Documents

OGC Intro, update and what’s new - Paikkatietoikkuna