Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Table of Contents

...

We have worked with the San Francisco Fire Department and other agencies to provide a set of flattened data products. Flattening just means that we provide a single table representation of what is actually multiple tables in a relational database. In this case we are joining four tables in EAS. You can see the data model hereThe flattening is accomplished using this database view.

Availability

The flattened data products are refreshed from our production system every weekday.
These data are available in the following locations

...

available in versioncolumn namedata typedescription
 

eas_address_base_id

inteas primary key for base address table
 

base_address_num

int 
 

base_address_suffix

string 
 

base_address_create_tms

timestamp 
 

base_address_retire_tms

timestamp 
 

street_name

string 
 

street_type

string 
1.1.8street_post_directionstringEAST, WEST, NORTH, SOUTH e.g. MISSION BAY BLVD NORTH
1.1.8street_full_street_namestringconcatenation of street_name, street_type, and street_post_direction
 

street_cnn

int 
 

eas_unit_address_id

inteas primary key for unit address table
 longitudedouble 
 latitudedouble 
 

unit_address_base_flg

booleanThis is an artifact of the relational data model. If false, this is a typical unit address. If true, the unit_number value goes along with the base address (not typical). In the vast majority of cases, a base address will not have a unit number itself, even though there may be units for that address.
 

unit_address

stringThe unit address number, letter, or fraction. For example: "A", "1/2", or "7". For legacy reasons, it is currently limited to 1 character. We are planning to expand it to 10 characters.
 unit_address_create_tmstimestamp 
 unit_address_retire_tmstimestamp 
1.1.7map_block_lotstringthe map_block_lot field for parcels
 block_lotstringthe block_lot (or assessor parcel number) field for a parcel
1.1.7parcel_date_map_adddateThis is the create date for a parcel. Parcels are created independent of addresses.
1.1.7parcel_date_map_dropdateThis is the retire date for a parcel. Parcels are retired independent of addresses. An unretired address that is linked to a retired parcel is an "invalid address" and needs to be corrected.
 eas_address_x_parcel_idinteas primary key to lookup parcels for a unit address
 address_x_parcel_create_tmstimestampthe create time stamp for when a parcel was linked to an address
 address_x_parcel_retire_tmstimestampthe retire time stamp for when a parcel was linked to an address
 zipcodeint