42 Results filtered by...
Filter
Skip to the results
Back
Clear All
Tags > accessibility

Sort

Sort by Recently Added

Filter

Categories

View Types

Tags

Show All...
Filter
42 Results filtered by
Tags > accessibility Clear All

People & 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.
Tags safemobility accessibility transport bookings activity and 3 more
API Docs
Created
February 18 2019
Views
1,225

Transport & Movement
Dataset
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.
Tags sensors accessibility travel transport parking
API Docs
Created
July 4 2018
Views
3,540

Transport & Movement
Map
This data contains locations of train stations and their accessibility information, such as hearing aid information.
Tags safemobility transport innovation pids accessibility and 4 more
Created
February 12 2018
Views
2,176

Assets & Infrastructure
Dataset
This dataset contains tactile ground surface indicators(TGSI) that are located within the central business district of the City of Melbourne.
TGSI are used to help vision impaired people navigate the urban environment to avoid hazards.
Tags assets walking footpath wayfinding accessibility
API Docs
Created
January 16 2018
Views
563

Assets & Infrastructure
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 assets accessibility panel sign
API Docs
Created
January 2 2018
Views
682

Property & Planning
Dataset
This public register of building permits lists all building permits for building works issued by Melbourne Certification Group, in and outside of the City of Melbourne, and also any building works issued by Private Building Surveyors within the City of Melbourne.
​The information provided is extracted from the records held by City of Melbourne.
For a definition of the building classification type please see the attachment.
Tags accessibility planning permits building
API Docs
Created
December 29 2017
Views
5,125

Finance & Operations
Dataset
This dataset contains service requests received from external customers. This data is collected through the council's Salesforce system. It contains information about the service type, status, and dates for received and closed. This dataset only contains a subset of the received requests as it is extracted from one of several customer requests systems.
Tags accessibility work customers requests assets and 2 more
API Docs
Created
December 29 2017
Views
629

Transport & Movement
Dataset
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 2016 calendar year.
Known data issues:
1. There are 342,475 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 2016 car parking event data there are 4,346 records where the parking event goes into 2017 and ends at midnight.
Tags sensors accessibility travel transport parking
API Docs
Created
December 20 2017
Views
1,414

Transport & Movement
Dataset
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.
Tags sensors accessibility travel transport parking
API Docs
Created
December 20 2017
Views
353

Transport & Movement
Dataset
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.
Tags sensors accessibility travel transport parking
API Docs
Created
December 20 2017
Views
362
Showing 1-10 of 42 results