Explore Map Tilesets

[Dianadec]

Description:

Refinement Notes: First, need to confirm what we need to show on the tileset (can be added to over time) - eg: Roads, park boundaries, water sources (lakes, rivers, streams), cities, townships Then figure out where that info is coming from and if we ever need to update the tileset where would we look for the source of truth

Can we copy a base layer and pull the typical bc gov base layer as a map tile or replicate it? - LM to provide to share. Note: ML says baselayers are different from tilesets.

Tile is in the background; base layers go on top (markers etc)

our own source (eg: tantalus) for tilesets specifically for protected areas

https://catalogue.data.gov.bc.ca/dataset/bc-basemap

Acceptance Criteria:

• need to explore more technically (after drivebc demo) what those endpoints are, how they can integrate with our own technology, and go from there. Where tilesheets are
• is there a capability to use datasets/technology and if so how?

Development Checklist:

• [ ] ...
• [ ] ...
• [ ] ...

Dependencies

• Blocked by
• Blocking

Relevant documentation as reference

Definition of Ready

• [ ] Acceptance criteria are included
• [ ] Wireframes are included (if applicable)
• [ ] Design / Solution is accepted by Product Owner (if applicable)
• [ ] Dependencies are identified (technical, business, regulatory/policy)
• [ ] Story has been estimated (under 13 pts)

Definition of Done

• In progress:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] UI meets accessibility requirements
  • [ ] Unit tests are written
  • [ ] Work is traceable in GitHub
  • [ ] PR linked to ticket number
  • [ ] If needed/required - Dev adds flag/label to highlight any migration steps necessary prior to PROD deployment
• Code review:
  • [ ] Code is peer reviewed and has passed CI/CD tests
• QA:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Code is potentially shippable to the production environment
  • [ ] Functional features have been tested and passed by QA
  • [ ] UI components tested by designer
  • [ ] Code is deployed to PROD when moved to 'done' column (unless requested otherwise by PO)
• PO Review:
  • [ ] Acceptance criteria are tested (Functionality meets the acceptance criteria defined in the ticket)
  • [ ] Reviewed and approved by Product Owner

Notes:

[Dianadec]

Note: shouldn't need arcgis to get vector tiles