locate address on map shows different location for same address

[Victoria]

The locate address on map function shows two different location for the same address depending on abbreviations. 106 CR 52 Avilla, IN puts the location in Noble County. 106 County Road 52 Avilla, IN put the location in Dekalb County.

Using Evergreen 3.0 Webclient using Chrome

[Dan Pearl (dpearl)]

"CR" is postal abbreviation for "Cross". I suspect the geolocation
algorithm is ignoring that part of the address.
I think that "County Road", "Cnty Rd", "CO RD" will all be located
correctly. (cf. USPS Pub 28)

On Mon, Jul 29, 2019 at 1:25 PM Victoria <email address hidden> wrote:

> Public bug reported:
>
> The locate address on map function shows two different location for the
> same address depending on abbreviations. 106 CR 52 Avilla, IN puts the
> location in Noble County. 106 County Road 52 Avilla, IN put the
> location in Dekalb County.
>
> Using Evergreen 3.0 Webclient using Chrome
>
> ** Affects: evergreen
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to
> Evergreen.
> Matching subscriptions: LP_Mail
> https://bugs.launchpad.net/bugs/1838318
>
> Title:
> locate address on map shows different location for same address
>
> Status in Evergreen:
> New
>
> Bug description:
> The locate address on map function shows two different location for
> the same address depending on abbreviations. 106 CR 52 Avilla, IN
> puts the location in Noble County. 106 County Road 52 Avilla, IN put
> the location in Dekalb County.
>
> Using Evergreen 3.0 Webclient using Chrome
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/evergreen/+bug/1838318/+subscriptions
>

[Jason Boyer (jboyer)]

Hi Victoria, Dan's comment above is spot-on. Google Maps (which is used on that Evergreen Indiana-specific page) doesn't treat CR as "county road" normally. If you enter the same two addresses in maps.google.com you'll also get two different locations. (Interestingly enough not the same two returned in our local custom page.) Since this is an issue in the Google Maps API it's not something that can easily be addressed by State Library staff (and not at all by the larger Evergreen community since it's not in the stock software.)

Jason