1 / 21

Hydrographic Data Strategy GeoTec 2010 April 13 th , 2010

Hydrographic Data Strategy GeoTec 2010 April 13 th , 2010. Shawn Kelleher, Project Manager & Monique Kuyvenhoven, Data Architect. Presentation Overview . HDS Background HDS Sub-Project Overview Data Model Structure Questions. HDS Background. Strategy written in 2007

eliora
Download Presentation

Hydrographic Data Strategy GeoTec 2010 April 13 th , 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. Hydrographic Data Strategy GeoTec 2010 April 13th, 2010 Shawn Kelleher, Project Manager & Monique Kuyvenhoven, Data Architect

  2. Presentation Overview • HDS Background • HDS Sub-Project Overview • Data Model Structure • Questions

  3. HDS Background • Strategy written in 2007 • Governance structure • Partnerships • Timeline • Project scope

  4. HDS Sub Project Updates • Merge Project • Topology QA/QC • National Hydro Network (NHN) • Data Content • Data Specifications • Data Maintenance • Small Scale Mapping

  5. Merge Project • Phase 1 – Merge connectivity and direction from WRIP water flow network into the existing NRVIS waterline layer • 114 Watersheds south of Far North completed • 1 Watershed in GTA remains • Far North (~50 Watersheds) done by NRCan • Additional ‘Topology Editing’ needed to make the network functional

  6. Topology QA/QC • Phase 2 – Topology editing and Quality Assurance testing completed • The Water Flow Network has many uses • Stream ordering • Watershed creation • Tracing/routing up and down stream • Will be utilized in the creation of small scale map products

  7. National Hydrographic Network (NHN) • Agreement signed with NRCan to support the NHN • Half of 115 watersheds delivered by Mar 31, 2010 in a NHN ‘hybrid model’ format • Remaining watersheds by Oct 31, 2010 • Far North watersheds done by NRCan • Prior to posting NHN data to GeoBase, NRCan will process hybrid watersheds • BDI developed NHN conversion process (manual and automated) using two ‘test’ watersheds • Process identifying additional topology/network integrity items that will be fixed in 2010/11

  8. Data Content • Geographic Names sourced from the Geographic Names Extent Layer (GEL) are being added to new water layers • Official geographic names including official alternates • Names linked to geographic name (toponymic) extents of officially named features • At present, 75% of the Lakes, Rivers and Streams have their extents defined in the GEL • Wetlands will not be included in the new Waterbody layer • Prior to implementing the new models, existing wetlands data will be made available

  9. Data Specifications • Finalizing the creation of ‘updated’ medium scale hydrographic data capture specs • Provide a standardized process to interpret larger scale data for the purpose of updating medium scale • In partnership with Conservation Ontario, developed comprehensive Imagery and Elevation Acquisition Guidelines • Province utilizing these guidelines for imagery acquisition projects (SWOOP II, COOP)

  10. Data Maintenance • WG will be formed to develop a methodology to update medium scale hydrography using waterpoly data collected from new imagery through the FRI Program • Pilot Projects - starting with Quetico Provincial Park • Issues • FRI capturing well beyond traditional specifications • 4.8 times more detailed • Will need to remove ‘excess’ vertices using smoothing algorithms • Features now being captured as polygons less than 5 m. wide • Need to re-align ‘new’ water polygons to ‘existing’ single line streams

  11. Data Maintenance The bottom portion of the image (green) is a LIO water polygon which has been clipped by the delivery boundary. The FRI water polygon (blue) has also been clipped to the boundary. The shorelines do not line up.

  12. The left image displays a LIO water polygon that contains a ‘delimiter’ that separates lakes from river polygons. The right image shows a new FRI water polygon (blue) that needs a delimiter added. Data Maintenance

  13. Water line being divided into many pieces by a new water polygon. The water line should be realigned to become one virtual segment through the water body rather than being broken into many segments of permanent and virtual flow. Data Maintenance

  14. Data Maintenance 3 2 3 Third party update data issues: 1) Directionality – ‘Red Segs’ - Flip 2) Virtual Flow – Add V/Flow 3) Network Integrity - Split 3

  15. Small Scale Hydrographic Mapping • Generalization tools and processes need to be developed/ modified and tested for: • Attribute filtering • Polygon simplification • Collapsing or aggregating polygons • Pruning linear features • Draft products will be vetted thru Working Group, Business Areas and HDS Steering Committee prior to implementation

  16. Small Scale Hydrographic Mapping • Draft small scale hydrographic model req’mts: • Support Cartographic/ WMS applications • Range of Scales (100K, 200K, 500K, 1M, 2M, 5M, 10M) • Small Scale products will extend beyond provincial boundary • Watercourse, Waterbody and Shoreline (derived) classes • Attributes identified • Official Geographic Names sourced from GEL • Watercourses will contain virtual flow through Waterbodies

  17. Data Model Structure • Scope of the data model • Changes to current structure • Maintenance Model • Consultation requirements

  18. Small Scale Classes

  19. Questions? Overall Project Questions: Shawn Kelleher A/Project Manager Hydrographic Data Strategy (705) 755-1296 shawn.kelleher@ontario.ca Data Modelling Questions: Monique Kuyvenhoven Data Architect, WRIP (705) 755-2202 monique.kuyvenhoven@ontario.ca

More Related