bcgov / bcgov/nr-bcap

GAP-UAT: Enable the Archaeological Sites layer by default in Spatial Edit Map Window

Open
#1,735 1 comment 0 reactions 0 assignees View on GitHub
GAP - UAT INV TRIAGE
Dominant language
Python
Stars
1
Forks
1
Avg merge
3d 18h
Merged PRs (30d)
14

Description

## Gap Details

**Found by**: UAT Inventory SMEs - cyn, lucas
**Ticket being tested**: unknown
**Sprint#:** n/a
**Test case#**: N/A
**Internet Browser used**: Chrome
**BCAP Version:** 2.0.0a25 (2026-09-09 04:00:49)

**Gap Description:**

The Archaeological Sites layer is not enabled with the other default layers when a user opens the Archaeology Site Spatial Edit window. This is something we expect to see at all times, and must not be a risk we take forgetting to do when editing sites.

This ticket is limited to the Spatial **Edit** window for MVP1. Enabling the layer by default in the Site Details map is a separate post-MVP1 enhancement.

**Screenshots (if applicable):**

Image

**Rationale / Business Context for Change:**

Inventory Archaeologists need surrounding archaeological sites visible while editing geometry. **If nearby sites are not visible, users may unknowingly create overlaps or inaccurate and unnecessarily complex site records.** The risk is especially high for users who do not know that the default map omits the layer.

**10 people have to get this right 10 times a day if it is not turned on, which is an uneccessary risk to take.**

**Proposed Solution (if applicable):**

Enable the Archaeological Sites layer by default whenever the Archaeology Site Spatial Edit window opens.

## Steps to Reproduce / Get us to where you were

1. Open an Archaeology Site record.
2. Open the Archaeology Site Spatial Edit window.
3. Review the enabled map layers.
4. Observe that the Archaeological Sites layer is not enabled by default.

## Acceptance Criteria

- [ ] The Archaeological Sites layer is enabled automatically each time the Archaeology Site Spatial Edit window opens.
- [ ] Site geometries within the current map extent are visible without the user manually enabling the layer.
- [ ] The default is applied for all users authorized to edit Archaeology Site spatial data.
- [ ] This change does not prevent a user from turning the layer off during the current editing session.
- [ ] The MVP1 change does not alter the Site Details map configuration unless that scope is separately approved.

## Test Case Drafts

1. Open Spatial Edit for a site near one or more other sites and confirm that the Archaeological Sites layer is already enabled and nearby geometries are visible.
2. Turn the layer off, close Spatial Edit, reopen it, and confirm that the default-enabled behaviour is applied to the new editing session.
3. Confirm the behaviour using accounts with each applicable Inventory editing role.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the issue through an Archaeology Site record and its Spatial Edit window, then trace how the default map layers are configured. Verify the Archaeological Sites layer is enabled when a new editing session opens, nearby geometries are visible, users can turn it off during the session, and the Site Details map remains unchanged; use the three drafted test cases for validation.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
frontend, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Active
Clarity
Clearly specified
Newbie friendliness
72/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.