GeoAvalanche infrastructure for interoperability

1. OGC Standards and web services
pipeline for managing CAAML data
Francesco Bartoli
GEOBEYOND SRL

2. What are open geospatial
standards?
A common way to overcome interoperability issues
Open Geospatial Consortium is the organization that
governs their specifications
The most appropriated for the context:
GML (Geography Markup Language) - base building block
already used by CAAML
WMS (Web Mapping Service) – for rendering information
on maps
WFS (Web Feature Service) – for streamlining vector
datasets
WCS (Web Coverage Service) – for streamlining raster
datasets
WPS (Web Processing Service) – for running and

3. What does really interoperability
mean?
I have defined CAAML I think it’s quite enough!
Given I have a contract what are the most
recommended reference implementation softwares
compliant with OGC WFS?
Do I need a spatial database? Yes you should use
one because the elements from CAAML schemas
are heavily based on the concept of location
INSPIRE gives specific guidance for online services
of EU Member States to be compatible in a cross-
boundary context
View services must be OGC WMS compliant
Download services must be OGC WFS compliant

4. I want the software!
GeoServer and the upstream GeoAvalanche server
OGC reference implementation for WMS, WFS, WCS
has the GML application schema extension to support
complex features from CAAML databases
has the INSPIRE plugin to support view and download
services
PostGIS is the most prominent spatial database
which is supported natively by
GeoServer/GeoAvalanche
Hale Studio (really you cannot believe this!) is the
magic tool to define and upload automatically a
mapping configuration from your CAAML database
model into an WFS output comform to the CAAML

5. Uhmm…really? Give me
examples!
http://localhost:8080/geoavalanche

6. Flexible Architecture
GraphQL
CAAML WFS WEB SERVICE
OGC WMS
OGC WFS
OGC CSW

7. Challenges
Involve as much as possible avalanche community
parties as they are the legal authorities and have the
ownership of source CAAML schemas and profiles
Educate them to adopt existing geospatial open
source technologies in order to publish OGC and
INSPIRE compliant datasets and services
Make the development and lifecycle of CAAML more
transparent and publicly available (a github
organization would be a worth out there)

8. Conclusions
Please stop to exchange unpleasant CAAML files
and implement your CAAML contract on top of OGC
WFS web services
Use OGC standards as much as possible, once they
are adopted the possibilities to exploit them are
endless
Don’t be lazy and store your CAAML datasets into a
spatial database
Be flexible and make developers happier to access
your CAAML database for back-office Create-Read-
Update-Delete operations. GraphQL is awesome

9. Thanks for your attention
https://github.com/geoavalanche/caaml-workshop -
CAAML workshop at ISSW 2018
https://github.com/geoavalanche/caaml - CAAML
sample data for the workshop
https://github.com/geoavalanche/geoavalanche-
server - GeoAvalanche server with CAAML
extension code repository
https://twitter.com/geoavalanche - Twitter account
info@geobeyond.it - - How to get support and add
new features