-
Notifications
You must be signed in to change notification settings - Fork 654
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
Type guessing on import for GEOJSON #1036
Comments
geojson already has types so in this case we should take care because some users could be using them. I will ask the guy who worked with us |
there was another thing related with integer limits, right? cc @Kartones |
Yes, it seems we're hitting int32 max value (all get converted to number 2147483647) upon importing files with really big integers, like this sample CSV:
|
merged in ogr2ogr master |
😃 |
cc @rafatower |
Worth noting: in gdal trunk there must be also a patch for a segfault when imporing csv files |
what do we do with this issue then? |
bump! |
Probably wait until @rafatower comes back from vacations... I'm kind of busy right now to do regression tests or see if everything's fine now :( |
So, @rafatower ? |
Current status: @javisantana, what's exactly the expectation of this feature? according to doc this is the only change regarding GeoJson:
|
guessing on boolean and dates |
The geojson specification only mentions these types:
Currently dates are imported correctly. Working my way through the code to enable |
I'm getting this error with
I think that means we lack one file in the deb package |
To recap:
|
Use ogr2ogr2 both for csv and geojson files #1036
And released! |
We should contact the same guy that helped us with csv.
cc/ @javisantana
The text was updated successfully, but these errors were encountered: