Properly handle latitude and longitude during Destination One import #30
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
DanielSiepmann
force-pushed
the
10565
branch
2 times, most recently
from
c3fc07b
to
3d88269
Compare
DanielSiepmann
force-pushed
the
10565
branch
2 times, most recently
from
32bb2c9
to
16c37c7
Compare
DanielSiepmann
changed the title
|
Currently missing an update wizard to migrate existing data. That's why I've set it to draft … Need to discuss with customer how to handle it. |
DanielSiepmann
force-pushed
the
10565
branch
4 times, most recently
from
a690102
to
83049bf
Compare
They sometimes use a different separator. The code is adjusted to always use same separator and precision. That will prevent the same location from showing up multiple times due to different latitude and longitude values.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
They were sometimes floats or strings using different separator.
The code is adjusted to handle the precision of float and streamline
separator.
That will prevent the same location from showing up multiple times due
to different latitude and longitude values.