Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Don't use decimal precision for integers in text writer #1869

Closed
tomvantilburg opened this issue Mar 22, 2018 · 1 comment
Closed

Don't use decimal precision for integers in text writer #1869

tomvantilburg opened this issue Mar 22, 2018 · 1 comment

Comments

@tomvantilburg
Copy link
Contributor

Currently all dimensions are written with the same precision (defaulting to 3) but this seems unneeded for integers and gives unexpected errors when trying to import the data into other programs (postgres in my case).

Current output:
`Intensity,ReturnNumber,NumberOfReturns,ScanDirectionFlag,EdgeOfFlightLine,Classification,ScanAngleRank,UserData,PointSourceId,GpsTime,X,Y,Z

60.000,1.000,1.000,0.000,0.000,9.000,8.000,1.000,210.000,78563061.316,139067.845,556254.579,-1.049`

Expected output:
60,1,1,0,0,9,8.000,1,210, 78563061.316, 139067.845, 556254.579, -1.049

@abellgithub
Copy link
Contributor

Frankly, this seems like a postgres problem.

I'll have to think about some reasonable way to handle this.

hobu pushed a commit that referenced this issue Sep 24, 2018
* Allow extraction of sidescan data.

* Add support for individual dimension precisions.
Close #1869

* Set proper dimensions based on datatype option.

* Add time support for mbio.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants