now checks shadow table if route element was created by gdb-integrator #110
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
runeanielsen
force-pushed
the
now-checks-shadow-table-digitized-events
branch
from
659c0ad to
f55cd87
Compare
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.
We have had issues where users copy-paste the geometry from a GIS solution, example is QGIS. The problem is that the user also copies the
ApplicationNamefield, and that results in the GDB integrator thinking that it was created by itself, and ignores the event.Now we have switched to checking the shadow table if the route elements exists, if it does we have created it, otherwise it is a new digitized event by the user.