Thread: 396 question
View Single Post
  #8  
Old December 13th 06, 03:16 PM posted to rec.aviation.owning
dlevy
external usenet poster
 
Posts: 30
Default 396 question

Pretty kewl. Thanks for taking the time to explain.

"Travis Marlatte" wrote in message
t...
I work for NAVTEQ - although I am not directly involved in the data
collection for our maps.

The location of addresses is derived in a couple of different ways and it
depends on the area as to how accurate it is. To save on space, the range
of addresses for a block is usually all that is present. The location of a
particular address, then, is merely an interpolation of where it is in the
range. This usually results in the location being off by a small error.

Less frequently, the addressing does not follow a logical pattern. The
only solution is to identify the location of each and every address -
which is only cost effective (both in data collection and in database
size) in high volume markets. i.e. it's a balance of customer satisfaction
and the cost of the database.

Other possibilities are that we purchased data from a government entity
and it is wrong. We do validate such data but it takes time. Validating is
plain, old hitting the streets and comparing our data against reality.

And, of course, it could just be a mistake.

On the NAVTEQ website, there is a feedback section where you can report
errors. Trust me, we review each and every report. NAVTEQ's website is
www.NAVTEQ.com and the direct link to the feedback section is
www.navteq.com/updates/mapfeedback.html.

-------------------------------
Travis
Lake N3094P
PWK