navteq and massgis

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

Upload: national-states-geographic-information-council

Post on 19-May-2015

875 views

Category:

Technology


3 download

DESCRIPTION

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

TRANSCRIPT

Page 1: NAVTEQ and MASSGIS

Making Public Private Partnership WorkMassachusetts / NAVTEQ Street Data Partnership

Page 2: NAVTEQ and MASSGIS

Overview

Partnership Data update Ongoing

maintenance Future path

This content was largely derived from Sean Sweeney’s presentation to URISA / NENA conference on addressing.

Page 3: NAVTEQ and MASSGIS

Multi-agency public-private

EOEEAMassGIS

EOPSSSETB

EOTPWOTP

Page 4: NAVTEQ and MASSGIS

PSAPs need roads data

Page 5: NAVTEQ and MASSGIS

No address ranges

Page 6: NAVTEQ and MASSGIS

MassGIS

Page 8: NAVTEQ and MASSGIS

NAVTEQ does the field work

Page 9: NAVTEQ and MASSGIS

NAVTEQ Project data work

-Leveraging field/data collection power with their state wide network. - Using NAVTEQ Maps as a base, MASS GIS cross- referenced our

database with several of their lists creating a list of “mismatches”. 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.

Created a streamlined process so the NAVTEQ Field team works directly with MASS GIS

True missing streets were driven and entered using our standard postal work process.

Created a standardized process to communicate each quarter.

ou

Page 10: NAVTEQ and MASSGIS

Project data work

MSAG standardization Compare NT to other data Integrate with EOT Conflation Lessons learned

Page 11: NAVTEQ and MASSGIS

MSAG Translation

Standardization…

…Abbreviation

Page 12: NAVTEQ and MASSGIS

Assign streets to MSAG communities

Page 13: NAVTEQ and MASSGIS

Identify missing streets

Page 14: NAVTEQ and MASSGIS

Verify against other data sets

Page 15: NAVTEQ and MASSGIS

Custom Tools

Page 16: NAVTEQ and MASSGIS

Integrate new NAVTEQ roads into EOT database

Legend

NAVSTREETS

EOT

Page 17: NAVTEQ and MASSGIS

Conflate NAVTEQ addresses onto EOT roads

Page 18: NAVTEQ and MASSGIS

MSAG Community boundaries Standardization

− Especially “ST”:

NAVTEQ Alias handling Address range handling Mixed-parity ranges:

Lessons learned

1 1

99 99

1 2

99 98

Page 19: NAVTEQ and MASSGIS

Lessons learned

Hard to compare many complex datasets No “right” answer

− Must match MSAG All takes time:

− 18 months to put partnership together− 2 years to get data updated

But payoff was there

Page 20: NAVTEQ and MASSGIS

On Going Maintenance Quarterly processing

Step 1: Standardize and Install in MapStar Step 2: Verify in office

− Compare to MSAG− Compare to EOT− Compare to Muni/Parcels

Step 3: Verify in field Step 4: Repeat

Page 21: NAVTEQ and MASSGIS

Data preparation

NAVTEQ

MASSGIS

SETB PSAPs

EOT

Page 22: NAVTEQ and MASSGIS

Web reporting tool

Page 23: NAVTEQ and MASSGIS

Future path

EOT Linework Future path: customized MSAG standardization Future path: point geocoding Future path: time-of-creation collection

Page 24: NAVTEQ and MASSGIS

Future path: EOT linework

Page 25: NAVTEQ and MASSGIS

Future path: customized MSAG standardization

MSAG Format

Multiple Input Sources

Standardize

FGDC Format

MSAG Format

Other Formats

Translate

Page 26: NAVTEQ and MASSGIS

Future path: point geocoding

Page 27: NAVTEQ and MASSGIS

Conclusion

Partnership is a win-win:− Mass GIS

Furthered mandate Improved roads for entire Commonwealth

− 911 Saved money Better data

− EOT Saved money Better data

− NAVTEQ Better data Received faster updating of streets and roads