-
Notifications
You must be signed in to change notification settings - Fork 32
Issues: duckdb/duckdb_spatial
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Save table that contains MultiLineString features to GeoJSON file
#337
opened Jun 11, 2024 by
jjcfrancisco
How do you identify a GEOMETRY column in a query when using ODBC?
#333
opened Jun 7, 2024 by
PeterAronson
The Spatial Extension appears to break ODBC bind parameters
#324
opened May 29, 2024 by
PeterAronson
Relative paths behave differently with spatial extension than with others
under review
#308
opened Apr 21, 2024 by
jaanli
ST_Read is much slower than geopandas.read_file to read remote GeoJSON
#290
opened Mar 22, 2024 by
daviewales
ST_Read crashes duckdb on Windows (but not Linux!) when reading from GeoJSON API
#289
opened Mar 22, 2024 by
daviewales
Inconsistent behavior of ST_READ in importing EMPTY geometry
GDAL
#273
opened Mar 4, 2024 by
cuteDen-ECNU
document more explicitly which projections are used and how distances are calcualted
documentation
Improvements or additions to documentation
#253
opened Feb 13, 2024 by
dberardo-com
Using "Spatial" extension to read excel is giving error with versions 0.9.0 and above. It throws "NotImplementedException: Not implemented Error: GDAL Error (6): Adding too many columns to too many existing features". The same code worked well with duck db0.8.1
GDAL
#230
opened Jan 15, 2024 by
debottamroychowdhury
1 task done
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.