35 E Ridge Court Cheshire

[HelloMrWillemain]

On OCA, we searched "35 E Ridge Court Cheshire" and got the pop up Location Search Failed. Changed the search to, "35 East Ridge..." and still search failed. Changed the search to, " EastRidge Court..." and that queried a location successfully.

Here is the funny part...after mapping the area the address drops down to Step 3: Confirm Dig Site as, "35 E Ridge Court..."!

This strikes me as strange that we are not successful in search for the address in its' various forms but specifically the format in which it drops down to after marking the area on the map? I would assume there are other users being impacted by this issue besides our internal opts.

Any information on the topic would be appreciated.

[polysteve]

What should happen is that when you try 35 eastridge ct, you should get the suggestion 35 east ridge ct and that should work when you select it. Note something like "east" or "e" which appears at the beginning or end of what looks like a street name is converted to "e" (or the appropriate abbreviation for other directions. You can use anything "e" or "east" and they will be treated the same. The apparent issue here is that the suggestion with the valid name does not succeed when you query on it. We will investigate further.

[HelloMrWillemain]

Thank you, Steve. Appreciate you investigating the issue.

Anthony R. Willemain Call Center Manager | PelicanCorp

[New PelicanCorp]

P: 203 248 5502 | M: 203 980 0806 E: Anthony.Willemain@pelicancorp.commailto:Anthony.Willemain@pelicancorp.com A: 2040 Whitney Ave. Hamden, CT 06517

www.pelicancorp.comhttp://www.pelicancorp.com/

[linkedin for email]https://www.linkedin.com/company/258579[twitter for email]https://twitter.com/PelicanCorp

From: polysteve notifications@github.com Sent: Tuesday, April 23, 2019 11:36 To: polysteve/MobileLocater MobileLocater@noreply.github.com Cc: Anthony Willemain anthony.willemain@pelicancorp.com; Author author@noreply.github.com Subject: Re: [polysteve/MobileLocater] 35 E Ridge Court Cheshire (#76)

What should happen is that when you try 35 eastridge ct, you should get the suggestion 35 east ridge ct and that should work when you select it. Note something like "east" or "e" which appears at the beginning or end of what looks like a street name is converted to "e" (or the appropriate abbreviation for other directions. You can use anything "e" or "east" and they will be treated the same. The apparent issue here is that the suggestion with the valid name does not succeed when you query on it. We will investigate further.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/polysteve/MobileLocater/issues/76#issuecomment-485856366, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AEFCISLPQBRD5AVG3LGQZY3PR4UETANCNFSM4HHYYL4Q.

The information contained in this email communication may be confidential. You should only read, disclose, re-transmit, copy, distribute, act in reliance on or commercialise the information if you are authorised to do so. If you are not the intended recipient of this email communication, please notify us immediately by email directly to the sender and then destroy any electronic or paper copy of this message.

[polysteve]

35 Eastridge Ct is an exact match in the Polytope API. Need to look into the interaction with OCA to understand what's going on.

[polysteve]

Further info, probably duplicating original comment. The primary issue is that the suggested "35 E Ridge Ct" address that is suggested is not valid but the originally entered address "35 Eastridge Ct" is valid as can be demonstrated by avoiding the suggestion and clicking on the (almost covered) "Search button. The two core questions then, are 1. why a suggestion is given when the original address is a match and 2. why a suggestion is given that will not match. This will take some detailed tracing of the network interactions between the Polytope (PT) API and OCA.

[polysteve]

Additional sub-issue: 35 East Ridge Ct shows on map so either map name wrong or should be a valid address.

[HelloMrWillemain]

387 W Spring Street West Haven - 387 Westspring Street West Haven

[polysteve]

Note: Suspicious that these names both begin with directions (east/west) suggesting that it may be a parsing issue.

[polysteve]

We now know how/why the parse fails on these addresses - if there is a house number followed by a direction [north, east, S, NE, etc] and the name of the street can also be a type of street, then it is parsed with the direction as the name of the street and the name as the type of street. 35 east ridge ct is treated as 35 E[street name] Ridge[type of street] Ct[second type of street], which does not match the real E[direction] Ridge[street name] Ct[type of street]. While this parse is possible, especially in places where two street types are common, e.g. Tacoma, WA, where 35 East E Ridge Ct is possible, it should be a second choice in CT. Fix ETA about a week.