documentation:next_cdm:lat_long
Add Latitude and Longitude to Location Table
Proposals are now housed on github
- Proposal Owner: Gowtham Rao
- Use cases: For standardized geospatial visualization and analysis
- Related proposals: http://www.ohdsi.org/web/wiki/doku.php?id=documentation:next_cdm:country
- Background: For standardized geospatial visualization and analysis, addresses need to be, at the minimum be geocoded into latitude and longitude. This allows it to put as a point on a map. This proposal is to add two fields, latitude and longitude to the location table.
- Backward compatible: Yes
- Impact: GIS workgroup
| 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 | No | varchar(50) | The address field 2, typically used for additional detail such as buildings, suites, floors, as it appears in the source data. |
| city | No | varchar(50) | The city field as it appears in the source data. |
| state | No | varchar(2) | The state field as it appears in the source data. |
| zip | No | varchar(9) | The zip or postal code as it appears in the source data |
| county | No | varchar(20) | The county as it appears in the source data |
| 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 | Geocoded latitude |
| longitude | No | float | Geocoded longitude |
documentation/next_cdm/lat_long.txt · Last modified: by clairblacketer