Text export from points incorrect (marginal case)


#1

If I export a random series of points all at Z0 (made just by using the command Points and clicking in the top viewport), I can get something like the following:

3 -3 0
5 4 0
8 1e+01 0
-0.2 1e+01 0
-4 0.9 0
-6 -5 0
0.9 -8 0
6 -3 0
2 5 0
-1 -3 0
-1e+01 -1 0
-7 7 0

As far as I can tell, this happens mostly when the number of significant digits specified on export is low and in any case only when they’re less than or equal to the number of digits in the file tolerance… but it shouldn’t happen in any case - 1e+01 just won’t fly in a text file that might need to get re-interpreted as numbers later…

Thx,
–Mitch


#2

Actually, they ought to be interpreted correctly. It’s standard mantissa+exponent notation and I suspect most parsers will recognize it as such:

ruby:

irb(main):001:0> -1e+01
=> -10.0
irb(main):002:0> -10
=> -10
irb(main):003:0> 1e+01
=> 10.0

python:

In [1]: 1e+01
Out[1]: 10.0

In [2]: -1e+01
Out[2]: -10.0

In [3]: [float(x) for x in '-1e+01 -1 1e+01 2.53e+02'.split()]
Out[3]: [-10.0, -1.0, 10.0, 253.0]

and even Office (I saved your table above into a .csv and imported it):

This looks like the proper notation for your export options. You specified 1 significant digit, right?

disclaimer: not a software user, just a Mathie :smile:


(Steve Baer) #3

I agree it isn’t pretty. I would be interested in knowing if you run across an importer that can’t deal with these numbers (apart from us human types).