Draft
Conversation
Owner
Author
|
The geonames dataset is quite large even compressed so unsure if its worth it, or could be an optional add on. Current exe is about 145MB (with normal compression setting in packaging) and adding the geonames data would more than double that for a feature that may not be used very often. In consideration... EXIF parsing also still needs effort to be robust. |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add reverse lookup from geonames dataset for GPS coordinates found in EXIF
EXIF parsing still needs a lot of cleanup due to complexity of potential ways EXIF data can be formed.