-
Notifications
You must be signed in to change notification settings - Fork 10
LOCATION
Robert Miller edited this page May 28, 2019
·
3 revisions
The LOCATION table represents a generic way to capture physical location or address information of Persons and Care Sites.
| Field | Required | Type | Description |
|---|---|---|---|
| location_id | Yes | integer | A unique identifier for each geographic location. |
| address_1 | No | varchar(50) | The address field 1, typically used for the street address, as it appears in the source data. |
| address_2 | Yes | varchar(50) | The address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data. |
| city | Yes | integer | The city as it appears in the source data. |
| state | Yes | varchar(2) | The state field as it appears in the source data. |
| zip | No | varchar(9) | The zip or postal code. |
| county | No | varchar(20) | The county. |
| country | No | varchar(100) | The country |
| location_source_value | No | varchar(50) | The verbatim information that is used to uniquely identify the location as it appears in the source data. |
| latitude | No | float | The geocoded latitude |
| longitude | No | float | The geocoded longitude |
| epsg | No | varchar(50) | coordinate reference system |
| location_type_concept_id | No | int | Provenance. TODO: nail this down. |
| location_source_value | No | varchar(100) | source identifier |
| data_source_id | No | varchar(50) | source of data. FK to data_source |
- TODO
Subject
Relation
Attribute
Metadata