This dataset contains hourly pedestrian counts since 2009 from pedestrian sensor devices located across the city. The data is updated on a monthly basis and can be used to determine variations in pedestrian activity throughout the day.The sensor_id column can be used to merge the data with the Pedestrian Counting System - Sensor Locations dataset which details the location, status and directional readings of sensors. Any changes to sensor locations are important to consider when analysing and interpreting pedestrian counts over time.Importants notes about this dataset:• Where no pedestrians have passed underneath a sensor during an hour, a count of zero will be shown for the sensor for that hour.• Directional readings are not included, though we hope to make this available later in the year. Directional readings are provided in the Pedestrian Counting System – Past Hour (counts per minute) dataset.The Pedestrian Counting System helps to understand how people use different city locations at different times of day to better inform decision-making and plan for the future. 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 – Past Hour (counts per minute)Pedestrian Counting System - Sensor Locations
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
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)
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
The City of Melbourne employs a contractor to perform traffic counts on roads throughout the municipality. The numbers of vehicles are recorded per hour and split into 12 categories based on the Austroads vehicle classification. Vehicle class 13 is used when the type of vehicle can’t be determined.
In the 2017/16 surveys all bikes, motorcycles and maximum speeds were captured. In the 2015 surveys not all surveys captured bikes, motorcycles and maximum speed. In the 2014 surveys no bikes, motorcycles or maximum speed were captured.
This data is designed to be joined to the road corridor data on road_segment and seg_id. Some records have more than one road segment this is because the survey crosses intersecting roads and the intersections have a road segment number. In the Road corridor table some road segments will have the same seg_id.
For a description of each field please see the attached data dictionary.
Known data issues: - 112 records had vehicle_class fields which contained the character '-'. This should value should be a 0 value.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
Current issue 23/09/2020 Please note: Sensors 67, 68 and 69 are showing duplicate records. We are currently working on a fix to resolve this.
This dataset contains minute by minute directional pedestrian counts for the last hour from pedestrian sensor devices located across the city. The data is updated every 15 minutes and can be used to determine variations in pedestrian activity throughout the day. The sensor_id column can be used to merge the data with the Sensor Locations dataset which details the location, status and directional readings of sensors. Any changes to sensor locations are important to consider when analysing and interpreting historical pedestrian counting data. Note this dataset may not contain a reading for every sensor for every minute as sensor devices only create a record when one or more pedestrians have passed underneath the sensor. The Pedestrian Counting System helps us to understand how people use different city locations at different times of day to better inform decision-making and plan for the future. 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 - Sensor Locations
This datasets shows historical pedestrian counting data in the park. The count is shown by region, with region 1 representing a 20 meters radius around the sensor, region 2 a 25 meters radius and region 3 a 30 meters radius.
Attribution-NonCommercial 4.0 (CC BY-NC 4.0)https://creativecommons.org/licenses/by-nc/4.0/
License information was derived automatically
This data shows traffic volumes for freeways
(excluding toll roads) and arterial roads in Victoria. The annual average daily
traffic volume is provided, including the number of commercial vehicles. The
data provided is for the current year, with values derived from traffic surveys
or estimates.
About this dataset
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This data shows traffic volumes for freeways\r
(excluding toll roads) and arterial roads in Victoria. The annual average daily\r
traffic volume is provided, including the number of commercial vehicles. The\r
data provided is for the current year, with values derived from traffic surveys\r
or estimates.
\r
About this dataset\r
\r
Data Currency Update - The Department of Transport and Planning apologises for the ongoing delay to the update of this valuable open dataset. We are actively working towards getting more up-to-date information into the public domain again and are committed to ensure the quality of the data is suitable to support the many use cases that we hear from the Open Data community. We appreciate your patience and ask that you bear with us as we work hard to rectify this issue.
Attribution 4.0 (CC BY 4.0)https://creativecommons.org/licenses/by/4.0/
License information was derived automatically
This dataset contains observed bike counts from sites across the city. These counts are often referred to "Super Tuesday" and is Australia’s biggest annual commuter bike count. The count also contains information for gender, and movement flow of people on bikes.
There is a large number of fields captured for this dataset, which has been compiled into an attached metadata document.
This GIS dataset contains traffic survey findings within the City of Casey. Information collected includes survey point locations, traffic volume counts, 85th percentile average speeds measurements, commercial vehicle proportions, and peak period usage levels.
Not seeing a result you expected?
Learn how you can add new datasets to our index.
This dataset contains hourly pedestrian counts since 2009 from pedestrian sensor devices located across the city. The data is updated on a monthly basis and can be used to determine variations in pedestrian activity throughout the day.The sensor_id column can be used to merge the data with the Pedestrian Counting System - Sensor Locations dataset which details the location, status and directional readings of sensors. Any changes to sensor locations are important to consider when analysing and interpreting pedestrian counts over time.Importants notes about this dataset:• Where no pedestrians have passed underneath a sensor during an hour, a count of zero will be shown for the sensor for that hour.• Directional readings are not included, though we hope to make this available later in the year. Directional readings are provided in the Pedestrian Counting System – Past Hour (counts per minute) dataset.The Pedestrian Counting System helps to understand how people use different city locations at different times of day to better inform decision-making and plan for the future. 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 – Past Hour (counts per minute)Pedestrian Counting System - Sensor Locations