.NET Development: Incorrect Geocoding for address

1 to 2 of 2

  1.  
    • CommentAuthorRaymondv
    • CommentTimeFeb 17th 2012
     
    After upgrading the Geobase DLLs, I'm having a problem Geocoding an address (or a potential address). We are just getting different results and it is concerning. For example, when I GeoCode the following:

    400 N Ave, Anacortes, Wa

    we get this potential address returned:

    411 Avey Ct, Kettle Falls, Washington

    Before, we used to get the 400 N Ave address returned.

    However, if I type in: 400 N, Anacortes, WA

    we do get the 400 N Ave address returned.

    I know that this is not an exact physical address, but shouldn't it return the same address as it used to. And why does it work with 400 N vs 400 N Ave???

    Mike
    • CommentAuthorAlex H
    • CommentTimeFeb 19th 2012
     
    Hi Mike,

    I've tested this with GeoBase 3.7.1.0, and I'm getting the same results - it looks like our forward GeoCoder is having some difficulties parsing this specific address, possibly because it has no "name", as such - just a prefix ("N") and a street type ("Ave").

    If you could drop us a line on gbsupport@telogis.com with your current GeoBase version and Map Data filename, along with any other problematic addresses you have found, we'll pass this on to our development team to help tune up the GeoCoder for future releases.

    Thanks,

    Alex

1 to 2 of 2

  1.