The only way to deal with this geocoding
issue is to use parcel data. In a preliminary study we looked at 3 different
street files, we got anything from 45 to 91% geocoding hits in county X
but 97% using parcels. BTW, MapInfo was near the bottom of the list. Maptitude
was the top. However just because Software A got x% and software B got y% hit
rate does not indicate anything about accuracy.
The procedure I use is to ask our IT GIS
person (he thought this process up) to batch USPS standardize addresses, and then
pass them through an ArcView geocoding to parcels as available, otherwise
streets, and then I geocode the exceptions in Maptitude, which has worked very
well.
However, we have not come up with a
validation, Q&A scheme that helps us determine a standard error of our
results.
One item that would help all Maptitude
users for someone
to make it clear just how to use parcel
data in Maptitude and to use other street files, like Navtech,
Dick H
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Monday, October 25, 2004
12:01 PM
To: [EMAIL PROTECTED]
Subject: Re: [Maptitude] Maptitude
vs MapInfo
I've actually confronted the folks at MapInfo with the
question because I used t o be pretty chummy with some of the directors and
VP's in my home town of Troy,
NY. They argued that their data
is cleaner and better, and they offer a broader selection of industry specific
datasets. And they're right depending on the dataset. For example, the streets
provided by Caliper are reprocessed tiger files and aren't street level
accurate. I know because they don't line up very accurately with my street
datasets, while the samples I recieved from MapInfo line up very well.
However
in defense of Caliper , they're street files are geocodable and include street
classifications. Where if you were to purchase the same level of street
date from MapInfo; they would be a dumb line layer. Samples I was
provided with were from a third party vendor and would have cost significanly
more for a dataset for the entire U.S.. I tried to keep my comparison
apples to apples, and pricing based on equal datasets. So my estimate actually
didn't include every single dataset, because in some cases MapInfo only offered
specific specialty datasets. For all intents and purposes, Calipers datasets
are perfect for most general business applications. I'm only concerned with meter
accuracies because I work in an engineering and survey level environement were
sub-meter accuracy is important:: But for most business type analysis you're
dealing with smaller scaled areas.
Viktor
Keenan de la Hoz - Senior GIS Technician
City of Phoenix
- Street Transportation Department
Design and Construction Management Division
(602) 534-0498
|
|
Seymour Dupa <[EMAIL PROTECTED]>
10/25/2004 10:37 AM
Please
respond to Maptitude
|
To: [EMAIL PROTECTED]
cc:
Subject: Re: [Maptitude]
Maptitude vs MapInfo
|
I wonder what MapInfo would say if the quetion was put
to them?
--- [EMAIL PROTECTED] wrote:
>
> A few years back I did a cost comparison analysis of
> Maptitude vs. MapInfo
> and the result was a difference of over $20,000,
=====
You only get one chance on this merry-go-round.
But if you do it right, once is enough.
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail
------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/C5grlB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/Maptitude/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
| Yahoo! Groups Sponsor |
ADVERTISEMENT
![click here]() | |
![]() |
Yahoo! Groups Links
