1 / 32

.NZ-DRA.A.Digital.Road.Atlas.for.New.Zealand

Comprehensive digital road atlas for New Zealand incorporating spatial data, suited for various purposes, with a focus on accuracy and time-stamped edits. Collaborative approach with open access and achievable precision.

vedac
Download Presentation

.NZ-DRA.A.Digital.Road.Atlas.for.New.Zealand

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. NZ-DRA A Digital Road Atlas for New Zealand Kim Ollivier Ollivier & Co

  2. Just Do It • What? • A maintained spatial database of the NZ road network and places. • When? • Build on existing open sets: LINZ, NZOpenGPS.org • Start now with an existing schema and data • Why? • Suitable for multiple purposes, govt and pvte • How? • Model on Canadian DRA1, DRA2, Geobase

  3. Existing Road Databases Closed: • NRCD – Terralink • NationalMap2 – Critchlow • SmartMap – Geosmart/AA • RAMM – CJN Technology Open: • OSM - Open Street Map • NZOpenGPS - Garmin focus • BDE Road - LINZ cadastral • ASP - Authoritative Streets & Places • Suburb - NZ Fire Service

  4. Essential Features • Simple Flexible Design • Open Access • Achievable Accuracy, +/- 10 m, 90% • Multi-level detail and purpose • Time stamped edits • Feedback from relevant authorities • Regulation to “encourage” collaboration of local and central govt

  5. A Creative Commons?

  6. DRA Data Model • Spatial: street intersections and road linework are stored as spatial entities • Temporal: data is versioned and has a lifespan • Conflation: Boundaries match road linework

  7. Spatial Query Intersection node at each segment junction

  8. Managing time • Admit and retire dates provide lifespan for each element • Queries by date allow extraction of data from any vintage

  9. Temporal query • Black roads vintage November 2001 • Pink roads vintage March 2003

  10. Boundary Conflation Police zone from independent layer

  11. Boundary Conflation Conflated zone

  12. Where 2.0 : TeleAtlas Only regulatory activity attributes

  13. DRA Tools • Intelligent data conditioning: Feature Manipulation Engine (FME), Java Conflation Suite (JCS) • Storage: PostgreSQL object relational database with PostGIS spatial extension • Table updates: SQL and ODBC • Programming: C++, Visual Basic, Perl • Manual spatial manipulation: Arc Tools • Visualization: Web Mapping, Geocoder • Updates/Issues: Bug tracking software

  14. Extendable Schema

  15. Canadian National Road Network Defines “State of the Art for National Datasets” www.geobase.ca

  16. DRA1 -> DRA2 -> NRN2 • Integrates 7 yrs of monthly snapshots • Facilitates provision of data and specialized services to numerous clients • Built on innovative, integrated technology and toolsets

  17. Data Quality • Accuracy - of what? • Completeness? • Geocoding -False Positives -False Negatives • Address Standards exist -but are widely ignored “If they are fit for their intended uses in operations, decision making and planning.” “If they correctly represent the real-world construct to which they refer.”

  18. A GIS Data Quality System Assess Data Quality Assessment Data Profiling Improve Recognise Prevent Data Cleaning Monitoring Data Integration Interfaces Ensuring Quality of Data Conversion and Consolidation Building Data Quality Metadata Warehouse Monitor Recurrent Data Quality Assessment

  19. High precision is no use for DRA “The myth that more precision is better and better” – Perry Evans, Mapquest, Where 2.0 2009 • 3G Cellphones ~200m triangulation • Basemaps ~100m short form coordinates • GPS Vehicle navigation ~25m uncorrected • DRA specification ~10m (90%) • Place is more important than Location

  20. Spatial Accuracy

  21. GPS tracks depend on time of day

  22. Accurate tracks are generalised

  23. Statistical Accuracy False Positives False negatives Completeness Score = Relevant Relevant + Missing Accuracy Score = Relevant - Errors Relevant Overall Score = Relevant - Errors Relevant + Missing

  24. Google Street View is offset

  25. Achievable Goals • DRA specification: 90% within 10 m • Lucky to get 90% attributes filled in • Even luckier to get 70% right NAR : required 99.5% attribute correctness

  26. Intended Applications

  27. Can anyone get addresses right?

  28. More confusion

  29. Feedbackupdates

  30. Typical Applications • Road user charges offroad refunds • Street map atlases by publishers • Civil defence • Reliable address location • Routable network • Tourism

  31. National Model Needs a champion to drive it It cannot be done by the private sector alone • Level 1 DRA in 2009? • Level 2 DRA in 2010?

  32. Demo Canadian NRN • Shape, GML, MID (51 MB) • KMZ Google Network file (139 kB) Te Araroa KMZ (3000 km trail)

More Related