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

geoarrow::io::geojson fails with very sparse columns #968

Open
JosiahParry opened this issue Dec 27, 2024 · 1 comment
Open

geoarrow::io::geojson fails with very sparse columns #968

JosiahParry opened this issue Dec 27, 2024 · 1 comment

Comments

@JosiahParry
Copy link
Contributor

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()'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.

@kylebarron
Copy link
Member

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.

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