1 / 34

Web Mapping Services Standards for Framework Datasets November 2010

Explore the role and development of web mapping services standards for authoritative, optimized, interoperable, and discoverable web maps. Examples and considerations are discussed.

cjill
Download Presentation

Web Mapping Services Standards for Framework Datasets November 2010

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Mapping Services Standards for Framework DatasetsNovember 2010 Moderator: Dorothy Mortenson Framework Coordinator: Milton Hill Panel Members: Erik Endrulat Tanya Haddad Eli Adam Rob McDougald

  2. Question for the day • Is there a role for web mapping services standards? • If so, now should we develop them?

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

  4. Considerations thru Examples • Example 1: 2005 Orthophotos • Example 2: Cartographic Sensitive Data • Example 3: Hydrography • Example 4: Dams

  5. 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

  6. 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

  7. 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?

  8. 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?

  9. The Panel • Erik Endrulat, Geospatial Enterprise Office Web Services available through Oregon GEO • Tanya Haddad, Oregon Coastal Atlas Metadata , Catalogs, and Services • Eli Adam, Lincoln County Interoperability; web feasibility/optimization • Rob McDougald, GeoMeridian Government Web Service Switchboard

  10. Panel Presentations

  11. Erik Endrulat Web Services available through Oregon GEO

  12. FrameworkThemes & Data Clearinghouses: Web Services @ Oregon GEO http://gis.oregon.gov | http://arcgis.com(search for Group=Oregon)

  13. Web Services @ Oregon GEO Web Service Example Stream imagery as WMS or ECWP to desktop or web client Saves $$$ by avoiding data duplication http://imagery.oregonexplorer.info/

  14. 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.

  15. OR Stimulus App. SOS Drop Box App. ODF LocatOR OWEB Investment Tracker Web Services @ Oregon GEO Add services directly into desktop client (ArcMap 10) Include (and reuse) services in web applications

  16. Tanya HaddadMetadata , Catalogs, and Services

  17. Mediation Mediation Harmonization Mediation Harmonization Harmonization Discoveryschool.com Interoperability I • The world (wide web) is a diverse place • To Harmonize or Mediate? – that is the question Mediation Harmonization

  18. 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)

  19. 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

  20. Eli AdamInteroperability; web feasibility/optimization

  21. Interoperability (server and client) • You can view the Oregon Imagery Explorer WMS in 100s of clients 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)

  22. Interoperability (server and client)

  23. Interoperability (server and client)

  24. 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)

  25. 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

  26. Rob McDougaldGovernment Web Service Switchboard

  27. Gov. Web Service Switchboard Rob McDougald, GeoMeridian RobMcDougald@GeoMeridian.com503.206.7202 Coming to you live from the dark recesses of Rob’s mind.

  28. 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.

  29. 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

  30. 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

  31. Why Gov. Web Service Switchboard • 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. ParcelWS Route API GIS User RoadWS Public User Business Application Integration Or …n(n-1)/2

  32. Questions for the Panel

  33. 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?

  34. Contacts • Erik Endrulat, Geospatial Enterprise Office (GEO) erik.endrulat@state.or.us (503)378-2781 • Tanya Haddad, Oregon Coastal Atlas tanya.haddad@state.or.us (971) 673-0962 • Eli Adam, Lincoln County eadam@co.lincoln.or.us (541)574-1289 • Rob McDougald, GeoMeridian RobMcDougald@GeoMeridian.com (503)206-7202 • Dorothy Mortenson, OR Water Resources mortendc@wrd.state.or.us (503)986-0857 • Milton Hill, GEO - Framework Coordinator milton.e.hill@state.or.us (503)378-3157

More Related