jiayuasu commented on issue #264: URL: https://github.com/apache/sedona-db/issues/264#issuecomment-3470890257
agree. The way it works with geojson now is via geopandas, which is not good. This is how it works now in SedonaDB SQL: https://sedona.apache.org/sedonadb/latest/reference/sql/. I think we can add native support for shapefile as well. ``` "SELECT * FROM 'https://raw.githubusercontent.com/geoarrow/geoarrow-data/v0.2.0/natural-earth/files/natural-earth_cities_geo.parquet'").show() ``` Andy has a similar request on DataFusion: https://github.com/apache/datafusion/issues/3773 ``` SELECT * FROM read_parquet('https://raw.githubusercontent.com/geoarrow/geoarrow-data/v0.2.0/natural-earth/files/natural-earth_cities_geo.parquet) ``` In Sedona Spark: ``` SELECT * FROM csv.`test.csv` SELECT * FROM parquet.`test.parquet` ``` ST_Read is more like a DuckDB's own syntax for GDAL. We can have a similar one for all cases but we don't need to maintain the same API as DuckDB like explicit spatial filters in ST_Read. We need to figure this out for raster as well. CC @jesspav -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
