Output Coordinates to CSV #115
Open
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
added 6 commits
July 12, 2016 16:39
|
I will test this tonight and get back to this |
|
I would recommend the Coordinates section is moved to either the end of the database, or the string is set to a maximum length. E.g. take for example this specific free draw shape: The coordinates section of the database becaomes way too big. This expands that columns and makes the database look pretty ugly, the image below is only a portion of the full coordinate list.
I would lean towards maybe having a 6-8 coordinate limit (some constant maximum string character length maybe), and placing this columns at the end of the database. If a user would like the full coordinate list of a free draw shape, they can choose to export it as CSV. |
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.
These changes enable the user to view the coordinates of the vertices of each polygon in the database and output to CSV. (This feature was driven by Chip Trepte as an end-user. Whether to include this in the master branch can be up for discussion, but for now it's up for comparison to and incorporation with master.)