Street Address issues in Hartford area

[HelloMrWillemain]

The first group(s) are ticket either searched incorrectly by the user but ultimately marked in one town and submitted as another. I believe this is a combination of errors from both the users and the way PC software is looking at the map data. I'm honestly not even sure if this is something you can help with. If you can at least help me understand what is going on and I can take that information back to the PC developers we can get this figured out. It is strange that the Hartford area is really the only area where this happens though. I have not seen another ticket in any area mark in one town and submitted for another. The system will normally throw a red flag and say NOPE this is not the right town but in Hartford and surround towns, it isn't doing that.

20201001011, 20201001022, 20201600621 - Mapped in East Hartford but submitted as Hartford

20201303911 - Mapped in West Hartford but Submitted in Hartford

20201301538 - Mapped in Hartford but Submitted in East Hartford

20201201352 - Mapped in Hartford but Submitted in West Hartford

20201103938 - This was a series of ticket for a large project on a street beginning in Bloomfield. The user was creating the series of ticket using the Continue Job tool. Reminder, this tool allow you to continue from where a previous ticket left off. This is the first ticket that crossed the town line of Bloomfield and Hartford. I am not sure if this one is within your control or not but still wanted to show you.

The next two seem a little more of a mapping data issue as the searches and map results do not match up.

20201503796 - Elliott Street East, Hartford - classic issue of the street name including a direction after the suffix and confusing the search to not find a match for (75 Elliott Street East HARTFORD). Because the user had a LOC Search Failed using that, they took out "East" and just used Elliott Street Hartford. Also the suggestion box will suggest; Elliott Street Esplanade Hartford and finds the same location and many other suggestions for the same area.

20201502043 - Searching; Maple Street HARTFORD finds Maple AVENUE in Hartford. Drop down suggestions is Maple AVE but you can bypass that suggestion and search for Maple St and it finds Maple Ave.

Hartford Area Issues.zip

[3DXScape]

Your analysis looks correct. I don't have any answers yet, but setting up to check them out.

I split into three sub-issues.

[HelloMrWillemain]

Sounds good. I had them broken down into three issue groups too.

Anthony R. Willemain Call Center Manager | PelicanCorp

[Logo PC.png]

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 --> @AWill811https://twitter.com/AWill811

From: Steve Smyth notifications@github.com Sent: Sunday, May 10, 2020 21:53 To: polysteve/MobileLocater MobileLocater@noreply.github.com Cc: Anthony Willemain anthony.willemain@pelicancorp.com; Author author@noreply.github.com Subject: Re: [polysteve/MobileLocater] Street Address issues in Hartford area (#80)

Your analysis looks correct. I don't have any answers yet, but setting up to check them out.

I split into three sub-issues.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/polysteve/MobileLocater/issues/80#issuecomment-626430269, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEFCISMJ2Q4NIIKA7IBMDULRQ5K6NANCNFSM4MI3CIKQ.

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.

[HelloMrWillemain]

Hello Steve,

Checking back for an update on these addresses…

Hope you are still well. Talk soon.

Anthony R. Willemain Call Center Manager | PelicanCorp

[Logo PC.png]

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 --> @AWill811https://twitter.com/AWill811

From: Anthony Willemain Sent: Monday, May 11, 2020 10:42 To: polysteve/MobileLocater reply@reply.github.com Subject: RE: [polysteve/MobileLocater] Street Address issues in Hartford area (#80)

Sounds good. I had them broken down into three issue groups too.

Anthony R. Willemain Call Center Manager | PelicanCorp

[Logo PC.png]

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 --> @AWill811https://twitter.com/AWill811

From: Steve Smyth notifications@github.com<mailto:notifications@github.com> Sent: Sunday, May 10, 2020 21:53 To: polysteve/MobileLocater MobileLocater@noreply.github.com<mailto:MobileLocater@noreply.github.com> Cc: Anthony Willemain anthony.willemain@pelicancorp.com<mailto:anthony.willemain@pelicancorp.com>; Author author@noreply.github.com<mailto:author@noreply.github.com> Subject: Re: [polysteve/MobileLocater] Street Address issues in Hartford area (#80)

Your analysis looks correct. I don't have any answers yet, but setting up to check them out.

I split into three sub-issues.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/polysteve/MobileLocater/issues/80#issuecomment-626430269, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AEFCISMJ2Q4NIIKA7IBMDULRQ5K6NANCNFSM4MI3CIKQ.

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.