TLE Parsing - parseDouble not a double
I have several TLE files that are giving me trouble when running them through Orekit typically with Field 1.9 the First Time Derivative of the Mean Motion
Field 1.9 is supposed to look like ".NNNNNNNN", but in my case sometimes the TLEs I receive look like ".NNNNNNN". Orekit first replaces all spaces with a 0 resulting in "0+.NNNNNNN" which it fails to parse as a double. I have a different code base we were using until converting to Orekit that is very old for parsing TLE files that would first trim leading/trailing spaces and then replace remaining spaces with 0 and then parseDouble. This has never given us errors.
My request is that Orekit handle parsing of these number fields in a slightly smarter way instead of starting with filling in zeroes that may break.
If these TLEs are definitively wrong then I suppose this is not an Orekit bug and should be labeled as a request.
(from redmine: issue id 196, created on 2015-04-09, closed on 2016-02-10)