Map Filtering: Determine which fields in the db we want to filter on

[Dianadec]

Description:

is it using the same as info services has?

Reference this previous ticket: https://github.com/bcgov/reserve-rec-api/issues/30

Acceptance Criteria:

• when typing in strathcona, strathcona will show up on a map and the list will show you what you can do in strathcona
• (activities for 3 parks only)

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]

Sprint planning notes:

• Is this an implementation ticket or?
• How might we find out what users would want to filter on?
• Waiting on ability to get public user feedback - Do they want to take a more exploratory approach and see all campgrounds in that search view? or do I just want to see a park at that higher level and select subarea in that park etc.

Some give-ins that we could filter on:

• Filter our parks based on certain types of activities or amenities. eg: bear caches and water sources.
• Next, we can get into the deeper level of search filtering functionality later on.

THIS OPTION ---> If implementation ticket:

• when typing in strathcona, strathcona will show up on a map and the list will show you what you can do in strathcona
• (activities for 3 parks only)