search

NewGraphEnvironment / fish_passage_skeena_2022_reporting

https://newgraphenvironment.github.io/fish_passage_skeena_2022_reporting
Creative Commons Zero v1.0 Universal
0 stars 2 forks source link

watershed elevation accuracy in tables and text #85

Open NewGraphEnvironment opened 1 year ago

NewGraphEnvironment commented 1 year ago

should link to similiar issue in bulkley 2022 if it exists

because of the way watershed areas are generated upstream of a point by fwapg using the elev_min is not a good representation of the elevation of the crossing and although the overall polygon created represents drainage area well - elev_min is not often accurate at all. for that reason it woiuld be best to remove elev_min from the object at the start (perhaps right after the pull from the sqlit in the tables script) and use the elev_site numbers to communicate

ex. Pinenut

"The elevation of the watershed ranges from a maximum of 1964m to 420m near the crossing"

however its actually about 150m lower....

image

NewGraphEnvironment commented 1 year ago

https://github.com/NewGraphEnvironment/fish_passage_bulkley_2022_reporting/issues/71

there was discussion regarding removing elev_min column in a PR

NewGraphEnvironment commented 1 year ago

Hm. Useful info though. Probably best to just filter out the Wako elevations and leave the rest in the table, but perhaps just reference site elev in text.