Web Mapping Services Standards for Framework Datasets November 2010 Panel Members: Erik Endrulat...

Web Mapping Services Standards for

Framework DatasetsNovember 2010

Panel Members:

Erik Endrulat

Tanya Haddad

Eli Adam

Rob McDougald

Moderator: Dorothy Mortenson

Framework Coordinator: Milton Hill

Question for the day

Is there a role for web mapping services standards?

If so, now should we develop them?

Visualization

Authoritative web map services that are cartographically representative, optimized for performance, interoperable, documented, and discoverable

Considerations thru Examples

Example 1: 2005 Orthophotos Example 2: Cartographic Sensitive Data Example 3: Hydrography Example 4: Dams

2005 Orthophotos – Role Model

Authoritative web mapping services Interoperable Easy to use Inclusive, established and robust Discoverable through Oregon Spatial Data

Library and ArcGIS Online

Considerations…Cartographic Sensitive Data

Some data, like geology, wetlands, land ownership, coastal hazards and transportation, may require specifications for cartographic representation.

There may be some required queries in order to generalize or may be some symbology required behind the representation of a dataset

Minimize the need for a legend

Hydrography

Data design is complex and uses events and routes.

To improve performance for WMS, these data need to be “flattened”.

Only publish a couple of attributes How should this simplification procedure be

integrated into the Framework Standard?

Dams

A “best available” dams dataset and posted on the GEO alpha list.

The data does not meet any specific data standards. Source agency intends to create a WMS after some

internal work GEO created a WMS for dams How and when do we decide a dataset is ready for

web publishing and who holds the authoritative dataset?

The Panel

Erik Endrulat, Geospatial Enterprise OfficeWeb Services available through Oregon GEO

Tanya Haddad, Oregon Coastal AtlasMetadata , Catalogs, and Services

Eli Adam, Lincoln CountyInteroperability; web feasibility/optimization

Rob McDougald, GeoMeridianGovernment Web Service Switchboard

Panel Presentations

Erik Endrulat Web Services available through Oregon GEO

Web Services @ Oregon GEO

Clearinghouses:

FrameworkFrameworkThemesThemes& Data& Data

http://gis.oregon.gov | http://arcgis.com (search for Group=Oregon)

Stream imagery as WMS or ECWP to desktop or web client

Saves $$$ by avoiding data duplication

Web Services @ Oregon GEO

Web Service Example

http://oe.oregonexplorer.info/imagery/

Web Services @ Oregon GEO

Current Process

Identify datasets Document metadata Create cartography Publish (ArcGIS

REST, WMS, SOAP) Register on Catalog

1. Existing data from OR Spatial Data Library

2. Web Service for desktop or Web app.

Add services directly into desktop client (ArcMap 10)

Web Services @ Oregon GEO

OWEB Investment Tracker

OR Stimulus App. SOS Drop Box App.

ODF LocatOR

Include (and reuse) services in web

applications

Tanya Haddad Metadata , Catalogs, and Services

Interoperability I

The world (wide web) is a diverse place

Discoveryschool.com

Mediation

Harmonization

Mediation

Harmonization

Mediation

Harmonization

HarmonizationMediation

To Harmonize or Mediate? – that is the question

Interoperability II

Standards give us just enough harmonization across applications to make life easier

Standards for different things can link together to allow chains of interactions

Metadata (FGDC, ISO) Data Catalogs (CSW) Data Services (WMS, WFS, WCS) Analysis (WPS)

Interoperability III

Lots of data is already available via OGC standards

Many clients to choose from – ArcMap is a very powerful option

If we do our metadatacorrectly and serve itvia catalogs, we canpoint our users to many types of dataservices

Eli Adam Interoperability; web feasibility/optimization

Interoperability (server and client)

You can view the Oregon Imagery Explorer WMS in 100s of clients (http://www.opengeospatial.org/resource/products/byspec) Web Map Service v.1.1.1

You can server WMS v.1.1.1 with hundreds of servers as well

Both clients and servers include numerous vendors (Autodesk, Bentley, ERDAS, ESRI, Intergraph, Oracle, PCI Geomatics) and open source projects (The Carbon Project, GeoServer, Mapserver, Universities, others)

Interoperability (server and client)

Interoperability (server and client)

Interoperability

WMS is an established standard first released in 2000 and updated more recently

Many existing WMS servers (USGS, other federal agencies, INSPIRE, etc)

There are even more projects that implement WMS client support but haven’t certified for compliance (OpenLayers, Google Earth/maps, VE, NASA World Wind, GDAL, udig, qgis, gvSIG, GRASS, many others)

Web optimization

Send the smallest sized data needed Consider single band pseudo-color rather

than 3 band rgb or even 4 band rgba Send only most useful non-derivable

fields You can have subsequent additional

specific requests for more data

Rob McDougaldGovernment Web Service Switchboard

Gov. Web Service

Switchboard

Rob McDougald, GeoMeridianRobMcDougald@GeoMeridian.com

503.206.7202

Coming to you live from the dark recesses of Rob’s

mind.

Today Everyone Is Issuing Phone Numbers

“Everyone” is standing up web services, web-based data services, web map services, and public APIs

We need middleware infrastructure to share web services. We need a web service switchboard so we don’t end up with this.

Do the math. n(n-1)/2. 10 web services = 45 point to point integrations.How many WS will you integrate with?

36 counties, 250 cities, 20 to 60 state agencies, X random APIs.

Risk. Ask your lawyer. “Sorry your Electitude. Someone changed “taxno””

We need “Authoritative Process” to get authoritative data.

Why Don’t We AUTHORIZE Our Own Phone Numbers?

The Solution: Build a governmental “informational infrastructure” to REUSE, integrate, MAINTAIN, and share data across ALL levels of government.

Build a middleware WS Switchboard. ESB, SOA, EAI, EA, XYZ PDQ

Build an “Authoritative Process” to manage the Switchboard. Governance.

“Another flaw in the human character is that everybody wants to build and nobody wants to do maintenance."  Kurt Vonnegut

Gov. Web Service Switchboard (ESB/SOA Middleware)

• Leverage EAI/ESB/SOA best practices. • Authoritative Process = standards, sustainability,

confidence, credibility, and funding.• SOA contract. SLA, data standards, WS standards, API

WSDL, metadata, maintenance strategy … • Committee structure

• Extend existing FIT, GIG, RLIS, EISPD governance models.• Adopt big boy IT practices

Or …n(n-1)/2

ParcelWS

RoadWS

RouteAPI

PublicUser

GISUser

Business Application Integration

• Automate and improve business processes.

• Re-use versus re-create services.• Eliminate point-to-point integration

challenges.• Easily design, deploy and re-use Web services.• Efficiently govern SOA-based initiatives.• Launch robust enterprise class solutions without

coding.• Leverage existing legacy applications investments.• Gain real-time visibility into operational and business

activity.

MAKE YOUR BUSINESSES FASTER, CHEAPER, BETTER, AND MORE TRANSPARENT.

Why Gov. Web Service Switchboard

Questions for the Panel

Question for the day

Is there a role for Web Mapping Services Standards?

If so, now should we develop them? – any additions to what was discussed?

What to do in the next 6 months?

Contacts Erik Endrulat, Geospatial Enterprise Office (GEO)

erik.endrulat@state.or.us(503)378-2781

Tanya Haddad, Oregon Coastal Atlastanya.haddad@state.or.us(971) 673-0962

Eli Adam, Lincoln Countyeadam@co.lincoln.or.us (541)574-1289

Rob McDougald, GeoMeridianRobMcDougald@GeoMeridian.com(503)206-7202

Dorothy Mortenson, OR Water Resourcesmortendc@wrd.state.or.us(503)986-0857

Milton Hill, GEO - Framework Coordinatormilton.e.hill@state.or.us(503)378-3157