Live availability
What the feed reports now
Available spaces, capacity, percentage full, practical status and the age of the reading. It may lag the physical car park.
Transparent by design
Live availability, historical patterns, future-date planning and Today’s Guidance answer different questions. This page explains how each signal helps and where uncertainty remains.
The data path
Transport for NSW publishes real-time occupancy data for supported Park & Ride facilities. ParkRide Planner’s Cloudflare backend retrieves and caches that public data, stores selected historical observations, and serves a consistent API to the iPhone and Apple Watch app.
The app does not make a new direct Transport for NSW request every time someone opens a screen. That design protects the public API, improves reliability and lets many commuters reuse the same fresh result.
View the Transport for NSW real-time car park occupancy information.
Four kinds of answer
Live availability
Available spaces, capacity, percentage full, practical status and the age of the reading. It may lag the physical car park.
Typical fill time
Recent same-weekday history helps describe when a facility usually became practically full. It is a baseline, not today’s forecast.
Today’s Guidance
Fill likelihood, current pressure and live pace help explain whether conditions look tight, normal or quieter than usual.
Future planning
A selected future date and arrival time use matching historical evidence. The app does not pretend future live data already exists.
Plan a date
Choose a future date and target arrival time to see whether comparable recent weekdays still had space when you plan to arrive. The chart remains a historical baseline for that weekday; there is no invented live point or current-day forecast.
This is useful for planning tomorrow or later in the week while keeping the distinction between observed history and current conditions clear.

Relevant days only
School holidays can change commuter parking patterns. When enough recent matching school-holiday weekdays exist for that car park, ParkRide Planner reports what those days did and how the planned arrival time performed.
Sparse holiday evidence stays descriptive. It does not become a confident exact-time forecast, and the app can still show the usual term-time weekday as a useful comparison.

Why “practically full”
A car park can still report a small number of spaces while being too tight for a commuter to treat as a dependable option. ParkRide Planner therefore distinguishes literal reported availability from a practical status intended for morning decisions.
This avoids presenting “three spaces left” as though those spaces will still be available after a drive to the station.
Drive-time context
If you enable optional location context, the app can ask Apple Maps for nearby sorting and a drive-time estimate. Your device location, saved address or place, and route estimate inputs are not sent to the ParkRide Planner backend.
The resulting travel time can help answer whether a car park that looks viable now is still likely to be viable when you arrive.
No black box
The parking guidance is calculated from structured parking data, recent patterns, time and optional on-device travel context. It does not depend on a generative AI model.
That keeps the core answer fast, explainable and suitable for Siri, widgets, Apple Watch and other commuter surfaces.
The honest limit
Parking changes quickly, public data can be delayed, and spaces may disappear while you drive. ParkRide Planner is intended to improve a commuter’s decision, not certify an outcome.
That is why the app shows freshness, uses ranges where appropriate and says “usually”, “expected” and “best chance” instead of promising certainty.