From 2a32c40183a337d73c93f7dab9c230a20727091c Mon Sep 17 00:00:00 2001 From: annegoldsack Date: Mon, 4 Nov 2024 18:39:43 +1000 Subject: [PATCH 1/4] Updates to 03,05,06,99 --- .vscode/settings.json | 3 + document/03-preamble.adoc | 10 +-- document/05-usage-personas.adoc | 39 ++++++++-- document/06-common-tasks.adoc | 132 +++++++++++++++++++++++--------- document/99-bibliography.adoc | 8 +- 5 files changed, 144 insertions(+), 48 deletions(-) create mode 100644 .vscode/settings.json diff --git a/.vscode/settings.json b/.vscode/settings.json new file mode 100644 index 0000000..54db2c4 --- /dev/null +++ b/.vscode/settings.json @@ -0,0 +1,3 @@ +{ + "asciidoc.antora.enableAntoraSupport": false +} \ No newline at end of file diff --git a/document/03-preamble.adoc b/document/03-preamble.adoc index e0feaa0..49fc8fd 100644 --- a/document/03-preamble.adoc +++ b/document/03-preamble.adoc @@ -4,7 +4,7 @@ This document is a Profile of <>. -In the Australian context, this standard applies to thoroughfare-based addressing i.e. street and water, as well as landmark addressing. It is designed as a replacement for <> Rural and urban addressing>>. This standard does not apply to other address classes such as postal or landmark at this time. Postal addressing is expected to adhere to <>. +In the Australian context, this standard applies to thoroughfare-based addressing i.e. street and water, as well as landmark addressing. It is designed as a replacement for <>. This standard does not apply to other address classes such as postal at this time. Postal addressing is expected to adhere to <>. This document focuses on assigning and maintaining addresses that allow the unambiguous determination of an object in the physical world for purposes of identification and location in the context of public administration and public service delivery. @@ -18,10 +18,10 @@ The following standard is needed for the application of this Australian Profile: The following documents inform aspects of this standard for Australia: -* <> Rural and urban addressing>> -* AS 4590.1:2017 Interchange of client information +* <> +* <> * <> -* ICSM Addressing 2035 Strategy and Supporting Addendum1 +* <> and <> The following document defines the addressing model used for address records: @@ -29,7 +29,7 @@ The following document defines the addressing model used for address records: === Terms & Definitions -[[access-point]] access point:: The position along a throughfare (road or water feature) where the public would normally access an address site. SOURCE: this standard +[[access-point]] access point:: The position along a thoroughfare (road or water feature) where the public would normally access an address site. SOURCE: this standard [[address]] address:: An address is structured information that allows the unambiguous determination of an object for purposes of identification and location (SOURCE ISO 19160-1:2015). The objects exist in the physical world (i.e. virtual objects are excluded) and can be outdoor (e.g. a building) or indoor (e.g. an office inside a building). SOURCE: this standard diff --git a/document/05-usage-personas.adoc b/document/05-usage-personas.adoc index b6a75c3..0083227 100644 --- a/document/05-usage-personas.adoc +++ b/document/05-usage-personas.adoc @@ -12,29 +12,31 @@ People and organisations in Australia perform different roles with respect to ad Those with a role in creating addresses. This including assigning street numbers and approving road and locality names. ==== Aggregator -Those with a role in aggregating addresses and associated information. This may including collating addresses, assigning geocodes or other geometries, and runnig validation processes. +Those with a role in aggregating addresses and associated information. This may including collating addresses, assigning geocodes or other geometries, and running validation processes. ==== Distributor Those with a role in distributing products and services centred around address data. ==== User -Those with a role in utilising address data, inclduing address validation. +Those with a role in utilising address data, including address validation. === Agents with Personas ==== Creator Agents who have a role as a creator of addresses in Australia include: -//THIS SECTION IS INCOMPLETE +//THIS SECTION IS INCOMPLETE - perhaps make a table * Local Government agencies ** Address numbering in New South Wales, Queensland, South Australia, Tasmania, Western Australia ** Road naming approval in Queensland (local government owned roads), South Australia, Tasmania, Western Australia + * State / Territory Government agencies ** Full address creation in Australian Capital Territory and Northern Territory ** Locality naming in Queensland, Victoria, Western Australia ** State controlled road naming in Queensland ** Road name approval in New South Wales, Victoria + * Developers (limited role) ** Sub address numbering suggestions ** Road name suggestions @@ -44,24 +46,49 @@ Agents who have a role as a creator of addresses in Australia include: Agents who have a role as an aggregator of addresses in Australia include: * State / Territory Government agencies +** Australian Capital Territory - https://www.data.act.gov.au/Land-Planning-and-Housing/ACT-Addressing/rwvc-ci8y/about_data[Department of Environment, Planning and Sustainable Development] +** New South Wales - https://www.spatial.nsw.gov.au/what_we_do/the_built_environment/addressing[Spatial Services, Department of Customer Service] +** Northern Territory - https://nt.gov.au/property/land/land-development/property-and-street-addresses[Survey Branch, Department of Infrastructure, Planning and Logistics] +** Queensland - https://www.qld.gov.au/environment/land/title/addressing[Spatial Information, Department of Resources] +** South Australia - https://www.sa.gov.au/topics/housing/planning-and-property[Department?] +** Tasmania - https://nre.tas.gov.au/land-tasmania/property-addressing[Location Services Branch, Department of Natural Resources and Environment Tasmania] +** Victoria - https://www.land.vic.gov.au/[Land Use Victoria, Department of Transport and Planning] +** Western Australia - https://www.landgate.wa.gov.au/location-data-and-services/discovering-landgate-data/property-street-address-data/[Landgate] + * National aggregators -** Australia Post -** Australian Bureau of Statistics -** Geoscape +** Australia Post - https://auspost.com.au/business/marketing-and-communications/access-data-and-insights/address-data[Postal Address File] +** Australian Bureau of Statistics - https://www.abs.gov.au/statistics/research/abs-address-register-users-guide[ABS Address Register] +** Geoscape - https://geoscape.com.au/solutions/g-naf/[Geocoded National Address File (G-NAF)] ==== Distributor Agents who have a role as a distributor of addresses in Australia include: * Local Government agencies + * State / Territory Government agencies +** Australian Capital Territory - https://www.data.act.gov.au/Land-Planning-and-Housing/ACT-Addressing/rwvc-ci8y/about_data[Department of Environment, Planning and Sustainable Development] +** New South Wales - https://www.spatial.nsw.gov.au/what_we_do/the_built_environment/addressing[Spatial Services, Department of Customer Service] +** Northern Territory - https://nt.gov.au/property/land/land-development/property-and-street-addresses[Survey Branch, Department of Infrastructure, Planning and Logistics] +** Queensland - https://www.qld.gov.au/environment/land/title/addressing[Spatial Information, Department of Resources] +** South Australia - https://location.sa.gov.au/index.html[LocationSA] +** Tasmania - https://nre.tas.gov.au/land-tasmania/property-addressing[Location Services Branch, Department of Natural Resources and Environment Tasmania] +** Victoria - https://www.land.vic.gov.au/[Department of Transport and Planning] +** Western Australia - https://www.landgate.wa.gov.au/location-data-and-services/discovering-landgate-data/property-street-address-data/[Landgate] + +* National Datasets +** Geocoded National Address File (G-NAF) - https://geoscape.com.au/solutions/g-naf/[Gesocape] +** Postal Address File (PAF) - https://auspost.com.au/business/marketing-and-communications/access-data-and-insights/address-data[Australia Post via third party resellers] + * Address data resellers ==== User Agents who have a role as a user of addresses in Australia include: +* Government * Emergency services * Postal and delivery service providers * Utility providers * Location service providers +* Insurers * The public \ No newline at end of file diff --git a/document/06-common-tasks.adoc b/document/06-common-tasks.adoc index ff24df2..fac18a8 100644 --- a/document/06-common-tasks.adoc +++ b/document/06-common-tasks.adoc @@ -1,12 +1,12 @@ == Common Tasks -This section describes the specific address information-related tasks that the personas listed in Section X frequently carry out. +This section describes the specific address information-related tasks that the personas listed in <<05-usage-personas, Usage Personas>> frequently carry out. -#TODO: make a Tasks vocab # +//TODO: make a Tasks vocab === Creator Tasks ==== Creating a new address -Addresses SHALL adhere to the https://linked.data.gov.au/def/addr[Australian address model], which in turn conforms with ISO 19160-1:2015. +Addresses SHALL adhere to the <>, which in turn conforms with <>. All address components SHALL be stored with lifecycle and provenance information, according to the https://linked.data.gov.au/def/lifecycle[lifecycle model]. @@ -18,7 +18,7 @@ Address creators SHALL use concepts from the relevant vocabularies to ensure dat An address SHALL be unique. -Each address SHALL be assigned at least one geocode with coordinates. +An addressable object SHALL have at least one spatial geometry stored against it.Each address SHALL be assigned at least one geocode with coordinates. The relationship between a new address and any address(es) that it replaces SHALL be recorded. @@ -50,21 +50,19 @@ An address SHALL be assigned to an addressable object. In instances where an address site has more than one point of access, alternative addresses may be created to reflect the additional access points. These additional addresses SHALL be stored against the same addressable object. -An addressable object SHALL have at least one spatial geometry stored against it. - *Address number* An address SHALL be assigned a unique number in relation to the access throughfare. The designation and form of an address number is crucial in enabling an address site to be readily located by emergency service responders and service delivery providers. -An address number SHALL be assigned to each separately owned or occupied area of land, and each separately owned or occupied building or part of a building. The address number assignation method relates to the address class. For throughfare addresses, address numbers follow general and specific address class principles. +An address number SHALL be assigned to each separately owned or occupied area of land, and each separately owned or occupied building or part of a building. The address number assignation method relates to the address class. For thoroughfare addresses, address numbers follow general and specific address class principles. *General address numbering principles* Address numbers SHALL be assigned prior to occupation and as early as practicable in the development process. -Address numbers SHALL be assigned according to the location of the point of access to the address site from the throughfare (road or water feature). +Address numbers SHALL be assigned according to the location of the point of access to the address site from the thoroughfare (road or water feature). Address number allocation SHALL ensure clear, logical and unambiguous numbering: @@ -72,15 +70,18 @@ Address number allocation SHALL ensure clear, logical and unambiguous numbering: * The datum point for address numbering SHOULD be at the commencement of the road from where access to that road is most common, or is planned to occur, at the point of naming. This SHALL take into account assignation of reserved numbering requirements in a staged development. * A number range SHALL NOT be assigned as an address number. Any existing ranges SHOULD be phased out. * An address number SHALL NOT be prefixed by alphabetical characters. -* Address sites SHALL be numbered using odd numbers on the left of the throughfare and even numbers on the right . -* Where there are no addresses numbers available for an address site due to existing allocations, alpha suffixes SHALL be assigned to the base number; with the exception that address sites that share access SHOULD be treated as sub-address sites. -* Alpha suffixes SHALL start at A, be assigned incrementally in the same direction as the numbering of addresses on the throughfare, and SHALL NOT extend beyond E. -* Renumbering of the road is required where there are more than five additional address sites requiring numbering in this way. -* In instances where an existing address site uses the base number, this MAY be retained (i.e. not have a suffix) provided it is in order. +* Address sites SHALL be numbered using odd numbers on the left of the throughfare and even numbers on the right. * A lot number SHALL NOT be used in place of an address number. * Where a road is renamed as a result of redesign or development, address sites SHALL be renumbered if required to ensure adherence to this standard. * Where an area of rural numbering is reclassified as urban, previously assigned rural numbers SHOULD be retained if urban numbering requirements can be met for the infill addressing. +Use of alpha suffixes:[[alpha-suffixes,use of alpha suffixes]] + +* Where there are no addresses numbers available for an address site due to existing allocations, alpha suffixes SHALL be assigned to the base number; with the exception that address sites that share access SHOULD be treated as sub-address sites (see <>). +** Alpha suffixes SHALL start at A, be assigned incrementally in the same direction as the numbering of addresses on the throughfare, and SHALL NOT extend beyond E. +** Renumbering of the road is required where there are more than five additional address sites requiring numbering in this way. +** In instances where an existing address site uses the base number, this MAY be retained (i.e. not have a suffix), provided it is in order. + *Urban address numbering* For addresses designated part of the https://linked.data.gov.au/def/address-classes/urban[urban address class], address numbers SHALL be reserved to meet potential future allocation needs, for example where there are unusually wide frontages or potential for infill development. @@ -93,9 +94,9 @@ For addresses designated part of the https://linked.data.gov.au/def/address-clas Address numbers SHALL NOT exceed five digits – for roads over 1000km long, address numbering SHALL be restarted at a different datum point, preferably a town, natural feature or major intersection, with numbering in the same direction. -In the absence of an access point, a rural number within the range determined by the rural numbering method may be assigned. The rural number SHALL be reassigned if an access point is subsequently created. +In the absence of an access point, a rural number within the range determined by the rural numbering method MAY be assigned. The rural number SHALL be reassigned if an access point is subsequently created. -In areas with multiple address access points within the minimum step intervals of 20m, the distance criteria may be varied as long as the overall integrity of the rural numbering system is maintained. Alternatively, suffixes may be added in accordance with [Section XX]. +In areas with multiple address access points within the minimum step intervals of 20m, the distance criteria may be varied as long as the overall integrity of the rural numbering system is maintained. Alternatively, suffixes may be added in accordance with <>. *Numbering for roads that cross both rural and urban areas* @@ -113,21 +114,21 @@ For addresses designated part of the https://linked.data.gov.au/def/address-clas For addresses designated part of the https://linked.data.gov.au/def/address-classes/river[river address class], river and creek address numbering uses the distance in metres upstream from a datum point (e.g. river mouth), divided by ten, and rounded to the nearest odd number on the true right and even number on the true left (i.e. to the direction in relation to the flow of the river). -*Sub-address numbering* +*Sub-address numbering[[sub_address_numbering,sub-address numbering]]* -Sub-address numbering SHALL be used for address sites contained within other address sites e.g. an apartment block or marina. A sub-address may utilise either the primary or an alternative address for the parent site. +Sub-address numbering SHALL be used for address sites contained within other address sites e.g. an apartment block or marina. A sub-address may utilise either the preffered or an alternative address for the parent site. The sub-address number SHOULD be stored with the https://linked.data.gov.au/def/subaddress-types[sub-address type], although this does not have to be provided within an address string. -A sub address number SHALL be unique regardless of subaddress (unit) type or building level. +A sub-address number SHALL be unique regardless of sub-address (unit) type or building level. -The sub-address number precedes the address for the parent site, and SHALL be formatted when used with a ‘/’ between the sub-address number and address number. +Within a formatted address string, the sub-address number precedes the address for the parent site, and SHALL be formatted when used with a ‘/’ between the sub-address number and address number. *Thoroughfare name* *Roads* -A road name SHALL be short, clear and unambiguous, and meet national naming principles. It SHALL NOT be offensive, racist, derogatory or demeaning. +A road name SHALL be short, clear and unambiguous, and meet relevant national and state or territory naming principles. It SHALL NOT be offensive, racist, derogatory or demeaning. All formed roads, including private roads, that are generally open to the public or to services SHALL be named. @@ -139,7 +140,7 @@ An unbroken section of road crossing an administrative boundary SHALL retain the A road name SHALL consist of a name element followed by a road type. The accepted road types are in the https://linked.data.gov.au/def/road-types[road types vocabulary]. The road type SHALL reflect the function and characteristics of the road as described in the vocabulary. -A road named after 2011 SHOULD NOT have a cardinal indicator after the road type. For roads named prior to this, road suffixes SHALL refer to the https://linked.data.gov.au/def/road-suffixes[affixes vocabulary]. +A road named after 2011 SHOULD NOT have a cardinal indicator after the road type. For roads named prior to this, road suffixes SHALL refer to concepts within the https://linked.data.gov.au/def/road-suffixes[affixes vocabulary]. The name element of a road name, regardless of road type, SHALL NOT be the same as, or similar in spelling or sound, to an existing road name in the same locality, an adjoining locality, or in the same local government area. @@ -155,7 +156,9 @@ The water throughfare SHALL indicate the https://linked.data.gov.au/def/go-categ *Locality Naming* -A locality name SHALL be short, unique within the country, and assigned according to national naming principles. It SHALL NOT be offensive, racist, derogatory or demeaning. +Naming SHALL first and foremost adhere to the https://www.icsm.gov.au/publications/principles-consistent-use-place-names[Australian principles for the consistent use of place names]. + +A locality name SHALL be short, unique within the country, and assigned according to national and state or territory naming principles. It SHALL NOT be offensive, racist, derogatory or demeaning. A locality name SHALL NOT be similar in spelling or sound to any other locality name with the country. @@ -171,24 +174,26 @@ A locality SHALL be assigned the geographical object category of https://linked. Locality boundaries SHALL be clearly defined, not overlap, and be contiguous. A locality SHALL NOT cross a Local Government boundary, and SHALL be contained within, and not cross, state or territory boundaries. -When defining a locality boundary, the following SHOULD be considered: +When defining a locality boundary, the following SHALL be considered: -* A locality boundary SHOULD define a community of interest -* Definite and distinguishable physical features or barriers SHOULD be used where appropriate e.g. creeks, rivers, ridgelines, centres of roads, railways. +* A locality boundary SHOULD define a community of interest. +* Definite and distinguishable physical features or barriers SHALL be used where appropriate e.g. creeks, rivers, ridgelines, centres of roads, railways. * The boundary SHOULD NOT, where possible, bisect properties in common ownership or land parcels. -A locality boundary SHOULD be enduring and changed only when necessary. However, these SHOULD be reviewed and amended where appropriate in areas subject to development. + +A locality boundary SHALL be enduring and changed only when necessary. However, these SHOULD be reviewed and amended where appropriate in areas subject to development. ===== Landmark class addresses -Addresses in the https://linked.data.gov.au/def/address-classes/landmark[landmark class] specify a location by reference to a named landmark. A landmark is a relatively permanent feature of the manmade landscape that has recognizable identity within a particular cultural context. +Addresses in the https://linked.data.gov.au/def/address-classes/landmark[landmark class] specify a location by reference to a named landmark. A landmark is a relatively permanent feature of the man made landscape that has recognisable identity within a particular cultural context. All landmark addresses SHALL comprise the following components: +*NB. THIS SECTION IS IN DRAFT AMD SUBJECT TO CHANGE* -(a) Landmark Name -(b) Locality (or city/town) name -(c) State or territory name +a. Landmark name +b. Locality (or city/town) name *N.B. What about areas outside of LGAs?* +c. State or territory name -Landmark addresses SHALL NOT include an address number or thoroughfare name, but SHOULD be linked to an associated throughfare address. +Landmark addresses SHALL NOT include an address number or thoroughfare name, but SHOULD be linked to an associated thoroughfare address. ===== Postal class addresses @@ -207,7 +212,7 @@ An address SHALL NOT be assigned against non contiguous areas, other than in rel When updating an existing address, address creators should adhere to the principles outlined in the section relating to creating a new address. -Any amendments to an address should be recorded according to the address and lifecycle models, including lifecycle and provenance information. +Any amendments to an address should be recorded according to the <> and https://linked.data.gov.au/def/lifecycle[lifecycle] models, including lifecycle and provenance information. ==== Retiring an address @@ -219,18 +224,73 @@ Address creators SHALL make address data available for address aggregators and/o An address SHALL NOT include personal information related to a person or organisation that owns or occupies the address site (or object) to which the address is assigned. === Aggregator Tasks -==== Vocabularies +==== Validation of address components Address aggregators SHALL validate address components against relevant vocabulary concepts to ensure data consistency. +===== Vocabularies used for addresses +* Geographical object categories: https://linked.data.gov.au/def/go-categories +* Building level types: https://linked.data.gov.au/def/building-level-types +* Subaddress types: https://linked.data.gov.au/def/subaddress-types +* stateOrTerritory: https://linked.data.gov.au/dataset/asgsed3/STE +* countryName: https://linked.data.gov.au/def/countries +* Address classes: https://linked.data.gov.au/def/address-classes +* Address status types: https://linked.data.gov.au/def/address-status-type +* Lifecycle Stage Types: https://linked.data.gov.au/def/lifecycle-stage-types +* Naming authority: https://linked.data.gov.au/def/naming-authority +* Record access: https://linked.data.gov.au/def/record-access +* Geocode types: https://linked.data.gov.au/def/geocode-types +* Spatial capture method:: https://linked.data.gov.au/def/spatial-capture-method +* Address Geographic Name Types: https://linked.data.gov.au/def/address-geographic-name-types +* Address Part Types: https://linked.data.gov.au/def/addr-part-types + +===== Vocabularies used for roads +* Road name part types: https://linked.data.gov.au/def/road-name-part-types +* Road types: https://linked.data.gov.au/def/road-types +* Geographical Name Affix: https://linked.data.gov.au/def/gn-affix +* Naming authority: https://linked.data.gov.au/def/naming-authority +* Geographical object categories: https://linked.data.gov.au/def/go-categories +* Transport Infrastructure Types: https://linked.data.gov.au/def//transport-infrastructure-types +* Transport Infrastructure Sub Types: https://linked.data.gov.au/def//transport-infrastructure-sub-types +* Road surfaces: https://linked.data.gov.au/def/road-surfaces +* Surface capture method: https://linked.data.gov.au/def/surface-capture-method +* Road operational statuses: https://linked.data.gov.au/def/road-operational-statuses +* Road user access: https://linked.data.gov.au/def/road-user-access +* Road travel direction: https://linked.data.gov.au/def/road-travel-direction +* Road lane count: https://linked.data.gov.au/def/road-lane-count +* Road trafficability: https://linked.data.gov.au/def/road-trafficability +* Population zone: https://linked.data.gov.au/def/population-zone +* Road seasonality: https://linked.data.gov.au/def/road-seasonality +* Ground relationship: https://linked.data.gov.au/def/ground-relationship +* Road owner: https://linked.data.gov.au/def/road-owner +* Road maintainer: https://linked.data.gov.au/def/road-maintainer +* State controlled road indicator: https://linked.data.gov.au/def/scr-indicator +* LRRS indicator: https://linked.data.gov.au/def/lrrs-indicator +* Spatial capture method: https://linked.data.gov.au/def/spatial-capture-method +* Positional accuracy: https://linked.data.gov.au/def/positional-accuracy +* Road cadastral relationship: https://linked.data.gov.au/def/road-cadastral-relationship +* Lifecycle Stage Types: https://linked.data.gov.au/def/lifecycle-stage-types +* Record access: https://linked.data.gov.au/def/record-access +* Road geometry notes: https://linked.data.gov.au/def/road-geometry-notes + +===== Vocabularies used for geographic names (including locality) +* Geographical object categories: https://linked.data.gov.au/def/go-categories +* Geographical Name Affix: https://linked.data.gov.au/def/gn-affix +* Geographical names part types: https://linked.data.gov.au/def/gn-part-types +* Record access: https://linked.data.gov.au/def/record-access +* Naming authority: https://linked.data.gov.au/def/naming-authority +* Lifecycle Stage Types: https://linked.data.gov.au/def/lifecycle-stage-types + ==== Digital equivalent address record -Any address assigned to an object SHALL have a digital equivalent address record in the authoritative state and national address datasets . This record SHALL be updated whenever an address is assigned or changed. +Any address assigned to an object SHALL have a digital equivalent address record in the authoritative state and national address datasets. This record SHALL be updated whenever an address is assigned or changed. === Distributor Tasks ==== Licence Provision Distributors SHALL specify the licences under which the address data is available and the terms and conditions for their use. -==== Metadata +==== Metadata Provision +Distributors SHALL provide relevant metadata. === User Tasks -==== Address validation \ No newline at end of file +==== Address validation +Address data users SHALL validate addresses against authoritative address data. \ No newline at end of file diff --git a/document/99-bibliography.adoc b/document/99-bibliography.adoc index ce458f3..4974e2f 100644 --- a/document/99-bibliography.adoc +++ b/document/99-bibliography.adoc @@ -2,6 +2,12 @@ [[ADDR2024]] ADDR2024:: Intergovernmental Committee on Surveying & Mapping, _Address Model_ (2024). https://linked.data.gov.au/def/addr +[[ADDR2035-1]] Addressing 2035 Strategy:: Intergovernmental Committee on Surveying and Mapping. _Addressing 2035 Strategy_ (2021). https://www.icsm.gov.au/publications/addressing-2035-strategy + +[[ADDR2035-2]] Addressing 2035 Strategy Technical Addendum:: ICSM. _Addressing 2035 Strategy Technical Addendum_ (2021). https://www.icsm.gov.au/publications/addressing-strategy-information-addendum + +[[AS4590]] AS 4590.1:2017:: Standards Australia. _Interchange of client information, Part 1: Data elements and interchange formats_ (2017). https://store.standards.org.au/product/as-4590-1-2017 + [[ISO10646]] ISO10646:: International Organization for Standardization, _ISO/IEC 10646: Information technology — Universal coded character set (UCS)_. https://www.iso.org/standard/76835.html [[ISO19160-1]] ISO19160-1:: International Organization for Standardization, _ISO 19160-1: Addressing Part 1: Conceptual model_ (2015). https://www.iso.org/standard/61710.html @@ -12,7 +18,7 @@ [[RFC2119]] RDF2119:: Internet Engineering Taskforce, _Key words for use in RFCs to Indicate Requirement Levels_ (1997) https://datatracker.ietf.org/doc/html/rfc2119 -[[ANZ4819]] AS/NZS4819:2011:: Standards Australia. _AS/NZS 4819:2011 Rural and urban addressing_. https://store.standards.org.au/product/as-nzs-4819-2011 +[[ANZ4819]] AS/NZS 4819:2011:: Standards Australia. _AS/NZS 4819:2011 Rural and urban addressing_. https://store.standards.org.au/product/as-nzs-4819-2011 [[ASNZSISO19160-4]] ASNZSISO19160-4:: Standards Australia. _AS/NZS ISO 19160.4: Addressing, Part 4: International postal address components and template language_ (2023). https://store.standards.org.au/product/as-nzs-iso-19160-4-2023 From b0cd347ad2968046ceb50060ec9e3afba5a5df0a Mon Sep 17 00:00:00 2001 From: annegoldsack Date: Tue, 5 Nov 2024 09:28:16 +1000 Subject: [PATCH 2/4] Update to readme --- README.adoc | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/README.adoc b/README.adoc index 9b21ff8..7d1d1a1 100644 --- a/README.adoc +++ b/README.adoc @@ -14,12 +14,12 @@ We encourage all contributions to this Standard! Please contribute by: -. Raising concerns/ideas within ICSM's Address Working Group +. Raising concerns/ideas within ICSM's Addressing Working Group . Creating Issue tickets within this repository's Issue Tracker -.. at https://github.com/Spatial-Information-QLD/addr-creation-maintenance/issues +.. at https://github.com/icsm-au/addr-creation-maintenance/issues . Creating Pull Requests to absorb changes against the document source files .. the source files are in the `document/` folder of this repository -.. Pull Requests should be lodged at https://github.com/Spatial-Information-QLD/addr-creation-maintenance/pulls +.. Pull Requests should be lodged at https://github.com/icsm-au/addr-creation-maintenance/pulls _If creating Pull Requests is a new/unknown thing for you, please communicate with the contacts below for help._ @@ -27,7 +27,7 @@ _If creating Pull Requests is a new/unknown thing for you, please communicate wi The information in this repository is available for reuse under the https://creativecommons.org/licenses/by/4.0/[Creative Commons 4.0 license], see the LICENSE file for the deed. -© Intergovernmental Committee on Survey ing and Mapping, 2024 +© Intergovernmental Committee on Surveying and Mapping, 2024 == Contacts @@ -38,11 +38,11 @@ For more information about these vocabularies, contact: GeoResources Division + Department of Resources + Queensland Government + -CadastralAdminDataHelp@resources.qld.gov.au +AddressQueensland@resources.qld.gov.au For further information, please visit: -https://www.resources.qld.gov.au/data-mapping + +https://www.qld.gov.au/environment/land/title/addressing + https://qldspatial.information.qld.gov.au/ For technical model implementation questions, contact: From 1c4a0a91712bdc9928f6a31d373d817fd148fbda Mon Sep 17 00:00:00 2001 From: annegoldsack Date: Tue, 5 Nov 2024 15:28:38 +1000 Subject: [PATCH 3/4] additional amends --- document/00-master.adoc | 2 + document/02-metadata.adoc | 4 +- document/03-preamble.adoc | 10 +- document/06-common-tasks.adoc | 276 +++++++++++++++----------- document/52-annex-c-vocabularies.adoc | 55 +++++ 5 files changed, 226 insertions(+), 121 deletions(-) create mode 100644 document/52-annex-c-vocabularies.adoc diff --git a/document/00-master.adoc b/document/00-master.adoc index ee7ae39..6d85b90 100644 --- a/document/00-master.adoc +++ b/document/00-master.adoc @@ -30,4 +30,6 @@ include::50-annex-a-extended-examples.adoc[] include::51-annex-b-identifiers.adoc[] +include::52-annex-c-vocabularies.adoc[] + include::99-bibliography.adoc[] diff --git a/document/02-metadata.adoc b/document/02-metadata.adoc index 3c5e996..00d9313 100644 --- a/document/02-metadata.adoc +++ b/document/02-metadata.adoc @@ -7,14 +7,14 @@ |**Name** | Address Creation & Maintenance Standard |**Description** | How addresses should be assigned and maintained to support Australia’s addressing infrastructure |**Created** | 2024-09-01 -|**Modified** | 2024-10-09 +|**Modified** | 2024-11-05 |**Issued** | 0000-00-00 |**Creator** | https://linked.data.gov.au/org/icsm-addrwg[ICSM's Addressing Working Group] |**Publisher** | https://linked.data.gov.au/org/icsm[Intergovernmental Committee on Surveying & Mapping (ICSM)] (ICSM@ga.gov.au) |**Provenance** | This standard was created in 2024 by the ICSM Addressing Working Group after the publication of ISO's publication in 2023 of ISO19160-2 Assigning and maintaining addresses for objects in the physical world and in 2024 of ICSM's publication of its Address Model. This standard is a profile of the former and instructions in the production of data conformant to the latter. |**Status** | Draft |**Version** | 0.0.1 -|**Code Repository** | https://github.com/Spatial-Information-QLD/addr-creation-maintenance +|**Code Repository** | https://github.com/icsm-au/addr-creation-maintenance |**License** | https://creativecommons.org/licenses/by/4.0/[Creative Commons Attribution 4.0 International (CC BY 4.0)] |**Copyright** | © Intergovernmental Committee on Surveying & Mapping, 2024 |=== diff --git a/document/03-preamble.adoc b/document/03-preamble.adoc index 49fc8fd..132cca9 100644 --- a/document/03-preamble.adoc +++ b/document/03-preamble.adoc @@ -31,7 +31,7 @@ The following document defines the addressing model used for address records: [[access-point]] access point:: The position along a thoroughfare (road or water feature) where the public would normally access an address site. SOURCE: this standard -[[address]] address:: An address is structured information that allows the unambiguous determination of an object for purposes of identification and location (SOURCE ISO 19160-1:2015). The objects exist in the physical world (i.e. virtual objects are excluded) and can be outdoor (e.g. a building) or indoor (e.g. an office inside a building). SOURCE: this standard +[[address]] address:: An address is structured information that allows the unambiguous determination of an object for purposes of identification and location (SOURCE: <>). The objects exist in the physical world (i.e. virtual objects are excluded) and can be outdoor (e.g. a building) or indoor (e.g. an office inside a building). SOURCE: this standard [[addressable-object]] addressable object:: Object that may be assigned an address. SOURCE: <> @@ -47,6 +47,8 @@ The following document defines the addressing model used for address records: [[address-site]] address site:: a site for which an address is being assigned. SOURCE: <> +[[alternative-address]] alternative address:: an assigned address that refers to an alternative access point to an address site. Requires a preferred address to have been assigned. SOURCE: this standard + [[alternative-name]] alternative name:: a name that is an alternative name to another name for the same feature. SOURCE: <> [[dual-name]] dual name:: a name that consists of two official names that must be used together, usually one indigenous and one European (e.g. ‘Aoraki/Mount Cook’). SOURCE: <> @@ -60,14 +62,18 @@ The following document defines the addressing model used for address records: [[IRI]] IRI:: Internationalized Resource Identifiers, IRIs, are a sequence of characters from the Universal Character Set. SOURCE: <> +[[preferred-address]] preferred address:: the assigned address that is preferred for usage and refers to the main access point to an address site. SOURCE: this standard + [[primary-address-site]] primary address site:: an address site that is not contained within another address site. It may contain a sub-address site. SOURCE: <> [[profile]] profile:: set of one or more base standards or subsets of base standards, and, where applicable, the identification of chosen clauses, classes, options and parameters of those base standards, that are necessary for accomplishing a particular function. SOURCE: <> -[[sub-address]] sub-address:: #TODO: complete me#. SOURCE: <> +[[sub-address]] sub-address:: an address number element that refers to a sub-address site. SOURCE: This standard>> [[sub-address-site]] sub-address site:: an address site that is contained within a primary address site e.g. an apartment within a building SOURCE: <>. Sometimes referred to as a secondary address site. SOURCE: this standard +[[thoroughfare]] thoroughfare:: a road or named water feature from which an address site can be accessed. SOURCE: this standard + [[thoroughfare-address]] thoroughfare address:: an address that is assigned with reference to the thoroughfare it is accessed from, for example a road or water feature. SOURCE: this standard === Conformance diff --git a/document/06-common-tasks.adoc b/document/06-common-tasks.adoc index fac18a8..8b90966 100644 --- a/document/06-common-tasks.adoc +++ b/document/06-common-tasks.adoc @@ -6,30 +6,27 @@ This section describes the specific address information-related tasks that the p === Creator Tasks ==== Creating a new address +===== General address principles Addresses SHALL adhere to the <>, which in turn conforms with <>. -All address components SHALL be stored with lifecycle and provenance information, according to the https://linked.data.gov.au/def/lifecycle[lifecycle model]. +An address SHALL be unique. -===== General address principles +All addresses and address components SHALL be stored with lifecycle and provenance information, according to the https://linked.data.gov.au/def/lifecycle[lifecycle model]. Address creators SHALL allocate a https://linked.data.gov.au/def/address-classes[class] to each address, and assign the relevant address components according to that class. -Address creators SHALL use concepts from the relevant vocabularies to ensure data interoperability. - -An address SHALL be unique. - -An addressable object SHALL have at least one spatial geometry stored against it.Each address SHALL be assigned at least one geocode with coordinates. +Address creators SHALL use concepts from the relevant <> to ensure data interoperability. The relationship between a new address and any address(es) that it replaces SHALL be recorded. ===== Thoroughfare class addresses -Addresses in the https://linked.data.gov.au/def/address-classes/thoroughfare[thoroughfare class] specify a location by reference to a thoroughfare i.e. a road or water feature name. An address SHALL NOT include more than one thoroughfare name. +Addresses in the https://linked.data.gov.au/def/address-classes/thoroughfare[thoroughfare class] specify a location by reference to a <> i.e. a road or water feature name. An address SHALL NOT include more than one <> name. -All throughfare addresses SHALL comprise at a minimum the following components: +All <> SHALL comprise at a minimum the following components: -a. Address number elements -b. Thoroughfare name (road or water feature name ) and type elements +a. Address number elements (which MAY include sub-adddress elements) +b. Thoroughfare name (road or water feature name) and type elements c. Locality name d. State or territory name @@ -48,51 +45,52 @@ h. Indigenous country An address SHALL be assigned to an addressable object. -In instances where an address site has more than one point of access, alternative addresses may be created to reflect the additional access points. These additional addresses SHALL be stored against the same addressable object. +In instances where an <> has more than one point of access, <> may be created to reflect the additional access points. These additional addresses SHALL be stored against the same <>. *Address number* -An address SHALL be assigned a unique number in relation to the access throughfare. +An address SHALL be assigned a unique number in relation to the access <>. -The designation and form of an address number is crucial in enabling an address site to be readily located by emergency service responders and service delivery providers. +The designation and form of an address number is crucial in enabling an <> to be readily located by emergency service responders and service delivery providers. -An address number SHALL be assigned to each separately owned or occupied area of land, and each separately owned or occupied building or part of a building. The address number assignation method relates to the address class. For thoroughfare addresses, address numbers follow general and specific address class principles. +An address number SHALL be assigned to each separately owned or occupied area of land, and each separately owned or occupied building or part of a building. The address number assignation method relates to the https://linked.data.gov.au/def/address-classes[class]. For <>, address numbers follow general and specific https://linked.data.gov.au/def/address-classes[class] principles. *General address numbering principles* Address numbers SHALL be assigned prior to occupation and as early as practicable in the development process. -Address numbers SHALL be assigned according to the location of the point of access to the address site from the thoroughfare (road or water feature). +Address numbers SHALL be assigned according to the location of the point of access to the <> from the <> (road or water feature). Address number allocation SHALL ensure clear, logical and unambiguous numbering: -* Address numbers SHALL be sequential positive integers from lowest to highest, and continue for the entire length of the named road even when it continues across administrative boundaries. -* The datum point for address numbering SHOULD be at the commencement of the road from where access to that road is most common, or is planned to occur, at the point of naming. This SHALL take into account assignation of reserved numbering requirements in a staged development. +* Address numbers SHALL be sequential positive integers from lowest to highest, and continue for the entire length of the named <> even when it continues across administrative boundaries. * A number range SHALL NOT be assigned as an address number. Any existing ranges SHOULD be phased out. * An address number SHALL NOT be prefixed by alphabetical characters. -* Address sites SHALL be numbered using odd numbers on the left of the throughfare and even numbers on the right. +* <> SHALL be numbered using odd numbers on the left of the <> and even numbers on the right. * A lot number SHALL NOT be used in place of an address number. -* Where a road is renamed as a result of redesign or development, address sites SHALL be renumbered if required to ensure adherence to this standard. -* Where an area of rural numbering is reclassified as urban, previously assigned rural numbers SHOULD be retained if urban numbering requirements can be met for the infill addressing. +* For addresses that refer to a road: +** the datum point for address numbering SHOULD be at the commencement of the road from where access to that road is most common, or is planned to occur, at the point of naming. This SHALL take into account assignation of reserved numbering requirements in a staged development. +** Where a road is renamed as a result of redesign or development, <> SHALL be renumbered if required to ensure adherence to this standard. +** Where an area of <> is reclassified as urban, previously assigned rural numbers SHOULD be retained if <> requirements can be met for the infill addressing. Use of alpha suffixes:[[alpha-suffixes,use of alpha suffixes]] -* Where there are no addresses numbers available for an address site due to existing allocations, alpha suffixes SHALL be assigned to the base number; with the exception that address sites that share access SHOULD be treated as sub-address sites (see <>). -** Alpha suffixes SHALL start at A, be assigned incrementally in the same direction as the numbering of addresses on the throughfare, and SHALL NOT extend beyond E. +* Where there are no addresses numbers available for an <> due to existing allocations, alpha suffixes SHALL be assigned to the base number; with the exception that <> that share access SHOULD be treated as <> (see <>). +** Alpha suffixes SHALL start at A, be assigned incrementally in the same direction as the numbering of addresses on the <>, and SHALL NOT extend beyond E. ** Renumbering of the road is required where there are more than five additional address sites requiring numbering in this way. -** In instances where an existing address site uses the base number, this MAY be retained (i.e. not have a suffix), provided it is in order. +** In instances where an existing <> uses the base number, this MAY be retained (i.e. not have a suffix), provided it is in order. -*Urban address numbering* +*Urban address numbering[[urban_numbering,urban numbering]]* For addresses designated part of the https://linked.data.gov.au/def/address-classes/urban[urban address class], address numbers SHALL be reserved to meet potential future allocation needs, for example where there are unusually wide frontages or potential for infill development. -An address site on a corner SHALL be assigned both a number indicating the main point of access, and an address number on the other road assigned as an alternative address (if access exists), or be reserved for future development. +An <> on a corner SHALL be assigned both a number indicating the main point of access, and an address number on the other road assigned as an <> (if access exists), or be reserved for future development. -*Rural address numbering* +*Rural address numbering[[rural_numbering,rural numbering]]* For addresses designated part of the https://linked.data.gov.au/def/address-classes/rural[rural address class], address numbering SHALL be determined by dividing the distance in metres from the datum point to the access point by ten, then rounding to the nearest odd number on the left or even number on the right side of the road (rural numbering method). -Address numbers SHALL NOT exceed five digits – for roads over 1000km long, address numbering SHALL be restarted at a different datum point, preferably a town, natural feature or major intersection, with numbering in the same direction. +Address numbers SHALL NOT exceed five digits; for roads over 1000km long, address numbering SHALL be restarted at a different datum point, preferably a town, natural feature or major intersection, with numbering in the same direction. In the absence of an access point, a rural number within the range determined by the rural numbering method MAY be assigned. The rural number SHALL be reassigned if an access point is subsequently created. @@ -100,9 +98,9 @@ In areas with multiple address access points within the minimum step intervals o *Numbering for roads that cross both rural and urban areas* -If a road name continues across rural and urban extents, the rural numbering method SHOULD be utilised but may be varied as necessary in urban areas to ensure numbering remains logical and unique. +If a road name continues across rural and urban extents, the <> method SHOULD be utilised but may be varied as necessary in urban areas to ensure numbering remains logical and unique. -Where a highway crosses an urban area in which another local name is used, numbering SHALL relate to each named road, both in assignment methodology and extent. Rural numbering SHALL encompass distances including the sections with local names. +Where a highway crosses an urban area in which another local name is used, numbering SHALL relate to each named road, both in assignment methodology and extent. <> SHALL encompass distances including the sections with local names. *Water address numbering* @@ -116,21 +114,62 @@ For addresses designated part of the https://linked.data.gov.au/def/address-clas *Sub-address numbering[[sub_address_numbering,sub-address numbering]]* -Sub-address numbering SHALL be used for address sites contained within other address sites e.g. an apartment block or marina. A sub-address may utilise either the preffered or an alternative address for the parent site. +<> SHALL be used for <> contained within other address sites e.g. an apartment block or marina (<>). + +<> numbers SHALL be sequential positive integers from lowest to highest, expect when alpha characters are used according to the <>. A number range SHALL not be assigned as a <>. + +A <> number within a <> SHALL be unique regardless of https://linked.data.gov.au/def/subaddress-types[sub-address type] or building level. + +The sub-address number SHOULD be stored with the https://linked.data.gov.au/def/subaddress-types[sub-address type], although this does not have to be provided within a formatted address string. -The sub-address number SHOULD be stored with the https://linked.data.gov.au/def/subaddress-types[sub-address type], although this does not have to be provided within an address string. +The full address assigned to a <> SHALL refer to the common <> access and may utilise either the <> or an <> address for the <>. -A sub-address number SHALL be unique regardless of sub-address (unit) type or building level. +Within a formatted address string, the sub-address number precedes the address for the <>, and SHALL be formatted when used with a ‘/’ between the <> number and address number. -Within a formatted address string, the sub-address number precedes the address for the parent site, and SHALL be formatted when used with a ‘/’ between the sub-address number and address number. +*Multi-level sub-address numbering[[multi-level-sub-address-numbering,multi-level sub-address numbering]]* -*Thoroughfare name* +For multi-level buildings where <> need to be assigned, the <> number SHALL concate two parts: -*Roads* +* Alphanumeric characters to represent the level within the building, including a level type code and/or level number +** Level type codes: +//Maybe make a collection for these? +*** B for a https://linked.data.gov.au/def/building-level-types/basement[basement level] +*** G for a https://linked.data.gov.au/def/building-level-types/ground[ground level] +*** LG for a https://linked.data.gov.au/def/building-level-types/lower-ground-floor[lower-ground level] +*** M for a https://linked.data.gov.au/def/building-level-types/mezzaine[mezzanine level] +*** OD for a https://linked.data.gov.au/def/building-level-types/observation-deck[observation deck level] +*** P for a https://linked.data.gov.au/def/building-level-types/parking[parking level] +*** PD for a https://linked.data.gov.au/def/building-level-types/podium[podium level] +*** RT for a https://linked.data.gov.au/def/building-level-types/rooftop[rooftop level] +*** UG for a https://linked.data.gov.au/def/building-level-types/upper-ground[upper-ground level] +** Where there are multiple levels for a particular https://linked.data.gov.au/def/building-level-type[building level type], a number MAY be added after the level type code. +** Level numbers SHALL increase with height for all above ground levels +** Level numbers SHALL increase with depth for all below ground levels +** The https://linked.data.gov.au/def/building-level-types/ground[ground level] SHALL be assigned 'G' and SHALL NOT be assigned a '0' or '1' +* Two digits to uniquely refer to the <> on that level (between 01 and 99) +** To be allocated in logical sequence to each <> +** For <> 1 to 9, a preceding zero will be added +** In instances where insufficient numbers are available for all <> on a level, an alternative method that ensures unique unambiguous numbering may be used. + +Some examples include: + +* https://linked.data.gov.au/def/subaddress-types/unit[Unit] 1 on https://linked.data.gov.au/def/building-level-types/basement[basement level] 2 would be assigned a sub-address of B201 +* https://linked.data.gov.au/def/subaddress-types/shop[Shop] 4 on the https://linked.data.gov.au/def/building-level-types/ground[ground floor] would be assigned a sub-address of G04 +* https://linked.data.gov.au/def/subaddress-types/apartment[Apartment] 36 on https://linked.data.gov.au/def/building-level-types/level[level] 7 would be assigned a sub-address of 736 +* https://linked.data.gov.au/def/subaddress-types/unit[Unit] 5 on https://linked.data.gov.au/def/building-level-types/level[level] 23 would be assigned a sub-address of 2305 +* https://linked.data.gov.au/def/subaddress-types/carpark[Carpark] 83 on https://linked.data.gov.au/def/building-level-types/parking[parking level] 4 would be assigned a sub-address of P483 + +*Thoroughfare Naming* + +*Road Naming* + +A road name SHALL be associated with a road object. A road name SHALL be short, clear and unambiguous, and meet relevant national and state or territory naming principles. It SHALL NOT be offensive, racist, derogatory or demeaning. -All formed roads, including private roads, that are generally open to the public or to services SHALL be named. +All formed roads, including private roads, that are generally open to the public or to services SHALL be named. The exception to this is a short private road or cul-de-sac from which five or less <> can be accessed, and which has no proposal to be extended. In this instance it can be treated as a driveway and address numbers assigned in relation to the named road to which the driveway connects. + +A road name should not be applied to an unformed designated section of road. A named road SHALL include only one section navigable by vehicles (or pedestrians), unless separated by a median strip. @@ -146,13 +185,13 @@ The name element of a road name, regardless of road type, SHALL NOT be the same A road name SHOULD be enduring and changed only when necessary. A road name SHOULD be changed when redesign or redevelopment breaks the road extent into two or more segments so it is no longer contiguous. -*Water features* +*Water Feature Naming* -For address sites accessed from the water and not accessible from a road, the throughfare component SHALL refer to the water feature name. The name SHALL be acceptable to the applicable naming authority. +For address sites accessed from the water and not accessible from a road, the <> component SHALL refer to the water feature name. The name SHALL be acceptable to the applicable naming authority. -The water throughfare SHALL indicate the https://linked.data.gov.au/def/go-categories[type of geographical object]. +A water feature name SHALL be associated with a geographical name object. -*Locality* +The water <> SHALL indicate the https://linked.data.gov.au/def/go-categories[type of geographical object]. *Locality Naming* @@ -170,24 +209,12 @@ A locality name SHALL NOT be substituted with a promotional name, neighbourhood, A locality SHALL be assigned the geographical object category of https://linked.data.gov.au/def/go-categories/locality[Locality]. -*Locality Boundaries* - -Locality boundaries SHALL be clearly defined, not overlap, and be contiguous. A locality SHALL NOT cross a Local Government boundary, and SHALL be contained within, and not cross, state or territory boundaries. - -When defining a locality boundary, the following SHALL be considered: - -* A locality boundary SHOULD define a community of interest. -* Definite and distinguishable physical features or barriers SHALL be used where appropriate e.g. creeks, rivers, ridgelines, centres of roads, railways. -* The boundary SHOULD NOT, where possible, bisect properties in common ownership or land parcels. - -A locality boundary SHALL be enduring and changed only when necessary. However, these SHOULD be reviewed and amended where appropriate in areas subject to development. - ===== Landmark class addresses +*NB. THIS SECTION IS IN DRAFT AND SUBJECT TO CHANGE* Addresses in the https://linked.data.gov.au/def/address-classes/landmark[landmark class] specify a location by reference to a named landmark. A landmark is a relatively permanent feature of the man made landscape that has recognisable identity within a particular cultural context. All landmark addresses SHALL comprise the following components: -*NB. THIS SECTION IS IN DRAFT AMD SUBJECT TO CHANGE* a. Landmark name b. Locality (or city/town) name *N.B. What about areas outside of LGAs?* @@ -199,98 +226,113 @@ Landmark addresses SHALL NOT include an address number or thoroughfare name, but Addresses in the https://linked.data.gov.au/def/address-classes/postal[postal class] specify points of postal delivery which have no definite relation to the location of the recipient, such as post office boxes, overseas military addresses and general delivery offices. Postal addresses are covered by the AS/NZS ISO 19160.4:2023 standard and components are not covered in this standard. -==== Assignation of address geometry -All addresses SHALL be associated with an addressable object that has associated geometry, with, at a minimum, a geocode. Geocodes SHALL be associated with a https://linked.data.gov.au/def/geocode-types[geocode type]. +==== Assignation of geometry + +===== Address geometry +All addresses SHALL be associated with an <> that has associated geometry, with, at a minimum, a <>. Geocodes SHALL be associated with a https://linked.data.gov.au/def/geocode-types[geocode type]. -The coordinates of a geocode SHALL be accompanied by explanation of their coordinate reference system, such as the relevant EPSG code. +The coordinates of a <> SHALL be accompanied by explanation of their coordinate reference system, such as the relevant EPSG code, and an indication of the https://linked.data.gov.au/def/positional-accuracy[positional accuracy]. -Addresses SHOULD be associated with an addressable object that has associated area geometry. +Each <> SHALL preferably be assigned an individual geocode, or if not practicable, share a <> assigned to the <>, <>, or <>. + +Addresses SHOULD be associated with an <> that has associated area geometry. An address SHALL NOT be assigned against non contiguous areas, other than in relation to two areas within the same complex e.g. a unit and an allocated garage or parking space within the same complex. -==== Updating an existing address +===== Thoroughfare geometry +A <> associated with a road object or geographical name object, SHALL have associated geometry. + +A road object SHALL have, as a minimum, an approximal centre line geometry. The geometry SHALL be accompanied by explanation of the coordinate reference system, such as the relevant EPSG code. + +===== Locality geometry +Each locality will have a defined areal extent and boundary. The geometry SHALL be accompanied by explanation of the coordinate reference system, such as the relevant EPSG code. + +Locality boundaries SHALL be clearly defined, not overlap, and be contiguous. A locality SHALL NOT cross a Local Government boundary, and SHALL be contained within, and not cross, state or territory boundaries. +When defining a locality boundary, the following SHALL be considered: + +* A locality boundary SHOULD define a community of interest. +* Definite and distinguishable physical features or barriers SHALL be used where appropriate e.g. creeks, rivers, ridgelines, centres of roads, railways. +* The boundary SHOULD NOT, where possible, bisect properties in common ownership or land parcels. + +A locality boundary SHALL be enduring and changed only when necessary. However, these SHOULD be reviewed and amended where appropriate in areas subject to development. + +==== Updating an existing address When updating an existing address, address creators should adhere to the principles outlined in the section relating to creating a new address. Any amendments to an address should be recorded according to the <> and https://linked.data.gov.au/def/lifecycle[lifecycle] models, including lifecycle and provenance information. ==== Retiring an address - When an address is retired it SHALL be assigned a lifecycle status of https://linked.data.gov.au/def/lifecycle-stage-types/retired[retired], according to the https://linked.data.gov.au/def/lifecycle[lifecycle model]. +Links SHALL be kept between any retired address and any address that replaces it. + ==== Provision of address data Address creators SHALL make address data available for address aggregators and/or address users. An address SHALL NOT include personal information related to a person or organisation that owns or occupies the address site (or object) to which the address is assigned. === Aggregator Tasks + +==== Consolidation of address data +Addresses provided by address creators SHALL be recorded according to the <> and https://linked.data.gov.au/def/lifecycle[lifecycle] models, including lifecycle and provenance information. + +The address source SHALL be recorded, indicating the relevant https://linked.data.gov.au/def/naming-authority[address creator authority]. + ==== Validation of address components -Address aggregators SHALL validate address components against relevant vocabulary concepts to ensure data consistency. - -===== Vocabularies used for addresses -* Geographical object categories: https://linked.data.gov.au/def/go-categories -* Building level types: https://linked.data.gov.au/def/building-level-types -* Subaddress types: https://linked.data.gov.au/def/subaddress-types -* stateOrTerritory: https://linked.data.gov.au/dataset/asgsed3/STE -* countryName: https://linked.data.gov.au/def/countries -* Address classes: https://linked.data.gov.au/def/address-classes -* Address status types: https://linked.data.gov.au/def/address-status-type -* Lifecycle Stage Types: https://linked.data.gov.au/def/lifecycle-stage-types -* Naming authority: https://linked.data.gov.au/def/naming-authority -* Record access: https://linked.data.gov.au/def/record-access -* Geocode types: https://linked.data.gov.au/def/geocode-types -* Spatial capture method:: https://linked.data.gov.au/def/spatial-capture-method -* Address Geographic Name Types: https://linked.data.gov.au/def/address-geographic-name-types -* Address Part Types: https://linked.data.gov.au/def/addr-part-types - -===== Vocabularies used for roads -* Road name part types: https://linked.data.gov.au/def/road-name-part-types -* Road types: https://linked.data.gov.au/def/road-types -* Geographical Name Affix: https://linked.data.gov.au/def/gn-affix -* Naming authority: https://linked.data.gov.au/def/naming-authority -* Geographical object categories: https://linked.data.gov.au/def/go-categories -* Transport Infrastructure Types: https://linked.data.gov.au/def//transport-infrastructure-types -* Transport Infrastructure Sub Types: https://linked.data.gov.au/def//transport-infrastructure-sub-types -* Road surfaces: https://linked.data.gov.au/def/road-surfaces -* Surface capture method: https://linked.data.gov.au/def/surface-capture-method -* Road operational statuses: https://linked.data.gov.au/def/road-operational-statuses -* Road user access: https://linked.data.gov.au/def/road-user-access -* Road travel direction: https://linked.data.gov.au/def/road-travel-direction -* Road lane count: https://linked.data.gov.au/def/road-lane-count -* Road trafficability: https://linked.data.gov.au/def/road-trafficability -* Population zone: https://linked.data.gov.au/def/population-zone -* Road seasonality: https://linked.data.gov.au/def/road-seasonality -* Ground relationship: https://linked.data.gov.au/def/ground-relationship -* Road owner: https://linked.data.gov.au/def/road-owner -* Road maintainer: https://linked.data.gov.au/def/road-maintainer -* State controlled road indicator: https://linked.data.gov.au/def/scr-indicator -* LRRS indicator: https://linked.data.gov.au/def/lrrs-indicator -* Spatial capture method: https://linked.data.gov.au/def/spatial-capture-method -* Positional accuracy: https://linked.data.gov.au/def/positional-accuracy -* Road cadastral relationship: https://linked.data.gov.au/def/road-cadastral-relationship -* Lifecycle Stage Types: https://linked.data.gov.au/def/lifecycle-stage-types -* Record access: https://linked.data.gov.au/def/record-access -* Road geometry notes: https://linked.data.gov.au/def/road-geometry-notes - -===== Vocabularies used for geographic names (including locality) -* Geographical object categories: https://linked.data.gov.au/def/go-categories -* Geographical Name Affix: https://linked.data.gov.au/def/gn-affix -* Geographical names part types: https://linked.data.gov.au/def/gn-part-types -* Record access: https://linked.data.gov.au/def/record-access -* Naming authority: https://linked.data.gov.au/def/naming-authority -* Lifecycle Stage Types: https://linked.data.gov.au/def/lifecycle-stage-types +Address aggregators SHALL validate address components against relevant <> to ensure data consistency. ==== Digital equivalent address record Any address assigned to an object SHALL have a digital equivalent address record in the authoritative state and national address datasets. This record SHALL be updated whenever an address is assigned or changed. +The address source SHALL be clearly articulated, indicating the relevant https://linked.data.gov.au/def/naming-authority[address creator authority]. + === Distributor Tasks -==== Licence Provision +==== Provision of address data and products +Address distributors SHALL ensure attribute values correlate with relevant <> to ensure data consistency. + +The address source SHALL be clearly articulated, indicating the relevant https://linked.data.gov.au/def/naming-authority[address creator authority]. + +The https://linked.data.gov.au/def/lifecycle-stage-types[lifecycle stage] of the address SHALL be indicated. + +An address SHALL NOT include personal information related to a person or organisation that owns or occupies the address site (or object) to which the address is assigned. + +==== Licence provision Distributors SHALL specify the licences under which the address data is available and the terms and conditions for their use. -==== Metadata Provision +==== Metadata provision Distributors SHALL provide relevant metadata. +==== Address validation services +Validation services SHALL only include addresses provided from authoritative sources. + +Validation services SHALL only include results applicable to the relevant https://linked.data.gov.au/def/address-classes[address class(es)]. + === User Tasks ==== Address validation -Address data users SHALL validate addresses against authoritative address data. \ No newline at end of file +Address data users SHALL validate addresses against authoritative address data. + +==== Address signage +Signage enables address users to identify and locate <> on the ground. + +All signage should first and foremost comply with applicable standards, legislation and byelaws. + +===== Locality name signs +Signage indicating the full unnabreviated locality name SHOULD be prominently displayed at significant boundary interfaces, particularly common traffic entry points. + +===== Thoroughfare name signs +Signage indicating each road name SHALL be placed at each road intersection to clearly identify the road to which the name applies. This includes all named private roads, access ways, tracks and pedestrian-only roads. The sign should be easy to read, including at night. + +The road name SHALL be in full with the exception of: + +* The road type MAY be abbreviated using the alternative labels identified in the https://linked.data.gov.au/def/road-types[road types vocabulary]. +* 'Mount' MAY be abbreviated to 'Mt' if required to keep sign length manageable. + +Road name signs SHOULD include address number ranges applicable to the segment of road. The sign SHOULD physically indicate the associated road direction. The address numbers on the sign SHALL be aligned with the physical order of the numbering on the ground, from closest to furthest, even if thisreversed the number range. + +Signage also SHOULD indicate any access restrictions, and MAY identify if a road is privately owned. + +===== Address number signs +Every occupied <> SHALL display address number signage that clearly identifies the associated <> with the official allocated address number, and, if applicable, <>. Signage SHALL be unambiguous, and clearly legible from where the <> is normally accessed. + diff --git a/document/52-annex-c-vocabularies.adoc b/document/52-annex-c-vocabularies.adoc new file mode 100644 index 0000000..e5d6772 --- /dev/null +++ b/document/52-annex-c-vocabularies.adoc @@ -0,0 +1,55 @@ +[[AnnexC]] +== Annex C: Relevant Vocabularies + +=== Vocabularies relevant to addresses +* Address classes: https://linked.data.gov.au/def/address-classes +* Address Geographic Name Types: https://linked.data.gov.au/def/address-geographic-name-types +* Address Part Types: https://linked.data.gov.au/def/addr-part-types +* Address status types: https://linked.data.gov.au/def/address-status-type +* Building level types: https://linked.data.gov.au/def/building-level-types +* countryName: https://linked.data.gov.au/def/countries +* Geocode types: https://linked.data.gov.au/def/geocode-types +* Geographical object categories: https://linked.data.gov.au/def/go-categories +* Lifecycle Stage Types: https://linked.data.gov.au/def/lifecycle-stage-types +* Naming authority: https://linked.data.gov.au/def/naming-authority +* Record access: https://linked.data.gov.au/def/record-access +* Spatial capture method:: https://linked.data.gov.au/def/spatial-capture-method +* stateOrTerritory: https://linked.data.gov.au/dataset/asgsed3/STE +* Subaddress types: https://linked.data.gov.au/def/subaddress-types + +=== Vocabularies relevant to roads +* Geographical Name Affix: https://linked.data.gov.au/def/gn-affix +* Geographical object categories: https://linked.data.gov.au/def/go-categories +* Ground relationship: https://linked.data.gov.au/def/ground-relationship +* Lifecycle Stage Types: https://linked.data.gov.au/def/lifecycle-stage-types +* LRRS indicator: https://linked.data.gov.au/def/lrrs-indicator +* Naming authority: https://linked.data.gov.au/def/naming-authority +* Population zone: https://linked.data.gov.au/def/population-zone +* Positional accuracy: https://linked.data.gov.au/def/positional-accuracy +* Record access: https://linked.data.gov.au/def/record-access +* Road cadastral relationship: https://linked.data.gov.au/def/road-cadastral-relationship +* Road geometry notes: https://linked.data.gov.au/def/road-geometry-notes +* Road lane count: https://linked.data.gov.au/def/road-lane-count +* Road maintainer: https://linked.data.gov.au/def/road-maintainer +* Road name part types: https://linked.data.gov.au/def/road-name-part-types +* Road operational statuses: https://linked.data.gov.au/def/road-operational-statuses +* Road owner: https://linked.data.gov.au/def/road-owner +* Road seasonality: https://linked.data.gov.au/def/road-seasonality +* Road surfaces: https://linked.data.gov.au/def/road-surfaces +* Road trafficability: https://linked.data.gov.au/def/road-trafficability +* Road travel direction: https://linked.data.gov.au/def/road-travel-direction +* Road types: https://linked.data.gov.au/def/road-types +* Road user access: https://linked.data.gov.au/def/road-user-access +* Spatial capture method: https://linked.data.gov.au/def/spatial-capture-method +* State controlled road indicator: https://linked.data.gov.au/def/scr-indicator +* Surface capture method: https://linked.data.gov.au/def/surface-capture-method +* Transport Infrastructure Sub Types: https://linked.data.gov.au/def//transport-infrastructure-sub-types +* Transport Infrastructure Types: https://linked.data.gov.au/def//transport-infrastructure-types + +=== Vocabularies relevant to geographic names (including locality) +* Geographical Name Affix: https://linked.data.gov.au/def/gn-affix +* Geographical names part types: https://linked.data.gov.au/def/gn-part-types +* Geographical object categories: https://linked.data.gov.au/def/go-categories +* Lifecycle Stage Types: https://linked.data.gov.au/def/lifecycle-stage-types +* Naming authority: https://linked.data.gov.au/def/naming-authority +* Record access: https://linked.data.gov.au/def/record-access \ No newline at end of file From 960350e2f739f0bdb7df0fddfea7e720a9d03c6a Mon Sep 17 00:00:00 2001 From: annegoldsack Date: Tue, 5 Nov 2024 16:07:46 +1000 Subject: [PATCH 4/4] table creation --- document/06-common-tasks.adoc | 32 +++++++++++++++++++------------- 1 file changed, 19 insertions(+), 13 deletions(-) diff --git a/document/06-common-tasks.adoc b/document/06-common-tasks.adoc index 8b90966..a1f2157 100644 --- a/document/06-common-tasks.adoc +++ b/document/06-common-tasks.adoc @@ -128,25 +128,31 @@ Within a formatted address string, the sub-address number precedes the address f *Multi-level sub-address numbering[[multi-level-sub-address-numbering,multi-level sub-address numbering]]* +//Maybe make a collection for these? +.Level type codes +[width="50%",cols="2,4",options="header"] +|========================================================= +|Code[[Code]] |Level Type + +|B|https://linked.data.gov.au/def/building-level-types/basement[Basement level] +|G|https://linked.data.gov.au/def/building-level-types/ground[Ground level] +|LG|https://linked.data.gov.au/def/building-level-types/lower-ground-floor[Lower-ground level] +|M|https://linked.data.gov.au/def/building-level-types/mezzaine[Mezzanine level] +|OD|https://linked.data.gov.au/def/building-level-types/observation-deck[Observation deck level] +|P|https://linked.data.gov.au/def/building-level-types/parking[Parking level] +|PD|https://linked.data.gov.au/def/building-level-types/podium[Podium level] +|RT|https://linked.data.gov.au/def/building-level-types/rooftop[Rooftop level] +|UG|https://linked.data.gov.au/def/building-level-types/upper-ground[Upper-ground level] +|========================================================= + For multi-level buildings where <> need to be assigned, the <> number SHALL concate two parts: -* Alphanumeric characters to represent the level within the building, including a level type code and/or level number -** Level type codes: -//Maybe make a collection for these? -*** B for a https://linked.data.gov.au/def/building-level-types/basement[basement level] -*** G for a https://linked.data.gov.au/def/building-level-types/ground[ground level] -*** LG for a https://linked.data.gov.au/def/building-level-types/lower-ground-floor[lower-ground level] -*** M for a https://linked.data.gov.au/def/building-level-types/mezzaine[mezzanine level] -*** OD for a https://linked.data.gov.au/def/building-level-types/observation-deck[observation deck level] -*** P for a https://linked.data.gov.au/def/building-level-types/parking[parking level] -*** PD for a https://linked.data.gov.au/def/building-level-types/podium[podium level] -*** RT for a https://linked.data.gov.au/def/building-level-types/rooftop[rooftop level] -*** UG for a https://linked.data.gov.au/def/building-level-types/upper-ground[upper-ground level] +. Alphanumeric characters to represent the level within the building, including a level type code (see <>) and/or level number ** Where there are multiple levels for a particular https://linked.data.gov.au/def/building-level-type[building level type], a number MAY be added after the level type code. ** Level numbers SHALL increase with height for all above ground levels ** Level numbers SHALL increase with depth for all below ground levels ** The https://linked.data.gov.au/def/building-level-types/ground[ground level] SHALL be assigned 'G' and SHALL NOT be assigned a '0' or '1' -* Two digits to uniquely refer to the <> on that level (between 01 and 99) +. Two digits to uniquely refer to the <> on that level (between 01 and 99) ** To be allocated in logical sequence to each <> ** For <> 1 to 9, a preceding zero will be added ** In instances where insufficient numbers are available for all <> on a level, an alternative method that ensures unique unambiguous numbering may be used.