Open
Conversation
Calendar npe
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.
The File geodatabase I receive contains points in the Oregon Lambert plane coordinate system.
These coordinates look like "x":776252.7670898438,"y":1372831.180480957, and can't be converted into the radians expected by Angle.
To address this, I load the dataset definition of the Feature to get the Well Known Text, then use that with geotools to transform the coordinates into WSG84.
If the feature doesn't have a WKT, no transform is performed.
If the coordinates are already in WSG84, an identity transform is used, which should not change the results.
This PR also contains a fix for the issue my dataset was having with the Calendar without a TimeZone.