1 / 7

User Requirements and Use Cases Workpackage 5

User Requirements and Use Cases Workpackage 5. Roger Longhorn Director, GI Projects Office, IDG (UK) Ltd MOTIIVE Project Steering Committee Leader e-mail: ral@alum.mit.edu. MOTIIVE Concept (Dec. 2003). Main Tasks

sheera
Télécharger la présentation

User Requirements and Use Cases Workpackage 5

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. User Requirements and Use Cases Workpackage 5 Roger Longhorn Director, GI Projects Office, IDG (UK) Ltd MOTIIVE Project Steering Committee Leader e-mail: ral@alum.mit.edu

  2. MOTIIVE Concept (Dec. 2003) Main Tasks Investigate interoperability issues for land-sea data integration by focusing on two marine data harmonisation projects conducted in the UK between 2001 and 2003 - the Integrated Coastal Hydrography (ICH) project and the Integrated Coastal Zone Mapping (ICZMap) project. Identify and analyze the specific workflows employed in achieving the projects’ objectives. Prepare a formal list of recommendations as guidelines for participants in WP6

  3. WP5 - Pre-standardisation Test Cases Work Undertaken • ICZMap data and workflow requirements were analysed (see Deliverable D7a). • ICH project data was not available. • SeaZone Solutions “Hydrospatial” product work. • SeaZone Feature Codes proposed • Governance issues – IHO, IOC • Marine/Coastal Community study (Deliverable 7b).

  4. Results – ICZMap Analysis With reference to ICZMap & SeaZone Hydrospatial coastal data “products” (integrated land and sea data): • OSGB topographic and UKHO hydrographic data is being integrated and (some) common codes are being used/developed. • Vertical datum issues “resolved”. • Standards, such as common Feature Codes would only be partially useful at this stage of the matching process – much is ‘brute force’ requiring significant human intervention in the workflows. • Once the integrated dataset is complete – and common Feature Type Codes have been agreed and institutionalized – future users will reap the benefits. • Over 250 marine Feature Type Codes identified as being of primary interest – presented to IHO for further consideration.

  5. Results – Marine/Coastal Community Study Policy drivers identified: • Monitoring, reporting and surveillance • Design and policy development • Emergency operations & disaster response User Cases identified and created: • EUROSION user requirement and expectation • MESH Project – Mapping European Seabed Habitats • DeCOVER Project – land cover data in Germany • RIKZ requirements (coastal management in NL) • MAOTDR – coastal law enforcement (Portugal) • DEDUCE and Catalunya provincial government needs INSPIRE and European ICZM

  6. Results – Marine/Coastal Community Study INSPIRE and European ICZM • Most coastal/marine data is in Annexes II and III, for ‘later’ implementation in INSPIRE. • Much of the practical work or applications wanted by the marine/coastal community is being left to the different thematic communities to define, i.e. marine/coastal. • Coastal data model and centralized framework for ICZM data collection and storage should b developed, addressing: Data availability Data gaps Data quality Data accessibility

  7. Results – Marine/Coastal Community Study INSPIRE and European ICZM –understanding INSPIRE • INSPIRE Metadata ‘roadmap’ produced for EUCC to distribute (25,000 on mail list and newsletter subscribers). • INSPIRE Data specification ‘roadmap’ in preparation for EUCC to be used at future conferences and distributed on-line and via newsletters. • What the community wants are practical guidelines, i.e. how to manage spatial metadata, how to encode the metadata, defining machine-readable metadata for service delivery, etc.

More Related