City Addresses
Point layer used to store all addresses within the city. Where available, and especially including businesses, the occupant is also stored.
Field Explanations[edit]
- STCODE: unique ID for each different street
- SEGMENT_ID: unique ID for each segment of each street
- [L|R]_ADD_[FROM|TO]: starting and ending addresses on each side of the street. Odd numbers should usually be on the left side and evens on the right. FROM should also be smaller than TO. Minimize gaps between segments e.g. (100-198, 200-298...) vs (100-150, 200-250...)
- STDIR, STNAME, STTYPE: components of the street name, e.g. "N", "Elm", and "St", respectively.
- FULNAME: concatenated components of the street name, e.g. "N Elm St"
- CLASS: residential, secondary arterial, collector, etc.
- OWNER: COD, TXDOT, etc.
- ZWAY_RUN: Direction of traffic for one-way streets. "ONEWAY_DIR" would be a more sensible name.
- SUBNAME: Subdivision, if any, that contains the street.
- FNODE1_1, TNODE1_1: FULNAME of the streets that intersect the beginning and end of the segment. want to rename. many fields use only the street name without the suffix. needs cleanup.
- EDIT_DATE: updated when the feature is edited in GIS
- ICA, ICA_MNTAIN, ICA_DATE: maintenance agreement doc#, party, and date active
- ESN_L, ESN_R: The emergency services region number (ESN) on each side of the road, usually the same.
- EST_YEAR: Year the road was originally built, only 5% of features are attributed with this.
- useless/gibberish/superfluous: FNODE_, TNODE_, LPOLY_RPOLY_, LENGTH, CL_, CL_ID, OBJECTID_1, OBJECTID, FNODE1, TNODE1, LPOLY1, RPOLY1, CL1, CL_ID_1
- [START|MID|END]_[X|Y]: These are used for some niche purpose. Should rearrange them to have mid in between the other two in the table.
