Table openpetra_trunk.public.p_location
Address and other data related to that address.

 Generated by
SchemaSpy
Legend: SourceForge.net
Primary key columns
Columns with indexes
Implied relationships
Excluded column relationships
< n > number of related tables
 
Column Type Size Nulls Auto Default Children Parents Comments
p_site_key_n numeric 10 0
m_extract.p_site_key_n m_extract_fk3 R
s_group_location.p_site_key_n s_group_location_fk2 R
This is the key that tell what site created this location, it will help to merge addresses when doing imports
p_location_key_i int4 10 0
m_extract.p_location_key_i m_extract_fk3 R
s_group_location.p_location_key_i s_group_location_fk2 R
p_building_1_c varchar 100  √  null The name of the building
p_building_2_c varchar 100  √  null The name of the building (continued)
p_street_name_c varchar 100  √  null The name of the street that the house is located on
p_locality_c varchar 100  √  null This is the first element of an address
p_suburb_c varchar 100  √  null The name of the suburb
p_city_c varchar 64  √  null This can be a post town or city
p_county_c varchar 64  √  null This can be a county (UK), a state (US), province (CDN), canton (CH) etc.
p_postal_code_c varchar 40  √  null This is the national post code
p_country_code_c varchar 8  √  null
p_country.p_country_code_c p_location_fk1 R
This is a code which identifies a country. It is taken from the ISO 3166-1-alpha-2 code elements.
p_address_3_c varchar 100  √  null This is the third element of an address (if required)
p_geo_latitude_n numeric 9,6  √  null The latitude of the location; a number between -90 and +90; precision is 6 digits (11cm)
p_geo_longitude_n numeric 9,6  √  null The longitude of the location; a number between -180 and +180; precision is 6 digits (11cm)
p_geo_km_x_i int4 10  √  null The distance in km of this location to the location 0 if location 0 was on the same longitude; this is for improving query performance
p_geo_km_y_i int4 10  √  null The distance in km of this location to the location 0 if location 0 was on the same latitude; this is for improving query performance
p_geo_accuracy_i int4 10  √  (-1) The accuracy of the stored geo data; -2: server did not respond; -1: not processed yet; 0: Unknown Location; 1: Country level accuracy; 2: Region; 3: Sub-Region; 4: Town/City/Village; 5: Post code; 6: Street; 7: Intersection; 8: Address level accuracy
p_restricted_l bool 1  √  false Indicates whether or not the location has restricted access. If it does then the access will be controlled by s_group_location.
s_date_created_d date 13  √  ('now'::text)::date
s_created_by_c varchar 20  √  null
s_user.s_user_id_c p_location_fkcr R
s_date_modified_d date 13  √  null
s_modified_by_c varchar 20  √  null
s_user.s_user_id_c p_location_fkmd R
s_modification_id_c varchar 150  √  null

Table contained 73.407 rows at Do Nov 10 18:00 MEZ 2011

Indexes:
Column(s) Type Sort Constraint Name
p_site_key_n + p_location_key_i Primary key Asc/Asc p_location_pk
s_created_by_c Performance Asc inx_p_location_fkcr_key1
s_modified_by_c Performance Asc inx_p_location_fkmd_key2
p_site_key_n + p_location_key_i Must be unique Asc/Asc inx_p_location_pk0
p_city_c Performance Asc p_city_k2
p_country_code_c Performance Asc p_country_k4
p_county_c Performance Asc p_county_k3
p_geo_km_x_i + p_geo_km_y_i Performance Asc/Asc p_geo_location_km_k5
p_locality_c Performance Asc p_locality_k1
p_postal_code_c Performance Asc p_postal_code_k0

Close relationships  within of separation: