Pirmin Kalberer
Pirmin Kalberer
Thanks! Were you able to test the examples?
@mpajkowski ?
The repo is now updated to Actix Web 2.0 and oauth2 3.0.0-alpha.9. But I still would prefer to wait for an oauth2 3.0 release before doing the PR.
In the geospatial world, geometries are almost exclusively used together with the PostGIS extension. So implementing the PostgreSQL geometric types has not very high priority. As mentioned, geozero supports encoding/decoding...
@nixpulvis The PostGIS tests were broken indeed. Here are the setup instructions: https://github.com/georust/geozero/blob/master/geozero/tests/data/postgis.sql#L1. Please report any failures in the geozero repo.
@bbqsrc if you want to read a geometry as part of a struct, you have to use `wkb::Decode` as field type ([Example](https://github.com/georust/geozero/blob/7af9b6645bea1158017f99fdbee46c0f3f05ef76/geozero/tests/postgis.rs#L284)), or you implement `sqlx::decode::Decode` for your geometry type...
In the meantime I got some miminal examples running: https://github.com/pka/ganja-rs. I still don't undertstand `1e02` in the PGA 2d examples. The generated modules don't have an `e02` and https://bivector.net/tools.html doesn't...
Current state: ``` failures: ---- raster::mdarray::tests::test_array_names stdout ---- thread 'raster::mdarray::tests::test_array_names' panicked at 'called `Result::unwrap()` on an `Err` value: NullPointer { method_name: "GDALOpenEx", msg: "" }', src\raster\mdarray.rs:644:83 note: run with `RUST_BACKTRACE=1`...
cc @geohardtke @ChristianBeilschmidt
GDAL version is 3.4.3