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.

Sign up for GitHub

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

Jump to bottom

BE: If I copy latitude and longitude from one Loc to another, it creates a new locality #33

Closed
tlammer opened this issue Jan 30, 2018 · 3 comments
Closed

BE: If I copy latitude and longitude from one Loc to another, it creates a new locality #33

tlammer opened this issue Jan 30, 2018 · 3 comments
Labels
Confirmed Fixed fixed
Milestone
6.7.00

Comments

@tlammer
Copy link
Contributor

tlammer commented Jan 30, 2018

If I copy the lat and long from one locality to another to make them match, it creates a new locality with all the same (apparent) information
@timo11 timo11 added invalid and removed invalid labels Jan 30, 2018
@timo11
Copy link
Contributor

timo11 commented Jan 30, 2018

Lat/Lngs are hopeless. Copying latitude from one loc to another does not mean the numeric lat/lng values match exactly.

timo11 added a commit that referenced this issue Jan 30, 2018
@timo11
fix or near fix for #33
8c631cb
@timo11 timo11 added the fixed label Jan 30, 2018
@timo11
Copy link
Contributor

timo11 commented Jan 30, 2018

but they can be less hopeless...

@timo11
Copy link
Contributor

timo11 commented Jan 30, 2018

duplication should happen only for rare, mathematically uncooperative cases.

@tlammer tlammer changed the title If I copy latitude and longitude from one Loc to another, it creates a new locality BE: If I copy latitude and longitude from one Loc to another, it creates a new locality Jan 31, 2018
@timo11 timo11 added this to the version 6.7.00 milestone Mar 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Confirmed Fixed fixed
Projects
None yet
Milestone
6.7.00
Development

No branches or pull requests
3 participants
@benanhalt @timo11 @tlammer