bcgov / bcgov/nr-bcap

SRQ8.2 - Make these layers available in BCAP

Open
#327 4 comments 0 reactions 0 assignees View on GitHub
*MVP 1 Feature HRIA-spatial
Dominant language
Python
Stars
1
Forks
1
Avg merge
3d 18h
Merged PRs (30d)
14

Description

**Given** a valid session
**When** looking at the map in BCAP
**Then** all of the identified layers are available for display.

AC:

- [ ] All of the layers identified in the Excel sheet are available in BCAP
- [x] Multiple layers can be active at one time
- [x] Layers must be viewable and toggle-able in the map layer panel
- [x] AOA and RAAD layers must remain compatible with all existing map tools (e.g., identify, overlay, measure)
- [x] Layer metadata (source, last updated) should be viewable when selected (details are captured in another ticket)
- [ ] Errors loading from BGGW should prompt a clear message: “Layer failed to load from BGGW – please try again or upload manually.”
- [x] All Branch users must have access to BCAP layers regardless of role, however, the manual uploads should only be available to the Branch users who uploads them (defined in the Layers spreadsheet provided by SMEs)
- [x] Layers should not significantly impact map performance or loading times

Please note that some come from BCGW and some not.

https://bcgov.sharepoint.com/:x:/r/teams/06659/Shared%20Documents/BCAP%20Shared%20Team%20Files/Build%20Requirements/Arch%20Branch%20working%20documents/BCAP%20Layer%20Requirements/@BCAP%20Spatial%20Layer%20Requirements.xlsx?d=w96a1fcf33197445ebf66dd2ff5794ddd&csf=1&web=1&e=fvT985

Contributor guide

No contributing guide indexed for this repository

Research direction

Review the linked Layers spreadsheet and the existing BCAP map and layer-panel entry points; first identify the full list of BCGW and manual-upload layers and their access rules. Done means every required layer is available and toggleable for valid sessions, failed BGGW loads show the specified message, and the stated map-tool compatibility and performance checks pass.

Written by the indexing model from the issue text.

Assessment

Domain
backend, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.