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.



Published on

Making Public Private Partnership Work: Massachusetts / NAVTEQ Street Data Partnership

Published in: Technology
  • Be the first to comment

  • Be the first to like this


  1. 1. Making Public Private Partnership Work<br />Massachusetts / NAVTEQ Street Data Partnership<br />
  2. 2. Overview<br />Partnership<br />Data update<br />Ongoing maintenance<br />Future path<br />This content was largely derived from Sean Sweeney’s presentation to URISA / NENA conference on addressing. <br />
  3. 3. Multi-agency public-private<br />EOPSS<br />SETB<br />EOTPW<br />OTP<br />EOEEA<br />MassGIS<br />
  4. 4. PSAPs need roads data<br />
  5. 5. No address ranges<br />
  6. 6. MassGIS<br />
  7. 7. 7<br />NAVTEQ Relationships<br />Automotive Manufacturers<br />System Vendors<br />Telematics<br />Internet & Wireless<br />Mobile Devices<br />Enterprise<br />
  8. 8. NAVTEQ does the field work<br />
  9. 9. NAVTEQ Project data work<br />-Leveraging field/data collection power with their state wide network.<br />- Using NAVTEQ Maps as a base, MASS GIS cross- referenced our database with several of their lists creating a list of “mismatches”.<br /> NAVTEQ processed the “mismatch” list through their Internal tools to determine the real missing data; and many initially listed were due to our internal spec, naming convention etc. Levels of match accuracy were created.<br /> Created a streamlined process so the NAVTEQ Field team works directly with MASS GIS <br />True missing streets were driven and entered using our standard postal work process. <br /> Created a standardized process to communicate each quarter.<br />ou<br />
  10. 10. Project data work<br />MSAG standardization<br />Compare NT to other data<br />Integrate with EOT<br />Conflation<br />Lessons learned<br />
  11. 11. MSAG Translation<br />…Abbreviation<br />Standardization…<br />
  12. 12. Assign streets to MSAG communities<br />
  13. 13. Identify missing streets<br />
  14. 14. Verify against other data sets<br />
  15. 15. Custom Tools<br />
  16. 16. Integrate new NAVTEQ roads into EOT database<br />
  17. 17. Conflate NAVTEQ addresses onto EOT roads<br />
  18. 18. MSAG<br />Community boundaries<br />Standardization<br />Especially “ST”:<br />NAVTEQ<br />Alias handling<br />Address range handling<br />Mixed-parity ranges:<br />Lessons learned<br />1<br />99<br />1<br />99<br />1<br />99<br />2<br />98<br />
  19. 19. Lessons learned<br />Hard to compare many complex datasets<br />No “right” answer<br />Must match MSAG<br />All takes time:<br />18 months to put partnership together<br />2 years to get data updated<br />But payoff was there<br />
  20. 20. On Going Maintenance Quarterly processing<br />Step 1: Standardize and Install in MapStar<br />Step 2: Verify in office<br />Compare to MSAG<br />Compare to EOT<br />Compare to Muni/Parcels<br />Step 3: Verify in field<br />Step 4: Repeat<br />
  21. 21. Data preparation<br />NAVTEQ<br />MASSGIS<br />SETB<br />PSAPs<br />EOT<br />
  22. 22. Web reporting tool<br />
  23. 23. Future path<br />EOT Linework<br />Future path: customized MSAG standardization<br />Future path: point geocoding<br />Future path: time-of-creation collection<br />
  24. 24. Future path: EOT linework<br />
  25. 25. Future path: customized MSAG standardization<br />Multiple Input Sources<br />Standardize<br />MSAG Format<br />Translate<br />FGDC Format<br />MSAG<br />Format<br />Other Formats<br />
  26. 26. Future path: point geocoding<br />
  27. 27. Conclusion<br />Partnership is a win-win:<br />Mass GIS<br />Furthered mandate<br />Improved roads for entire Commonwealth<br />911<br />Saved money<br />Better data<br />EOT<br />Saved money<br />Better data<br />NAVTEQ<br />Better data<br />Received faster updating of streets and roads<br />