This dataset contains status, location and directional information for each pedestrian sensor device installed throughout the city. The sensor_id column can be used to merge the data with related datasets.

Since the inauguration of the Pedestrian Counting System in 2009, some sensor devices have been removed or relocated. This may be for various reasons such as construction works. Others may be inactive due to a temporary issue. This is detailed in the notes column. Any changes to sensor locations are important to consider when analysing and interpreting historical pedestrian counting data.

Sensors are typically installed under an awning or on a street pole to form a counting zone on the footpath below. They record bi-directional pedestrian movements through the zone, 24 hours, every day. Locations are selected based on three criteria – retail and event activity, regular pedestrian use and the egress and entry flow to these areas. The system records movements, not images, so no individual information is collected. New sensor devices have been recently installed, with more to come in the near future as part of the city’s commitment to expanding the system.

Status field:
This field indicates if the sensor is expected to be active and is manually maintained as needed. A pedestrian sensor with an active value ('A') may be unavailable in some situations.

A representation of pedestrian volume which compares each location on any given day and time can be found in our Online Visualisation.

Related datasets:
Pedestrian Counting System – 2009 to Present (counts per hour)
Pedestrian Counting System – Past Hour (counts per minute)

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 2017 calendar year.

Known data issues:

1. There are 860 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 (April 2018) 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.

Data that is excluded:

In the 2017 car parking event data there are 3,858 records where the parking event goes into 2018 and ends at midnight.

This data contains locations of train stations and their accessibility information, such as hearing aid information.

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 2016 calendar year.

Known data issues:

1. There are 342,475 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.

Data that is excluded:

In the 2016 car parking event data there are 4,346 records where the parking event goes into 2017 and ends at midnight.

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 2015 calendar year.

Known data issues:

1. There are 453,178 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.

Data that is excluded:

In the 2015 car parking event data there are 4,138 records where the parking event goes into 2016 and ends at midnight.

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 2014 calendar year.

Known data issues:

1. There are 1,126,441 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.

Data that is excluded:

In the 2014 car parking event data there are 3,377 records where the parking event goes into 2015 and ends at midnight.

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 2013 calendar year

Known data issues:

1. There are 987,179 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.

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.

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.

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/