Two culvert crossing is entered as two records.
Crossing 61504 is primary record, delete 61502 (overflow)

http://a100.gov.bc.ca/pub/pscismap/imageViewer.do?assessmentId=61615

102988 (MASSE, 2014) appears to be duplicate, a reassessment of 50246 (GRAINGER, 2011)

stream_crossing_id : 198380, Five Mile Creek

A phase 1 submission sheet was submitted to PSCIS yesterday (April 27) containing one crossing that was surveyed in 2022 for the Ministry of Transportation. There is a mistake in the UTM field. The value inputted was 9 when it should have been 10. This submission needs to be removed from the system.

• Note: The UTM was changed and the spreadsheet was re submitted today (April 28).
• Below is a screenshot of the submission confirmation (the one with the incorrect UTM that needs to be removed).

see NewGraphEnvironment/fish_passage_peace_2022_reporting#110

Generating SQL for deleting a duplicate is fairly straightforward, add script that does this

Latest in PSCIS is a culvert assessed as a barrier in 2014.
Imagery clearly shows a bridge has been installed.

Hi Simon, here is a table showing all the pscis ids for our phase 1 sites. It was entered into the system twice. We'd like to retain everything from stream_crossing_id 198109 down to 198117, and get rid of the duplicates which are from 198108 up to 198100. In reference to issue here: NewGraphEnvironment/fish_passage_bulkley_2022_reporting#41

As per the issue here: NewGraphEnvironment/fish_passage_bulkley_2022_reporting#5. Crossing 197657 should be aligned with modelled crossing 1800067.

103055 (VAST, 2012) is a reassesment of site 50194 (GRAINGER, 2011).

It seems many points for project id 841 (VAST, 2012) are of dubious quality.

Point is currently on a mountaintop above Crossing Creek.
Based on description it should be down near 62185 at Red Canyon Creek.

Locations of 62186 and 62187 also look suspect.

Latest in PSCIS for this crossing at Foreman Rd is a 2014 culvert barrier assessment.
The crossing has been remediated: https://news.gov.bc.ca/releases/2020TRAN0099-001219

for example:
https://openmaps.gov.bc.ca/geo/pub/wfs?service=WFS&version=2.0.0&request=GetFeature&typeName=WHSE_FISH.PSCIS_ASSESSMENT_SVW&outputFormat=json&SRSNAME=epsg%3A4326&CQL_FILTER=STREAM_CROSSING_ID%3D3318

A form may be more useful than the existing template:
https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#creating-issue-forms

This may be going a bit far with a beta feature but is pretty neat: https://stefanbuck.com/blog/codeless-contributions-with-github-issue-forms

VAST (2012) assessed two culverts at this location. Primary flow of channel was through 62244 in 2012 but migrated over to 62245 when reassessment was done (MASSE, 2015).

Site 62244 should just be deleted (or the info transferred over into initial assessment of 62245). Because older assessment data is not available via PSCIS warehouse views it won't make much difference to users either way.

Coordinates are on side channel of North Thompson.
stream_name = unknown trip to Craigellachie Creek
Likely an incorrect digit in the easting value, or perhaps the zone is wrong.

Describe the bug

stream_crossing_id: 3138, McQuarrie Creek

• crossing type_code should be CBS
• barrier_result_code should be BARRER
• see http://a100.gov.bc.ca/pub/pscismap/imageViewer.do?assessmentId=3138 and satellite imagery

Scoring may need to be reviewed.

Describe the problem

A clear and concise description of which crossing(s) is/are affected, what the problem is, and how the data differs from what is expected.
Identify the crossing with its stream_crossing_id, include references to other crossings, links photos, etc as needed.

EXAMPLE:

stream_crossing_id: 3138, McQuarrie Creek

• crossing type: currently OBS/Pipe Arch, should be CBS/Round
• barrier_result_code: currently PASSABLE, should be BARRER
• see http://a100.gov.bc.ca/pub/pscismap/imageViewer.do?assessmentId=3138 and satellite imagery

Screenshots
If applicable, add map/photo screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

Describe the problem

See output of https://github.com/smnorris/bcfishpass/blob/main/01_prep/02_pscis/sql/05_pscis_points_duplicates.sql

Currently there are >200 crossings that are likely to be duplicates (487 records in the duplicates table, but each record from a set of duplicates is included)

The usual reasons for duplication include (but are not limited to):

• re-assessments that did not include the original stream_crossing_id in the reassessment submission
• separate assessments of two pipes at a single crossing (contrary to PSCIS assessment guide, mostly just in older assessments)
• two crossings have been snapped to the same stream when one is on an unmapped stream

Hot spots (10 or more):

 ALBN                 |    10
 GRAI                 |    10
 LARL                 |    10
 TABR                 |    10
 HORS                 |    12
 REVL                 |    16
 KOTL                 |    16
 SETN                 |    16
 HOLB                 |    17
 KETL                 |    18
 PARS                 |    20
 MORI                 |    20
 LFRA                 |    22
 KOTR                 |    24
 ELKR                 |    28
 SALM                 |    29
 BULK                 |    32
 MCGR                 |    32