From 9258f685d81e01c650e03454a68f93743c916f61 Mon Sep 17 00:00:00 2001 From: Nicholas Car Date: Wed, 9 Oct 2024 22:56:21 +1000 Subject: [PATCH] many updates --- document/00-master.adoc | 6 +- document/03-preamble.adoc | 39 ++ document/04-introduction.adoc | 8 +- document/07-good-practices-old.adoc | 382 ++++++++++++++++++ document/07-good-practices.adoc | 382 +----------------- document/08-governance-framework-old.adoc | 159 ++++++++ document/08-governance-framework.adoc | 1 - document/09-reqs-recs.adoc | 66 +++ document/50-annex-a-extended-examples.adoc | 0 ...fiers.adoc => 51-annex-b-identifiers.adoc} | 4 +- 10 files changed, 661 insertions(+), 386 deletions(-) create mode 100644 document/07-good-practices-old.adoc create mode 100644 document/08-governance-framework-old.adoc create mode 100644 document/09-reqs-recs.adoc create mode 100644 document/50-annex-a-extended-examples.adoc rename document/{50-annex-a-identifiers.adoc => 51-annex-b-identifiers.adoc} (98%) diff --git a/document/00-master.adoc b/document/00-master.adoc index 697f7b3..32f93f7 100644 --- a/document/00-master.adoc +++ b/document/00-master.adoc @@ -17,8 +17,12 @@ include::07-good-practices.adoc[] include::08-governance-framework.adoc[] +include::09-reqs-recs.adoc[] + :sectnums!: -include::50-annex-a-identifiers.adoc[] +include::50-annex-a-extended-examples.adoc[] + +include::51-annex-b-identifiers.adoc[] include::99-bibliography.adoc[] diff --git a/document/03-preamble.adoc b/document/03-preamble.adoc index a3137ad..e0feaa0 100644 --- a/document/03-preamble.adoc +++ b/document/03-preamble.adoc @@ -88,6 +88,45 @@ For process and information to be conformant with this standard, the imperatives Address information created following processes outlined in this standard _MUST_ conform to the <> with conformance to it tested as per it's https://linked.data.gov.au/def/addr#AnnexB[Annex B: Validation] section. +=== Namespaces + +Namespaces, in this document's context, are managed <> which allow further IRIs to be created within their scope. Namespaces are allocated to macro data objects and provide IRIs for all the micro data objects within that object. + +For example, the IRI for the <> is `+https://linked.data.gov.au/def/addr+` and the namespace of `+https://linked.data.gov.au/def/addr/+` (the Address Model's IRI + `/`) allows for IRIs to be created for elements within the model such as one for the `AddressableObject` class which is `+https://linked.data.gov.au/def/addr/AddressableObject+`. + +When used in some forms of data and human-readable text, IRIs can either be written in full or in a shortened form using prefixes for known namespace. For example, the `Addresable Object` mentioned above can be written in full like this: + +`+https://linked.data.gov.au/def/addr/AddressableObject+` + +or in prefixed form with the prefix `addr` for the namespace `+https://linked.data.gov.au/def/addr/+` like this: + +`addr:AddressableObject` + +The prefixed namespaces used in this document are: + +[width=100%, frame=none, grid=none, cols="1,5,4"] +|=== +|Prefix | Namespace | Description + +| `*addr*` | `*+https://linked.data.gov.au/def/addr/+*` | <> +| `*addrcm*` | `*+https://linked.data.gov.au/def/addrcm/+*` | *This Document* +| `addreq` | `+https://linked.data.gov.au/def/addrcm-req/+` | https://linked.data.gov.au/def/addrcm-req[Address Creation & Maintenance Requirements Vocabulary] +| `als` | `+https://linked.data.gov.au/def/address-lifecycle-stage-type/+` | https://linked.data.gov.au/def/lifecycle-stage-types[Address Lifecycle Stage Types vocabulary] +| `apt` | `+https://linked.data.gov.au/def/address-part-type/+` | https://linked.data.gov.au/def/addr-part-types[Address Part Types vocabulary] +| `asgsed3` | `+https://linked.data.gov.au/dataset/asgsed3/+` | https://linked.data.gov.au/dataset/asgsed3[Australian Statistical Geographies Standard Dataset, Release 3] +| `cn` | `+https://linked.data.gov.au/def/cn/+` | https://linked.data.gov.au/def/cn[Compound Naming Model] +| `ex` | `+http://example.com/+` | Generic examples +| `geo` | `+http://www.opengis.net/ont/geosparql#+` | https://docs.ogc.org/is/22-047r1/22-047r1.html[OGC GeoSPARQL] +| `gt` | `+http://www.opengis.net/ont/geocode-types/+` | https://linked.data.gov.au/def/geocode-types[Geocode types vocabulary] +| `ls` | `+https://linked.data.gov.au/def/lifecycle/+` | https://linked.data.gov.au/def/lifecycle[Lifecycle Model] +| `owl` | `+http://www.w3.org/2002/07/owl#+` | https://www.w3.org/TR/owl2-overview/[Web Ontology Language ontology] +| `rdf` | `+http://www.w3.org/1999/02/22-rdf-syntax-ns#+` | https://www.w3.org/TR/rdf-concepts/[The RDF Concepts Vocabulary] +| `rdfs` | `+http://www.w3.org/2000/01/rdf-schema#+` | https://www.w3.org/TR/rdf12-schema/[RDF Schema ontology] +| `sdo` | `+https://schema.org/+` | https://schema.org[schema.org model] +| `skos` | `+http://www.w3.org/2004/02/skos/core#+` | https://www.w3.org/TR/skos-reference/[Simple Knowledge Organization System (SKOS) ontology] +| `time` | `+http://www.w3.org/2006/time#+` | https://www.w3.org/TR/owl-time/[Time Ontology in OWL] +| `xsd` | `+http://www.w3.org/2001/XMLSchema#+` | https://www.w3.org/TR/xmlschema-2/[XML Schema Definitions ontology] +|=== //// === Notation diff --git a/document/04-introduction.adoc b/document/04-introduction.adoc index 0e3bd7c..933068b 100644 --- a/document/04-introduction.adoc +++ b/document/04-introduction.adoc @@ -1,3 +1,9 @@ == Introduction -This is a placeholder \ No newline at end of file +This is a placeholder + +* abstract +* purpose +* history +* big picture +* doc structure \ No newline at end of file diff --git a/document/07-good-practices-old.adoc b/document/07-good-practices-old.adoc new file mode 100644 index 0000000..cbb9f3d --- /dev/null +++ b/document/07-good-practices-old.adoc @@ -0,0 +1,382 @@ +== Good Practice for assigning and maintaining addresses + +=== General + +==== Objectives + +===== Requirement 1. /req/goodPractice/general/objectives +A good practice shall specify one or more objectives for which addresses are assigned and shall be guided by these objectives. +This standard specifies requirements for address assignment in Australia to enable each address to be readily and unambiguously identified and located. +Objectives of the standard are: + Localities can be uniquely and clearly identified + Roads and other access thoroughfares can be uniquely and clearly identified and located + Assigned addressing numbering ensures addresses can be uniquely and clearly identified and located + Signage ensures assigned addresses can be readily identified and located +These objectives are to apply to all addressable locations throughout Australia, including indigenous communities and private communities such as mining towns and retirement villages. +It is noted that addresses previously confirming to AS/NZS 2819:2011 should meet this standard. Addresses created prior to AS/NZS 2819:2011 may not adhere to requirements as AS/NZS 4819:2011 explicitly noted that the standard was not to be applied retrospectively. + +===== Recommendation 1. /rec/goodPractice/general/objectivesforPublicGood +An objective should specify that the assignment and maintenance of addresses is done with the purpose of benefitting governance and society and thereby achieving public good. +Making address assignment and maintenance data open benefits governance and society by enhancing transparency, facilitating efficient urban planning, infrastructure development, emergency response, and ensuring equitable access to essential services, ultimately contributing to the public good. + +==== Context + +===== Requirement 2. /req/goodPractice/general/context +A good practice shall specify the context in which the address assignment and maintenance takes place and shall be guided by this context. +When new housing, business complexes, or other types of development occur, local government are responsible for assigning and maintaining addresses for their jurisdiction. However, for Australian Capital Territory (ACT) and Northern Territory, the role is fulfilled by the territory government. +State and territory governments aggregate these addresses into authoritative jurisdictional datasets. Data products and services are then distributed through various channels, including to the national data provider. PSMA Australia Limited (a public company owned by the nine governments of Australia; trading as Geoscape Australia) collate data at the national level. + +==== Conceptual Model + +===== Requirement 3. /req/goodPractice/general/conceptualModel +A good practice shall specify the conceptual model for the classes (types) of addresses assigned and maintained through the good practice. This includes a description of the address reference system, i.e., a set of address components and the rules for their combination into addresses. +Australia is currently developing a national addressing model. Review is being taken of use of the Queensland conceptual model as a national model: https://linked.data.gov.au/def/addr +• Address Model: Address Model +• Roads model: Roads Model +• Geographical Names model: Geographical Names Model +• Compound naming model: Compound Naming Model +• Cadastral model: Cadastral Model +• Lifecycle model: Lifecycle Model + +===== Recommendation 2. /rec/goodPractice/general/ISO19160-1Profile +The conceptual model that describes classes (types) of addresses assigned and maintained through the good practice should conform to ISO 19160-1:2015. +NOTE 1 Amongst others, ISO 19160-1:2015 requires that a conformant address model clearly specifies how the position of an address is represented in the model. ISO 19160-1:2015 provides two ways for doing this: 1) an address has coordinates to specify its position; 2) the position of the address is inferred from the addressed object. [SOURCE: ISO 19160-1:2015, 6.1] +NOTE 2 Postal addresses are defined and described in ISO 19160-4:2017, a profile of ISO 19160-1:2015. +EXAMPLE 14 The draft NZ profile of ISO 19160-1:2015 describes its conformance to ISO 19160-1:2015. The NZ profile defines six address classes: Thoroughfare, Water, Service Delivery, Rural Post Delivery, Thoroughfare4819, and Water4819. New addresses (excluding NZ Post addresses for service delivery and rural post delivery) quality assured by the LINZ address team are assessed against the Thoroughfare4819 and Water4819 classes, and these classes align with the requirements in AS/NZS 4819:2011. + +===== Recommendation 3. /rec/goodPractice/general/intellectualPropertyRights +A good practice should specify to whom the intellectual property rights of the address assignment method and the address data belong. At the least, government organizations should have free access to the address data for services to ensure the health, safety and welfare of the public. +TBC + +==== License + +===== Requirement 4. /req/goodPractice/general/license +A good practice shall specify the licences under which the address data is available and the terms and conditions for their use. Different licenses may apply for different users. + +===== National + +Australia – The national address dataset is released quarterly under a modified Creative Commons Attribution 4.0 International license (CC BY 4.0), which adds a restriction relating to the use of the open G-NAF for the sending of mail . + +===== Jurisdictions + +====== Australian Capital Territory + +ACT - https://creativecommons.org/licenses/by/3.0/au/deed.en + +====== New South Wales + +New South Wales – open data service? + +====== Northern Territory + +Northern Territory - Addresses are managed by the Survey Branch of the Department of Infrastructure, Planning and Logistics. [Cannot find data on https://data.nt.gov.au/] + +====== Queensland + +Queensland – Addresses are available as open data through QSpatial, licensed under a Creative Commons - Attribution 4.0 International licence. https://creativecommons.org/licenses/by/4.0/ + +====== South Australia + +South Australia - [Cannot find data other than rural address locations in LocationSAMapViewer] + +====== Tasmania + +Tasmania – Addresses are available through theList, licensed under a Creative Commons licence. https://creativecommons.org/licenses/by/3.0/au/deed.en + +====== Victoria + +Victoria – Addresses are available as open data through VicMap, licensed under a Creative Commons - Attribution 4.0 International licence. https://creativecommons.org/licenses/by/4.0/ + +====== Western Australia + +Western Australia – Subscription data? + +===== Recommendation 4. /rec/goodPractice/general/facilitateAssignment +A good practice should specify a method for assigning values to address components that could be automated to speed up or facilitate address assignment and maintenance. +EXAMPLE 19 AS/NZS 4819:2011, Rural and urban addressing, contains a clause for addressing rural properties based on the measured distance along the road, from a defined datum point, the accessway of the property is, with odd numbers on the left side of the road and even numbers on the right. +Use of vocabularies +• Address alias types: https://linked.data.gov.au/def/address-alias-type +• Address classes: https://linked.data.gov.au/def/address-classes +• Address status types: https://linked.data.gov.au/def/address-status-type +• Geocode types: https://linked.data.gov.au/def/geocode-types +• Level types: https://linked.data.gov.au/def/level-types +• Record access: https://linked.data.gov.au/def/record-access +• Sub-address types: https://linked.data.gov.au/def/subaddress-types +• Information source: https://linked.data.gov.au/def/source +• Ground relationship: https://linked.data.gov.au/def/ground-relationship +• LRRS indicator: https://linked.data.gov.au/def/lrrs-indicator +• 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 classifications: https://linked.data.gov.au/def/road-classifications +• 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 sub-classes: https://linked.data.gov.au/def/road-sub-classes +• Road suffixes: https://linked.data.gov.au/def/road-suffixes +• 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 +• Information source: https://linked.data.gov.au/def/source +• Geographical names part types: https://linked.data.gov.au/def/gn-part-types +• Geographical name statuses: https://linked.data.gov.au/def/gn-statuses +• Geographical objects categories vocabulary: https://linked.data.gov.au/def/go-categories + +==== Communication Through Physical Identifiers + +===== Requirement 5. /req/goodPractice/general/communicationThroughPhysicalIdentifiers +A good practice shall specify how addresses will be communicated through physical identifiers. +EXAMPLE 26 Addresses are communicated by street name signs on street corners and number signs on buildings. +EXAMPLE 27 AS/NZS 4819:2011, Rural and urban addressing, specifies that “it is desirable that the possible range and direction of numbers be included on the road name sign”. +To support emergency services, street numbers shall be visible from the access point to the address site. + +===== Recommendation 5. /rec/goodPractice/general/keepingAddressDataInSynch +A good practice should specify a method for keeping addresses in the physical world in synch with address data. + +TBC + +=== Principles + +==== Addressing principles + +===== Recommendation 6. /rec/goodPractice/principles/addressing/unambiguity +An address shall be assigned to an addressable object in the physical world so that it allows the unambiguous determination of the object for purposes of identification and location (ISO 19160-1:2015). +NOTE 1 The position of an address can be represented in two ways: 1) The position is specified by coordinates in the ‘position’ attribute. 2) The position is inferred from the addressed object. See 6.1 in ISO 19160-1:2015. +A thoroughfare address shall be assigned that conforms to the list of mandatory components to enable unambiguity, and enable it to be readily located. + +===== Sustainable Assignment Method + +===== Requirement 6. /req/goodPractice/principles/addressing/sustainableAssignmentMethod +Addressing shall be sustainable in the sense that additional addresses can be added without breaking the consistency of the address assignment method of existing addresses. +EXAMPLE 4 Leaving spaces between numbers when addresses are initially assigned makes it possible to assign additional addresses later when densification takes place. Alternatively, a number can be assigned based on the distance from an intersection of origin of the street. + +===== Piloting Assignment Method + +===== Requirement 7. /req/goodPractice/principles/addressing/pilotingAssignmentMethod +The assignment method shall be piloted or tested before rolling it out on a larger scale. +TBC + +===== Device Independence + +===== Requirement 8. /req/goodPractice/principles/addressing/deviceIndependence +Unambiguous location of the object shall be possible without requiring the use of a digital device. +This requirement is necessitated, for example, in the case of an emergency when an object needs to be identified and located in the absence of connectivity (e.g., through signage when standing in front of it). +EXAMPLE 5 During the 2019-20 Australian wildfires there was widespread loss of connectivity due to direct fire damage to telecommunications infrastructure. This resulted in a prolonged loss of internet access to location information [e.g., address] which hampered firefighters who had to rely on radio (verbal) communication. + +Address elements in reverse allow gradually pinpointing of address +State à Locality à Road / Waterway à Number + +An address shall be unique +A sub address number shall be unique regardless of subaddress (unit) type or building level +An address shall be assigned a unique number in relation to the access throughfare +An address shall not contain two road names +Each address shall be assigned at least one geocode with coordinates + +===== No Personal Information + +===== Requirement 9. /req/goodPractice/principles/addressing/noPersonalInformation +An address shall not include information about an individual or organization, owning the object to which it is assigned, or living and/or working at the object to which the address is assigned. +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. + +===== Dimensions Congruent With Objectives + +===== Requirement 10. /req/goodPractice/principles/addressing/dimensionsCongruentWithObjectives +Addresses shall be of an address class with dimensions congruent with the context in which they are assigned and maintained, and with the objectives for which they are assigned and maintained. +TBC + +===== Suitable Components + +===== Requirement 11. /req/goodPractice/principles/addressing/suitableComponents +The address components of an address class shall be suitable to meet the objectives for which that class is designed. +Each address shall be assigned a class as in https://linked.data.gov.au/def/address-classes, which use the components as laid out below. All addresses will be associated with an addressable object that has associated geometry, with, at a minimum, a geocode. Geocodes will be associated with a geocode type from https://linked.data.gov.au/def/geocode-types. All address components will be stored with lifecycle and provenance information. +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 . + +====== Thoroughfare + +Addresses in the Thoroughfare class specify a location by reference to a thoroughfare i.e. a road or water feature name. +All throughfare addresses shall comprise at a minimum the following components: +(a) Address number elements +(b) Thoroughfare name (road or water feature name ) and type elements +(c) Locality name +(d) State or territory name +The combination of these four components shall create a unique address, which reflects the point of access to the address site. +An address may also include the following additional components: +(a) Address site name +(b) Building name +(c) Landmark name +(d) Sub-address type +(e) Level type and number +(f) Postcode +(g) Country +(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. +An addressable object shall have at least one spatial geometry stored against it. + +======= Address number + +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. + +======= 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 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. + A number range shall not be assigned as an address number. And existing ranges phased out. + A primary address number shall not be prefixed by alphabetical characters. + Primary 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 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. + 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. + +======= Urban address numbering + +For addresses designated part of the 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. + +======= Rural address numbering + +For addresses designated part of the 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. +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 7.2.1.1.1.1. + +======= 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. +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. + +======= Water address numbering + +Addresses fall under the class of water if the site cannot be accessed from a road, and is instead accessed from a water feature or island. +For addresses designated part of the inlet address class, inlet or bay address numbering uses the distance in metres from a datum point at one end of the inlet or bay, divided by ten, and rounded to the nearest number. +For addresses designated part of the island address class, numbering uses the distance in metres clockwise from a datum point, divided by ten, and rounded to the nearest number. +For addresses designated part of the 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 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. +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. +The sub-address number should be stored with the sub-address type from https://linked.data.gov.au/def/subaddress-types, although this does not have to be provided within an address string. + +======= Thoroughfare name + +======== Roads + +An address shall not include more than one road name. +A road name shall be short, clear and unambiguous, and meet national 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 . +A named road shall include only one section navigable by vehicles (or pedestrians), unless separated by a median strip. +A road shall only have one name, other than part of a highway that is assigned a local name where it passes through a town or city. +An unbroken section of road crossing an administrative boundary shall retain the same name. +A road name shall consist of a name element followed by a road type. The accepted road types are in https://linked.data.gov.au/def/road-types. 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 should refer to https://linked.data.gov.au/def/road-suffixes. +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. +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 + +For address sites accessed from the water and not accessible from a road, the throughfare component should refer to the water feature name. The name shall be acceptable to the applicable naming authority. +The water throughfare should indicate the type of geographical object from https://linked.data.gov.au/def/go-categories. + +======= 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. +A locality name should not be similar in spelling or sound to any other locality name with the country. +A dual or alternative name shall not be assigned to a locality. +A locality name should be enduring and changed only when necessary. +A locality name should not be substituted with a promotional name , neighbourhood, or regional name in an address. +A locality shall be assigned the geographical object category of https://linked.data.gov.au/def/go-categorieslocality. + +======== Boundaries + +Locality boundaries shall be clearly defined, not overlap, and be contiguous. A locality should not cross a Local Government boundary, and should be contained within, and not cross, state or territory boundaries. +When defining a locality boundary, the following should 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. + 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. + +======= Landmark + +Addresses in the 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 . +All landmark addresses shall comprise the following components: +(a) Landmark Name +(b) Locality (or city/town) name +(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. + +====== Postal + +Addresses in the 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 will follow the AS/NZS ISO 19160.4:2023 standard and components are not covered in this profile. + +==== Address Data Principles + +===== Represents Address In Physical World + +===== Requirement 12. /req/goodPractice/principles/addressData/representsAddressInPhysicalWorld +Address data shall represent the addresses assigned to objects in the physical world. +TBC + +===== Interoperability + +===== Requirement 13. /req/goodPractice/principles/addressData/interoperability +Address data shall be interoperable between public administration systems, such as the cadastre, population register or urban information systems. +TBC + +===== Data Maintenance + +===== Requirement 14. /req/goodPractice/principles/addressData/dataMaintenance +Address data shall be maintained through processes and systems that consider general purpose data management principles, as well as specific requirements due to the geospatial nature of address data. +An address shall be recorded with the location coordinates for the point or access from the thoroughfare to which it is addressed. +The recording of an alternative address shall enable it to be readily distinguished from the related primary address. +The recording of a sub-address and the recording of its primary address shall enable them to be readily related to each other. +Road and water feature names shall be recorded in relation to the localities they pass through. +Locality names shall be recorded in relation to the state/territory within which it is located. +Information about address components that are obsolete shall be retained within lifecycle information including dates. +The relationship between a new address and any address(es) that it replaces shall be recorded. + +===== Digital Maintenance + +===== Requirement 15. /req/goodPractice/principles/addressData/digitalMaintenance +In the case of digital address data, the data shall be maintained in an address data management system with appropriate software solutions, such as spatial database management systems and/or geographic information systems. +TBC + +===== Recommendation 7. /rec/goodPractice/principles/addressing/equivalentDigitalRecord + +===== Recommendation 8. /rec/goodPractice/principles/addressing/updateAddressData + +===== Recommendation 9. /rec/goodPractice/principles/addressData/conformsToISO19160-1 +Address data should conform to ISO 19160-1:2015, or a profile thereof. +TBC + +===== Recommendation 10. /rec/goodPractice/principles/addressData/conformsToISO19160-4 +For postal addressing, address data should conform to ISO 19160-4:2017, or a profile thereof. +TBC + +===== Recommendation 11. /rec/goodPractice/principles/addressData/conformsToISO19160-3 +The quality of address data should be described conformant to ISO 19160-3:2020, or a profile thereof. +TBC + +===== Recommendation 12. /rec/goodPractice/principles/addressData/sharing +In the case of digital address data, the data should be shared through address retrieval solutions that preserve and maintain data integrity, e.g., through spreadsheets or APIs. +TBC diff --git a/document/07-good-practices.adoc b/document/07-good-practices.adoc index cbb9f3d..d25dc9a 100644 --- a/document/07-good-practices.adoc +++ b/document/07-good-practices.adoc @@ -1,382 +1,2 @@ -== Good Practice for assigning and maintaining addresses +== Good Practices -=== General - -==== Objectives - -===== Requirement 1. /req/goodPractice/general/objectives -A good practice shall specify one or more objectives for which addresses are assigned and shall be guided by these objectives. -This standard specifies requirements for address assignment in Australia to enable each address to be readily and unambiguously identified and located. -Objectives of the standard are: - Localities can be uniquely and clearly identified - Roads and other access thoroughfares can be uniquely and clearly identified and located - Assigned addressing numbering ensures addresses can be uniquely and clearly identified and located - Signage ensures assigned addresses can be readily identified and located -These objectives are to apply to all addressable locations throughout Australia, including indigenous communities and private communities such as mining towns and retirement villages. -It is noted that addresses previously confirming to AS/NZS 2819:2011 should meet this standard. Addresses created prior to AS/NZS 2819:2011 may not adhere to requirements as AS/NZS 4819:2011 explicitly noted that the standard was not to be applied retrospectively. - -===== Recommendation 1. /rec/goodPractice/general/objectivesforPublicGood -An objective should specify that the assignment and maintenance of addresses is done with the purpose of benefitting governance and society and thereby achieving public good. -Making address assignment and maintenance data open benefits governance and society by enhancing transparency, facilitating efficient urban planning, infrastructure development, emergency response, and ensuring equitable access to essential services, ultimately contributing to the public good. - -==== Context - -===== Requirement 2. /req/goodPractice/general/context -A good practice shall specify the context in which the address assignment and maintenance takes place and shall be guided by this context. -When new housing, business complexes, or other types of development occur, local government are responsible for assigning and maintaining addresses for their jurisdiction. However, for Australian Capital Territory (ACT) and Northern Territory, the role is fulfilled by the territory government. -State and territory governments aggregate these addresses into authoritative jurisdictional datasets. Data products and services are then distributed through various channels, including to the national data provider. PSMA Australia Limited (a public company owned by the nine governments of Australia; trading as Geoscape Australia) collate data at the national level. - -==== Conceptual Model - -===== Requirement 3. /req/goodPractice/general/conceptualModel -A good practice shall specify the conceptual model for the classes (types) of addresses assigned and maintained through the good practice. This includes a description of the address reference system, i.e., a set of address components and the rules for their combination into addresses. -Australia is currently developing a national addressing model. Review is being taken of use of the Queensland conceptual model as a national model: https://linked.data.gov.au/def/addr -• Address Model: Address Model -• Roads model: Roads Model -• Geographical Names model: Geographical Names Model -• Compound naming model: Compound Naming Model -• Cadastral model: Cadastral Model -• Lifecycle model: Lifecycle Model - -===== Recommendation 2. /rec/goodPractice/general/ISO19160-1Profile -The conceptual model that describes classes (types) of addresses assigned and maintained through the good practice should conform to ISO 19160-1:2015. -NOTE 1 Amongst others, ISO 19160-1:2015 requires that a conformant address model clearly specifies how the position of an address is represented in the model. ISO 19160-1:2015 provides two ways for doing this: 1) an address has coordinates to specify its position; 2) the position of the address is inferred from the addressed object. [SOURCE: ISO 19160-1:2015, 6.1] -NOTE 2 Postal addresses are defined and described in ISO 19160-4:2017, a profile of ISO 19160-1:2015. -EXAMPLE 14 The draft NZ profile of ISO 19160-1:2015 describes its conformance to ISO 19160-1:2015. The NZ profile defines six address classes: Thoroughfare, Water, Service Delivery, Rural Post Delivery, Thoroughfare4819, and Water4819. New addresses (excluding NZ Post addresses for service delivery and rural post delivery) quality assured by the LINZ address team are assessed against the Thoroughfare4819 and Water4819 classes, and these classes align with the requirements in AS/NZS 4819:2011. - -===== Recommendation 3. /rec/goodPractice/general/intellectualPropertyRights -A good practice should specify to whom the intellectual property rights of the address assignment method and the address data belong. At the least, government organizations should have free access to the address data for services to ensure the health, safety and welfare of the public. -TBC - -==== License - -===== Requirement 4. /req/goodPractice/general/license -A good practice shall specify the licences under which the address data is available and the terms and conditions for their use. Different licenses may apply for different users. - -===== National - -Australia – The national address dataset is released quarterly under a modified Creative Commons Attribution 4.0 International license (CC BY 4.0), which adds a restriction relating to the use of the open G-NAF for the sending of mail . - -===== Jurisdictions - -====== Australian Capital Territory - -ACT - https://creativecommons.org/licenses/by/3.0/au/deed.en - -====== New South Wales - -New South Wales – open data service? - -====== Northern Territory - -Northern Territory - Addresses are managed by the Survey Branch of the Department of Infrastructure, Planning and Logistics. [Cannot find data on https://data.nt.gov.au/] - -====== Queensland - -Queensland – Addresses are available as open data through QSpatial, licensed under a Creative Commons - Attribution 4.0 International licence. https://creativecommons.org/licenses/by/4.0/ - -====== South Australia - -South Australia - [Cannot find data other than rural address locations in LocationSAMapViewer] - -====== Tasmania - -Tasmania – Addresses are available through theList, licensed under a Creative Commons licence. https://creativecommons.org/licenses/by/3.0/au/deed.en - -====== Victoria - -Victoria – Addresses are available as open data through VicMap, licensed under a Creative Commons - Attribution 4.0 International licence. https://creativecommons.org/licenses/by/4.0/ - -====== Western Australia - -Western Australia – Subscription data? - -===== Recommendation 4. /rec/goodPractice/general/facilitateAssignment -A good practice should specify a method for assigning values to address components that could be automated to speed up or facilitate address assignment and maintenance. -EXAMPLE 19 AS/NZS 4819:2011, Rural and urban addressing, contains a clause for addressing rural properties based on the measured distance along the road, from a defined datum point, the accessway of the property is, with odd numbers on the left side of the road and even numbers on the right. -Use of vocabularies -• Address alias types: https://linked.data.gov.au/def/address-alias-type -• Address classes: https://linked.data.gov.au/def/address-classes -• Address status types: https://linked.data.gov.au/def/address-status-type -• Geocode types: https://linked.data.gov.au/def/geocode-types -• Level types: https://linked.data.gov.au/def/level-types -• Record access: https://linked.data.gov.au/def/record-access -• Sub-address types: https://linked.data.gov.au/def/subaddress-types -• Information source: https://linked.data.gov.au/def/source -• Ground relationship: https://linked.data.gov.au/def/ground-relationship -• LRRS indicator: https://linked.data.gov.au/def/lrrs-indicator -• 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 classifications: https://linked.data.gov.au/def/road-classifications -• 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 sub-classes: https://linked.data.gov.au/def/road-sub-classes -• Road suffixes: https://linked.data.gov.au/def/road-suffixes -• 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 -• Information source: https://linked.data.gov.au/def/source -• Geographical names part types: https://linked.data.gov.au/def/gn-part-types -• Geographical name statuses: https://linked.data.gov.au/def/gn-statuses -• Geographical objects categories vocabulary: https://linked.data.gov.au/def/go-categories - -==== Communication Through Physical Identifiers - -===== Requirement 5. /req/goodPractice/general/communicationThroughPhysicalIdentifiers -A good practice shall specify how addresses will be communicated through physical identifiers. -EXAMPLE 26 Addresses are communicated by street name signs on street corners and number signs on buildings. -EXAMPLE 27 AS/NZS 4819:2011, Rural and urban addressing, specifies that “it is desirable that the possible range and direction of numbers be included on the road name sign”. -To support emergency services, street numbers shall be visible from the access point to the address site. - -===== Recommendation 5. /rec/goodPractice/general/keepingAddressDataInSynch -A good practice should specify a method for keeping addresses in the physical world in synch with address data. - -TBC - -=== Principles - -==== Addressing principles - -===== Recommendation 6. /rec/goodPractice/principles/addressing/unambiguity -An address shall be assigned to an addressable object in the physical world so that it allows the unambiguous determination of the object for purposes of identification and location (ISO 19160-1:2015). -NOTE 1 The position of an address can be represented in two ways: 1) The position is specified by coordinates in the ‘position’ attribute. 2) The position is inferred from the addressed object. See 6.1 in ISO 19160-1:2015. -A thoroughfare address shall be assigned that conforms to the list of mandatory components to enable unambiguity, and enable it to be readily located. - -===== Sustainable Assignment Method - -===== Requirement 6. /req/goodPractice/principles/addressing/sustainableAssignmentMethod -Addressing shall be sustainable in the sense that additional addresses can be added without breaking the consistency of the address assignment method of existing addresses. -EXAMPLE 4 Leaving spaces between numbers when addresses are initially assigned makes it possible to assign additional addresses later when densification takes place. Alternatively, a number can be assigned based on the distance from an intersection of origin of the street. - -===== Piloting Assignment Method - -===== Requirement 7. /req/goodPractice/principles/addressing/pilotingAssignmentMethod -The assignment method shall be piloted or tested before rolling it out on a larger scale. -TBC - -===== Device Independence - -===== Requirement 8. /req/goodPractice/principles/addressing/deviceIndependence -Unambiguous location of the object shall be possible without requiring the use of a digital device. -This requirement is necessitated, for example, in the case of an emergency when an object needs to be identified and located in the absence of connectivity (e.g., through signage when standing in front of it). -EXAMPLE 5 During the 2019-20 Australian wildfires there was widespread loss of connectivity due to direct fire damage to telecommunications infrastructure. This resulted in a prolonged loss of internet access to location information [e.g., address] which hampered firefighters who had to rely on radio (verbal) communication. - -Address elements in reverse allow gradually pinpointing of address -State à Locality à Road / Waterway à Number - -An address shall be unique -A sub address number shall be unique regardless of subaddress (unit) type or building level -An address shall be assigned a unique number in relation to the access throughfare -An address shall not contain two road names -Each address shall be assigned at least one geocode with coordinates - -===== No Personal Information - -===== Requirement 9. /req/goodPractice/principles/addressing/noPersonalInformation -An address shall not include information about an individual or organization, owning the object to which it is assigned, or living and/or working at the object to which the address is assigned. -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. - -===== Dimensions Congruent With Objectives - -===== Requirement 10. /req/goodPractice/principles/addressing/dimensionsCongruentWithObjectives -Addresses shall be of an address class with dimensions congruent with the context in which they are assigned and maintained, and with the objectives for which they are assigned and maintained. -TBC - -===== Suitable Components - -===== Requirement 11. /req/goodPractice/principles/addressing/suitableComponents -The address components of an address class shall be suitable to meet the objectives for which that class is designed. -Each address shall be assigned a class as in https://linked.data.gov.au/def/address-classes, which use the components as laid out below. All addresses will be associated with an addressable object that has associated geometry, with, at a minimum, a geocode. Geocodes will be associated with a geocode type from https://linked.data.gov.au/def/geocode-types. All address components will be stored with lifecycle and provenance information. -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 . - -====== Thoroughfare - -Addresses in the Thoroughfare class specify a location by reference to a thoroughfare i.e. a road or water feature name. -All throughfare addresses shall comprise at a minimum the following components: -(a) Address number elements -(b) Thoroughfare name (road or water feature name ) and type elements -(c) Locality name -(d) State or territory name -The combination of these four components shall create a unique address, which reflects the point of access to the address site. -An address may also include the following additional components: -(a) Address site name -(b) Building name -(c) Landmark name -(d) Sub-address type -(e) Level type and number -(f) Postcode -(g) Country -(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. -An addressable object shall have at least one spatial geometry stored against it. - -======= Address number - -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. - -======= 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 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. - A number range shall not be assigned as an address number. And existing ranges phased out. - A primary address number shall not be prefixed by alphabetical characters. - Primary 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 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. - 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. - -======= Urban address numbering - -For addresses designated part of the 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. - -======= Rural address numbering - -For addresses designated part of the 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. -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 7.2.1.1.1.1. - -======= 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. -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. - -======= Water address numbering - -Addresses fall under the class of water if the site cannot be accessed from a road, and is instead accessed from a water feature or island. -For addresses designated part of the inlet address class, inlet or bay address numbering uses the distance in metres from a datum point at one end of the inlet or bay, divided by ten, and rounded to the nearest number. -For addresses designated part of the island address class, numbering uses the distance in metres clockwise from a datum point, divided by ten, and rounded to the nearest number. -For addresses designated part of the 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 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. -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. -The sub-address number should be stored with the sub-address type from https://linked.data.gov.au/def/subaddress-types, although this does not have to be provided within an address string. - -======= Thoroughfare name - -======== Roads - -An address shall not include more than one road name. -A road name shall be short, clear and unambiguous, and meet national 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 . -A named road shall include only one section navigable by vehicles (or pedestrians), unless separated by a median strip. -A road shall only have one name, other than part of a highway that is assigned a local name where it passes through a town or city. -An unbroken section of road crossing an administrative boundary shall retain the same name. -A road name shall consist of a name element followed by a road type. The accepted road types are in https://linked.data.gov.au/def/road-types. 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 should refer to https://linked.data.gov.au/def/road-suffixes. -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. -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 - -For address sites accessed from the water and not accessible from a road, the throughfare component should refer to the water feature name. The name shall be acceptable to the applicable naming authority. -The water throughfare should indicate the type of geographical object from https://linked.data.gov.au/def/go-categories. - -======= 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. -A locality name should not be similar in spelling or sound to any other locality name with the country. -A dual or alternative name shall not be assigned to a locality. -A locality name should be enduring and changed only when necessary. -A locality name should not be substituted with a promotional name , neighbourhood, or regional name in an address. -A locality shall be assigned the geographical object category of https://linked.data.gov.au/def/go-categorieslocality. - -======== Boundaries - -Locality boundaries shall be clearly defined, not overlap, and be contiguous. A locality should not cross a Local Government boundary, and should be contained within, and not cross, state or territory boundaries. -When defining a locality boundary, the following should 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. - 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. - -======= Landmark - -Addresses in the 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 . -All landmark addresses shall comprise the following components: -(a) Landmark Name -(b) Locality (or city/town) name -(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. - -====== Postal - -Addresses in the 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 will follow the AS/NZS ISO 19160.4:2023 standard and components are not covered in this profile. - -==== Address Data Principles - -===== Represents Address In Physical World - -===== Requirement 12. /req/goodPractice/principles/addressData/representsAddressInPhysicalWorld -Address data shall represent the addresses assigned to objects in the physical world. -TBC - -===== Interoperability - -===== Requirement 13. /req/goodPractice/principles/addressData/interoperability -Address data shall be interoperable between public administration systems, such as the cadastre, population register or urban information systems. -TBC - -===== Data Maintenance - -===== Requirement 14. /req/goodPractice/principles/addressData/dataMaintenance -Address data shall be maintained through processes and systems that consider general purpose data management principles, as well as specific requirements due to the geospatial nature of address data. -An address shall be recorded with the location coordinates for the point or access from the thoroughfare to which it is addressed. -The recording of an alternative address shall enable it to be readily distinguished from the related primary address. -The recording of a sub-address and the recording of its primary address shall enable them to be readily related to each other. -Road and water feature names shall be recorded in relation to the localities they pass through. -Locality names shall be recorded in relation to the state/territory within which it is located. -Information about address components that are obsolete shall be retained within lifecycle information including dates. -The relationship between a new address and any address(es) that it replaces shall be recorded. - -===== Digital Maintenance - -===== Requirement 15. /req/goodPractice/principles/addressData/digitalMaintenance -In the case of digital address data, the data shall be maintained in an address data management system with appropriate software solutions, such as spatial database management systems and/or geographic information systems. -TBC - -===== Recommendation 7. /rec/goodPractice/principles/addressing/equivalentDigitalRecord - -===== Recommendation 8. /rec/goodPractice/principles/addressing/updateAddressData - -===== Recommendation 9. /rec/goodPractice/principles/addressData/conformsToISO19160-1 -Address data should conform to ISO 19160-1:2015, or a profile thereof. -TBC - -===== Recommendation 10. /rec/goodPractice/principles/addressData/conformsToISO19160-4 -For postal addressing, address data should conform to ISO 19160-4:2017, or a profile thereof. -TBC - -===== Recommendation 11. /rec/goodPractice/principles/addressData/conformsToISO19160-3 -The quality of address data should be described conformant to ISO 19160-3:2020, or a profile thereof. -TBC - -===== Recommendation 12. /rec/goodPractice/principles/addressData/sharing -In the case of digital address data, the data should be shared through address retrieval solutions that preserve and maintain data integrity, e.g., through spreadsheets or APIs. -TBC diff --git a/document/08-governance-framework-old.adoc b/document/08-governance-framework-old.adoc new file mode 100644 index 0000000..090a891 --- /dev/null +++ b/document/08-governance-framework-old.adoc @@ -0,0 +1,159 @@ +== Governance Framework + +=== General + +==== Strategy + +*Requirement 16* `addrcm-req:strategy` + +A governance framework shall be guided by a strategy for assigning addresses to objects. The strategy shall be based on policies and guidelines. + +TBC + +==== Policies + +*Requirement 17* `addrcm-req:policies` + +A governance framework shall exercise authority and control over address assignment and maintenance through policies with well defined decision-making structures and procedures. + +TBC + +*Recommendation 13* `addrcm-req:policiesSupportObjectivesAndContext` + +The policies should support the objectives and context. + +TBC + +==== Good Practice + +*Requirement 18* `addrcm-req:goodPractice` + +A governance framework shall specify the good practice according to which addresses shall be assigned and maintained (see clause 8). + +TBC + +=== Addressing Stakeholders + +==== Identification + +*Requirement 19* `addrcm-req:identification` + +A governance framework shall identify the addressing stakeholders involved in the processes and decision-making related to assignment and maintenance of addresses. + +TBC + +==== Responsibilities + +*Requirement 20* `addrcm-req:responsibilities` + +A governance framework shall assign at least one responsibility to each stakeholder in the governance framework, and they shall be accountable for their responsibilities. + +TBC + +==== Mandates + +*Requirement 21* `addrcm-req:mandates` + +Assignment of responsibilities to stakeholders shall consider legal and other mandates. Responsibilities are assigned to each stakeholder in the governance framework based on the extent of the mandate of the respective stakeholders. + +TBC + +==== Resourcing + +*Requirement 22* `addrcm-req:resourcing` + +Stakeholders shall take responsibility for how they are funded, resourced and organized to fulfil their responsibilities in the governance framework. + +TBC + +==== Sustainability + +*Requirement 23* `addrcm-req:sustainability` + +Funding and resourcing of stakeholders in a governance framework shall be sustainable, i.e., ongoing and able to be maintained in the long run. + +TBC + +=== Processes + +==== Specification + +*Requirement 24* `addrcm-req:specification` + +A governance framework shall specify and coordinate the processes for assigning and maintaining addresses, as specified in 8.3.1, and if address data is maintained, it shall specify and coordinate the required processes related to address data, specified in 8.3.2. Each process comprises a series of tasks towards achieving a specified goal. + +TBC + +==== Tasks + +*Requirement 25* `addrcm-req:tasks` + +A governance framework shall assign at least one stakeholder to each task in a process. + +TBC + +==== Addressing Processes + +===== Initiation Process + +*Requirement 26* `addrcm-req:initiationProcess` + +A governance framework shall specify and coordinate a process for initiating the assignment or maintenance of an address. + +TBC + +*Recommendation 14* `addrcm-req:consultationProcess` + +A governance framework should specify and coordinate a process for consultation when new address component values are assigned or changed due to maintenance. + +TBC + +===== Purpose Values Process + +*Requirement 27* `addrcm-req:proposeValuesProcess` + +A governance framework shall specify and coordinate a process for proposing new values or changes to address components values. + +TBC + +===== Approval Process + +*Requirement 28* `addrcm-req:approvalProcess` + +A governance framework shall specify and coordinate a process for approving or rejecting the proposed new address assignment or changes to an address due to maintenance. + +TBC + +===== Announcement Process + +*Requirement 29* `addrcm-req:announcementProcess` + +A governance framework shall specify and coordinate a process for the announcement of a newly assigned address or changes to an address due to maintenance. + +TBC + +===== Communication Process + +*Requirement 30* `addrcm-req:communicationProcess` + +A governance framework shall specify a process for communicating addresses in the physical world, following approval of assignment or maintenance of an address. + +TBC + +==== Address Data Processes + +===== Update Process + +*Requirement 31* `addrcm-req:updateProcess` + +A governance framework shall specify and coordinate a process for updating the authoritative dataset after approval of assignment or maintenance of an address. + +TBC + +===== Distribution Process + +*Requirement 32* `addrcm-req:distributionProcess` + +A governance framework shall specify and coordinate a process for making address data available after an update to the authoritative dataset. + +TBC diff --git a/document/08-governance-framework.adoc b/document/08-governance-framework.adoc index fbecc5f..8d8de66 100644 --- a/document/08-governance-framework.adoc +++ b/document/08-governance-framework.adoc @@ -1,3 +1,2 @@ == Governance Framework -_For assigning and maintaining addresses_ \ No newline at end of file diff --git a/document/09-reqs-recs.adoc b/document/09-reqs-recs.adoc new file mode 100644 index 0000000..3d4edc9 --- /dev/null +++ b/document/09-reqs-recs.adoc @@ -0,0 +1,66 @@ +== Requirements & Recommendations + +=== Requirements + +[cols="1,4,10"] +|=== +| ID | Label | Definition + +| 1 | https://linked.data.gov.au/def/addrcm-req/objectives[Objectives] | A good practice shall specify one or more objectives for which addresses are assigned and shall be guided by these objectives +| 2 | https://linked.data.gov.au/def/addrcm-req/context[Context] | A good practice shall specify the context in which the address assignment and maintenance takes place and shall be guided by this context +| 3 | https://linked.data.gov.au/def/addrcm-req/conceptualModel[Context] | A good practice shall specify the conceptual model for the classes (types) of addresses assigned and maintained through the good practice. This includes a description of the address reference system, i.e., a set of address components and the rules for their combination into addresses +| 4 | https://linked.data.gov.au/def/addrcm-req/license[License] | A good practice shall specify the licences under which the address data is available and the terms and conditions for their use. Different licenses may apply for different users +| 5 | https://linked.data.gov.au/def/addrcm-req/communicationThroughPhysicalIdentifiers[Communication Through Physical Identifiers] | A good practice shall specify how addresses will be communicated through physical identifiers +| 6 | https://linked.data.gov.au/def/addrcm-req/sustainableAssignmentMethod[Sustainable Assignment Method] | Addressing shall be sustainable in the sense that additional addresses can be added without breaking the consistency of the address assignment method of existing addresses +| 7 | https://linked.data.gov.au/def/addrcm-req/pilotingAssignmentMethod[Piloting Assignment Method] | The assignment method shall be piloted or tested before rolling it out on a larger scale +| 8 | https://linked.data.gov.au/def/addrcm-req/deviceIndependence[Device Independence] | Unambiguous location of the object shall be possible without requiring the use of a digital device +| 9 | https://linked.data.gov.au/def/addrcm-req/noPersonalInformation[No Personal Information] | An address shall not include information about an individual or organization, owning the object to which it is assigned, or living and/or working at the object to which the address is assigned +| 10 | https://linked.data.gov.au/def/addrcm-req/dimensionsCongruentWithObjectives[Dimensions Congruent With Objectives] | Addresses shall be of an address class with dimensions congruent with the context in which they are assigned and maintained, and with the objectives for which they are assigned and maintained +| 11 | https://linked.data.gov.au/def/addrcm-req/suitableComponents[Suitable Components] | The address components of an address class shall be suitable to meet the objectives for which that class is designed +| 12 | https://linked.data.gov.au/def/addrcm-req/representsAddressInPhysicalWorld[Represents Address In Physical World] | Address data shall represent the addresses assigned to objects in the physical world +| 13 | https://linked.data.gov.au/def/addrcm-req/interoperability[Interoperability] | Address data shall be interoperable between public administration systems, such as the cadastre, population register or urban information systems +| 14 | https://linked.data.gov.au/def/addrcm-req/dataMaintenance[Data Maintenance] | Address data shall be maintained through processes and systems that consider general purpose data management principles, as well as specific requirements due to the geospatial nature of address data +| 15 | https://linked.data.gov.au/def/addrcm-req/digitalMaintenance[Digital Maintenance] | In the case of digital address data, the data shall be maintained in an address data management system with appropriate software solutions, such as spatial database management systems and/or geographic information systems +| 16 | https://linked.data.gov.au/def/addrcm-req/strategy[Strategy] | A governance framework shall be guided by a strategy for assigning addresses to objects. The strategy shall be based on policies and guidelines +| 17 | https://linked.data.gov.au/def/addrcm-req/policies[Policies] | A governance framework shall exercise authority and control over address assignment and maintenance through policies with well defined decision-making structures and procedures +| 18 | https://linked.data.gov.au/def/addrcm-req/goodPractice[Good Practice] | A governance framework shall specify the good practice according to which addresses shall be assigned and maintained (see clause 8) +| 19 | https://linked.data.gov.au/def/addrcm-req/identification[Identification] | A governance framework shall identify the addressing stakeholders involved in the processes and decision-making related to assignment and maintenance of addresses +| 20 | https://linked.data.gov.au/def/addrcm-req/responsibilities[Responsibilities] | A governance framework shall assign at least one responsibility to each stakeholder in the governance framework, and they shall be accountable for their responsibilities +| 21 | https://linked.data.gov.au/def/addrcm-req/mandates[Mandates] | Assignment of responsibilities to stakeholders shall consider legal and other mandates. Responsibilities are assigned to each stakeholder in the governance framework based on the extent of the mandate of the respective stakeholders +| 22 | https://linked.data.gov.au/def/addrcm-req/resourcing[Resourcing] | Stakeholders shall take responsibility for how they are funded, resourced and organized to fulfil their responsibilities in the governance framework +| 23 | https://linked.data.gov.au/def/addrcm-req/sustainability[Sustainability] | Funding and resourcing of stakeholders in a governance framework shall be sustainable, i.e., ongoing and able to be maintained in the long run +| 24 | https://linked.data.gov.au/def/addrcm-req/specification[Specification] | A governance framework shall specify and coordinate the processes for assigning and maintaining addresses, as specified in 8.3.1, and if address data is maintained, it shall specify and coordinate the required processes related to address data, specified in 8.3.2. Each process comprises a series of tasks towards achieving a specified goal +| 25 | https://linked.data.gov.au/def/addrcm-req/tasks[Tasks] | A governance framework shall assign at least one stakeholder to each task in a process +| 26 | https://linked.data.gov.au/def/addrcm-req/initiationProcess[Initiation Process] | A governance framework shall specify and coordinate a process for initiating the assignment or maintenance of an address +| 27 | https://linked.data.gov.au/def/addrcm-req/proposeValuesProcess[Purpose Values Process] | A governance framework shall specify and coordinate a process for proposing new values or changes to address components values +| 28 | https://linked.data.gov.au/def/addrcm-req/approvalProcess[Approval Process] | A governance framework shall specify and coordinate a process for approving or rejecting the proposed new address assignment or changes to an address due to maintenance +| 29 | https://linked.data.gov.au/def/addrcm-req/announcementProcess[Announcement Process] | A governance framework shall specify and coordinate a process for the announcement of a newly assigned address or changes to an address due to maintenance +| 30 | https://linked.data.gov.au/def/addrcm-req/communicationProcess[Communication Process] | A governance framework shall specify a process for communicating addresses in the physical world, following approval of assignment or maintenance of an address +| 31 | https://linked.data.gov.au/def/addrcm-req/updateProcess[Update Process] | A governance framework shall specify and coordinate a process for updating the authoritative dataset after approval of assignment or maintenance of an address +| 32 | https://linked.data.gov.au/def/addrcm-req/distributionProcess[Distribution Process] | A governance framework shall specify and coordinate a process for making address data available after an update to the authoritative dataset +|=== + + +=== Recommendations + +[cols="1,4,10"] +|=== +| ID | Label | Definition + +| 1 | https://linked.data.gov.au/def/addrcm-rec/objectivesForPublicGood[Objectives For Public Good] | An objective should specify that the assignment and maintenance of addresses is done with the purpose of benefitting governance and society and thereby achieving public good +| 2 | https://linked.data.gov.au/def/addrcm-rec/iso19160-1-profile[ISO 19160-1 Profile] | The conceptual model that describes classes (types) of addresses assigned and maintained through the good practice should conform to ISO 19160-1:2015 +| 3 | https://linked.data.gov.au/def/addrcm-rec/intellectualPropertyRights[Intellectual Property Rights] | A good practice should specify to whom the intellectual property rights of the address assignment method and the address data belong. At the least, government organizations should have free access to the address data for services to ensure the health, safety and welfare of the public. +| 4 | https://linked.data.gov.au/def/addrcm-rec/facilitateAssignment[Facilitate Assignment] | A good practice should specify a method for assigning values to address components that could be automated to speed up or facilitate address assignment and maintenance +| 5 | https://linked.data.gov.au/def/addrcm-rec/keepingAddressDataInSynch[Keeping Address Data In Synch] | A good practice should specify a method for keeping addresses in the physical world in synch with address data. +| 6 | https://linked.data.gov.au/def/addrcm-rec/unambiguity[Unambiguity] | An address shall be assigned to an addressable object in the physical world so that it allows the unambiguous determination of the object for purposes of identification and location (ISO 19160-1:2015). + +A thoroughfare address shall be assigned that conforms to the list of mandatory components to enable unambiguity, and enable it to be readily located. +| 7 | https://linked.data.gov.au/def/addrcm-rec/equivalentDigitalRecord[Equivalent Digital Record] | TODO: add definition +| 8 | https://linked.data.gov.au/def/addrcm-rec/updateAddressData[Update Address Data] | TODO: add definition +| 9 | https://linked.data.gov.au/def/addrcm-rec/conformsToIso19160-1[Conforms To ISO 19160-1] | Address data should conform to ISO 19160-1:2015, or a profile thereof +| 10 | https://linked.data.gov.au/def/addrcm-rec/conformsToIso19160-4[Conforms To ISO 19160-4] | For postal addressing, address data should conform to ISO 19160-4:2017, or a profile thereof +| 11 | https://linked.data.gov.au/def/addrcm-rec/conformsToIso19160-3[Conforms To ISO 19160-3] | The quality of address data should be described conformant to ISO 19160-3:2020, or a profile thereof +| 12 | https://linked.data.gov.au/def/addrcm-rec/sharing[Sharing] | In the case of digital address data, the data should be shared through address retrieval solutions that preserve and maintain data integrity, e.g., through spreadsheets or APIs +| 13 | https://linked.data.gov.au/def/addrcm-rec/policiesSupportObjectivesAndContext[Policies Support Objectives And Context] | The policies should support the objectives and context +| 14 | https://linked.data.gov.au/def/addrcm-rec/consultationProcess[Consultation Process] | A governance framework should specify and coordinate a process for consultation when new address component values are assigned or changed due to maintenance +|=== \ No newline at end of file diff --git a/document/50-annex-a-extended-examples.adoc b/document/50-annex-a-extended-examples.adoc new file mode 100644 index 0000000..e69de29 diff --git a/document/50-annex-a-identifiers.adoc b/document/51-annex-b-identifiers.adoc similarity index 98% rename from document/50-annex-a-identifiers.adoc rename to document/51-annex-b-identifiers.adoc index bef4b94..30d03a4 100644 --- a/document/50-annex-a-identifiers.adoc +++ b/document/51-annex-b-identifiers.adoc @@ -1,5 +1,5 @@ -[[AnnexA]] -== Annex A: Identifiers +[[AnnexB]] +== Annex B: Identifiers _This section is normative_