These are lightweight standards for Australian councils publishing open data. This is an open collaboration between councils, Open Knowledge Australia, MAV Technology, the Local Government Spatial Reference Group and other interested participants.

Steve Bennett (Open Knowledge) and Will McIntosh (City of Melbourne) chair the group.

Why

To allow datasets from different councils to be easily joined up into something bigger, to support research, app development, knowledge exchange between councils, and use by the public.

See the number of datasets already published by councils on the Open Council Data Map.

Principles

We try to make conforming to the standard as easy as possible.

  1. As few required fields as possible.
  2. These are interoperability standards are for transforming already-collected data only.
  3. Match common field names as much as possible.
  4. Field names must be 10 characters or fewer, due to Shapefile attribute limitations.

General guidelines

For more advice, including licensing, please see the Open Council Data Toolkit.

Participate

These standards are maintained in a Github repository that anyone can contribute to.

You can help create and refine these standards by:

Councillors

Councillors 0.1

Councillors are the elected representatives of the council, usually representing a specific ward (area). The spreadsheet can include just the current elected councillors, or previous councillors too.

General recommendations

  Recommendation
Format CSV, RSS
Dataset name [Council name] councillors
data.gov.au tags opencouncildata, councillors, elections

Required fields

Field Description
name Name of the councillor. Do not include “Cr” or “Councillor” prefix.
Field Description
title The title of the councillor, such as “Lord Mayor”, “Deputy Mayor”, or “Councillor”.
ward_name Name of the ward the councillor represents.
ward_id External ID of the ward. In Victoria, this should be the VicMap WARD_NUM (eg, Glenferrie is 50704)

Optional fields

Field Description
term_start Date the member’s term began.
term_end Date the member’s term ends/ended. For currently serving councillors, this can be ommitted or be the date of the next election.
portfolio The portfolio held by the councillor, if any. Multiple portfolios should be separated by semicolons.
phone_office Office phone number.
phone_mobile Mobile phone number.
email Email address.
url URL to page with more information about the councillor.
image_url URL to image of the councillor.

Financial report

Financial report 0.1 (draft for comment)

(Comments welcome!)

A financial report is a collection of spreadsheets put out each year by a council reporting on its financial activities over the previous financial year. It includes a balance sheet, income and expenditure statements, capital works programme and so on.

Several states have standard (Microsoft Excel based) formats in which these reports are written and submitted to a central authority. The OpenCouncilData standard given here is a machine-readable (CSV) format that closely mirrors the Victorian Local Government Model Financial Report. Councils in other states should follow a similar process for their state’s model financial report, if it exists.

Each of the different components of the report (balance sheet, capital works programme etc) should be published as a separate CSV file. We recommend publishing them all as resources (files) within a single dataset (CKAN package), for open data platforms that support that kind of structure.

Important: unlike the Excel-based format, CSV files should not include any subtotals such as “Total income” or “Total non-current assets”.

CSVs are grouped such that all the numeric values within one file have the same “direction”, and can thus be meaningfully summed. For example, liabilities must be subtracted from assets, so they are in a separate file.

  • All values should be in thousands of dollars. (That is, 300 means $300,000)
  • Do not include $ signs or commas.
  • Remember that category names containing commas must be enclosed in double quotes: "Plant, machinery and equipment"

Balance sheet - assets

This is the template to be followed, with a sample value of $1,234,000 for the first item. 2016 should be replaced with the current year, and 1234 represents the actual value that would be included (in thousands of dollars). Multiple years can be included as additional columns.

Category, Item, 2016
Current assets,Cash and cash equivalents,1234
Current assets,Trade and other receivables
Current assets,Other financial assets
Current assets,Inventories
Current assets,Non-current assets classified as held for sale
Current assets,Other assets
Non-current assets,Trade and other receivables
Non-current assets,Investments in associates and joint ventures
Non-current assets,"Property, infrastructure, plant and equipment"
Non-current assets,Investment property
Non-current assets,Intangible assets

Balance sheet - liabilities

Category, Item, 2016
Current liabilities, Trade and other payables
Current liabilities, Trust funds and deposits
Current liabilities, Provisions
Current liabilities, Interest-bearing loans and borrowings
Non-current liabilities, Provisions
Non-current liabilities, Interest-bearing loans and borrowings

Balance sheet - equity

Category, Item, 2016,
Equity, Accumulated surplus
Equity, Reserves

Statement of Capital works

Category, Item,2016
Property,Land
Property,Land improvements
Property,Buildings
Property,Heritage Buildings
Property,Building improvements
Property,Leasehold improvements
Plant and equipment,Heritage plant and equipment
Plant and equipment,"Plant, machinery and equipment"
Plant and equipment,"Fixtures, fittings and furniture"
Plant and equipment,Computers and telecommunications
Plant and equipment,Library books
Infrastructure,Roads
Infrastructure,Bridges
Infrastructure,Footpaths and cycleways
Infrastructure,Drainage
Infrastructure,"Recreational, leisure and community facilities"
Infrastructure,Waste management
Infrastructure,"Parks, open space and streetscapes"
Infrastructure,Aerodromes
Infrastructure,Off street car parks
Infrastructure,Other infrastructure

Statement of Capital Works - summary

Category, Item,2016
Represented by,New asset expenditure
Represented by,Asset renewal expenditure
Represented by,Asset expansion expenditure
Represented by,Asset upgrade expenditure

Comprehensive Income Statement – income

Category, Item, 2016
Income,Rates and charges
Income,Statutory fees and fines
Income,User fees
Income,Grants - operating
Income,Grants - capital
Income,Contributions - monetary
Income,Contributions - non monetary
Income,"Net gain (or loss) on disposal of property, infrastructure, plant and equipment"
Income,Fair value adjustments for investment property
Income,Share of net profits (or loss) of associates and joint ventures 
Income,Other income

Comprehensive Income Statement – expenses

Category, Item, 2016
Expenses, Employee costs
Expenses, Materials and services
Expenses, Bad and doubtful debts
Expenses, Depreciation and amortisation
Expenses, Borrowing costs
Expenses, Other expenses

Statement of Cash Flows

Category, Item, 2016
Cash flows from operating activities,Rates and charges
Cash flows from operating activities,Statutory fees and fines
Cash flows from operating activities,User fees
Cash flows from operating activities,Grants - operating
Cash flows from operating activities,Grants - capital
Cash flows from operating activities,Contributions - monetary
Cash flows from operating activities,Interest received
Cash flows from operating activities,Dividends received
Cash flows from operating activities,Trust funds and deposits taken
Cash flows from operating activities,Other receipts  
Cash flows from operating activities,Net GST refund/payment
Cash flows from operating activities,Employee costs
Cash flows from operating activities,Materials and services
Cash flows from operating activities,Trust funds and deposits repaid
Cash flows from operating activities,Other payments
Cash flows from investing activities,"Payments for property, infrastructure, plant and equipment"
Cash flows from investing activities,"Proceeds from sale of property, infrastructure, plant and equipment"
Cash flows from investing activities,Payments for investments
Cash flows from investing activities,Proceeds from sale of investments
Cash flows from investing activities,Loans and advances made
Cash flows from investing activities,Payments of loans and advances
Cash flows from financing activities,Finance costs
Cash flows from financing activities,Proceeds from borrowings
Cash flows from financing activities,Repayment of borrowings
Cash flows from financing activities,Net increase (decrease) in cash and cash equivalents
Cash flows from financing activities,Cash and cash equivalents at the beginning of the financial year

Statement of Changes in Equity

Additional years can be included as extra rows.

Year,Item,Total,Accumulated Surplus,Revaluation Reserve,Other Reserves
2016,Balance at beginning of the financial year
2016,Surplus/(deficit) for the year
2016,Net asset revaluation increment/(decrement)
2016,Transfers to other reserves 
2016,Transfers from other reserves

Parks and open spaces

Parks and open spaces 0.1

(Comments welcome!)

Parks, open spaces, recreation areas with attributes describing whether facilities such as picnic areas, barbecues, toilets and dog-off-leash areas are present.

Councils are encouraged to also provide distinct datasets for public toilets, dog walking zones, footpaths, and street furniture with exact locations. See the relevant standards.

Find datasets tagged [parks] on data.gov.au

General recommendations:

  Recommendation
Format GeoJSON in EPSG:4326
Dataset name [Council name] Parks and open spaces. [Or “Parks and” a term used by your council]
data.gov.au tags parks, opencouncildata
Spatial type Polygon and/or point. (A point dataset can be useful for non-GIS data users.) It may be useful to split larger parks into smaller polygons to make the attributes more localised.

Required fields

Field Description
name Name of the park.
Field Description
amenities Comma-separated list of keywords from this list: bbq, picnic table, toilets, oval, dog off-leash, drink tap, parking, playground. Invent new keywords if required - please provide feedback.
description Free text description.
url URL with more information.
image URL of representative image.
address Street address.

Venues for hire

Venues for Hire 0.2 (draft for comment)

(Comments welcome!)

Venues for hire are spaces that can be hired by members of the public to run private events. Typically they include town halls, community halls, auditoriums, meeting rooms, sports facilities and outdoor spaces.

Find datasets tagged [venues] on data.gov.au

General recommendations:

  Recommendation
Format Point data. CSV (preferred), GeoJSON
Dataset name [Council name] venues for hire
data.gov.au tag venues, opencouncildata

Required fields

Field Description
lat, lon Latitude, longitude, decimal degrees. (EPSG:4326)
name Name of the venue, which should be unique. For example, “Glenroy Community Hall”
type One of: hall, community centre, function room, meeting room, auditorium, gallery, sports, outdoor, building (for whole buildings that don’t fit other categories), or use your own if needed.
Field Description
address Street address.
capacity The number of people the space holds.
accessible yes if accessible for wheelchair users, no if not.
access Free text description of accessibility. For example, “Wheelchair lift at front entrance, and accessible toilets.”
image URL of one image of the venue.
url URL of a page with more information about the venue.
description Free text description of the venue.
fee_desc Free text description of fees charged. (Generally these are complex and have parameters such as time of day, day of week, concessions available etc.)
facilities Comma-separated list of keywords representing facilities available at the venue: kitchen, wi-fi, projector, stage, chairs, tables, speakers, microphone, video recording

Optional fields

Field Description
notes Free text description of any special notes related to hiring. For example, “All functions must finish by 10pm Sunday to Thursday or by 11pm Fridays and Saturdays.”
alcohol One of sold (there is a bar which sells alcohol), no (alcohol must not be brought to the venue), allowed (hirers may provide alcohol - include any restrictions in notes field)
phone Phone number to call for more information about the venue.
email Email address for more information about the venue.
form_url URL for booking this venue, either with online form or PDF.
dimensions Free text field for the dimensions of the venue. For example: “14m by 14m, with 6m by 3m stage”.
ref The internal council ID for the venue, if any.

Facilities

Childcare Centres 0.1 (draft for comment)

(Comments welcome!)

“Facilities” are a broad range of services and amenities provided by the council which generally meet three criteria: - they are in a specific building - they are accessible by certain members of the public, at least sometimes - they generally involve interaction with staff.

The range of services provided varies greatly across the country. It would be very difficult to define a precise vocabulary which every council agrees on, so if none the proposed types fits your need, please use another, and please open an issue or start a discussion to suggest it.

Find datasets tagged [facilities] on data.gov.au

General recommendations:

  Recommendation
Format Point data. CSV (preferred), GeoJSON
Dataset name [Council name] services and facilities
data.gov.au tag facilities, opencouncildata

Required fields

Field Description
lat, lon Latitude, longitude, decimal degrees. (EPSG:4326)
name Name of the facility. Each should be unique if at all possible.
type Primary classification, from the list above.

Types: library, aged care, neighbourhood house, health clinic, medical service, food service, place of worship, childcare, kindergarten, swimming pool, gym

Field Description
owned_by The council name, or other organisation, that owns the facility.
managed_by The council name, or other organisation, that manages the facility.
contact_ph The facility’s telephone number.
url A URL with more information about the facility.
subtype A subclassification according to the council’s needs. (No defined list of these at present.)
address Street address. E.g. “274 Gower Street, Preston, VIC 3072”
access Free text description of accessibility. For example: “Fully accessible to wheelchair users; disabled parking at front.”
monday, tuesday, wednesday, thursday, friday, saturday, sunday Normal opening hours on each day, in 24 hour HH:MM-HH:MM format. For example: 08:00-17:30.
holiday Normal opening hours on public holidays.

Optional fields

Field Description
type2 If a facility fits equally into several categories (for example, a childcare centre is also a kindergarten), add the extra type here. If there are two distinct services housed together (for example, a childcare centre and a maternal health clinic), it’s better to have two distinct entries with slightly different locations.
ref The internal council ID for the facility, if any.

Animal registrations

Animal registrations 0.2

(Comments welcome!)

Registrations of animals (usually cats and dogs).

This may be a spatial dataset if it includes the location of the property where the animal is registered, or it may be non-spatial.

It is up to the council to decide whether to include data with privacy considerations such as location. This standard makes no recommendation on that issue.

General recommendations:

  Recommendation
Format CSV, also optionally GeoJSON if location data included.
Dataset name [Council name] animal registrations
data.gov.au tag animal-registrations, opencouncildata, ocd-animal-registrations-0.2

Required fields

Field Description
name The registered name of the animal. If not known, it should be left blank. For example: Rex
type The kind of animal: dog, cat, etc.
Field Description
breed The breed of animal. Cross breeds can be indicated by as Poodle X. For example: Kelpie
colour A simple description of the animal’s colouring. Tri indicates three colours, usually black, tan and white. For example: Grey, Black and white
sex Male or female: M or F
desexed Whether the animal has been desexed (neutered). Y or N
ref The animal’s registration identifier.
microchip Whether the animal has been fitted with a microchip. Y or N

Optional fields

Field Description
lat, lon Latitude, longitude, decimal degrees of the property where the animal is registered. See the note in intro. (EPSG:4326)
suburb The suburb in which the animal is registered. For example: Inverleigh
postcode The postcode in which the animal is registered. For example: 4563
expiration The date on which the registration expires. A date in the past or a blank value, indicates that the animal is currently unregistered.
birth_year Year the animal was born.
tattoo Whether the animal has been tattooed, usually in the ear to indicate desexing. Y or N
deceased Whether the animal is deceased. Y or N
class A council-specific registration classification. This can include terms like Working dog, Pet, Pensioner.

3D buildings

3D buildings 0.2

A 3D model (not just outline plus height) of buildings and other physical features, used for planning, architecture and communicating proposed construction. Model files should be textured if possible.

A collection of 3D model files should be bundled with a point origin file, to correctly locate each 3D model file in real-world coordinates.

File Contents
origins.csv (1 file) one row per model, with latitude and longitude of the origin of that file
(modelname).3ds (1+ files) one file per model. Each model must be oriented with north (increasing latitude) along the positive Y axis, and east (increasing longitude) along the positive X axis.

In the fields below, “council ID” means the text string identifying the council, given by the part of the council’s website before “.vic.gov.au”. Hence, “melbourne”, “geelong”, “corangamite” etc.

General recommendations:

  Recommendation
Format Autodesk 3DS. (It has many limitations but is widely used and understood.) CityGML is another emerging possibility.
Dataset name [Council name] 3D Buildings
data.gov.au tag opencouncildata-3d-buildings-0.2

Required fields for origins.csv

Field Description
filename filename of the model referred to. For example: buildings.3ds
lat latitude of the origin (Y value 0), in decimal degrees. For example: -37.5
lon longitude of the origin (X value 0), in decimal degrees. For example: 144.5
elevation elevation of the origin (Z value 0) relative to sea level, in metres.
Field Description
status status of the physical building. One of: proposed (in the planning process, work not yet begun), construction, built (finished), demolished (demolition has commenced). If not provided, built is assumed.
desc text description of the building.
updated date of most recent update to this model file, in ISO 8601 format.
date_built date of expected or actual finishing of construction, in ISO 8601 format. For example: 2012-12-11
ref council-specific identifier for the model.

Optional fields

Field Description
src source of the model as a whole. One of: AAM (AAM Group), council ID, architect (provided by any architecture firm), or other value as appropriate.
textur_src source of texture imagery. One of: Pictometry, Earthmine, Graphical, None, or other value if appropriate.
geom_src source of geometry. One of: Pictometry (provided by Pictometry), architect (provided by any architecture firm), council ID (created by the council, such as the GIS team), or other value as appropriate.
date_demol date of expected or actual demolition, in ISO 8601 format, or blank if none.
file_url URL where model file can be downloaded. This should be a direct download link, not a landing page.
height height of building in metres. For example: 44.5
material primary external building material, one of: brick, wood, glass, concrete or other value as appropriate.
footprint council-specific ID of building footprint separately maintained by the council.
bldg_id council-specific ID for the building itself.
prop_id council-specific ID for the property housing the building.
plan_id planning application ID.
plan_auth planning body in which the plan_id applies.
version version of the model, in council-specific format.
suburb name of suburb building is within.

Fields under discussion

  • isPrimary
  • renderType: textured, color_layers
  • IsWFinding: Yes, No
  • ModelNorth: WGS84, Normal
  • Position: XYZ, Minimum Z, Normal
  • IsLOD: Yes, No
  • PlansDMRef
  • Easting
  • Northing

Wards

Wards 0.1

Administrative subdivisions of councils, particularly used for elections.

Find datasets tagged [wards] on data.gov.au

General recommendations:

  • Format: Polygon geospatial data. GeoJSON (preferred), Shapefile
  • Dataset name: [Council name] council wards
  • data.gov.au tag: opencouncildata-wards-0.1

Required fields

  • name: Name of the ward, eg “Buckley”.

Optional fields

  • councillor: The name of the councillor that currently represents the region.
  • portfolio: The portfolio held by the councillor, if any.
  • lga: The name of the council which this ward belongs to.

Trees

Trees 1.3

Trees registers contain locations and information about individual trees within the council boundaries. They usually include “street trees”, sometimes “park trees”, but rarely trees on private property or in bushland. Reasons for collecting the data including planning future growth or maintenance of canopy cover, and managing risk of falling branches.

OpenTrees.org shows council tree inventories already published.

Find datasets tagged [trees] on data.gov.au

General recommendations:

  Recommendation
Format CSV (preferred), Shapefile, GeoJSON
Dataset name [Council name] Street and Park Trees
data.gov.au tag trees, opencouncildata, ocd-trees-1.3

When information is available only as a range (eg, diameter is recorded as 100-150cm), the middle of the range should be presented as the field name, with an additional _min and _max. For example, dbh: 125, dbh_min: 100, dbh_max, 150.

If the information is only available as an unbounded range (eg, height greater than 5 metres), then do the same with no _max. For example, height: 5, height_min: 5.

Required fields:

Field Description
lat, lon Latitude, longitude, decimal degrees. (EPSG:4326)
Field Description
genus Botanical genus, in title case. eg: Eucalyptus
species Botanical genus, in title case. Leave blank if not known (not “Sp.”). eg: Regnans
dbh Diameter at breast height (130cm above ground), in centimetres. eg: 60. (See General recommendations for ranges.)
year_min Lower bound on year that tree is expected to live to. (That is, a tree surveyed in 2008 with useful life expectancy range of 10-15 years would be 2018).
year_max Upper bound on year that tree is expected to live to. (2023 in this example)

Optional fields:

Field Description
crown Width in metres of the tree’s foliage (also known as crown spread). eg: 6 (See General recommendations for ranges.)
height Height in metres. eg: 4. (See General recommendations for ranges.)
common Common name for species (non-standardised), in title case. eg: Myrtle Beech
location Where the tree is located: park, street, council
ref Council-specific identifier, enabling joining to other datasets. eg 9128
maintenance number of months, how often the tree is inspected. eg 24
maturity one of young, semi-mature, mature, over-mature
planted date of planting, in ISO8601. eg 1998-04-02
updated date of addition to database or most recent revision, in ISO8601. eg 2012-06-08
health Health of tree growth: one of stump, dead, poor,fair,good
structure Solidity of tree, unlikelihood of falling. One of failed, poor, fair, good
variety Any part of the scientific name below species level, including subspecies or variety.
description Other information about the tree that is not its scientific name or species.
family Botanical family.
dbh_min, dbh_max, height_min, height_max, crown_min, crown_max See General recommendations.
ule_min, ule_max Lower and upper bound on useful life expectancy, when surveyed, in years. eg: 15. See also year_max,year_min
address Street address.

Toilets

Toilets 1.2

Public toilets known about or operated by the council.

Find datasets tagged [toilets] on data.gov.au

General recommendations:

  Recommendation
Format CSV (preferred), GeoJSON, Shapefile,
Dataset name [Council name] Public Toilets
data.gov.au tag toilets, opencouncildata, ocd-toilets-1.2

Required fields

Field Description
lat, lon Latitude, longitude, decimal degrees of building centroid or entrance. (EPSG:4326)
Field Description
name A description that may help identify the facility (eg, “Smith Reserve Playground”)
female Whether toilets for women are available (yes,no). (Tag unisex toilets as yes)
male Whether toilets for men are available (yes, no). (Tag unisex toilets as yes)
wheelchair Whether toilets accessible by wheelchair users are available. (yes, no)
trsfr_side What side the transfer hand rail is located for the toilet to assist with getting up/down. (left, right)
week_open What time the toilets open on weekdays, in 0-padded 24 hour time. 00:00 for always open/closed.
week_close What time the toilets close on weekdays, in 0-padded 24 hour time. 24:00 for always open, 00:00 for always closed.
sat_open As above for Saturdays.
sat_close As above for Saturdays.
sun_open As above for Sundays.
sun_close As above for Sundays.

Optional fields

Field Description
comment Any additional comments, such as for opening hours that can’t be represented in the above scheme.
access_cmt Additional comments about accessibility, such as if the toilets are inside a building that is difficult to access.
needle_bin Whether a syringe disposal bin is present (yes/no).
operator The name of the organisation managing the toilet (eg, your council name, or a business name.)
drink_tap Whether water for drinking is available (yes/no)

Road closures

Road closures 0.2

(Comments welcome!)

Locations of planned and unplanned road closures due to events, maintenance, natural events or other reasons. For maximum usefulness, this dataset should be updated whenever new information is available (perhaps hourly). Past closures should be removed from the dataset within a short period (eg, 1 day) in order to keep the whole dataset size manageable.

General recommendations:

  Recommendation
Format GeoJSON in EPSG:4326
Dataset name [Council name] Road Closures
data.gov.au tags road-closures, opencouncildata, ocd-roadclosures-0.2
Spatial type Line data is preferred (representing each segment of road that is affected), but points (general location of closure) and polygon (region in which all roads are closed) are acceptable.

If possible, sort the data with most imminent closures first.

Required fields

Field Description
status The level of impact: closed (no movement), restricted (speed restrictions and possible lane closures), open (open, included if necessary to avoid doubt), detour (this line feature is a recommended detour around another closure)
start_date Date of start of closure, in ISO8601 format: 2015-06-04
start_time Time of start of closure, in ISO8601 local timezone format: 08:30+10 (preferred) or no timezone format: 08:30. For an unplanned closure without an exact known start date, use any time in the past. Do not use UTC format
Field Description
end_date,end_time As for start_date, start_time for the anticipated end of the closure, if known.
reason One of: Works (including road works, building construction, water mains), Event, Unplanned (e.g. emergency maintenance), Crash, Natural (fire, flood, weather)
reason_desc Free text description of the reason for the closure or restriction.
status_desc Free text description of the extent of the closure or restriction.
direction Direction in which traffic is affected. One of Both, Inbound,Outbound,North,South,West,East, etc.
updated The most recent date and time at which this information was known to be current, in combined ISO8601 format (eg, 2015-06-04T08:15+10)

Optional fields

Field Description
source The source of the closure, eg Victoria Police, Western Energy
delay_mins The number of minutes delay anticipated for motorists proceeding through an affected area. Can be either a single number 15 or a range 5-10.
impact The level of impact this is expected to have on traffic flows in the area, from 1 (minimal) to 5 (severe). This is intended to aid in filtering data for mapping.
ref A council-specific identifier.
event_id A council-specific identifier for an associated event, if any.
url A website link for more information.
phone A phone number to call for more information.
daily_start, daily_end For works across multiple days, the time at which closure begins and ends each day, in ISO8601 local timezone (preferred) or no timezone format.

Parking zones

Parking zones 0.2

(Comments welcome!)

Areas in which parking is regulated, including on-street metered and unmetered parking, no-parking zones and car parks.

Councils are encouraged to include parking zones provided by private operators, for maximum utility.

General recommendations:

  Recommendation
Format GeoJSON in EPSG:4326
Dataset name [Council name] Parking Zones
data.gov.au tags parking-zones, opencouncildata, ocd-parking-zones-0.2
Spatial type Polygon. Each polygon represents one area within which restrictions are identical. For parking on both sides of a street, two separate polygons should be used.

Required fields

  • mode: see description in Time-dependent restrictions
Field Description
updated The most recent date and time at which this information was known to be current, in combined ISO8601 format (eg, 2015-06-04T08:15+10)
ref The council’s identifier for the parking zone.

Time-dependent restrictions

Field Description
start, end Time at which this parking restriction commences/ends, in 24 hour time. Times outside this range are assumed to be free, unless additional restrictions given.
For example: 17:30
days Semicolon-delimited list of days on which this restriction applies. If times are different on different days, create a separate set of restrictions for the other days as explained below.
For example: Friday;Saturday;Sunday.
mode Semicolon-delimited list of one or more of: free,fee,loading zone,no standing,no parking,clearway, disabled
minsmax Maximum stay in minutes. For modes that imply no parking (eg, no standing), do not include this field, or with value 0 if necessary. To express the absence of a maximum stay, include this field with value -1
For example: 120
hourlyfee Cost in dollars per hour for the first hour of parking. If paying for one hour is not possible (eg, maximum stay is 30 minutes at $2.20), still convert it to an hourly rate (eg, 4.40).
onlyfor If parking is restricted to a certain type of vehicle, provide a semicolon-delimited list of: motorcycle,bus,etc.
notfor If parking is prohibited for certain types of vehicle, provide a semicolon-delimited list of: caravan, etc.
start2, end2, mode2, hourlyfee2, etc. When different times of day have different restrictions, specify them with additional columns ending in 2,3 etc.

Optional fields

Field Description
operator The organisation that manages this parking zone. eg Melbourne, VicRoads, Interpark.
sensor Whether an electronic sensor detects overstays. yes/no
type One of street (on-street parking), carpark
feemode ticket,meter,android,ios,web
payment Options for physical payments. One or more of: card,coin,note. Do not include payment types for smartphone/web payments, which are assumed to support credit card.
info_url The URL of a webpage with more information about parking in this area.
capacity The maximum number of vehicles that can be accommodated simultaneously.

Garbage collection zones

Garbage collection zones 2.2

Zones are physical regions within which residential garbage collection of a given type (waste for landfill, recycling, green waste) are collected on the same day.

Zones that share the same boundaries should be provided as a single polygon with multiple sets of tags (rub_day, grn_day etc).

OpenBinMap.org shows garbage collection zones already published.

Find datasets tagged [waste-collection] on data.gov.au

General recommendations:

  Recommendation
Format GeoJSON (preferred) in EPSG:4326, Zipped shapefile
Dataset name [Council name] Garbage Collection Zones
data.gov.au tags waste-collection, ocd-garbage, ocd-garbage-2.1

Required fields:

At least one of the following fields should have a value. If multiple collection types share a zone, publish a single polygon with values in several columns. For example, in one area, rubbish is collected on Tuesdays, and recycling is every second Thursday. If the zones are different (even if overlapping), publish multiple polygons.*

Field Description Example
rub_day Day of the week when rubbish is collected. monday
rub_weeks Number of weeks between rubbish collections. Leave blank for one-off or irregular collections. 2
rub_start Date of one rubbish collection, to calculate future collection dates from, in ISO 8601. 2015-04-01
rub_dates (optional) Comma-separated list of dates of future collections. Use this for irregular collections, or in addition to other fields to facilitate data use. 2015-04-01,2015-04-08,2015-04-15,2015-04-22
rec_day, rec_weeks, rec_start, rec_dates Schedule for recycling collection, as above.  
grn_day, grn_weeks, grn_start, grn_dates Schedule for green waste collection, as above.  
hw_day, hw_weeks, hw_start, hw_dates Schedule for hard waste collection, as above.  
Field Description Example
name a short name used by your council to identify a zone “Monday Area 2”

Optional fields:

Field Description Example
desc A free text field.  
rub_name, rec_name, grn_name, hw_name A short name describing the physical bin used for that collection Landfill bin (red lid)
rub_desc, rec_desc, grn_desc, hw_desc free text field with specific comments about rules for acceptable rubbish collection.  
rub_url, rec_url, grn_url, hw_url URL pointing to a page with more information specifically about each collection. If there is no page specifically about a type, leave it blank and use the info_url field.  
rub_scope, rec_scope, grn_scope, hw_scope one of:
all (all residents receive this service)
optional (residents need to sign up to the service),
booked (residents sign up for individual collection dates)
 
rub_ok, rec_ok, grn_ok, hw_ok semi-colon separated list of things that can be included in this collection type. Plastic bottles; tin cans
rub_notok, rec_notok, grn_notok, hw_notok semi-colon separated list of things that must not be included in this collection type. Nappies; car batteries.
info_url The page on your council website with information about garbage collection in general. This can be an alternative to, or in addition to, a description field. e.g. http://www.geelongaustralia.com.au/residents/waste/  
missed_ph The phone number to call for a missed rubbish collection.  

Footpaths

Footpaths 0.2

(Comments welcome!)

Footpaths known about or maintained by the council.

General recommendations

  • Format: Polyline geospatial data. GeoJSON (preferred), Shapefile
  • Dataset name: [Council name] council footpaths
  • data.gov.au tag: footpaths, opencouncildata, ocd-footpaths-0.2

Required fields

(None)

Field Description
paved Is the surface a hard material such as asphalt, concrete or slate? yes or no.
surf The main construction material used to create the footpath. Use one of the following values where possible:
Asphalt, Concrete, Brick (including slate, cobbles, setts), Gravel (including all graded, unsealed surfaces such as crushed limestone and chert), Sand, Natural (earth, grass, rocks), Boardwalk (including wooden and synthetic bridge decks) , Sprayseal.
width The width in meters of the footpath. E.g. 1.8
wheelchair Accessibility for wheelchair users. yes (no steps, suitable for unassisted use), assisted (occasional small steps navigable with assistance), no (significant obstacles such as steps, bollards or a steep gradient)

Optional fields

Field Description
surf_desc A free-text description of the surface and condition. E.g. “Gravel path with steps and erosion control channels.”
operator The name of the council or other organisation (eg VicRoads) maintaining this footpath.
ref Council specific reference id for the footpath segment.
bicycle Are bicycles allowed on this footpath? (Designated bike paths should be provided in a separate “bike paths” dataset.) One of: allowed (bicycles are allowed, as in most parks), no (bicycles are forbidden)

Events

Events 0.1

(Comments welcome!)

Public events such as concerts, festivals or workshops organised or promoted by the council.

General recommendations

  • Format: Various file formats have different benefits for different audiences. We recommend publishing in several formats if practical.
    • CSV: Very widely supported and easy to work with.
    • JSON: Preferred format for mobile and web developers.
    • GeoJSON: Preferred format for web map developers.
    • RSS/Atom: Useful for applications which can consume “feeds” of data.
  • Dataset name: [Council name] events
  • data.gov.au tag: events, opencouncildata, ocd-events-0.1

Required fields

Field Description
date The date on which the event begins, in YYYY-MM-DD format.
title A short name for the event, for example Hamlet in the park
description A longer description of the event. This could include HTML.
Field Description
lat,lon Location using decimal degrees of latitude and longitude.
location Location given as text, such as a street address.
time_start,time_end Start and end times, in HH:MM (24 hour) format.
info_url URL of a web page with more information about the event.

Optional fields

Field Description
date_end Date on which the event ends, if multiple days.
image_url URL of an image to accompany the text.
ref Council-specific identifier.
category Council-specific classification of the event.

Drainpipes

Drainpipes 0.2

(Comments welcome!)

Drain pipes known about or maintained by the council.

Find datasets tagged [drainpipes] on data.gov.au

General recommendations:

  Recommendation
Format GeoJSON (preferred), Shapefile
Dataset name [Council name] council drain pipes
data.gov.au tag drainpipes, opencouncildata, ocd-drainpipes-0.2

Required fields

(none)

Field Description
carrying The contents of the pipe: Drinking water, Stormwater, Sewage
material One of: Plastic,Concrete,Brick (including stonework), Metal,Earthenware, Earth

Optional fields

Field Description
mat_desc Free text description of the building material (eg Fibre-reinforced concrete)
form The general shape. One of: Pipe (closed, buried pipe), Exposed (closed pipe at least partially visible), Open, Culvert
height_mm The height in millimetres of the drain pipe if it’s not symmetrical.
width_mm The width in millimetres of the drain pipe.
built The date the drain pipe was constructed.
ref Council specific reference id for the drain pipe segment.
comment Free text, other information as relevant.
operator Name of council or organisation responsible for maintainance.

Dog walking zones

Dog walking zones 0.1

(Comments welcome!)

Dog walking zones are regions within which dog walking is permitted off-leash, on-leash, or not at all. Councils are encouraged to provide comprehensive information on where dog walking is allowed or restricted, including other sources of regulations such as state or national parks.

Find datasets tagged [dog-walking] on data.gov.au

General recommendations

  Recommendation
Format GeoJSON (preferred) in EPSG:4326; zipped shapefile
Dataset name [Council name] Dog Walking Zones
data.gov.au tags dog-walking, opencouncildata, ocd-dogzones-0.1

Polygon areas should not overlap, with the single exception of the Default polygon described under name.

Required fields

Field Description
status The default dog-walking status for this area, one of: offleash (also known as “free roam areas”), onleash, no (also known as “dog ban areas”)
Field Description
name A short name used by your council to identify a zone, such as “Fido Beach”. If the special name Default is used, this is taken to describe general default regulations for public areas throughout the council area, and should be on a polygon covering the whole LGA boundary.
regulation free text field describing the source of the regulation in force. For example, Council or State park regulations
comment Free text field that could include more specific restrictions (eg, no dogs within 20 metres of playgrounds), information on dog waste management, etc.
off_rules Free text field with specific rules about off-leash dog walking (eg, effective voice control required).

Optional fields

Field Description
url URL pointing to more information about dog walking in this area.
ref internal council reference number, if any.
on_rules Free text field with specific rules about on-leash dog walking.
no_rules Free text field with specific rules about dog-prohibited areas.
status_1 a different status restriction (as above) that applies during a limited set of dates and/or hours. Outside those dates/hours, status applies. Either dates_1, or hours_1, or both, must be provided.
dates_1 Comma-separated, slashed pairs of dates definining ranges during which this status applies (eg, 2015-12-01/2016-01-28,2016-04-03/2016-04-13)
hours_1 Hyphenated range of 0-padded 24-hour times defining time range during which this status applies (eg, 18:00-08:30). (Comma-separated ranges allowed if necessary.)
status_2,dates_2,hours_2 An additional status that overrides status_1 in complex situations.

For example, these restrictions: “Off-leash permitted from 1 December until 28 February and during the Victorian Easter school holidays each year between the hours of 6.00pm and 9.00am. At all other times during this period dogs are permitted on-leash in this area. Outside of these dates dogs are permitted off-leash at all time”

This would be implemented as:

  • status:offleash
  • status_1: onleash
  • dates_1: 2015-12-01/2016-02-28,2016-03-25/2016-04-11
  • hours_1: 18:00-09:00

Customer service centres

Customer service centres 0.1

(Comments welcome!)

Customer service centres are places where citizens go to pay fees (rates, fines, pet registration), deposit planning applications, or otherwise interact with council services.

General recommendations:

  • Format: Point data. CSV (preferred), GeoJSON, Shapefile
  • Dataset name: [Council name] customer service centres
  • data.gov.au tag: customer-service-centres, opencouncildata, ocd-customer-service-centres-0.1

Required fields

field description
lat, lon Latitude, longitude, decimal degrees. (EPSG:4326)
field description
name A name identifying the centre. E.g. “Preston Customer Service Centre”
services Comma-separated list of services provided by the centre. For example: “pet registration,parking fines,rates”. Possible values include:
pet registration, parking fines, rates, planning, building permits, building permit, planning permit, engineering permit, general permit, infringements, licensing, pet registration, general tourism information, lodgements, keys, engineering permits, temporary car parking permits, collection/drop off, disabled parking application, fencing requests, local laws permit, pension rebate, stat dec, property information request (or other, please provide feedback)
address Street address. E.g. “274 Gower Street, Preston, VIC 3072”
languages Comma separated list of non-English languages spoken at the centre (or provided by phone interpreter), in ISO 639-1 (two-letter) codes. For example: it,vi,zh
access Free text description of accessibility. For example: “Fully accessible to wheelchair users; disabled parking at front.”
monday, tuesday, wednesday, thursday, friday, saturday, sunday Normal opening hours on each day, in 24 hour HH:MM-HH:MM format. For example: 08:00-17:30.
holiday Normal opening hours on public holidays.

Optional fields

Field Description
desc Free text description of services or other information.
phone Telephone number of this center, if any.

Childcare centres

Childcare Centres 0.1

(Comments welcome!)

Facilities that look after young children during the day.

Find datasets tagged [childcare-centres] on data.gov.au

General recommendations:

  Recommendation
Format Point data. CSV (preferred), GeoJSON
Dataset name [Council name] childcare centres
data.gov.au tag childcare-centres, opencouncildata, ocd-childcare-centres-0.1

Required fields

Field Description
lat, lon Latitude, longitude, decimal degrees. (EPSG:4326)
name Name of the centre
Field Description
operator The council (or company) that operates the centre.
contact_ph The centre’s telephone number.
url A URL with more information about the centre.

Optional fields

Field Description
ref The internal council ID for the centre, if any.

Building accessibility ratings

Building accessibility ratings 1.1

Some councils provide ratings on accessibility of buildings for wheelchair users. These ratings are in high demand by certain community groups wanting to choose venues suitable for all their members. These ratings may be available for only council buildings, or more broadly.

There are no known standards for this kind of data, and some councils combine them in different ways (eg, a rating of 0, 1 or 2 for the building as a whole).

Find datasets tagged [accessibility] on data.gov.au

General recommendations:

  Recommendation
Format CSV (preferred), Shapefile, GeoJSON
Dataset name [Council name] Building Accessibility Ratings
data.gov.au tag building-accessibility, opencouncildata, ocd-building-accessibility-1.1

Required fields

Field Description
lat, lon Latitude, longitude, decimal degrees of centroid or entrance to building. (EPSG:4326)
Field Description
entrance Access into the building and its main services.
yes: an unpowered, wheelchair user can enter the building and access public services without assistance
assisted: a wheelchair user can enter the building if assisted. For example, a steep ramp, or a lift requiring an authorised operator.
no: there is limited or no access for wheelchair users. For example, a cinema with a ramp entrance, but steps to individual theatres.
parking yes: disabled parking spaces are available
no: there is no designated disabled parking
toilets yes: toilets suitable for wheelchair users are available
no: there are no toilets suitable for use by wheelchair users
name A name identifying the building, organisation or business name.
address The building’s street address.

Optional fields

Field Description
id A council-specific identifier that can used to link to other council-published data for that building, such as a building footprint.
assessed Date of most recent accessibility assessment, in ISO 8601 (YYYY-MM-DD).
comment Text description supplementing the entrance,parking and toilets fields.