Degree symbol is making reader break
See original GitHub issueIn the ~Parameter Information
section of the attached here, the reader.py
is throwing an error presumably when it encounters the degree symbol in the latitude and longitude fields.
LATI . 0° 0' 0 N :Latitude
LONG . 0° 0' 0 E :Longitude
The error message I’m getting has something to do with codecs. Is this something we can fix with the reader or it a problem that has to do with my Python installation?
[1045387215_top100ft.txt] (https://github.com/kinverarity1/lasio/files/1410966/1045387215_top100ft.txt)
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
Degree Symbol °
List of degree symbols where used in degrees of arc, degree of hour in geo coordinates, degrees of temperature. Make html degree sign,...
Read more >Best way to encode Degree Celsius symbol into web page?
The degree sign belongs to the number, and not to the "C". You can regard the degree sign as a number symbol, just...
Read more >Numbers | Grammar and Punctuation - Blogs @ MU
When mixed, break them up by alternating numerals and spelling. ... However, the placement of the numbers and degree symbol varies.
Read more >How to type the degree° symbol on iPhone, iPad, and Mac
Open the app you're typing in and make sure the keyboard is up and ready. Access the numeric keyboard by tapping the 123...
Read more >How to Insert Degree Symbol (°C) in Excel (7 Easy Ways)
What would happen to the number if it's not a numeric value? It would still be a number but with the degree symbol...
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 Free
Top 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
I can’t reproduce the error! Is it because I’m running windows and thus the default python encoding is correct?
The philosophy I’ve been guided by is to make it “just work” out of the box, so perhaps the default behaviour should be:
Does this sound like a happy medium?
Closing until confirmation