ptaillandier
ptaillandier
The problem comes the fact that the grid is in WGS84 - GAMA has to project the grid in a projected CRS, which can lead to error in the coordinate...
Very interesting. However, for me, the default behavior should be `"333%444" split_with ("%%", true)` to be consistent with older versions of GAMA and because it seems to be a lot...
2018 .... it is very recent considering the long history of GAMA 😅 Le jeu. 3 mars 2022 à 10:09, Alexis Drogoul ***@***.***> a écrit : > Should I mention...
The proposed solution (using gt-geojsondatastore) is worse than the existing one: gt-geojsondatastore suffers from several major flaws: lack of documentation, inconsistency with Shapefiledatastore, many questionable design choices, no usage examples....
I was not able to reproduce this bug (GAMA git version, windows 10, chrome).
Hi, There is two issues here: 1. The points_on and any_location_in operators work only for 2D shape 2. The built-in geometries (cube, sphere....) are not real 3D geometries, but 2D...
Hi, I have the same error as Thomas. To be totally honest, I'm not surprised: this skill wasn't designed to be run in parallel and there are many elements that...
It will be very difficult to fix this one: the clean_network operators deeply relies on the JTS operators (i.e. intersects) that do not work in 3D...
We can just replace the default "event" by the new defined one.
Hi, I can't test the script because some files with the shapefile are missing (.shx, .dbf and .prj files) Cheers, Patrick Le dim. 14 nov. 2021 Ã 20:31, litingzhen ***@***.***>...