Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Pims-1858 Truncate Address From Geocoder #2523

Merged
merged 8 commits into from
Jul 15, 2024

Conversation

TaylorFries
Copy link
Collaborator

🎯 Summary

PIMS-1858:

Made the following changes:

  • truncated address on first comma from geocoder
  • updated address model for geocoder
    • is fields were being returned as a string not bool
    • also updated logic for creating address1
    • more work will have to go into this logic block before we use it
  • added a 10m setback to geocoder call
    • theoretically this should move the point away from the road and toward the center of the parcel
    • I have found a few instances that it still misses the parcel

🔰 Checklist

  • I have read and agree with the following checklist and am following the guidelines in our Code of Conduct document.
  • I have performed a self-review of my code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have made corresponding changes to the documentation where required.
  • I have tested my changes to the best of my ability.
  • My changes generate no new warnings.

Copy link

🚀 Deployment Information

The React APP Image has been built with the tag: 2523. Please make sure to utilize this specific tag when promoting these changes to the TEST and PROD environments during the APP deployment. For more updates please monitor Image Tags Page on Wiki.

@TaylorFries TaylorFries marked this pull request as draft July 11, 2024 20:15
Copy link

codeclimate bot commented Jul 11, 2024

Code Climate has analyzed commit 132ca7f and detected 0 issues on this pull request.

The test coverage on the diff in this pull request is 100.0% (50% is the threshold).

This pull request will bring the total coverage in the repository to 93.7%.

View more on Code Climate.

Comment on lines +37 to +38
url.searchParams.append('locationDescriptor', 'accessPoint');
url.searchParams.append('setBack', '10');
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Was curious about what this locationDescriptor did, so I did some tests with it on/off:
All tests done with 467 Lampson St.
With lines 37 and 38 commented out, I get this:
image

With line 38 commented out only, I get this:
image

And with both lines present, I get this:
image

It seems like adding these lines might have reduced the accuracy of the location somehow.

Yet, with 1407 Haultain St (a weird split parcel), I get this with them both active:
image

And this with neither active:
image

With them, accuracy was 2/2 checked. Without, it was 1/2. so I think it's still worth it.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It really could go either way - it just depends on each parcel. But I found the same, on parcels that geocoder sends a good point it makes the point worse but still acceptable, on parcels that geocoder sends a bad point it makes it better.

@TaylorFries TaylorFries merged commit aa2ac65 into main Jul 15, 2024
13 checks passed
@TaylorFries TaylorFries deleted the PIMS-1858-trunc-address-geocoder branch July 15, 2024 14:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants