-
Notifications
You must be signed in to change notification settings - Fork 43
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
Missing Row in Shapefile using ST_Read() #414
Comments
I discovered the undocumented function ST_ReadSHP() which does not exhibit this issue.
Also get the same correct result using
|
Yeah, this was quite a ride to chase down but it turns out that in our file system abstraction layer we plug into GDAL, we did not have the same behavior regarding when a file handle should return EOF as was expected by GDAL. GDAL seems to consider a file handle to be "set" to EOF once it tries to read past the end of the file (e.g. The Should be solved in #415 |
Awesome. Thanks for tracking it down and for the explanation. |
duckdb is omitting a row from some shapefiles. Here's an example using NYC Open Data
The shapefile has 5 rows.
Duckdb only shows 4 rows.
Queens is missing.
Also tried using Python/fiona which also properly has 5 rows:
The text was updated successfully, but these errors were encountered: