16 Results filtered by...
Filter
Skip to the results
Back
Clear All

Tags > travel

Sort

Sort by Recently Added

Filter

Categories

View Types

Tags

Show All...
Tags > travel Clear All

Transport
Dataset
The City of Melbourne has installed in-ground parking bay sensors in most CBD parking bays. These sensors record when a vehicle arrives and when it departs. Each record also includes the parking restriction for the bay and whether the vehicle has overstayed that restriction. This is the data for the 2012 calendar year.
Known data issues:
1. There are 1,139,275 records that have the text ‘OLD’ at the end of the restriction in the field named ‘Sign’. This has been investigated and determined the text refers to one of two things, either:
· At the time of the parking event the restriction that has been captured is correct but when the data was extracted from the server (July 2017) the restriction had since changed.
· (Or) The particular sensor has since been replaced.
2. There are a number of records that have a negative value in the duration in field ‘seconds’. This occurs due to a sensor detecting an arrival time being after the departure time.
3. There are a number of records where the arrival and departure times have not been recorded. If the time has not been recorded the time is calculated from midnight of the arrival day to either midnight of the departure day or to the departure time.
Tags accessibility parking sensors transport travel
API Docs
Created
December 19 2017
Views
582

Transport
Dataset
The City of Melbourne has installed in-ground parking bay sensors in most CBD parking bays. These sensors record when a vehicle arrives and when it departs. Each record also includes the parking restriction for the bay and whether the vehicle has overstayed that restriction. This is the data for the 2011 calendar year
Known data issues:
1.There are 488,167 records that have the text ‘OLD’ at the end of the restriction in the field named ‘Sign’. This has been investigated and determined the text refers to one of two things, either:
· At the time of the parking event the restriction that has been captured is correct but when the data was extracted from the server (July 2017) the restriction had since changed.
· (Or) The particular sensor has since been replaced.
2. There are a number of records that have a negative value in the duration in field ‘seconds’. This occurs due to a sensor detecting an arrival time being after the departure time.
3. There are a number of records where the arrival and departure times have not been recorded. If the time has not been recorded the time is calculated from midnight of the arrival day to either midnight of the departure day or to the departure time.
Tags accessibility parking sensors transport travel
API Docs
Created
November 27 2017
Views
758

Transport
Dataset
This dataset contains detailed daily information on parking restrictions in each Pay Stay zone. There can be multiple restrictions per Pay Stay zone per day.
This data can be linked to both the street segment Pay Stay zone dataset.
https://data.melbourne.vic.gov.au/Transport-Movement/Pay-stay-zones-linked-to-street-segments/7q9g-yyvg
and also the sign plate Pay Stay zone dataset
https://data.melbourne.vic.gov.au/Transport-Movement/Sign-plates-located-in-each-pay-stay-zone/wwkr-v8s7
The datasets can be joined on Pay Stay zone.
For further information on Pay Stay https://www.paystay.com.au/
Tags parking paystay restrictions signs travel
API Docs
Created
November 3 2017
Views
1,825

Transport
Dataset
A sign plate is where the parking restrictions are displayed. This data set displays parking sign plates that are within a Pay Stay zone. There can be multiple restrictions per Pay Stay zone
This data can be linked to both the street segments to a Pay Stay zone dataset https://data.melbourne.vic.gov.au/Transport-Movement/Pay-stay-zones-linked-to-street-segments/7q9g-yyvg
and also the Pay Stay parking restricions dataset
https://data.melbourne.vic.gov.au/Transport-Movement/Pay-Stay-Restrictions/ambt-72qg
The datasets can be joined on Pay Stay zone.
For further information on Pay Stay https://www.paystay.com.au/
Tags parking paystay restrictions signs travel
API Docs
Created
November 1 2017
Views
2,806

Transport
Dataset
This dataset contains each Pay Stay zone and the street segment that it is linked to. The Pay Stay zone can go across multiple street segments and also one street segment can have multiple Pay Stay zones.
This data can be linked to both the sign plate Pay Stay zone dataset.
https://data.melbourne.vic.gov.au/Transport-Movement/Sign-plates-located-in-each-pay-stay-zone/wwkr-v8s7
and also the Pay Stay parking restrictions dataset
https://data.melbourne.vic.gov.au/Transport-Movement/Pay-Stay-parking-restrictions/ambt-72qg
The datasets can be joined on Pay Stay zone.
To create a spatial dataset the street segment can be joined with the road corridor dataset on the street segment id.
https://data.melbourne.vic.gov.au/Property-Planning/Road-corridors/9mdh-8yau
For further information on Pay Stay https://www.paystay.com.au/
Tags parking paystay street travel
API Docs
Created
November 1 2017
Views
35,746

Transport
Dataset
Upcoming Changes: Please note that our parking system is being improved and this dataset may be disrupted. See more information here.
Contains information from in-ground car parking bay sensors across the city with status indicating if a car is present or not present, the spatial coordinate of the sensor, and the street marker id.
Accessing the most current data:
To access the most recent data please use the v2.0 SODA API endpoint
or the CSV download link. Accessing the data from Socrata's v2.1 SODA API will access cached data which is only updated hourly.
Additional information:
Further information about City of Melbourne's parking sensors can be found here.
How the data joins:
There are three datasets that make up the live parking sensor release. They are the on-street parking bay sensors, on-street parking bays and the on-street car park bay restrictions.
The way the datasets join is as follows. The on-street parking bay sensors join to the on-street parking bays by the marker_id attribute. The on-street parking bay sensors join to the on-street car park bay information by the bay_id attribute. The on-street parking bays and the on-street car park bay information don’t currently join.
Outages
This dataset is updated through network relays and can be disrupted causing delays in data updates. Users of this data are encouraged to monitor the dataset's last updated timestamp in the catalogue API JSON endpoint to check for delays in the data being updated.
Disclaimer
While all due care has been taken to ensure the data of this website is accurate, current and available please note:
· there may be errors or omission in it
· there may be occasions where the data is not available and/or the website will be unavailable.
The City of Melbourne and its employees accept no responsibility for any loss, damage, claim, expense, cost or liability whatsoever (including in contract, tort including negligence, pursuant to statue and otherwise) arising in respect of or in connection with accessing, using or reliance upon the data in this website, or the unavailability of the data or the website.
Tags accessibility disability near real-time parking travel and 5 more
API Docs
Created
August 10 2017
Views
41,715