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

interpolation sorting #528

Closed
missinglink opened this Issue Mar 29, 2017 · 1 comment

Comments

Projects
None yet
2 participants
@missinglink
Member

missinglink commented Mar 29, 2017

currently we don't re-sort interpolated results, in the case where there are one-or-more housenumber level accuracy results, we should consider sorting the more granular matches so they appear first.

eg:

1)	Lancaster Drive Northeast, Hayesville, OR, USA
2)	Lancaster Drive Northeast, Cedar Rapids, IA, USA
3)	Lancaster Drive Northeast, Salem, OR, USA
4)	521 Lancaster Drive Northeast, Four Corners, OR, USA

vs:

1)	521 Lancaster Drive Northeast, Four Corners, OR, USA
2)	Lancaster Drive Northeast, Hayesville, OR, USA
3)	Lancaster Drive Northeast, Cedar Rapids, IA, USA
4)	Lancaster Drive Northeast, Salem, OR, USA

note: for requests using the focus.point API it might be best to leave the sorting as-is.

@dianashk dianashk self-assigned this Apr 20, 2017

@dianashk

This comment has been minimized.

Show comment
Hide comment
@dianashk

dianashk Apr 20, 2017

Contributor

This is done, however the focus.point parameter is not considered. We always sort addresses higher. However, the order of the addresses shouldn't change relative to each other, so this should not be a problem.

Contributor

dianashk commented Apr 20, 2017

This is done, however the focus.point parameter is not considered. We always sort addresses higher. However, the order of the addresses shouldn't change relative to each other, so this should not be a problem.

@dianashk dianashk added the in review label Apr 20, 2017

@dianashk dianashk closed this Apr 20, 2017

@wafflebot wafflebot bot removed the in review label Apr 20, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment