-
We should have auto-build of the plugin with geodiff for various platforms.
-
Currently the client on 'pull' needs to do a bunch of calls to geodiff.
local = gpkg in project directory - may be locally modified (based on v1)
base = gpkg in a side directory - keeps original d…
-
I assumed that if no change has been made to the geopackage (https://github.com/qgis/QGIS/issues/23991) and with geodiff integration, there won't be any update of the file when syncing. But my file on…
-
When I try to sync a project I get this error:
![image](https://user-images.githubusercontent.com/2649047/65582609-a7268d00-df75-11e9-86b2-9759ac22684a.png)
-
This is related to awkwardness of Geopackage again.
To reproduce, your survey layer should be gpkg
1- Download and open a project in QGIS through the plugin
2- Add a new feature to the survey lay…
-
There are surely more tools that will be helpful here (especially in light of #3). List them.
-
Given two DEMs, A.tif and B.tif, the command
geodiff A.tif B.tif
can be hundreds of times slower than
geodiff B.tif A.tif
That happens if A.tif covers a huge area but B.tif a smaller one. I think…
-
Como maioria desses ruas ja existe no banco dados, com formas corretas ou não, precisamos baixar estes objetos, e fazer um geodiff para identificar objetos iguais.
Pitfalls: o tamanho no objetos do O…
-
When geodiff takes the difference of two DEMs, it masks the no-data values in the first DEM, but not in the second one, which is not right.
The function dem_to_geodetic also needs to be modified to …
-
The current approach of transforming a DEM to a point cloud:
geodetic_to_cartesian(dem_to_geodetic(create_mask(DEM, nodata)))
has an issue. A no-data point in the DEM gets transformed by dem_to_geod…