Transcript Geoservices
Webservices, aka Geoservices The realisation of an SDI at the Dutch Ministry of Transport, Public Works and Water Management (VenW) Wim de Haas, projectmanager ADAGUC 3OCT2006 ADAGUC 3OCT2006 Outline • • • • • • • Aim of this presentation Brief introduction of the Ministry Geoservices OSS Historical perspective and user view Pittfalls beyond the usual suspects Conclusions 2 ADAGUC 3OCT2006 Deliverables ADAGUC • Open Source conversion tools • Selected atmospheric datasets in GIS format • Web service to demonstrate the usability of the above to the geospatial and atmospheric community. 3 ADAGUC 3OCT2006 Aim of this presentation • To share experiences on the development and use of OS Geotools • To give inside information on the practical use of OSS in a central government, showcasing Geoservices • To give some points of view on the mechanisms in the OSS field 4 ADAGUC 3OCT2006 Putt’s Law Technology is dominated by two types of people: those who understand what they do not manage, and those who manage what they do not understand. 5 ADAGUC 3OCT2006 The Ministry of Transport, etc. The core tasks of V&W are: • to offer protection against floods • to guarantee safe and reliable connections over land, water and through the air • to ensure clean and sufficient water • Rijkswaterstaat (RWS) is the executive branche of the Ministry of Transport 6 ADAGUC 3OCT2006 Water-based infrastructure Water-based infrastructure under Rijkswaterstaat management : State-managed waters: approx. 850 km of major rivers, approx. 300 km of major canals; North Sea; Delta region; Wadden Sea; IJsselmeer region • Flood defences: 300 km out of a total of 3565 km of primary flood defences • Water management structures: 10 dams, 9 discharge sluices, 2 guard locks, 50 navigation locks 7 ADAGUC 3OCT2006 Land-based infrastructure Land-based infrastructure under Rijkswaterstaat management : • 3250 km of main roads (of which > 2100 km of motorway), approx. 1000 km with traffic control systems • 14 tunnels, 7 road traffic control centres, 91 DRIPs, 51 Entry Point devices, 11 rush hour lanes, 5 wildlife overpasses Total economic value: approx. EUR 25 billion 8 ADAGUC 3OCT2006 Geoservices (1) Geoservices solutions facilitate communication between departments: • By standardizing on open interfaces • Using OGC standards • Design principle: All applications will be designed as a network of services • The motto: Build whatever you want to build guided by Geoservices, unless you have solid reasons to go without 9 ADAGUC 10 3OCT2006 Geoservices (2) • Geoservices = Open Standards • Geoservices = Architecture built on OGC interfaces (WMS,WFS,WCS,SLD,GML) • Geoservices = – – – – Data visualisation Data access Data discovery Metadata • Current focus on technical interoperability, not semantic interoperability • BTW: VenW, so KNMI too, is member of OGC ADAGUC 11 3OCT2006 Geoservices (3) 2. Requestor localizes data/service Registry Find 1. Provider publices data and services at Registry Publish Requestor Provider Bind 3. Requestor start service ADAGUC 12 3OCT2006 Geoservices (4) WCS support netCDF funded by NASA OSS : Proprietary software : • Mapserver v4.8 • IONIC RedSpiderWeb, Catalog, Enterprise • GDAL • OGR • Chameleon v2.4 • GeoServer v1.0 • ESRI ArcGIS, ArcIMS, ArcSDE • Oracle Spatial 10g r1 • LizardTech • Deegree v1.0 • Mapbuilder v1.0 Still: GIS friendlyness is our focus ADAGUC 13 3OCT2006 OSS (Thanks to Paul Ramsey) • By definition: software in which the code is available for distribution and modification • A lot to choose from: BSD, MIT, GPL, LGPL • What makes some OSS projects successful and others not? • Can we measure the success of OSS projects? Successful OSS projects and how to measure them ADAGUC 14 3OCT2006 A community of shared interest is what drives a successful project • The software itself is designed in a modular manner • The software is extremely well documented • The software core design and development process is transparent • The core team itself is modular and transparent • IP rights: provenance tracking ADAGUC 15 3OCT2006 Outline • • • • • • • Aim of this presentation Brief introduction of the Ministry Geoservices OSS Historical perspective and user view Pittfalls beyond the usual suspects Conclusions ADAGUC 16 3OCT2006 Historical perspective: Gartner (2003) on Open Source Applications 20062004-2006: Experimenting 2000-2004: Under the radar Me-too extensions User is developer Basics in place Innovation Start Geoservices Trusting? Technical maturity Skills availability Stack alignment ISV support Acquisition costs Product ‘repurposing’ Niche roles Awareness Geoservices Service and support Change management Risk management Total costs Relevant standards Geoservices considered a stable product ADAGUC 17 3OCT2006 Historical perspective: Quality OSS: Real Benefits, Hidden Costs Assurance Benefits Licensing Model No Licenses (Upfront or Upgrade) No Overcommitment No Supplier or License Management No Ongoing Maintenance Peer Support Groups Mutual Dev. Model Open-Source Software Mktg. Hype Social Movement Political Hype Selection/ Audit Fees Internal Support After Gartner 2003 Skill Transfer and Training Costs Internal Disposal Maintenance and and Replacement Development ADAGUC 18 3OCT2006 Political hype • Motie Vendrik 20NOV2002: government shall stimulate the use of OSS and open standards, pursuing that in 2006 all government bodies shall adopt open standards • Succeeded by a statement of the minister of Economic Affairs on 2FEB2004: new legislation to lower the barriers for smaller and younger companies to do business with the government Costs: Internal maintenance and development ADAGUC 19 3OCT2006 • DIY: you’re at the steering wheel • Fun if you like it: change management, release cycles is more of an issue compared to traditional software development opportunities for OSS companies (packaging) • It’s all about creating trust both internally and externally ADAGUC 20 3OCT2006 Benefits: Quality guarantee • OSS provides an excellent tool for keeping ALL vendors on edge: true interoperability is not something written down in a white paper, but proofs itself only in real production environments • OSS fits the equation ADAGUC 21 3OCT2006 Remember Putt’s Law? Technology is dominated by two types of people: those who understand what they do not manage, and those who manage what they do not understand. ADAGUC 22 3OCT2006 The not so obvious pittfalls (1) First comment on Putt’s Law: • A third type of people can be identified who neither manage nor understand the technology, whether it be OSS or Open Standards: the end-users • And after all, why should they? – Why rebuild everything we already have – Open standards may be working, but what about my functionality? • A technology driven programme contrasts with functionality driven users ADAGUC 23 3OCT2006 The not so obvious pittfalls (2) Users, management and IT have different perspectives: • Users are data centered, IT is services centered, and management has a strong budget focus and they all have different timescales • In R&D environments end-users are developers too ADAGUC 24 3OCT2006 Concluding remarks • Everybody can exchange geo-information via the geoservices framework • OSS is not for the faint at heart • OSS is not longer developer centric, but instead, users are becoming more into play • After burner: the only successful SDI’s are backed up by legislation: European Water Directive, INSPIRE ADAGUC 25 3OCT2006 Some application screenshots ADAGUC 26 3OCT2006 Implementatie 2 ADAGUC 27 3OCT2006 Implementatie 3 ADAGUC 28 3OCT2006 Implementatie 4 ADAGUC 29 3OCT2006 URL’s http://www.rijkswaterstaat.nl/apps/geoservices/portaal/ http://www.rijkswaterstaat.nl/services/geoservices/basispa kket/dtb? http://www.rijkswaterstaat.nl/services/geoservices/basispa kket/grenzen? ADAGUC 30 3OCT2006 Questions? Wim de Haas mailto:[email protected]