Open Interfaces for GEOINT DataLuis Bermudez

2

Executive Director Innovation Program, OGC

Challenges

3

4

70 petabytes of satellite imagery

30 gigabytes per satellite imageFrom Digital Globe presentation at OGC Location Powers Sept 2016

5

21 Billion Connected Devices in the Global Internet of Things in 2020

6

UAV What is the accuracy

Image distortion

What type of platform?

00010011101010010001000110101001

Data ProcessingSensor

Types?

What are all the sensors in the platform

Web Services

7

8

A Servicedefines Interfaces

An Interfacedefines Operations

9

Web Server

ClientsServer with Images

ApplicationProgramInterfaces(API)

What operations should we use to retrieve a map on the web?

- getMap- getImage- get2dmap- map = new xyz.Map (center ..)- etc.

Interfaces

11

ClientsServer with Images

ApplicationProgramInterfaces(API)

12

- getMap- getImage- get2dmap- getPNG- getlocation- map = new xyz.Map (center ..)- etc.

An interface defines Operations

13

Heterogeneous Services

14

Heterogeneous Services

15

Heterogeneous Services

16

Agreement

17

This is what OGC open standards do

e.g. Web Map Service (WMS)

18

Interoperability

Increase ability to access, fuse and apply diverse content when and where needed is critical to situational awareness and disaster planning/ response in cross-boundary and cross-domain settings

19

Interoperability in the context of Intelligence, Surveillance, and Reconnaissance (ISR)

J28 division chief from http://www.jfcom.mil/newslink/storyarchive/2007/pa071607.htm

doesn’t have to worry about where his information is coming from

plug and play ISR capabilities

20

Figure 5. OV1- High Level Concept for EC EmpireChallenge(EC)08

OGC

21

22

Open Geospatial Consortium (OGC)

Leading International consortium for advancing open geospatial standards

23

Open Geospatial Consortium (OGC)

• 70 standards• 550 members• 5000 users in the portal• 100 innovation projects• 230 compliant products• 900 implementations

24

StandardDefines operations

Rules

Formal rules

Consensus and approved

Open Standards

• Freely and publicly available • Non discriminatory• No license fees• Vendor neutral • Data neutral• Based on consensus

25

26

Standard… and are widely implemented

For WMS41 organizations

92 compliant products3 reference implementations

Randomlyselectedcompletelistathttp://www.opengeospatial.org/resource/products

Standards by Purpose

27

Open Interfaces

28

29

Images

Geospatial Data Types

30

Images

- RasterJPEG, PNG, TIFF, GeoTIFF, KML, ..

Vector graphics

Geospatial Data Types

31

Images Vectorpoint

lines

polygons

Geospatial Data Types

32

Geospatial Data Types

Images Vector Sensors

33

API Challenges

ImagesWhat format should we use?

What API?

34

Geospatial Data Types

Images Vector Sensors

35

Geospatial Data Types and Services

Images Vector Sensors

WMS WCS WFS

SOS

Sensor Things API

WMS

36

37

Interface to help share maps over the webWeb Map Service (WMS)

Link

38

WMS Operations

•GetCapabilities•GetMap•GetFeatureInfo (Optional)•DescribeLayer (Optional•GetLegendGraphic (Optional)

39

GetCapabilities

Link

40

GetCapabilities Response

41

GetCapabilities - Layer

42

GetCapabilities Layer Style Section

43

GetMap - Request Example

Link

44

Example Image from a GetMap request

45

GetMap - Request

•The service provides seven map layers: DTM, Overview etc. •The coordinate reference system EPSG:27700 is the Ordnance Survey National Grid reference system. •The image returned is a PNG transparent format with width 400 and height 300 pixels, and background color is white (Hex code=0xffffff).

46

GetMap Request without the overview layer

47

GetMap Transparency / Translucency

The map image can be overlayed with maps from other servers. In those cases it may be helpful to request the top level image in a format which supports a transparency such as the alpha channel. Then we can see what is below this map image.

48

GetMap Scale Limits will help select best image depending on the scale

49

GetMap - Zooming

•The client can "zoom in" and "zoom out" of the map by calculating new values for the BBOX (bounding box) parameter. The same applies to all map navigation functions like panning or selecting a completely new area.

• It is important to note that the server only returns an image to the client, but no additional information about the size, coordinate system, scale, etc

50

Reprojecting Maps CRS=EPSG:22770 CRS=EPSG:4326

51

GetFeatureInfo to get X and Y information from a previous GetMap request

X =231

y =280400,3000,300

0,0

52

GetFeature Info Request

53

GetFeature Info Request

http://metaspatial.net/cgi-bin/ogc-wms.xml?VERSION=1.3.0&REQUEST=GetFeatureInfo&SERVICE=WMS&LAYERS=osm_points&QUERY_LAYERS=osm_points&WIDTH=400&HEIGHT=300&CRS=EPSG:27700&BBOX=427966.6666666667,106800,431833.3333333333,109700&INFO_FORMAT=text/html&EXCEPTIONS=XML&X=231&Y=280

54

GetFeatureInfo - Response in HTML

55

GetFeatureInfo - Response in GML

56

GetFeatureInfo - INFO_FORMAT parameter

57

Getting a legend via GetLegendGraphic

58

Error Messages

59

INIMAGE Error Message

60

Exceptions

WFS

61

62

Feature

63

Feature has Properties

64

Geospatial Feature

65

Generalization

•Class = Feature Type = Tree Properties of Tree: – Height– Location

•All my Trees will have a height and location.

66

Feature Instance

•My favorite tree in Cartagena is the one in front of the hotel Colombia.

•Height = 5 m•Location = 10.407793,-75.551262

67

Web Feature Service (WFS)

Web Service used to:•Publish Features•Access Features•Edit Features

68

WFS Operations

•GetCapabilities - summary of the service•DescribeFeatureType - structure of the feature types•GetFeature - get the feature instance•Transaction - create, update and delete geographic features

•Lock Feature - protects a feature record when updating it

69

SEDAC WFS Server

70

GetCapabilities

•Provides metadata about the service •Provides list of feature types•Provides list of supported filters

71

WFS GetCapabilties

72

Response GetCapabilities

73

Response GetCapabilities

74

75

WFS DescribeFeatureType

76

Response GetFeatureType request

77

GetFeature Request

Link

http://sedac.ciesin.org/geoserver/ows?service=wfs&version=1.0.0&request=GetFeature&typeName=esi:esi-environmental-sustainability-index-2005_water-quality&maxFeatures=5

78

GetFeature Response

79

GetFeature Response

80

WFS Test Server Part of Testbed 12

•http://ogctestbed12.lat-lon.de/deegree/services/wfs?service=WFS&request=GetCapabilities

•Data follows 90% DGIWG Profile

81

Testbed 13 NSG profile development

82

Filtering by property values

GML

83

84

Geographic Markup Language (GML)

•Defines an abstract feature model • Provides XML Schemas

•Provides primitives: – Geometry– Feature Types–Coordinate Reference Systems

•Topology

85

Geographic Markup Language (GML)

• Temporal information and dynamic features • Definitions and dictionaries• Units, measures and values• Directions • Observation• Coverages• Default styling

86

Communities develop their own application schemas

87

Modeling Feature Types

88

Examples

• CityGML - 3D urban objects • GeoSciML - geoscience • AIXM – Aviation• ALKIS/ATKIS - German National Cadastre• AgroXML - Used in Farm Management InformationSystems• CSML – Climate Science Modelling• WaterML - Hydrology

89

DGIWG

https://www.dgiwg.org/dgiwg/htm/documents/standards_implementation_profiles.htm

WCS

90

91

Web Coverage Service (WCS)

92

Multi Spectral Imagery

93

WCS Operations

• GetCapabilities: delivers an XML-encoded description of service properties and the data holdings offered by the server inquired

• DescribeCoverage: delivers XML-encoded descriptions of coverages (such as their location in space and time)

• GetCoverage: delivers a coverage (or part thereof), either as original data or processed, in some suitable data format (e.g. tiff, png, jpeg, NetCDF)

SOS

94

95

Sensor Web

96

SOS GetCapabilities

97

SOS DescribeSensor

98

SOS GetObservation

Sensor Things API

99

100

OGC SensorThings APIInterface for Internet of Things

http://developers.sensorup.com/docs/

101

Data stream

102

About What?

a

Thing

103

How?

Sensor

104

Querying data from bike stations

•Endpoint: http://toronto-bike-snapshot.sensorup.com/v1.0/

105

Base Pathhttp://toronto-bike-snapshot.sensorup.com/v1.0/

106

Base Pathhttp://toronto-bike-snapshot.sensorup.com/v1.0/

107

Which Things are available in the server? http://toronto-bike-snapshot.sensorup.com/v1.0/Things

108

Getting a Datastream for a thing http://toronto-bike-snapshot.sensorup.com/v1.0/Things(206047)/Datastreams

109

Note: Datastreams define the unit of measurement http://toronto-bike-snapshot.sensorup.com/v1.0/Things(206047)/Datastreams

110

Getting the Observations related to a stream http://toronto-bike-snapshot.sensorup.com/v1.0/Datastreams(206051)/Observations

111

Complex Query

•Expands Datastreams and observations in one query

•Feature of Interest = 7000:Ft. York / Capreol Crt.•Start time = 2017-01-01T11:30:00.000Z•End time = 2017-03-01T11:30:00.000Z

112

Complex Query (cont)

Link

113

Complex Query Response

114

Complex Query Response Complex Query Response (cont )

115

Charts

http://share.sensorup.com

116

Sensor Things API more than GET

117

Error Codes

GeoPackage

118

119

OGC GeoPackage file format• A SQLite container

– Smal reliable and self contained– Serverles and zero-configuration– transactional SQL database– Limit of a file ~ 140 terabytes

• vector features• tile matrix sets of imagery and raster maps at various scales• attributes (non-spatial data)• extensions

http://www.geopackage.org

120

Vectors in GeoPackaage as Simple Features

121

Edit annotations on the field via mobile device

122

Access Elevation

Data

123

Spot Reporting

124

Summary

•Maps use WMS•Vector use WFS – encoding GML•Mobile formats use GeoPackage•Sensor data SOS or SensorThings API•Coverage data use WCS

Scenario

125

126

Scenario Discussion

Compliance

127

128

Why Compliance?

129

We have great open standards

130

Implementations are not always perfect

131

Interoperability can be fully achieved

132

Need to do a healthy test

133

Increase confidence of solution providers

"Achieving OGC certification is extremely important to us as an organization - we are proud to have more than 20 products compliant with OGC standards."

Stan Tilman | Hexagon Geospatial

134

Create more business opportunities for solution providers

135

Create more business opportunities for solution providers

136

Benefits for buyers of solutions

Minimize the delay, cost, frustration of reworking disparate implementations

137

138

139

How long this it take?

•Once the application is passing the test (1-2 months), organizations asking for compliance can:

•Make an online request 5-10 minutes.•OGC will verify and respond in 1-3 days.

140

What if your application is not passing the test?

•Use the community forum citeforum@lists.opengeospatial.org

•About 300 members participate in the forum:– Each test suite has a lead – OGC has alliances with groups supporting the

test (answering questions, fixing bugs, etc.)

141

142

Tests available for certification

Validation portal

http://cite.opengeospatial.org/t

eamengine/

143

How to ask for Compliance“Purchaserseeksgeospatialproductsthatprovidemaximuminteroperabilitywithpurchaser’sanddatasharingpartner’ssystems.Toaccomplishthis,purchaserseekstomakemaximumuseofopenstandardsprovidedbytheOpenGeospatialConsortium(OGC),ISO...”OGCComplianceOverview- GuideforSoftwareAcquisitionWhitepaper(15-002r5)http://docs.opengeospatial.org/wp/15-002r5/15-002r5.html

144

How to verify that a product is compliant?

145

Tools are opensourceand used in

other projects

146

Links

• OGC validation portal:https://github.com/opengeospatial/teamengine

• Source code Test code repositorieshttps://github.com/opengeospatial?page=2&query=ets

• Building the testing facility on the cloud https://github.com/opengeospatial/teamengine-builder/blob/master/build-amazon-instance.rst

• Virtualization Guidehttps://github.com/opengeospatial/teamengine/blob/master/src/site/asciidoc/virt-guide.adoc

Contact Information

•Luis Bermudez • lbermudez@opengeospatial.org•Twitter: @berdez•https://www.linkedin.com/in/bermudez

147