AndreaBozzo/ceres-open-data-index huggingface dataset:
Bicycle Network

This dataset contains a simplified network representation of bike paths across City of Melbourne. The dataset can be used to create a digital bicycle network with route modelling capabilities that integrated existing bicycle infrastructure. The network has been created to be used with ArcGIS network analyst. The resulting network was connected to the City of Melbourne property layer through centroids created for this project: The network can assist in multiple modelling tasks including catchment analysis and route analysis. The download is a zip file containing compressed .json files Please see the metadata attached for further information.
Microclimate Sensor Locations - Historical

Note: these sensors are removed and new microclimate sensors are installed in the City. Please check https://data.melbourne.vic.gov.au/explore/dataset/microclimate-sensors-data/table/ This dataset contains the historical location and location description for each microclimate sensor device installed throughout the city. Each microclimate sensor device will have several climate sensors embedded inside. Sensor devices are typically installed on a street pole and locations are selected based on relevant project criteria. Since the beginning of the Microclimate Sensor Readings dataset in 2019, some sensor devices have been relocated. This may be for various reasons such as construction works or re-assignment to new climate projects. 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). Site_id refers to the location of the unique sensor device which may have changed over time. Related datasets: [Microclimate Sensor - Sensor Readings]
Development Activity Model Footprints

This dataset contains spatial information about development activity located within the City of Melbourne municipal area. Developments may have one of four statuses. Applied, Approved and Under Construction, and Complete. Site content is derived from a range of sources at various times and as such the content may not be free from errors, omissions or defects. Inconsistencies may occur in some data sets. The City of Melbourne uses its best endeavours to ensure that the information is reliable. The development polygons are representational only and are not intended for analytical or comparative purposes. The polygons are simplified polygons of an indicative floor plate for the podium (if relevant) and tower. The height data is an approximation of the height of the building and does not show the architectural features of the buildings. Further information is provided in the attached pdf document below. This is provided to help users understand the currency and reliability of the site content which often involves complex processes to derive the information. The aim is to provide users with facts about the source of the content and when it was collected. Users can then make an informed decision as to whether the site content is appropriate for their particular purpose and information needs. Although all due care has been taken to ensure that this data is correct, no warranty is expressed or implied by City of Melbourne in its use. Please note we are aware of update issues and are currently investigating.
City of Melbourne 3D Point Cloud 2018

[3D point cloud] representing all physical features (e.g. buildings, trees and terrain) across City of Melbourne. The data has been encoded into a .las file format containing geospatial coordinates and RGB values for each point. The download is a zip file containing compressed .las files for tiles across the city area. The geospatial data has been captured in Map Grid of Australia (MGA) Zone 55 projection and is reflected in the xyz coordinates within each .las file. Also included are RGB (Red, Green, Blue) attributes to indicate the colour of each point. Capture Information - Capture Date: May 2018 - Capture Pixel Size: 7.5cm ground sample distance - Map Projection: MGA Zone 55 (MGA55) - Vertical Datum: Australian Height Datum (AHD) - Spatial Accuracy (XYZ): Supplied survey control used for control (Madigan Surveying) – 25 cm absolute accuracy Limitations: Whilst every effort is made to provide the data as accurate as possible, the content may not be free from errors, omissions or defects. Sample Data: For an interactive sample of the data please see the link below. [https://cityofmelbourne.maps.arcgis.com/apps/webappviewer3d/index.html?id=b3dc1147ceda46ffb8229117a2dac56d] Preview: Download: A zip file containing the .las files representing tiles of point cloud data across City of Melbourne area. [Download] Point Cloud Data (4GB)
Pedestrian Network

This dataset contains a line network representing pedestrian walking routes throughout the City of Melbourne. It features links to additional land subdivisions and incorporates additional elements/attributes. The network has been created with the intent to assist interested stakeholder in multiple modelling tasks including catchment analysis and route analysis. The network emulates pedestrian behaviour, by allowing free movement in low traffic areas while penalising busy crossings with traffic lights. The network also connects to the City of Melbourne property layer through property centroids and connectors for all the different properties in the dataset. The download is a zip file containing compressed .json files. Please see the metadata attached for further information.
Pedestrian Counting System - Past Hour (counts per minute)

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]
Pedestrian Counting System - Sensor Locations

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)]
On-street Car Park Bay Restrictions

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.
On-street Car Parking Sensor Data - 2012

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. Download: [Download] compressed CSV (1.51GB, 52.5 million rows)
On-street Parking Bays

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
City of Melbourne Municipal Greenhouse Gas Emissions 2013-2020

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.
Tertiary Students Profile 2019

Contains rounded student numbers for 2016-2019. Refer to links below for data quality statements. Data obtained on request from: 1. Australian Government Department of Education, Skills and Employment - Higher Education Student Data (current at December 2020); and 2. National Centre for Vocational Education Research - Total VET Students and Courses (current at March 2021). Higher education data is based on student attendance at campus locations in Victoria and Melbourne LGA. More information: [here]. NCVER data is based on student attendance at campus locations in Victoria and Melbourne LGA. The sum of students may not add to the total as students may have attended multiple campus locations in a calendar year. More information: [here].
Indicators of quality of life and city services by year

The World Council on City Data (WCCD) awarded the City of Melbourne a platinum designation for its compliance with ISO 37120 (http://www.iso.org/iso/catalogue_detail?csnumber=62436), the world’s first international standard for city indicators. Reporting to the standard allows cities to compare their service delivery and quality of life to other cities globally. The City of Melbourne was one on 20 cities to, globally to help pilot this program and is one of sixteen cities to receive the highest level of accreditation (platinum). Having an international standard methodology to measure city performance allows the City of Melbourne to share data about practices in service delivery, learn from other global cities, rank its results relative to those cities, and address common challenges through more informed decision making. Indicators include: Fire and emergency response; Governance; Health; Recreation; Safety; Shelter; Solid Waste; Telecommunications and Innovation; Transportation; Urban Planning; Wastewater; Water and Sanitation; Economy; Education; Energy; Environment; and Finance. City of Melbourne also submitted an application for accreditation, on behalf of ‘Greater Melbourne’, to the World Council on City Data and this resulted in an ‘Aspirational’ accreditation awarded to wider Melbourne. A summary of Melbourne's results is available here (http://open.dataforcities.org/). Visit the World Council on City Data’s Open Data Portal to compare our results to other cities from around the world.
Café, restaurant, bistro seats

Data collected as part of the City of Melbourne's Census of Land Use and Employment (CLUE). The data covers the period 2002-2024. It show business establishments with their trading name, business address, industry (ANZSIC4) classification, number of dining seats (classified by indoor/outdoor), location and CLUE block and small area designation. For more information about CLUE see [http://www.melbourne.vic.gov.au/clue]
Tree planting zone schedules, with years (Urban Forest)

Under the Urban Forest Strategy, there are ten Precinct Plans that provide detailed information about how planting will occur in local streets to meet the objectives of the strategy. A planting schedule for streets in each precinct has been developed in consultation with the community and is based on: - Community priorities - Location and density of vulnerable residents - Opportunities for new planting - Hot and very hot streets, as shown in thermal imaging - Useful Life Expectancy of existing trees - Existing canopy cover This dataset shows the anticipated timeframe for tree planting in each street across the City of Melbourne. This timing is provisional and subject to change. The schedule for some streets may be moved forward or delayed by capital works, developments or renewal projects that impact on tree planting or survival. To learn more about the Urban Forest Strategy and Precinct Plans, visit http://www.melbourne.vic.gov.au/sustainability/urbanforest/pages/urbanforest.aspx
Garbage collection zones

Polygon data of Garbage Collection Zones for the City of Melbourne. Includes waste and recycling, with date, repeat and interval in ISO8601. Data was created following the [Open Council Data Standards]. Data field metadata can be found here: http://standards.opencouncildata.org/#/garbage-collection-zones. Although all due care has been taken to ensure that these data are correct, no warranty is expressed or implied by the City of Melbourne in their use.
Residential dwellings

Data collected as part of the City of Melbourne's Census of Land Use and Employment (CLUE). The data covers the period 2002-2024. The dwelling data is based on the Council's property rates database, using a simplified classification schema of Residential Apartment, House/Townhouse and Student Apartment. The count of dwellings per residential building is shown. For more information about CLUE see [http://www.melbourne.vic.gov.au/clue]
Floor space per ANZSIC for blocks

Data collected as part of the City of Melbourne's Census of Land Use and Employment (CLUE). The data covers the period 2002-2024. It shows floor space (in square meters) per city (CLUE) block, classified by their ANZSIC1 industry and small area allocation. The City of Melbourne creates unique codes to account for floor space allocated to residential space, vacant space, open space and common area. These unique codes are not included within ANZSIC 1 classification and therefore these floor areas are not included in this data set. This dataset has been confidentialised to protect the commercially sensitive information of individual businesses. Data in cells which pertain to two or fewer businesses have been suppressed and are shown as a blank cell. The row totals refer to the true total, including those suppressed cells. To see column total values for the entire municipality, please refer to the 'Floor space per CLUE industry in municipality' dataset. Non-confidentialised data may be made available subject to a data supply agreement. For more information contact cityfacts@melbourne.vic.gov.au For CLUE block spatial files see [Blocks for Census of Land Use and Employment (CLUE) — CoM Open Data Portal] For more information about CLUE see [http://www.melbourne.vic.gov.au/clue] For more information about the ANZSIC industry classification system see [http://www.abs.gov.au/ausstats/abs@.nsf/mf/1292.0]
Business establishments per ANZSIC for blocks

Data collected as part of the City of Melbourne's Census of Land Use and Employment (CLUE). The data covers the period 2002-24. It shows the number of business establishments per city (CLUE) block, classified by their ANZSIC1 industry and small area allocation. To see total values for the entire City of Melbourne municipality please refer to the 'Business establishments per ANZSIC in municipality' dataset. A business establishment is defined as a • Commercial occupant in a building • Separate land use • Any permanent presence of economic activity in accordance with standard Industry classification (ANZSIC). Hence, if one organisation has its presence in several buildings in the CLUE area, each time it will be counted as a separate establishment. Consequently, the count of establishments presented in CLUE represents the number of locations, rather than 'enterprises'. For more information about CLUE see [http://www.melbourne.vic.gov.au/clue] For more information about the ANZSIC industry classification system see [http://www.abs.gov.au/ausstats/abs@.nsf/mf/1292.0]
Floor space per space use for blocks

Data collected as part of the City of Melbourne's Census of Land Use and Employment (CLUE). The data covers the period 2002-2024. It shows floor space (in square metres) per city (CLUE) block, classified by their space use and small area allocation. This dataset has been confidentialised to protect the commercially sensitive information of individual businesses. Data in cells which pertain to two or fewer businesses have been suppressed and are shown as a blank cell. The row totals refer to the true total, including those suppressed cells. To see column total values for the entire municipality, please refer to the 'Floor space per space use in municipality' dataset. Non-confidentialised data may be made available subject to a data supply agreement. For more information contact cityfacts@melbourne.vic.gov.au For CLUE block spatial files see [https://data.melbourne.vic.gov.au/explore/dataset/blocks-for-census-of-land-use-and-employment-clue/information/] For space use definitions see [Census of Land Use and Employment - Definitions] For more information about CLUE see [http://www.melbourne.vic.gov.au/clue]