130 likes | 288 Views
Inspire - MIWP 11-12-18 Meeting. BRGM (French Geological Survey ) Sylvain Grellet / François Tertre S.Grellet@brgm.fr / F.Tertre@brgm.fr. BRGM Background. Active in OGC, Inspire, CGI ( GeoSciML , EarthResourceML ) since early times
E N D
Inspire - MIWP 11-12-18 Meeting BRGM (French Geological Survey) Sylvain Grellet / François Tertre S.Grellet@brgm.fr / F.Tertre@brgm.fr
BRGM Background Inspire - MIWP 11-12-18 Meeting • Active in OGC, Inspire, CGI (GeoSciML, EarthResourceML) since early times • Implementation of the rationale in EU or international GeoScience projects for years • UML -> xsd • SOA, OGC services.
Objectives for thoseMIWPs Inspire - MIWP 11-12-18 Meeting Discussing pure GML issues (which version) is one thing… …shouldn’t we solve the feasibility of the Inspire rationale first ? … and properly maintain reference xsds without being in a rush ?
Feedback : some examples (server side) Inspire - MIWP 11-12-18 Meeting ProMine : Geoserver 2.3 on EarthResourceML (MR in Inspire)-> xml conform to an app-schema with complex features but performance issues OneGeology-Europe (2011) : hard to expose complex features with performances -> specific tool development (eXows) to expose GeoSciML. Min4EU - Inspire MR specs extended (now) : planned to use a ‘pre-configured’ Deegree
Feedback : some examples (server side) Inspire - MIWP 11-12-18 Meeting • Tests for the French COVADIS on national standards for natural risk zones (now): • Simple Feature with MapServer compliant to a given app-schema does not really work: can't define a specific namespace and associated URL to be used in the WFS output • After discussion with committers, ComplexFeature would apparently require refactoring the sourcecode.
Issues Inspire - MIWP 11-12-18 Meeting • For more than 10 years, we (incl. BRGM) sell a rationale that does not fully work yet in production mode • Most of the time software (server, desktop GIS...) designed on an "offline basis", xsds embedded within the source code => Not a real XML aware (XMLSpy, oXygen, …) way of working, => Will cause issues when updating the schemas (link to maintenance discussion)
Issues Inspire - MIWP 11-12-18 Meeting • Very few solutions available out there : • Ex for the server side: • OpenSource : • * Geoserver2.5 : said to solve the performance issue. Not tested at BRGM yet, • * Deegree3.3.x : will be tested under Min4EU • * … • Vendor Side ? • Conclusion • We should work on two aspects • 1°/ Help enhance the implementation (client, server) • 2°/ Lower the implementation barrier in Inspire
Issues Inspire - MIWP 11-12-18 Meeting • Very few solutions available out there : • Ex for the server side: • OpenSource : • * Geoserver2.5 : said to solve the performance issue. Not tested at BRGM yet, • * Deegree3.3.x : will be tested under Min4EU • * … • Vendor Side ? • Conclusion • We should work on two aspects • 1°/ Help enhance the implementation (client, server) • 2°/ Lower the implementation barrier in Inspire
Whish list – enhance the implementation Inspire - MIWP 11-12-18 Meeting • Have an “Inspire-labeled” compatibility matrix • To help people find out what to use, to help steer communities / vendors. • Example for server • could add : link to external application schema • Have cookbooks • such as http://data.gov.uk/sites/default/files/library/INSPIREWFSCookbook_v1.0.pdf
Whish list – lower the barrier Portrayal Class ‘BoreholeView’ ‘Borehole’ Xsd Generation Linked to SF-0 DSI / ISTN / SDI COVADIS – 22/01/2014 – s.grellet@brgm.fr Inspire - MIWP 11-12-18 Meeting • Add portrayal classes to Inspire. • Example GeoSciML : portrayal class designed to be SF-0 compliant
Whish list – lower the barrier Inspire - MIWP 11-12-18 Meeting • Add portrayal classes to Inspire • Will help split from conceptual model to exchange scenarii, • Will help answer questions about what Feature exposed in the WFS : • all FeatureTypes in the Schema ? • only those in the Portayal chapter ? • how many associations should be traversed ?
Xsds maintenance Inspire - MIWP 11-12-18 Meeting • Are Xsd provided by JRC mandatory (in the IRs) or just a de facto standard ? => De facto standard : less pressure if we change them • Tools have to be developed in an XML aware way (see previous slides) -> to avoid recompiling libs associated to those tools • A permanent EU group has to be set up to coordinate the maintenance and communicate on it • MIG representative + drafting teams representatives + implementers
Xsds maintenance Inspire - MIWP 11-12-18 Meeting • Vendor / open-source when claiming Inspire compatibility should point to the schema version they support • Published schema have to remain online for a couple while and remain un-touched • Bug fixing / changes have • to be clearly separated • even if they breaks retrocompatibility (with schema) • if they change what’s in the IR’s it’s another issue. =>please don’t create fake classes to maintain the link with previous version we tried to be conceptually clean for years !