Explore pulling traffic and counter data through Trafx

[LindsayMacfarlane]

Description:

Determine if there is an API or other mechanism to pull traffic and counter data from Trafx into A&R to help automate data entry process for staff.

Acceptance Criteria:

• [ ] Determine if there is an API available
• [ ] Explore what is needed to pull/ingest data into our system
• [ ] Get a walk through of Trafx from A&R team
• [ ] Determine if any data manipulation may be required
• [ ] Create future tickets as needed (e.g., ability to correct data once in system)

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:

[LindsayMacfarlane]

This was discussed at the October 11 prioritization session. Additional notes from the conversation:

• Explore what is possible
• What does it look like to get the API
• Determine if any data manipulation is required
• Get a walk through of Trafx
• Would need a way to correct the data (traffic counters are error prone)

[LindsayMacfarlane]

Previous documentation done by RST to link to Trafx api:

p_&_r_visitor_statistics_report_and_dashboard_prototype_technical_document_v2.docx code is in bcgov-c for now but some of you may have access and uses OpenSearch! https://github.com/bcgov-c/rvs-card/blob/main/README.md