Table Report
For STNETGDB
Columns in blue were once a stand alone coverage or shapefile that has been incorporated into the new stnetgdb.
Note: At
the bottom of this document are fields that were dropped from the stnetgdb
layer.
|
Column
details |
1. OBJECTID (U1)
Physical
data type:
NUMBER
Allow
NULLs:
Not allowed
Description:
The primary key for the stnetgdb table.
2. LENGTH
Physical
data type:
NUMBER
Allow
NULLs:
Allowed
Description:
The length of the arc segment (feet)
3. L_ADD_FROM
Physical
data type:
NUMBER (6)
Allow
NULLs:
Allowed
Description:
The left side (from) of the road house address
4. L_ADD_TO
Physical
data type:
NUMBER(6)
Allow
NULLs:
Allowed
Description:
The left side (to) of the road house address
5. LADD_SIDE
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
The side of the road in which the address range should be
taken.
6. R_ADD_FROM
Physical
data type:
NUMBER(6)
Allow
NULLs:
Allowed
Description:
The right side (from) of the road house address
7. R_ADD_TO
Physical
data type:
NUMBER(6)
Allow
NULLs:
Allowed
Description:
The right side (to) of the road house address
8. RADD_SIDE
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
The side of the road in which the address range should be
taken.
9. ADD_MIN
Physical
data type:
NUMBER(6)
Allow
NULLs:
Allowed
Description:
The minimum street number value for the segment.
10. ADD_MAX
Physical
data type:
NUMBER(6)
Allow
NULLs:
Allowed
Description:
The maximum street number value for the segment.
11. STREET
Physical
data type:
VARCHAR2(50)
Allow
NULLs:
Allowed
Description:
Street name. Includes prefix
direction, street name, street type, and
suffix direction.
12. PRE_DIR
Physical
data type:
VARCHAR2(2)
Allow
NULLs:
Allowed
Description:
Street prefix direction.
13. STREET_NAME
Physical
data type:
VARCHAR2(30)
Allow
NULLs:
Allowed
Description:
Street name
14. STREET_TYPE
Physical
data type:
VARCHAR2(4)
Allow
NULLs:
Allowed
Description:
Street type
15. SUF_DIR
Physical
data type:
VARCHAR2(2)
Allow
NULLs:
Allowed
Description:
Street suffix direction.
16. PAVE_CODE
Physical
data type:
NUMBER (1)
Allow
NULLs:
Allowed
Description:
Code for whether or not street is maintained by Pima
County.
|
0 |
Not maintained by the County |
|
1 |
Paved road, maintained by the County |
|
2 |
Dirt Road, maintained by the County |
|
3 |
IGA - Pima
County maintained |
|
4 |
IGA -
Other jurisdiction maintained |
17. PAVE_IGA
Physical
data type:
NUMBER(1)
Allow
NULLs:
Allowed
Description:
Code for whether or not a street is an IGA road
|
0 |
Not an IGA Road |
|
1 |
IGA – Pima County maintained |
|
2 |
IGA – Other jurisdiction maintained |
18. PAVE_HALF
Physical
data type:
NUMBER(1)
Allow
NULLs:
Allowed
Description:
Code for whether or not the county maintains the left or right side of
the road
|
0 |
Not a half-n-half road |
|
1 |
Half-n-half road with the county maintaining the
left side |
|
2 |
Half-n-half road with the county maintaining the
right side |
|
x |
Variation to the above |
19. LEGNUM
Physical
data type:
NUMBER(1)
Allow
NULLs:
Allowed
Description:
Reference number used in the Pima County Street Atlas when the street
name
is too long to fit as
annotation.
20.
SCENIC_ROUTE
(This layer use
to be called STSCENIC)
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road is scenic route.
|
Y =
YES |
|
N =
NO |
21.
BUS_ROUTE (This layer use
to be called BUSROUTE)
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road is part of a bus route.
|
Y =
YES |
|
N =
NO |
22.
BIKE_ROUTE (This layer use
to be called BIKE_RTE)
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road is part of a bike route.
|
Y =
YES |
|
N =
NO |
23.
MAJOR_ROUTE (This layers use
to be called STCL_MAJ)
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road is a major route.
|
Y =
YES |
|
N =
NO |
24. LANE_CAT
Physical
data type:
NUMBER(1)
Allow
NULLs:
Allowed
Description:
The number of lanes in one direction.
|
1 |
One lane road , in one direction |
|
2 |
Two lane road, in one direction |
|
3 |
Three lane road, in one direction |
25. SPEED_CAT
Physical
data type:
NUMBER(1)
Allow
NULLs:
Allowed
Description:
The speed category of the road segment.
|
2=65-80
MPH |
|
3=55-64
MPH |
|
4=41-54
MPH |
|
5=31-40
MPH |
|
6=21-30
MPH |
|
7=6-20
MPH |
|
8=< 6
MPH |
26. FUNC_CAT
Physical
data type:
NUMBER (1)
Allow
NULLs:
Allowed
Description:
The functional category of each of the road segment.
|
1=INTERSTATE |
|
2=US
ROUTE |
|
3=STATE
ROUTE |
|
4=LOCAL ROADS
MAJOR |
|
5=LOCAL ROADS
MINOR |
27.
FHWA_FUNC_CAT (This layer use to be called
STFCLASS)
Physical
data type:
NUMBER (1)
Allow
NULLs:
Allowed
Description:
The federal highway designation of the functional category of the
roads.
|
1=Rural
Interstate |
|
2=Rural
Principal Arterial |
|
6=Rural Minor
Arterial |
|
7= Rural
Major Collector |
|
8= Rural
Minor Collector |
|
9=Rural
Local |
|
11=Urban
Interstate |
|
12=Urban Other
Freeway |
|
14=Urban
Principal Arterial |
|
16=Urban Minor
Arterial |
|
17=Urban
Collector |
|
19=Urban
Local |
|
0=Not Classified |
28. ROUNDABOUT
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road segment is part of a
roundabout
|
Y =
YES |
|
N =
NO |
29. OVERPASS
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road segment is an overpass.
|
Y =
YES |
|
N =
NO |
30. BRIDGE
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road segment is a bridge.
|
Y =
YES |
|
N =
NO |
31. MORATORIUM
Physical
data type:
DATE
Allow
NULLs:
Allowed
Description:
The date in which the road was constructed. Once a moratorium date has been
established for a road segment that road can not have any construction on it for
5 years
|
DATE
|
32. ROAD_SOURCE_CAT
Physical
data type:
NUMBER(1)
Allow
NULLs:
Allowed
Description:
Indicates the source of the road such as from a
subdivision,USGS,
|
1 |
SUBDIVISION |
|
2 |
USGS |
|
3 |
OTHER |
33.
DIRECTION_OF_TRAVEL
Physical
data type:
VARCHAR2(50)
Allow
NULLs:
Allowed
Description:
The direction of travel for the road segment. Valid entries are Both Directions or One
Way
|
BOTH DIRECTIONS |
|
ONE WAY |
34.
DIRECTION_DESCRIPTION
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
The direction description indicating direction of travel
N,S,E,W
|
N,S,W,E |
35. DIVIDER
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if there is a divider on the road segment
|
Y =
YES |
|
N =
NO |
36. INTERSECTION
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road segment is part of an
intersection.
|
Y =
YES |
|
N =
NO |
37. TURN_RESTRICTION
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicates by Y/N if the road segment has a turn
restriction.
|
Y =
YES |
|
N =
NO |
38. ROAD_TURN_CAT
Physical
data type:
NUMBER(1)
Allow
NULLs:
Allowed
Description:
The road turn restriction of the road segment. The road restriction can be a legal,
physical and logical turn restriction.
|
1 =
LEGAL |
|
2 =
PHYSICAL |
|
3 =
LOGICAL |
|
0 = NO TURN
RESTRICTION |
39. TURN_LANES
Physical
data type:
VARCHAR2(50)
Allow
NULLs:
Allowed
Description:
The template for the turn restriction. Indicated by Y or N if there is a turn
lane.
|
YYNNNNYY = THE
ROAD TEMPLATE SHOWING THE NUMBER OF TURN LANES |
40. AR_AUTO
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road is accessible by automobiles.
|
Y =
YES |
|
N =
NO |
41. AR_BUS
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road is accessible by buses.
|
Y =
YES |
|
N =
NO |
42. AR_TAXI
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road is accessible by taxi’s.
|
Y =
YES |
|
N =
NO |
43. AR_CARPOOL
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road segment is accessible by carpool
automoblies.
|
Y =
YES |
|
N =
NO |
44. AR_PED
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road segment if accessible by
pedistrans.
|
Y =
YES |
|
N =
NO |
45. AR_BICYCLE
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road segment is accessible by
bicycles.
|
Y =
YES |
|
N =
NO |
46. AR_TRUCKS
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road segment is accessible by trucks such as
tracter trailers.
|
Y =
YES |
|
N =
NO |
47. AR_THROUGH
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road segment is a though access
road.
|
Y =
YES |
|
N =
NO |
48. AR_EMERGEN
Physical
data type:
VARCHAR2(1)
Allow
NULLs:
Allowed
Description:
Indicated by Y/N if the road segment is accessible by emergency
automobiles.
|
Y =
YES |
|
N =
NO |
49. ROADID
Physical
data type:
LONG
Allow
NULLs:
Allowed
Description:
This is the persistant identifier for the road segment.
|
Dropped
Columns |
ADD_O
Physical
data type:
NUMBER(1)
Allow
NULLs:
Not allowed
Description:
This field was an addressing field to indicate wether the field had an
address range.
Recommend
Field to use:
ADD_MIN OR ADD_MAX
QC
Physical
data type:
NUMBER(1)
Allow
NULLs:
Not allowed
Description:
This was a field used to indicate that the road segment was QC’d by
staff