Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.
Practical Experience of INSPIRE Annex I Testing: Transforming Data into INSPIRE Data Specifications and Making Data Access...
Overview of INSPIRE Testing Call<br />Objectives of INSPIRE testing were to:<br />Understand the feasibility of transformi...
Overview of INSPIRE Testing Call<br />Only 60 of 89 tests involved full transformation test rest were paper exercise<br />...
Snowflake Software’s Experiences <br />Snowflake Software was directly and indirectly involved with 10 organisations acros...
Transforming Data into INSPIRE Themes<br />Two key approaches are advocated for transforming and publishing data into INSP...
Making INSPIRE Data Accessible via INSPIRE Download Services<br />GO Publisher Desktop, Agent and WFS were also used to de...
Demonstration: Transforming HMLR data into INSPIRE Cadastral Parcels <br />Test the feasibility and benefits of using Comm...
Defining the Translation: GO Publisher Desktop<br />Database tables and columns<br />XML schema elements<br />Pull down li...
Visualising output: GML Viewer<br />
The Solution Architecture<br />
Differences between HMLR and INSPIRE data specifications<br />HMLR<br />INSPIRE Cadastral Parcel<br />Land registry datase...
Issues: Managing identity and feature lifecycles as INSPIRE GML application schema requires 3 different identifiers:</li><...
Benefits of GO Publisher<br />High productivity was achieved<br />Configuration alone was sufficient<br />No programming o...
Benefits of On-the-Fly Translation using GO Publisher<br />Re-use existing database infrastructure<br />Minor disruption t...
Summary of Key Outcomes and Experiences<br />All organisations using GO Publisher were able to successfully demonstrate th...
Summary of Key Outcomes and Experiences<br />Many organisations identified areas where further work would be needed to bet...
Conclusions<br />A number of technical and business issues exist that need to be addressed at various levels (organisation...
Upcoming SlideShare
Loading in …5
×

INSPIRE Annex Testing

614 views

Published on

INSPIRE Annex Testing

Published in: Technology
  • Be the first to comment

  • Be the first to like this

INSPIRE Annex Testing

  1. 1. Practical Experience of INSPIRE Annex I Testing: Transforming Data into INSPIRE Data Specifications and Making Data Accessible via Download Services<br />Debbie Wilson<br />debbie.wilson@snowflakesoftware.com<br />
  2. 2. Overview of INSPIRE Testing Call<br />Objectives of INSPIRE testing were to:<br />Understand the feasibility of transforming and publishing data into proposed INSPIRE Annex I data specification<br />Demonstrate ability to access data via INSPIRE Download Services<br />Evaluate costs and benefits of publishing data into the INSPIRE data specification via Download Services<br />89 testing reports were received from 16 Member States from >70 organisations:<br />
  3. 3. Overview of INSPIRE Testing Call<br />Only 60 of 89 tests involved full transformation test rest were paper exercise<br />Of those organisations using COTS software ~40% used Snowflake’s GO Publisher Desktop & WFS<br />
  4. 4. Snowflake Software’s Experiences <br />Snowflake Software was directly and indirectly involved with 10 organisations across Europe:<br />
  5. 5. Transforming Data into INSPIRE Themes<br />Two key approaches are advocated for transforming and publishing data into INSPIRE themes:<br />Offline Transformation: Data is transformed and stored into the INSPIRE data specification (i.e. flat files or separate database)<br />On-the-fly Transformation: Data is stored once and transformed into the INSPIRE data specification on request by the download service<br />Offline transformation may be the most suitable option for datasets that are not updated regularly <br />On-the-fly transformation is most suitable for datasets that are updated regularly and where organisations need to support data access to a wide range end users in different data specifications defined for different use cases<br />Both approaches were evaluated during the testing phase<br />
  6. 6. Making INSPIRE Data Accessible via INSPIRE Download Services<br />GO Publisher Desktop, Agent and WFS were also used to demonstrate how organisations can develop download and direct access services <br />INSPIRE Implementing Rules define two types of Download Service:<br />Basic Download Service: Files can be downloaded for local use via HTTP/FTP <br />Advanced Download Service: User can define the extent (geographic, temporal, attribute) of the data they need to be downloaded through either: Data Ordering Services or Web Feature Services (WFS)<br />
  7. 7. Demonstration: Transforming HMLR data into INSPIRE Cadastral Parcels <br />Test the feasibility and benefits of using Commercial Off-The-Shelf (COTS) software for INSPIRE<br />Develop the translation without software customisation or development of bespoke scripts<br />Work quickly and productively to reduce costs<br />Refine the translation over several iterations within a limited time period<br />Implement Simple and Advanced Download Services to explore the practical issues of implementing real business requirements<br />On-the-fly translation to avoid replicating database infrastructure <br />Source data from the existing HMLR data model to avoid disruption to existing business processes<br /> “manage once, publish many times”<br />Implement an “industrial strength” solution<br />
  8. 8. Defining the Translation: GO Publisher Desktop<br />Database tables and columns<br />XML schema elements<br />Pull down lists populated from the XML schema<br />Preview panel<br />
  9. 9. Visualising output: GML Viewer<br />
  10. 10. The Solution Architecture<br />
  11. 11. Differences between HMLR and INSPIRE data specifications<br />HMLR<br />INSPIRE Cadastral Parcel<br />Land registry dataset<br />No boundaries or index sets<br />Title is the unit of management<br />Only titles have unique identifiers<br />No reference point values<br />Cadastral index model<br />Boundaries & index sets included<br />Parcel is the unit of management<br />Polygons have unique identifiers<br />Reference point geometry allowed<br /><ul><li>Despite these different viewpoints, it is possible to map each component object within a land title to a cadastral parcel.
  12. 12. Issues: Managing identity and feature lifecycles as INSPIRE GML application schema requires 3 different identifiers:</li></ul>INSPIRE Identifier <br />National Identifier<br />gmlID<br />
  13. 13. Benefits of GO Publisher<br />High productivity was achieved<br />Configuration alone was sufficient<br />No programming or scripting skills were needed<br />Several iterations of the translation were achieved in a limited time-frame<br />Supported progression from simple to advanced services<br />Initially deployed as simple file creation<br />Translation re-deployed as a WFS to support user querying<br />Mature “Industrial Strength” solution<br />Although INSPIRE Quality of Service Requirements were not evaluated in this test, scalability and performance has already been proven in previous deployments<br />The number of independent evaluations and our existing operational deployment base means that the technology is well tested and reliable<br />
  14. 14. Benefits of On-the-Fly Translation using GO Publisher<br />Re-use existing database infrastructure<br />Minor disruption to existing business processes<br />Extra translations added at low cost<br />Low initial investment - costs scale with increasing levels of data traffic<br />Example Architecture of an SDI<br />
  15. 15. Summary of Key Outcomes and Experiences<br />All organisations using GO Publisher were able to successfully demonstrate that they could transform their data into INSPIRE Annex data specifications<br />However, several issues relating to data transformation and publication were identified by many organisations:<br />Insufficient time to adequately undertake testing (few application tests)<br />Complexities involved in undertaking conceptual mapping of their data model to INSPIRE GML application schema (xsd) or UML model<br />In-experience of staff to transform data from their source format into GML<br />Lack of harmonisation in the way common concepts were modelled and to be implemented in v2.0 (e.g. Identifiers, lifecycle information, naming conventions)<br />
  16. 16. Summary of Key Outcomes and Experiences<br />Many organisations identified areas where further work would be needed to better understand how to operationally publish data into the INSPIRE specifications, particularly where this is achieved on-the-fly:<br />Identifier Management<br />Managing feature lifecycles particularly those features generated on-the-fly<br />Translating between different codelist values<br />Measuring and quantifying quality of transformed output (geometric and attribute) to ensure that it is consistent with source data quality levels and other data quality levels<br />Metadata: how can organisations integrate the creation and publication of metadata into operational data management and publication workflows<br />
  17. 17. Conclusions<br />A number of technical and business issues exist that need to be addressed at various levels (organisational, inter-agency and Member State)<br />Organisations need to perform more extensive testing to better understand how to incorporate requirements of INSPIRE data specifications into their business processes, datasets, products and infrastructure<br />Responsibility for creation and maintenance of some themes falls across multiple agencies or has been devolved to multiple organisations responsible for a specific geographic region (e.g. transport: road, rail, aviation, water, devolved administrations, local/regional authorities):<br />Need to better understand impact of cross-border/edge-matching issues<br />How can data be seamlessly integrated when combining data from multiple organisations for a single INSPIRE data specification<br />Organisations need facilities to support each other so they can share experiences and ensure everyone can better understand what they need to do to publish their data<br />
  18. 18. Questions?<br />debbie.wilson@snowflakesoftware.com<br />For demo of HMLR testing go to: <br />http://www.youtube.com/user/snowflakesoftware#p/u/14/V4Ut8kKL5YI<br />

×