Upcoming Changes: Please note that our parking system is being improved and this dataset may be disrupted. See more information here. Each row contains information about the restrictions that apply to one parking bay. Each restriction consists of a set of columns: 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 restrictions by the bay_id attribute. The on-street parking bays and the on-street car park bay restrictions don’t currently join. Field information: - FromDay: The first day in the range on which this restriction applies (0=Sunday, 6=Saturday) - ToDay: The final day in the range, inclusive. (1-5=Monday to Friday) - StartTime: The time each day when the restriction applies. - EndTime: The time each day when the restriction ends. - TypeDesc: The type of restriction. Eg: "2P Meter" (two hour parking, paid for using a meter), "Disabled Only" (only vehicles with disabiled permits can park). - Description: A compact, human-readable description of the overall restrictions. TKT A stands for Ticket Area covers multiple bays within that area. DIS ONLY and DIS are both disabled parking spaces - Duration: The time that a vehicle can park in the spot (assuming they can legally park there). - DisabilityExt: For bays that aren't limited to disabled permits, how much time a vehicle with disabled permit can spend in the spot. Usually twice the regular amount of time. - EffectiveOnPH: Does this restriction apply on public holidays. - Exemption: Which vehicles are exempt. There can be multiple restrictions, occurring at non-overlapping times. Each restriction is a set of columns with a number: FromDay1, ToDay1, StartTime1, EndTime1, etc. 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.

Upcoming Changes: Please note that our parking system is being improved and this dataset may be disrupted. See more information here. Each row contains information about the restrictions that apply to one parking bay. Each restriction consists of a set of columns: 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 restrictions by the bay_id attribute. The on-street parking bays and the on-street car park bay restrictions don’t currently join. Field information: - FromDay: The first day in the range on which this restriction applies (0=Sunday, 6=Saturday) - ToDay: The final day in the range, inclusive. (1-5=Monday to Friday) - StartTime: The time each day when the restriction applies. - EndTime: The time each day when the restriction ends. - TypeDesc: The type of restriction. Eg: "2P Meter" (two hour parking, paid for using a meter), "Disabled Only" (only vehicles with disabiled permits can park). - Description: A compact, human-readable description of the overall restrictions. TKT A stands for Ticket Area covers multiple bays within that area. DIS ONLY and DIS are both disabled parking spaces - Duration: The time that a vehicle can park in the spot (assuming they can legally park there). - DisabilityExt: For bays that aren't limited to disabled permits, how much time a vehicle with disabled permit can spend in the spot. Usually twice the regular amount of time. - EffectiveOnPH: Does this restriction apply on public holidays. - Exemption: Which vehicles are exempt. There can be multiple restrictions, occurring at non-overlapping times. Each restriction is a set of columns with a number: FromDay1, ToDay1, StartTime1, EndTime1, etc. 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.

Upcoming Changes: Please note that our parking system is being improved and this dataset may be disrupted. See more information here. This dataset contains spatial polygons which represent parking bays across the city. Each bay can also link to it's parking meter, and parking sensor information. 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 information. 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 restrictions by the bay_id attribute. The on-street parking bays and the on-street car park bay information don’t currently join. Please see City of Melbourne's disclaimer regarding the use of this data. https://data.melbourne.vic.gov.au/stories/s/94s9-uahn

Upcoming Changes: Please note that our parking system is being improved and this dataset may be disrupted. See more information here. This dataset contains spatial polygons which represent parking bays across the city. Each bay can also link to it's parking meter, and parking sensor information. 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 information. 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 restrictions by the bay_id attribute. The on-street parking bays and the on-street car park bay information don’t currently join. Please see City of Melbourne's disclaimer regarding the use of this data. https://data.melbourne.vic.gov.au/stories/s/94s9-uahn

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. Download: Download compressed CSV (1.17GB, 37.5 million rows)

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. Download: Download compressed CSV (1.17GB, 37.5 million rows)

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. Download: Download compressed CSV (1.56GB, 51.5 million rows)

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. Download: Download compressed CSV (1.56GB, 51.5 million rows)

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. Download: Download compressed CSV (1.13GB, 35.9 million rows)

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. Download: Download compressed CSV (1.13GB, 35.9 million rows)