Last active
April 7, 2024 18:39
-
-
Save NewGraphEnvironment/5d6120dc46b8a6b16dad7631981ecbed to your computer and use it in GitHub Desktop.
package development
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rfp - reproducable field projects | |
+ retrieve metadata | |
- QGIS project generation | |
- mergin/git integration to track commit messages for pushed mergin versions in git | |
- mergin project creation | |
- mergin status testing | |
- mergin permissions tracking and | |
- background_layers.gpkg | |
- retrieve metadata from bcdata catalougue and elsewhere when provided with schema.table names | |
- tables showing layers in QGIS projects and | |
- tables showing layer metadata for layers in QGIS projects | |
- tables for mergin permissions | |
- documentation of workflows (diagrams?) and layers used for dbh used to do analysis | |
dbh - database helpers | |
- queries to build params for site selection | |
- explore and manage database | |
- set up database on remote machine? | |
rff - reproducable field forms | |
- build tables using excel templates used to submit data to province as "templates" | |
- add value added columns for information we want/need | |
- store QGIS style files for application to field forms by rfp | |
- track csv and Rdata (if necessary - doubt it) versions of field forms in git repos | |
- burn utms to columns from sf objects | |
- pscis assessment form | |
- fiss fish data form | |
- vegetation monitoring forms | |
- climate change param prediction validation? ie. if we use GIS to predict risk does field investigations verify? | |
fpr - fish passage reporting | |
- import forms | |
- munge | |
rrh - reproducable reporting helpers | |
- fpr_kable | |
- fpr_make_hydrograph | |
where does fpr_sp_watershed_stats belong? | |
fpr_make_geopackage? | |
fpr_sheet_trim? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment