OpenActive W3C Community Group
Developer ReferenceData ValidatorDataset Dashboard
  • W3C Community
  • Join the group
  • Upcoming Meetings
  • Key Discussions
  • Community Group Meetings (2021-24)
    • 2025-02-19 Specification Development Plan
    • 2024-10-23 - Routes Update
    • 2024-05-22 W3C/AEF Show & Tell - Stabilising and improving OpenActive's infrastructure
    • March and April 2024 meetings cancelled
    • 2024-02-21 Phase 5 Extension and Club Data
    • 2023-10-18 OpenActive and Open Referral UK
    • 2023-06-21 Approaches to maintaining the OpenActive tech infrastructure
    • 2023-05-24 Data Quality Explorer Demo
    • 2023-04-26 Data Quality, Activities and Priorities
    • 2023-03-29 Facilities and Activities
    • 2023-03-01 Data Quality Update
    • 2023-02-15 Active Places
    • 2023-01-18 Focus for year ahead
    • 2022-12-07 Data Quality Reporting
    • 2022-11-09 Reporting Data Quality
    • 2022-10-26 High Frequency Sessions
    • 2022-10-12 Data Quality in OpenActive
    • 2022-09-14 - Ways of working
    • 2022-06-08 - Accessibility
    • 2022-04-20 - LGBT+ Inclusion
    • 2022-03-02 - Safeguarding Requirements
    • 2022-02-02 - Block Bookings
    • 2021-12-06 - Social Prescribing Attributes, Places, and Block Bookings
    • 2021-11-24 - Dependent Accounts
    • 2021-11-10 - Access Pass Requirements
    • 2021-10-27 - Terminology in the Membership Proposal
    • 2021-10-13 - Membership Proposal Review
    • 2021-09-29 - Requirements for the Membership Proposal
    • 2021-07-14 - Phase 4 Technical Communication Channels
    • 2021-06-30 - Phase 3 Summary
    • 2021-06-02 - Facility Types, pt. 2
    • 2021-05-26 - Facility Types
    • 2021-04-07 - Updates to the Opportunity specification
  • 2021-01-13 - Dataset Site Specification
  • Meetings - Technical Working Group
    • 2022-07-07 - Final Review and Signoff
    • 2022-06-23 Spec Finalisation Scheduling
    • 2022-06-09 - Preliminary Review, pt. 2
    • 2022-05-26 - Preliminary Review, pt. 1
    • 2022-01-27 - Worked examples of dependent account handling
    • 2022-01-20 - Dependent Accounts, Updating Personal Data, and Late Cancellation Policies
    • 2022-01-13 - Facility Booking, Customer Age, Sections 9 & 10, Appendices D & G
    • 2022-01-06 - Sections 7 & 8, Appendices E & F
    • 2021-12-09 - Appendices C6, C7, C9, D3, D4, continued
    • 2021-12-02 - Appendices C6, C7, C9, D3, D4, D5; Sections 5 & 6
    • 2021-11-25 - Modelling Dependent Accounts
    • 2021-11-18 - Modelling Customer Accounts and Customers
    • 2021-11-11 - Terminology; Sections 1 & 2; Appendices A&B
    • 2021-11-04 - Terminology
  • Meetings Archive
    • 2020-11-18 - Accessibility Specification
    • 2020-11-04 - Documentation Review
    • 2020-10-07 - Schedules
    • 2020-09-23 - 1:1 Coaching Sessions
    • 2020-09-09 - The Dataset Site Specification cont..
    • 2020-08-26 - Dataset Site Specification (cont.)
    • 2020-07-15 - Dataset Site Specification
    • 2020-07-01 - Opportunity API
    • 2020-06-17 - Improving the RPDE specification
    • 2020-06-03 - Modelling Facilities
    • 2020-05-06 - Revisiting Accessibility
    • 2020-04-22 - Safeguarding
    • 2020-04-08 - Wrapping Up Virtual Events
    • 2020-03-25 - Virtual Events and other COVID-19 proposals
    • 2020-03-11 - Customer authentication continued
    • 2020-02-12 - Opportunity Specification Proposals
    • 2020-01-29 - Customer Authentication continued
    • 2019-12-04 - Safeguarding and HTML support
    • 2019-11-20 - Customer Authentication
    • 2019-11-06 - Finalising the Routes Specification
    • 2019-09-25 - References vs Objects
      • 2019-10-09 - Difficulty Level and Prerequisites
    • 2019-09-11 - Safeguarding and the Opportunity Specification
    • 2019-08-14 - Routes versioning and data publication
    • 2019-07-31 - Routes Initial Implementation
    • 2019-07-17 - Routes Workshop Follow-up
    • 2019-07-03 - Routes Workshop Preparation
    • 2019-06-19 - Modelling Opportunities: Difficulty Level/Prerequisites
    • 2019-06-05 - Modelling Opportunities: Difficulty Level
    • 2019-05-22 - Routes Data Exploration
    • 2019-05-08 - Routes and Accessibility Planning
    • 2019-04-10 - Booking: Workshop followup
    • 2019-04-02 - Booking Finalisation Workshop
    • 2019-03-27 - Booking: Overview and feedback
    • 2019-03-13 - Booking: Overview and feedback
    • 2019-02-27 - Booking: Overview and direction check
    • 2019-02-13 - Booking: Cancellations and Refunds
    • 2019-01-30 - Booking: Cancellations and Refunds
    • 2019-01-16 - Booking: Walkthrough
    • 2018-12-05 - Booking: Tax
    • 2018-11-21 - Booking: Tax
    • 2018-11-16 - Activity List Tool
    • 2018-11-07 - Booking Feedback
    • 2018-10-24 - Accessibility requirements
    • 2018-10-10 - Booking API Update and Feedback
    • 2018-09-12 - Booking API 1.0
    • 2018-08-30 - Modelling Event Types
    • 2018-08-15 - Booking
    • 2018-08-01 - Routes, Model V2
    • 2018-07-18 - Validator
    • 2018-07-04 - Roadmap
    • 2018-06-20 - Facilities
    • 2018-06-06 - Facilities
    • 2018-04-25 - Opportunity Model, Booking
    • 2018-04-11 - Virtual Events, Booking, Governance
    • 2018-03-28 - GetTheData, ageRange, genderRestriction, amenities
    • 2018-03-14 - "Amenity Use", Booking, RDPE 1.1
    • 2018-02-28 - Facilities, Booking, Validation
    • 2018-02-14 - Booking
    • 2018-01-31 - Booking
    • 2018-01-17 - Facilities
    • 2017-12-13 - Booking
    • 2017-11-29 - Activity List
    • 2017-11-15 - Audit of Published Data
    • 2017-11-02 - Data Usability
    • 2017-06-21 - Activity List
    • 2017-05-24 - Modelling Events
    • 2017-05-10 - Accessibility, Activity List
    • 2017-04-26 - Event attendance, Booking
    • 2017-04-12 - Modelling Events, Activities
    • 2017-03-29 - Modelling Events, Activities
    • 2017-03-13 - Modelling Events, Activities
    • 2017-02-22 - Modelling Events, Activities
    • 2017-01-25 - Initial draft model
    • 2016-12-07 - Introductions
Powered by GitBook
On this page
  • Summary
  • Video
  1. Community Group Meetings (2021-24)

2024-10-23 - Routes Update

Previous2025-02-19 Specification Development PlanNext2024-05-22 W3C/AEF Show & Tell - Stabilising and improving OpenActive's infrastructure

Last updated 3 months ago

Summary

We had an interesting discussion on the state of play of the specifications and various initiatives around sharing route information.

Startig with a quick Intro to the OpenActive's route guidance specifications, which initially focused on guided activities but expanded to encompass self-directed activities due to increased demand (especially around COVID). Sport England's interest stems from the accessibility and health benefits of outdoor activities.

National Trust's path inventory (). The National Trust has mapped its paths using OpenStreetMap, including details like path type (public right of way, permissive, etc.) and barriers (gates, stiles). They have not implemented all the optional attributes in the Route Specification v1.0, but there is alignment with the core aspects.

There's a lack of consensus amongst providers regarding grading and accessibility standards. The National Trust is working on a comprehensive list of path attributes (80-100) and exploring consistent terminology with other organisations (e.g. Natural England, National Landscape Partnership). The focus is on “describing the path rather than the person” to allow users to make informed choices and the initial scope is walking / running.

Challenges include data capture for thousands of kilometres of paths, defining and consistently representing accessibility for diverse needs (wheelchair users, visually impaired, etc.), and standardising data collection across various organisations.

Slow Ways () are creating a network of walking routes that connect all of Britain’s towns, cities and national parks. They piloted an interesting alternative data approach, using Uber's H3 hexagons to describe landscape characteristics and accessibility at different scales.

British Cycling () is interested in creating accessible cycling routes but faces similar challenges in defining accessibility for non-standard cycles. They have routes, including the Let’s Ride platform which has an OpenActive feed of group rides (though there are a few data issues there), and they also have clubs, which may not have a fixed base or location.

Paddle UK () wants to incorporate open data for paddle trails, including what is along the way, which can vary depending on river conditions.

The Stream Initiative () - a number of Water Authorities are also exploring sharing data on routes and related activities at sites like reservoirs.

The ODI and our role in OpenActive () The Open Data Institute (ODI) works with governments and organisations to build and promote better data ecosystems and data infrastructure. We have been funded by Sport England to steward the OpenActive standards and specifications, provide technical support, and facilitate community engagement. The standards aim to encourage wider adoption of open data to promote physical activity.

Discussion () around various issues, barriers and challenges to sharing data and getting people more active, and next steps.

Next Steps: Strategic direction and outreach

With National Trust, the ODI is exploring if there is more we can do to promote the work at a senior level to ensure the right organisations are included in conversations.

Next Steps: Agreeing path attributes and terminology

We will support and facilitate further work to reach consensus on the path attributes and to reflect this in the Route Guidance specification and guidance for publishers and consumers. We recognise the need to find the appropriate level of flexibility within the specification to balance standardisation with the needs of different audiences.

Next Steps: Supporting data publishers

We’re also keen to support those implementing open data. Please get in touch if you’d like to arrange a chat about mapping your data to the Route Guidance data model, creating a data feed, or to share any feedback on the specifications and documentation.

Video

starts 2:38
starts 17:15
starts 23:24
starts 27:34
starts 29:12
starts 32:39
starts 35:54