Intended Audience and Contact Information
| Contact | Chief Data Officer, Office of the CIO |
|---|---|
| UDM Domain | Location |
| Intended Audience | Internal UBC |
Purpose
This standard aims to achieve consistency around the data collected for UBC Campus Address (Vancouver and Okanagan campuses), and the format in which it is collected and stored in across the University. This standard applies to UBC applications which collect UBC Campus Addresses. Exceptions are listed in the Dispensation section. This includes standardized physical location data for civic and non-civic addresses at UBC to be shared with emergency responders.
Standard
The standard for coding UBC Campus Location address is adopted from the Physical Address and Geocoding Standards, developed by the government of British Columbia.
The conceptual model consists of an information model that defines the hierarchy, classes and spatial associations needed to represent sites and physical addresses, and a service model for geocoding. The complete model is described here.
The coding schema is described here.
The following are the data elements that make up a campus address.
| Attribute | Requirement | Definitions | Examples |
|---|---|---|---|
| Unit _Designator | Optional | The type of unit. | APT, BLDG, BSMT, FLR, LOBBY, LWR, PAD, PH, REAR, RM, SIDE, SITE, SUITE, TH, UNIT, UPPR. |
| Unit_Number_Prefix | Optional | A single alphabetic character or list of alphabetic characters and ranges, that is placed before the unit number | |
| Unit_Number | Optional | The number or range of numbers that identify units/ suites/buildings within a building or complex. For ADDRESS_DESCRIPTOR = CampusBldg, this must be a single value not a range. | 100, 101-110 |
| Unit _Number_Suffix | Optional | A single alphabetic character or list of alphabetic characters and ranges, that follow the unit number. | |
| Site_Name | Required |
A string containing the name of a site. A business or occupant name should only be used if it is permanently affixed to the site and the site has no other, more generic name (ADDRESS_DESCRIPTOR = {Occupant, Commercial}). If a site is a unit within a complex, it may have a sitename in addition to a unitNumber and unitNumberSuffix. This site name will be repeated for each unit. |
Audain Art Centre, Nitobe Garden, UBC Security |
|
Super_Full_Site_Descriptor |
Optional | Name of all units, buildings and sites in parent site hierarchy separated by a double dash. To identify buildings in a complex or sub-buildings in a building. |
Spruce House (sub-building) -- Ponderosa Commons East (building) – Ponderosa Commons Residence (complex) |
| Civic_Number | Required | The number assigned to a site on a street by an address authority | |
| Civic_Number_Suffix | Optional | A letter or fraction following the civic number. | |
| Street_Name | Required | Recognized by the municipality as the official name of the street. | |
| Street_Type | Required | The type of street. Use the full word. | Avenue, Drive, Mall, Boulevard, Crescent, Lane, Road, Place, Court, Mews, Row, Walk |
| Street_Direction | Optional |
Canada Post street direction. |
NW, SW |
| Locality | Required |
The name of the locality assigned to a given site by an address authority. |
Vancouver |
| Postal_Code | Optional |
Postal Code assigned by Canada Post for the purposes to deliver mail. Required once STATUS = Complete (Canada Post assigns postal code) |
|
| Province_Code | Required | The ISO 3166-2 Sub-Country Code. | BC |
| Attribute | Requirement | Definitions | Examples |
|---|---|---|---|
| Is_Non_Civic_Address |
Required |
True if address has no assigned civic number |
True = 1, False = 0 |
| Is_Official_Address | Required | True if address is official; false if unofficial (e.g. former address) | True = 1, False = 0 |
| Narrative_Location | Optional | Step by step directions to a non-civic address location | |
| Is_Primary | Required | True if this is the primary building address for the purposes of Workday/IRP. | True = 1, False = 0 |
| Status | Required |
The state or condition of the address |
Current, Pending, Retired, Temporary, Other |
| Is_Mailing_Address | Required | True if this a Canada Post or Campus Mail mailing address. |
True = 1, False = 0 (To be able to remove things like Totem building addresses that are not for mailing). |
| Mail_Provider | Optional | Identifies which organization delivers the mail. | Canada Post or Campus Mail |
| Is_Annunciator | Required | If annunciator panel is located near the address point. | True = 1, False = 0 |
| Address_Descriptor | Required | Describes the address usage at all levels of the hierarchy. | (See table below for Address Descriptor Attribute) |
| Locality_Descriptor | Required | Describes the nature of the address location. | Municipality |
| Site_Point_Descriptor | Required | Describes the location of the address point. | (See table below for Address Descriptor Attribute) |
| Footprint_ID | Optional |
The ID of the polygon that has this address, if any. This could be an ID for a parcel, building, or poi. This is required if: ADDRESS_DESCRIPTOR = Any Building Type, Outdoor, Complex. |
|
| Footprint_Descriptor | Optional | Describes the footprint area that the address point is associated to. | (See table below for Footprint Descriptor Attribute) |
| Bldg_UID | Required | BLDG_UID for a foreign key. |
Accepted Data Values and Rules for Address Descriptor
Following are the accepted data values for Address Descriptor.
| Accepted data value | Definition |
|---|---|
| Campus Building | Address assigned at the building level that is associated with UBC organizational purposes (Examples: Academic buildings, Nest, UBC Hospital). |
| Emergency |
Address assigned for emergency access only (Note: not every address has an annunciator panel associated with it). |
| Commercial | Address assigned to a retail unit in a building |
| Outdoor | Address assigned to an outdoor area of the campus (examples: Nitobe Memorial Garden, athletic fields) |
| Complex | Address assigned at the complex level to a group of related buildings (example: Totem Park Residence) |
|
NeighbourhoodBuilding |
Address assigned at the building level that is associated to a neighbourhood building on campus |
| Other Building | Address assigned at the building level that is not a campus building or neighbourhood building (examples: Hillel House, RCMP, MT Innovations) |
| Occupant | Address assigned to an occupant in a building (example: security in UBC Bookstore building) |
| Indoor | Address assigned to an interior space that is not a street address |
| Residential | Address assigned to a residential unit in a building |
Accepted Data Values and Rules for Site Point Descriptor
Following are the accepted data values for Site Point Descriptor:
| Accepted data value | Definition |
|---|---|
| Parcel | Located somewhere within the parcel (used for parcels that have a legal address). |
| FrontDoor | Located at the entrance to the unit or building |
| Rooftop |
Building centroid or rooftop, somewhere within building footprint. |
| EmergencyAccess | Address points that are specifically for emergency access only (does not include all sites where annunciators are located). |
| ServiceAccess | Loading bay or other service entrance. |
|
FrontGate |
Located at the point of access to the site, for example the locked gate of a secured outdoor area. |
| Accepted data value | Definition |
|---|---|
| Building | A building polygon/footprint |
| Complex | A complex of buildings (MultiPolygon, example: Totem Park Residence). |
| OutdoorArea |
Examples: Garden, field, plaza. |
| IndoorArea | Interior area of a building. examples: occupant, sub-buildings, units. |
| SecureOutdoorArea | If the area is behind a locked gate (examples: botanical garden, Nitobe). |
|
Parcel |
A legal parcel. |
Compliance
This standard Campus Addresses must be complied with through every stage of the data lifecycle with the exception of any dispensations (see Dispensation section):
- All applications must collect Campus Address as recommended in this standard.
- Enterprise Data Integration must adopt this standard.
Dispensation
Legacy systems are exempt from this data standard. As systems are replaced, adoption of this standard is required. Examples of legacy systems are:
- Student Information System (SIS)
- Human Resource Management System (HRMS)
- Finance Management System (FMS)
As existing systems change to adopt this standard, the Enterprise Data Governance team needs to be informed.