Modelling data was pinned to incorrect stream but was corrected in bcfishpass. Now the bcfishpass object needs to be updated. This will require a build of the database on our side or a dump from simon loaded to one of the remote servers
In theory adding the photos to the map should just be a run of source('scripts/02_prep_reporting/0180-photos-extract-metadata.R') as per the run.R file instructions... oh the theories....
Because csv to xref_pscis_modelled_crossings was changed - subsequent change to bcfishpass (stream ID) may need to be manually applied to the existing bcfishpass object (or wahtever used to generate watershed)
Moving the downstream route measure slightly so that it falls below the road and below the incorrect tributary may be a good move to capture all that watershed in the tributary.
Modelling data was pinned to incorrect stream but was corrected in bcfishpass. Now the
bcfishpass
object needs to be updated. This will require a build of the database on our side or a dump from simon loaded to one of the remote serversIn theory adding the photos to the map should just be a run of
source('scripts/02_prep_reporting/0180-photos-extract-metadata.R')
as per therun.R
file instructions... oh the theories....Because csv to xref_pscis_modelled_crossings was changed - subsequent change to bcfishpass (stream ID) may need to be manually applied to the existing
bcfishpass
object (or wahtever used to generate watershed)Moving the downstream route measure slightly so that it falls below the road and below the incorrect tributary may be a good move to capture all that watershed in the tributary.