221 Results
Filter
Skip to the results
Back
Clear All

Sort

Sort by Recently Updated

Filter

Categories

View Types

Tags

Show All...

Transport
Dataset
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 parking sensor near real-time vacancy transport and 5 more
API Docs
Updated
February 23 2021
Views
31,060

Transport
Dataset
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

Tags pedestrian sensors foot traffic traffic flow safemobility
API Docs
Updated
February 23 2021
Views
6,716

Environment
Dataset
This dataset contains historical readings for soil sensors within parks across the City of Melbourne. The sensors take a variety of readings such as salinity, temperature and moisture. The units and readings are included within the data. This dataset can be joined to the soil sensor locations dataset using the site id column. This dataset contains a large number of records, to download only a particular sensor's readings see our attached guide on how to filter data.
Different readings taken (based on unit column):
- %VWC: Volumetric water content is a numerical measure of soil moisture. It is simply the ratio of water volume to soil volume.
- ºC: Temperature in degrees celsius.
- µS/cm: Salinity is the measure of the concentration of dissolved (soluble) salts in water from all sources. (microseimens per centimetre)
Note this dataset may not contain a reading for every sensor for every hour as the sensor devices might not have a reading for each value. There may be situations where no readings are reported for all sensors or only some readings are reported at a particular site.
Tags soil sensor moisture salinity temperature and 1 more
API Docs
Updated
February 23 2021
Views
176

Environment
Dataset
This dataset contains location and location description for each set of microclimate sensor device installed throughout the city. Sensors are typically installed on a street pole and locations are selected based on relevant project criteria.
Since the beginning of the Microclimate Sensor Readings in 2019, some sensor devices have been relocated. This may be for various reasons such as construction works. Any changes to sensor locations are important to consider when analysing and interpreting historical data.
The site_id column can be used to merge the data with related dataset (linked below).
Tags climate environment air quality sensor environmental monitoring and 7 more
API Docs
Updated
February 23 2021
Views
838

Environment
Dataset
This dataset contains environmental readings from microclimate sensors located across the city. The data is updated every hour in fifteen minute increments and can be used to determine variations in microclimate changes throughout the day. Microclimate data includes:
- Ambient air temperature
- Relative humidity
- Barometric pressure
- Particulate matter 2.5
- Particulate matter 10
- Average wind speed
The Microclimate Sensor Readings helps us to understand temperature, relative humidity, pressure, particulate matter 2.5, particulate matter 10, and average wind speed at different locations and different times of day to better inform decision-making and plan for the future.
Additional values are included in this dataset to provide an easier way to correlate the data with the official EPA Victoria data. These can be identified with the value 'epa' included in the type column. EPA Victoria report air quality readings in 1 hour and 24 hour averages . This includes; ambient air temperature readings in 1 hour average, relative humidity readings in 1 hour average, particulate matter 2.5 readings in 1 hour and 24 hour averages, and particulate matter 10 readings in 1 hour and 24 hour averages.
The site_id column can be used to merge the data with the Sensor Locations dataset which contain the sensor location. Any changes to sensor locations are important to consider when analysing and interpreting historical microclimate data.
Note this dataset may not contain a reading for every sensor for every 15 minutes as the sensor devices might not have a reading for each value. There may be situations where no readings are reported for all sensors or only some readings are reported at a particular site.
For the description of each sensor please see the sensor type attachment.
Tags sensor microclimate environment air quality environmental monitoring and 5 more
API Docs
Updated
February 23 2021
Views
1,700

City Council
Dataset
This dataset contains all the non parking sign panels, such as Stop signs, wayfinding, speed restrictions within the City of Melbourne. A sign panel is the part of the sign that display the information.
This dataset also contains information regarding disabled access, as referenced in the data by the use of DDA acronym.
Tags sign panel accessibility assets
API Docs
Updated
February 22 2021
Views
930

Events
Dataset
This dataset contains active and planned activities across the City of Melbourne area. Activities include city works (such as proposed road closures, footpath works or reserved parking permits) and event bookings. The information is derived from permits which are issued by City of Melbourne.
Each activity includes geo-spatial information to indicate the general area of the activity. The spatial information is not indicative of the activity size as the activity may only take up a small portion of the area for the entry.
The start and end date fields indicate that the event/activity is expected to occur within this time range. The actual activity may be active for significantly shorter duration than the start and end dates.
Additional column value information can be found in the attachment (.xlsx) below.
Tags disruption events activities activity bookings and 3 more
API Docs
Updated
February 22 2021
Views
2,042

Transport
Dataset
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)

Tags pedestrian sensors foot traffic traffic flow locations and 3 more
API Docs
Updated
February 22 2021
Views
5,658

Transport
Map
This dataset shows all of the streets and laneways within the City of Melbourne. This dataset is used in order for people to create their own map of the city and can be used to label the streets with their names down the centre of the road as is the standard for labelling streets on maps.
Tags roads names safemobility accessibility streets
Updated
February 22 2021
Views
3,543

Property
Map
Contains the location information (latitude and Longitude, Northing and Easting) of every property address within the City of Melbourne
Tags property safe mobility addresses street
Updated
February 22 2021
Views
9,690