yutannihilation commented on issue #163:
URL: https://github.com/apache/sedona-db/issues/163#issuecomment-3344505921
It seems I get a different error (on macOS, with the latest GitHub version).
``` r
library(sedonadb)
library(sf)
#> Linking to GEOS 3.13.0, GDAL 3.8.5, PROJ 9.5.1; sf_use_s2() is TRUE
st_read(
"https://raw.githubusercontent.com/geoarrow/geoarrow-data/v0.2.0/example-crs/files/example-crs_vermont-utm.fgb"
) |>
sd_to_view("vermont")
#> Reading layer `example-crs_vermont-utm' from data source
#>
`https://raw.githubusercontent.com/geoarrow/geoarrow-data/v0.2.0/example-crs/files/example-crs_vermont-utm.fgb'
#> using driver `FlatGeobuf'
#> Simple feature collection with 1 feature and 0 fields
#> Geometry type: POLYGON
#> Dimension: XY
#> Bounding box: xmin: 625858.2 ymin: 4733644 xmax: 775539.6 ymax: 4989818
#> Projected CRS: WGS 84 / UTM zone 18N
sd_read_parquet(
"https://github.com/geoarrow/geoarrow-data/releases/download/v0.2.0/microsoft-buildings_point_geo.parquet"
) |>
sd_to_view("buildings")
sd_sql(
"
SELECT
count(*)
FROM
buildings
JOIN vermont
WHERE
ST_Intersects (buildings.geometry, ST_Transform (vermont.geometry,
'EPSG:4326'))
"
) |>
st_as_sf()
#> Error: type_coercion
#> caused by
#> External error: SedonaDB internal error: Extension type not implemented:
<geoarrow.polygon>:List(Field { name: "rings", data_type: List(Field { name:
"vertices", data_type: Struct([Field { name: "x", data_type: Float64, nullable:
false, dict_id: 0, dict_is_ordered: false, metadata: {} }, Field { name: "y",
data_type: Float64, nullable: false, dict_id: 0, dict_is_ordered: false,
metadata: {} }]), nullable: false, dict_id: 0, dict_is_ordered: false,
metadata: {} }), nullable: false, dict_id: 0, dict_is_ordered: false, metadata:
{} }).
#> This issue was likely caused by a bug in SedonaDB's code. Please help us
to resolve this by filing a bug report in our issue tracker:
https://github.com/apache/sedona-db/issues
```
<sup>Created on 2025-09-29 with [reprex
v2.1.1](https://reprex.tidyverse.org)</sup>
--
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]