Invalid values during Coordinate conversion.
See original GitHub issue🐞 Problem When converting from Cartesian to BL, we may run across a divide by zero error as discussed in #343. The same error can also be encountered when converting from Cartesian to Spherical with all x, y, and z zero.
💡 Possible solutions
📋 Steps to solve the problem
- Comment below about what you’ve started working on.
- Add, commit, push your changes
- Submit a pull request and add this in comments -
Addresses #<put issue number here>
- Ask for a review in comments section of pull request
- Celebrate your contribution to this project 🎉
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Invalid result in coordinate transformation [closed]
1 Answer 1 ... 2) It also appears that your "flat Easting coordinate" value i.e., 1677500 looks off. Perhaps the correct value was...
Read more >Coordinate Conversion is auto correcting invalid input ...
Enter the following invalid coordinate: 45 300s|100 30.0w. The tool auto corrects the 300s to 5 minutes and creates the following output:
Read more >001293: Coordinate conversion failed for <value> records.
Any record in the input table with invalid notation is not converted to a valid point in the output table. Solution. Check the...
Read more >Troubleshooting - Blue Marble Geographics
If the output coordinates seem invalid, check to make sure your input and output coordinate system definitions are appropriate, and that the format...
Read more >How To: Identify and fix when the Add XY Data tool does not ...
Reason: The Add XY Data tool must know what the original coordinate system was during the point collection in order to properly plot...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Change the implementation to this solves this.
Fixed in #351