You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reading the attached file using the geojson reader fails when using a batch size < 6807. I believe this is because the column man_made has 1 non-null value.
It may be nice to have something similar to readr::read_csv()'s guess_max which can be used to specify how far to scan the file to guess the column types. This would be similar to polar's infer_schema_length.
Additionally, it would be nice if we could fallibly skip what was failed to be read.
The text was updated successfully, but these errors were encountered:
GeoJSON is probably the weakest reader we have (aside from PostGIS), and essentially the only reader left where we have a pure-geozero implementation.
Ideally we'd be able to reuse arrow-json, but I think that will fail on the geometry column, as it doesn't currently support union types I don't think.
Reading the attached file using the geojson reader fails when using a batch size < 6807. I believe this is because the column
man_made
has 1 non-null value.osm-edinburgh-central.geojson.zip
It may be nice to have something similar to
readr::read_csv()
'sguess_max
which can be used to specify how far to scan the file to guess the column types. This would be similar to polar's infer_schema_length.Additionally, it would be nice if we could fallibly skip what was failed to be read.
The text was updated successfully, but these errors were encountered: