search

NewGraphEnvironment / dff-2022

Building digital field forms and processing data collected using R, postgresql, QGIS and other tools
Creative Commons Zero v1.0 Universal
0 stars 3 forks source link

script to update `bcfishpass` layers in `background_layers.gpkg` #139

Closed NewGraphEnvironment closed 4 months ago

NewGraphEnvironment commented 10 months ago

actually https://github.com/NewGraphEnvironment/dff-2022/commit/79598bbf26df5d04defff6f5dfdd4bd16d1226a8 closes this piece of the puzzle

closing https://github.com/NewGraphEnvironment/dff-2022/issues/124 should do the rest

NewGraphEnvironment commented 4 months ago

Looks like we have a ton layers that are missing info related to this project tracking https://github.com/NewGraphEnvironment/fish_passage_fraser_2023_reporting/issues/1

Not sure why but will try rebuilding the background_layers.gpkg with latest rfp_* scripts. Guessing this is an issue with the scripts in https://github.com/NewGraphEnvironment/dff-2022/tree/master/scripts/qgis at the time of update mergin v29 . Looks like the aws stored layers were updated but all the bcdata layers are empty. Perhaps the gpkg was essentially erased with a flag such as overwrite in the ogr2ogr calls when update_aws script was run and the update_bcdata was not.

Another anomoly occurs in the v35 version of the Fraser project and that is that the observespp_* layers do not come through to QGIS. Its extra weird because the species values are present in the gpkg but for some reason they are not visible in QGIS (even though othe colon seperaed arrayss such as barriers_anthropogenic_* do come through. so odd.

image

image

NewGraphEnvironment commented 4 months ago

update went well:

image

NewGraphEnvironment commented 4 months ago

anomoly in the the Fraser project that the observespp_* layers do not come through to QGIS is related to .qgs styles somehow. Reimporting the crossings layer from the geopackage reappears the values...