The City of Melbourne Social Indicators Survey (CoMSIS) was conducted for the first time in 2018. The survey collects data, annually, about the state of health, well-being, participation and connection of communities in the Melbourne Local Government Area, primarily to report on key Council Plan 2017-21 municipal outcome indicators.
This dataset provides indicator results for 1,212 residents surveyed via telephone and online. Data has been provided by suburb, gender and age groups and has been weighted according to population proportions. Responses such as don't know, not sure, not applicable etc. were excluded in the calculation of indicators. The sample sizes shown reflect this accordingly.

The City of Melbourne Social Indicators Survey (CoMSIS) was conducted for the first time in 2018. The survey collects data, annually, about the state of health, well-being, participation and connection of communities in the Melbourne Local Government Area, primarily to report on key Council Plan 2017-21 municipal outcome indicators.
This dataset provides indicator results for 1,212 residents surveyed via telephone and online. Data has been provided by suburb, gender and age groups and has been weighted according to population proportions. Responses such as don't know, not sure, not applicable etc. were excluded in the calculation of indicators. The sample sizes shown reflect this accordingly.

This dataset contains the Greenhouse Gas Emissions (GHG) from activities taking place within the geographic boundary of the City of Melbourne Local Government Area.

The City of Melbourne uses the Global Protocol for communities (GPC) method to measure and report municipal greenhouse emissions. Emissions are reported annually through the Carbon Disclosure Project (CDP) platform, which is a requirement of Global Covenant of Mayors and C40 membership.

Emission sources are broken down across the sectors: Stationary energy, Transportation and Waste. They are categorized by their "scope" which distinguishes between emissions that physically occur within the city (scope 1), from those that occur from the use of electricity and supplied by grids potentially crossing city boundaries (scope 2), from those that occur outside the city but are driven by activities taking place within the city’s boundaries (scope 3). All GHG emissions are presented in units of metric tonnes CO2 equivalent (tCO2e).

In cases where there are limitations on data availability notation keys have been used. NO indicates that an activity or process does not occur or exist within the city. IE signifies GHG emissions for this activity are presented in another category of the inventory. NE is used when emissions occur but have not been estimated or reported due to unavailability of data.

Preparing and reporting this data helps us to understand where the city's emissions come from. It allows us to plan our emission reduction activities to take effective action to mitigate climate change.

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).

Related datasets:
Microclimate Sensor - Sensor Readings

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.

Related datasets:
Microclimate Sensor - Sensor Locations

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. An event will include if a vehicle was present or not which can determine stay time and vacancy time.

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.

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. An event will include if a vehicle was present or not which can determine stay time and vacancy 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 period of Jan 1st 2020 to May 2020. This dataset was released to support customer requests to understand the impact of Covid-19 on city movement.

This dataset contains the locations of where soil sensors have been deployed across the city. The readings are stored in the soil sensor readings dataset. The sensors take a variety of readings such as salinity, temperature and moisture. The units and readings are included within the readings dataset. The dataset joins to the soil sensor readings dataset by matching the site_id column.