Java Server Face Manual
2
The process of implementing your geodatabase design involves building the geodatabase • Use ArcCatalog tools to create the various geodatabase datasets. There are a number • Use an existing geodatabase data model template. This can be one (or more) of the data models available at the ESRI Web site ( ), or a template that someone else provides to you. That saves you the step of defining the geodatabase structure using the ArcCatalog tools. You’ll likely use the tools, though, to Importing data to a geodatabase and editing are discussed in Chapter 3, ‘Data Compilation and Editing’. Once you’ve solidified your geodatabase design, you’ll want to document it for reference. Various methods can be used to describe your database design and decisions: drawings, a variety of industries. Key FromMeasure Name ToMeasure Measure Route Table Accidents_Refmkr Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Detailed information for Albany County point accident locations along routes OBJECTID OID String Yes 9 The route the accident occurred on Yes 0 0 2 The location along the route for the accident MUNI String Yes 2 Municipality where the accident occurred POLICE_DPT String Yes 5 The police department that documented the accident PRECINCT String Yes 4 The police precinct CASE_NUM String Yes 7 The case number for the accident NUM_KILLED Double Yes 0 0 The number of people killed NUM_INJURY Double Yes 0 0 The number of people injured EXT_INJURY String Yes EXT_INJURY 5 The extent of injuries ACCD_DATE String Yes 11 The date of the accident ACCD_TIME String Yes 2 The time of the accident NUM_VEH Double Yes 0 0 The number of vehicles involved LOCATION String Yes LOCATION 1 The general location of the accident ACCD_TYPE String Yes ACCD_TYPE 2 The type of accident COLL_TYPE String Yes COLL_TYPE 1 The type of collision PED_LOC String Yes PED_LOC 1 The location of any pedestrians involved PED_ACTION String Yes PED_ACTION 2 What the pedestrian was doing when the accident occurred ROAD_SURF String Yes ROAD_SURF 1 The road surface condition WEATHER String Yes WEATHER 1 The weather conditions ROAD_CHAR String Yes ROAD_CHAR 1 The road characteristics TRAF_CNTL String Yes TRAF_CNTL 1 Traffic control devices LIGHT_COND String Yes LIGHT_COND 1 The light conditions at the time of the accident ROUTE_RM Measure Table PMS_Refmkr Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Preventative Maintenance Screen records along reference marker routes OBJECTID OID String Yes 9 The route identifier for the PMS record Small Integer Yes 0 0 2 The from location along the route Small Integer Yes 0 0 2 The to location along the route AADT_X_100 Small Integer Yes 0 0 2 Accident volume NO_ROADW Small Integer Yes 0 0 2 Number of roadways NO_LANES Small Integer Yes 0 0 2 Number of Lanes AREA_TYPE Small Integer Yes 0 0 2 Pavement area type CULTURE Small Integer Yes 0 0 2 *** FATAL_ACC Small Integer Yes 0 0 2 Number of fatal accidents INJ_ACC Small Integer Yes 0 0 2 Number of injury accidents PDO_ACC Small Integer Yes 0 0 2 Number of property damage only accidents INTRS_ACC Small Integer Yes 0 0 2 Accidents in intersection NON_IN_ACC Small Integer Yes 0 0 2 Accidents not in intersection TOT_ACC Small Integer Yes 0 0 2 Total accidents END_DATE String Yes 6 End date for the pavement record REG_CNTY String Yes 2 County within the DOT region SERV_RANKN Single Yes 0 0 Severity rank for the section of pavement ROUTE_RM F_RM T_RM Table Capital_Improvements_Milept Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Capital Improvement Project locations along milepoint routes OBJECTID OID MAJOR_PIN String Yes 6 Major project number String Yes 9 The route the project occurs along Single Yes 0 0 Starting milepoint reference Single Yes 0 0 Ending milepoint reference CENT_LN_MI Single Yes 0 0 Place a succinct description of the field in this text PROJ_TITLE String Yes 60 Description of the project LET_DATE String Yes 11 The date the project was let out for construction PSE_ESTIMATE Double Yes 0 0 Project supervisor cost estimate PSE_DATE String Yes 11 Project supervisor estimate date PROJ_EST Double Yes 0 0 Project cost estimate CONST_COST Double Yes 0 0 Construction Cost PROJ_MGR_F String Yes 15 Project Manager (first) PROJ_MGR_L String Yes 18 Project Manager (last) WORK_TYPE String Yes 60 Type of project work SUB_WRK_TYPE String Yes 60 More detailed project classification PROJ_STUS_ String Yes 60 Project status REGION_NUM String Yes 2 DOT Region number for the project LASTUPDATE String Yes 11 Last date the information was updated LET_QUARTE Small Integer Yes 0 0 2 The quarter the project was let for construction FISC_YEAR Small Integer Yes 0 0 2 The fiscal year for the project CAL_YEAR Small Integer Yes 0 0 2 The calendar year for the project ROUTE BGN_MILEPT END_MILEPT Table HAL_Refmkr Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Statistically High Accident sections along reference marker routes and intersections OBJECTID OID String Yes 13 The GIS route the accident location is referenced to Small Integer Yes 0 0 2 The start point along the route Small Integer Yes 0 0 2 The end point along the route HAL_YR String Yes 4 The year for which the High Accident Location data exists RT_NUM String Yes 4 A number assigned to a highway by either federal or state governments SEG_LEN Double Yes 0 0 The count of the number of reference markers multiplied by 1/10th HAL_TYPE String Yes 3 Identifies whether the High Accident Location is a (PIL), (SDL) or a (PII). REG_CO String Yes 2 Code that identifies the county within a region REGION String Yes 1 The DOT region for the HAL AVG_VOL String Yes 6 Computed total average volume EXPOSURE Double Yes 0 0 The Million Vehicle Mile count for the section of road CLSF_CDE String Yes 3 Calculated classifications for accident related rates, percentages and costs NUM_FAT_ACC Double Yes 0 0 Number of fatal accidents NUM_INJ_ACC Double Yes 0 0 Number of injury accidents NUM_PDO_ACC Double Yes 0 0 Number of property damage only accidetns NUM_INT_ACC Double Yes 0 0 Number of intersection accidents UCL Double Yes 0 0 Upper limit of statistical confidence for HAL type RED_IND Double Yes 0 0 Accident reductions required to obtain normal accident status SEV_RANK Double Yes 0 0 Severity rank of the High Accident Location ROUTE_GIS From_RM To_RM Table Sufficiency_Ratings_Milept Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Pavement Sufficiency data file for 2000 OBJECTID OID String Yes 9 The GIS route referenced Single Yes 0 0 The from mile along the route Single Yes 0 0 The to mile along the route Sufficiency String Yes 1 Year 2000 surface score STMP String Yes 4 Start milepost location SHNUM String Yes 5 State highway number RES String Yes 3 Residency code RD String Yes 1 Number of roadways LN String Yes 1 Number of lanes PWD String Yes 2 Pavement width SHWD String Yes 2 Shoulder width SHT String Yes 1 Shoulder type CYS String Yes 1 Current year surface score MWD String Yes 1 Road median width MT String Yes 1 Road median type SURFT String Yes 1 Surface type BASET String Yes 1 Base type SUBBT String Yes 1 Sub-base type TERA String Yes 1 Terrain AREA String Yes 1 Area type CULT String Yes 1 Culture PARK String Yes 1 Percent Parking PASS String Yes 2 Passing sight distance TRK String Yes 2 Percent of trucks TRYR String Yes 2 Traffic count year (2 digits) DHV String Yes 4 Design hour volume (*10) AADT String Yes 5 AADT volume (*10) FC String Yes 2 Functional Class HCC String Yes 1 Highway control code YS String Yes 1 Year scored (current year) YLW String Yes 2 Year of latest work ACC String Yes 1 Access control ARC String Yes 3 Adjusted rated capacity VC String Yes 4 Volume-capacity rating NHS String Yes 1 National highway system DOMDIS String Yes 6 Dominant distress REC String Yes 1 Record code = 1 TRRT String Yes 1 Tandem truck TRKYR String Yes 2 Truck classification year WRKT String Yes 1 Work type OLAP String Yes 1 Route status - overlap code PVT String Yes 1 Pavement type GISRTE FMILE TMILE Simple feature class RefmkrRoute Contains Z values Contains M values Geometry Polyline Yes No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Routes with measures that correspond to reference marker locations along roads OBJECTID OID Shape Geometry Yes String Yes 9 The route number Shape_Length Double Yes 0 0 ROUTE Simple feature class MileptHistRoute Contains Z values Contains M values Geometry Polyline Yes No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Historical layer of Milepost routes OBJECTID OID Shape Geometry Yes ROUTE String Yes 9 ACTIVE String Yes 1 YEAR_ACTIVATED Small Integer Yes 0 0 2 YEAR_RETIRED Small Integer Yes 0 0 2 Shape_Length Double Yes 0 0 Route Identifier If the route status is active The year the route was activated The year the route was retired Simple feature class OffstateRoute Contains Z values Contains M values Geometry Polyline Yes No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Routes along non-state roads OBJECTID OID Shape Geometry Yes ROUTE String Yes 9 ACTIVE String Yes 1 YEAR_ACTIVATED Small Integer Yes 0 0 2 YEAR_RETIRED Small Integer Yes 0 0 2 Shape_Length Double Yes 0 0 Route Identifier If the route status is active The year the route was activated The year the route was retired Simple feature class ThruwayRoute Contains Z values Contains M values Geometry Polyline Yes No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls New York Thruway maintained by Thruway Authority OBJECTID OID Shape Geometry Yes ROUTE String Yes 12 Route Number Shape_Length Double Yes 0 0 Simple feature class CoupletRoute Contains Z values Contains M values Geometry Polyline Yes No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Divided highways separated by more than 200 feet OBJECTID OID Shape Geometry Yes ROUTE String Yes 9 Route Identifier ACTIVE String Yes 1 If the route status is active YEAR_ACTIVATED Small Integer Yes 0 0 2 The year the route was activated YEAR_RETIRED Small Integer Yes 0 0 2 The year the route was retired Shape_Length Double Yes 0 0 Simple feature class AlbReferencePoint Contains Z values Contains M values Geometry Point No No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Albany area Reference Points, simulates NSDI Framework transportation reference points (FTRP) OBJECTID OID Shape Geometry Yes FTRP_ID String Yes 17 Unique national reference point identifier Simple feature class AlbReferenceLine Contains Z values Contains M values Geometry Polyline No No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Albany area Reference Lines, simulates NSDI Framework transportation reference segments (FTSeg) OBJECTID OID Shape Geometry Yes CATEGORY String Yes 12 Category of road NAME String Yes 32 Name of road Shape_Length Double Yes 0 0 FTSEG_ID String Yes 17 Unique national road identifier Simple feature class ReferencePoint Contains Z values Contains M values Geometry Point No No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls OBJECTID OID Shape Geometry Yes FTRP_ID String Yes 17 State DOT Reference Points, simulates NSDI Framework transportation reference points (FTRP) Unique national reference point identifier Simple feature class ReferenceLine Contains Z values Contains M values Geometry Polyline No No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls OBJECTID OID Shape Geometry Yes Shape_Length Double Yes 0 0 FTSEG_ID String Yes 17 State DOT Reference Lines, simulates NSDI Framework transportation reference segments (FTSeg) Unique national road identifier Coded value domain ACCD_TYPE Description Field type Split policy Merge policy ACCD_TYPE String Default Value Default Value 01 Collision With Motor Vehicle 02 Collision With Pedestrian 03 Collision With Bicyclist 04 Collision With Animal 05 Collision With RailRoad Train 06 Collision With In-Line Skater 10 Collision With Other 11 Collision With Light/Support Utility 12 Collision With Guard Rail 13 Collision With Crash Cushion 14 Collision With Sign Post 15 Collision With Tree 16 Collision With Building/Wall 17 Collision With Curbing 18 Collision With Fence 19 Collision With Bridge/Structure 20 Collision With Culvert/Head Wall 21 Collision With Median/Barrier 22 Collision With Snow Embankment 23 Collision With Earth Element/Rock Cut/Ditch 24 Collision With Fire Hydrant 25 Collision With Guiderail End 26 Collision With Median Barrier End 27 Collision With Other Barrier 30 Collision With Other Fixed Object 31 Overturned 32 Fire/Explosion 33 Submersion 34 Ran Off Road Only 40 Other Non-Collision ?? Invalid Code ZZ Not Reported Coded value domain COLL_TYPE Description Field type Split policy Merge policy COLL_TYPE String Default Value Default Value 0 Left Turn (With Other Car) 1 Rear End 2 Overtaking 3 Left Turn (Against Other Car) 4 Right Angle 5 Right Turn (Against Other Car) 6 Right Turn (With Other Car) 7 Head On 8 Side Swipe 9 Other ? Invalid Code Z Not Reported Coded value domain COUNTY Description Field type Split policy Merge policy COUNTY String Default Value Default Value 11 Albany Coded value domain EXT_INJURY Description Field type Split policy Merge policy EXT_INJURY String Default Value Default Value 1 Apparent Death 2 Unconscious 3 Semi-Conscious 4 Incoherent 5 Shock 6 Conscious ? Invalid Code A Incapacitating Injury B Non-Incapacitating Injury C Possible Injury K Killed X Unknown Coded value domain LIGHT_COND Description Field type Split policy Merge policy LIGHT_COND String Default Value Default Value 1 Daylight 2 Dawn 3 Dusk 4 Dark Road Lighted 5 Dark Road Unlighted ? Invalid Code Z Not Reported Coded value domain LOCATION Description Field type Split policy Merge policy LOCATION String Default Value Default Value 1 First Event Occurred On Road 2 First Event Occured Off Road ? Invalid Code, Not Reported Coded value domain PED_ACTION Description Field type Split policy Merge policy PED_ACTION String Default Value Default Value 00 Pedestiran Not Involved/Unreported 01 Crossing With Signal 02 Crossing Against Signal 03 Crossing, No Signal, Marked Crosswalk 04 Crossing, No Signal or Crosswalk 05 Along Highway With Traffic 06 Along Highway With Traffic 07 Along Highway Against Traffic 08 Child Getting On/Off Schoolbus 09 Getting On/Off Vehicle 10 Pushing/Working On Car 11 Working in Roadway 12 Playing in Roadway 13 Other Action in Roadway 14 Not in Roadway ?? Invalid Code Coded value domain PED_LOC Description Field type Split policy Merge policy PED_LOC String Default Value Default Value 0 Pedestrian Not Involved/Unreported 1 Pedestrian At Intersection 2 Pedestrian Not At Intersection ? Invalid Code Coded value domain ROAD_CHAR Description Field type Split policy Merge policy ROAD_CHAR String Default Value Default Value 1 Straight And Level 2 Straight/Grade 3 Straight At Hillcrest 4 Curve And Level 5 Curve And Grade 6 Curve And Hillcrest ? Invalid Code Z Not Reported Coded value domain ROAD_SURF Description Field type Split policy Merge policy ROAD_SURF String Default Value Default Value 0 Other 1 Dry 2 Wet 3 Muddy 4 Snow/Ice 5 Slush ? Invalid Code Z Not Reported Coded value domain ROAD_SYS Description Field type Split policy Merge policy ROAD_SYS String Default Value Default Value - Interstate 0 Parking Lot, Other Non-Traffic 1 State 2 County 3 Town 4 City Street 5 Parkway 6 Thruway 7 Northway 8 Limited Access 9 Unknown ? Invalid Code Z Not Reported Coded value domain TRAF_CNTL Description Field type Split policy Merge policy TRAF_CNTL String Default Value Default Value + Stopped School Bus & Stopped School Bus - Other 0 RR Crossing Gates 1 None 2 Traffic Signal 3 Stop Sign 4 Flashing Light 5 Yield Sign 6 Officer/Flagman/Guard 7 No Passing Zone 8 RR Crossing Sign 9 RR Crossing Flash Light C Highway Work Area (Construction) D Maintenance Work Area E Utility Work Area ? Invalid Code Z Not Reported Coded value domain WEATHER Description Field type Split policy Merge policy WEATHER String Default Value Default Value 0 Other 1 Clear 2 Cloudy 3 Rain 4 Snow 5 Sleet/Hail/Freezing Rain 6 Fog/Smoke/Smog ? Invalid Code Z Not Supported Simple feature class MileptRoute Contains Z values Contains M values Geometry Polyline Yes No Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Routes with measure defined according to milepost markers along roads OBJECTID OID Shape Geometry Yes String Yes 9 ACTIVE String Yes 1 YEAR_ACTIVATED Small Integer Yes 0 0 2 YEAR_RETIRED Small Integer Yes 0 0 2 Shape_Length Double Yes 0 0 Route Identifier If the route status is active The year the route was activated The year the route was retired ROUTE FromMeasure Name ToMeasure FromMeasure Name ToMeasure FromMeasure Name ToMeasure Y coordinate X coordinate Table Incidents_XY Data type Field name Prec- ision Scale Length Domain Default value Allow nulls Incidents with an absolute X/Y value OBJECTID OID INC_ID Integer Yes 0 Unique incident identifier EST_DURATI Double Yes 0 0 Estimated duration of the accident INCIDENT_S String Yes 17 Place a succinct description of the field in this text INC_TYPE String Yes 20 Type of incident LANES_BLOC String Yes 15 Number of lanes blocked by the incident DATE_ Date Yes 0 0 8 Date the incident occurred Double Yes 0 0 X coordinate in UTM Double Yes 0 0 Y Coordinate in UTM X_COOR Y_COOR Line event table Line event table Line event table Line event table Point event table Point event table Route event source Route event source Key Topology R1Route_Topology Cluster tolerance 0.006185288 Participating feature classes and ranks Topology rules ReferenceLIne ReferenceLIne ReferenceLIne ReferenceLIne ReferenceLIne Comparision feature class RouteMPHist RouteOffState RouteRefmkr RouteMilept ReferenceLine ReferencePoint RouteCouplet Feature class RouteThruway 5 5 5 5 1 5 5 Rank 5 ReferencePoint ReferenceLIne RouteOffState RouteRefmkr RouteMilept RouteMPHist ReferenceLine ReferenceLine RouteCouplet Origin feature class ReferenceLine RouteThruway Must be covered by feature class of Must be covered by feature class of Must be covered by feature class of Must be covered by feature class of Must not over Must not intersect or touch interior Must be covered by feature class of Topology rule Endpoint must be covered by Must be covered by feature class of The geodatabase structure Feature dataset R1Route Topology R1Route_Topology Geodatabase Line feature class ReferenceLine Point feature class ReferencePoint Line feature class RouteCouplet Line feature class RouteMilept Line feature class RouteMPHist Line feature class RouteOffState Line feature class RouteRefmkr Line feature class RouteThruway Table Accidents_Refmkr Table Capital_Improvements_Milept Table HAL_Refmkr Table Incidents_XY Table PMS_Refmkr Table Sufficiency_Ratings_Milept Table Transform_Output Feature dataset Imlications Line feature class albroad_arc Line feature class r1route_arc Geodatabase Table Accidents_Refmkr Feature dataset Implications Line feature class albroad_arc Line feature class r1route_arc Feature dataset R1Route Line feature class ReferenceLine Line feature class ReferencePoint Topology R1Route_Topology Line feature class RouteCouplet Line feature class RouteMilept Line feature class RouteMPHist Line feature class RouteOffState Line feature class RouteRefmkr Line feature class RouteThruway Table Capitol_Improvements_Milept Table HAL_Refmkr Table Incidents_XY Table PMS_Refmkr Table Sufficiency_Ratings_Milept Table Transform_Output Event layer Event layer Event layer Event layer The Catalog view t H E a R C g i s t R A N S P O R T A T I O N d A T A M O D E L The thematic layers Layer Map use Data source Representation Spatial relationships Map scale and accuracy Symbology and annotation Line events Display and analyze DOT assets, activities, and incidents Department of Transportation departmental systems Linear-referenced line events Line events are coincident with routes Based on route geometry and measures Typically drawn as thick lines colored by single attribute Layer Map use Data source Representation Spatial relationships Map scale and accuracy Symbology and annotation Routes Used to display events on DOT maintained roads State Department of Transportation Polylines with measures Should share geometry with base maps and navigation Typical map scales range from 1:24 000 to 1:250 000 Typically drawn as thick lines colored by single attribute Layer Map use Data source Representation Spatial relationships Map scale and accuracy Symbology and annotation Point events Display and analyze DOT assets, activities, and incidents Department of Transportation departmental systems Linear-referenced point events Point events occur along routes Based on route geometry and measures Typically drawn as circles colored by single attribute Layer Map use Data source Representation Spatial relationships Map scale and accuracy Symbology and annotation Digital orthophoto Map background Aerial photogrammetry and satellite sources Raster Raster cells cover the image area 1 to 2.5 meter cell size Tone, contrast, and balance of gray scale or color presentation Layer Map use Data source Representation Spatial relationships Map scale and accuracy Symbology and annotation Reference layer A common underlying geometry for all transportation users Multiple agencies, could be a national dataset Lines and points Could share geometry with routes Typical map scales range from 1:24 000 to 1:250 000 Simple gray lines as background reference Layer Map use Data source Representation Spatial relationships Map scale and accuracy Symbology and annotation Basemap Map background Topographic maps and other cartographic data sources Raster or vector maps Should share geometry with routes and navigation Typical map scales range from 1:24 000 to 1:250 000 Detailed transportation symbolized by class such as bridges, overpasses Layer Map use Data source Representation Spatial relationships Map scale and accuracy Symbology and annotation Navigation For routing, navigation, and logistics Basemap features plus navigation properties Edges, transfers, turns, travel costs Topology networks, share geometry with routes and base maps Typical map scales range from 1:24 000 to 1:250 000 Varies with the source data product
-
Upload
mathias-eder -
Category
Documents
-
view
264 -
download
0
description
Java Server Face Manual
Transcript of Java Server Face Manual
Using ArcGIS Desktop
84
The process of implementing your geodatabase design involves building the geodatabase
structure, and then populating it with your data. There are two ways to build thegeodatabase structure.
• Use ArcCatalog tools to create the various geodatabase datasets. There are a number
of tools in ArcCatalog that let you create new feature datasets, feature classes, tables,relationship classes, topologies and other geodatabase datasets. These tools arediscussed as separate topics later in this chapter.
• Use an existing geodatabase data model template. This can be one (or more) of the
data models available at the ESRI Web site (http://support.esri.com/datamodels), or
a template that someone else provides to you. That saves you the step of defining the
geodatabase structure using the ArcCatalog tools. You’ll likely use the tools, though, to
modify the templates to match your design. The process for importing and modifying ageodatabase data model template is discussed as a separate topic later in this chapter.
Importing data to a geodatabase and editing are discussed in Chapter 3, ‘Data Compilation
and Editing’.
Document your geodatabase design Once you’ve solidified your geodatabase design, you’ll want to document it for reference.
Various methods can be used to describe your database design and decisions: drawings,
map layer examples, schema diagrams, reports, and metadata documents. The data modelssection at http://support.esri.com/datamodels has sample geodatabase documentation froma variety of industries.
Key
FromMeasure
Name
ToMeasure
Measure
Route
TableAccidents_Refmkr
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Detailed information for AlbanyCounty point accident locations alongroutes
OBJECTID OID
String Yes 9 The route the accident occurred on
Small Integer Yes 0 0 2 The location along the route for the accident
MUNI String Yes 2 Municipality where the accident occurred
POLICE_DPT String Yes 5 The police department that documented the accident
PRECINCT String Yes 4 The police precinct
CASE_NUM String Yes 7 The case number for the accident
NUM_KILLED Double Yes 0 0 The number of people killed
NUM_INJURY Double Yes 0 0 The number of people injured
EXT_INJURY String Yes EXT_INJURY 5 The extent of injuries
ACCD_DATE String Yes 11 The date of the accident
ACCD_TIME String Yes 2 The time of the accident
NUM_VEH Double Yes 0 0 The number of vehicles involved
LOCATION String Yes LOCATION 1 The general location of the accident
ACCD_TYPE String Yes ACCD_TYPE 2 The type of accident
COLL_TYPE String Yes COLL_TYPE 1 The type of collision
PED_LOC String Yes PED_LOC 1 The location of any pedestrians involved
PED_ACTION String Yes PED_ACTION 2 What the pedestrian was doing when the accident occurred
ROAD_SURF String Yes ROAD_SURF 1 The road surface condition
WEATHER String Yes WEATHER 1 The weather conditions
ROAD_CHAR String Yes ROAD_CHAR 1 The road characteristics
TRAF_CNTL String Yes TRAF_CNTL 1 Traffic control devices
LIGHT_COND String Yes LIGHT_COND 1 The light conditions at the time of the accident
ROUTE_RM
Measure
TablePMS_Refmkr
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Preventative Maintenance Screenrecords along reference marker routes
OBJECTID OID
String Yes 9 The route identifier for the PMS record
Small Integer Yes 0 0 2 The from location along the route
Small Integer Yes 0 0 2 The to location along the route
AADT_X_100 Small Integer Yes 0 0 2 Accident volume
NO_ROADW Small Integer Yes 0 0 2 Number of roadways
NO_LANES Small Integer Yes 0 0 2 Number of Lanes
AREA_TYPE Small Integer Yes 0 0 2 Pavement area type
CULTURE Small Integer Yes 0 0 2 ***
FATAL_ACC Small Integer Yes 0 0 2 Number of fatal accidents
INJ_ACC Small Integer Yes 0 0 2 Number of injury accidents
PDO_ACC Small Integer Yes 0 0 2 Number of property damage only accidents
INTRS_ACC Small Integer Yes 0 0 2 Accidents in intersection
NON_IN_ACC Small Integer Yes 0 0 2 Accidents not in intersection
TOT_ACC Small Integer Yes 0 0 2 Total accidents
END_DATE String Yes 6 End date for the pavement record
REG_CNTY String Yes 2 County within the DOT region
SERV_RANKN Single Yes 0 0 Severity rank for the section of pavement
ROUTE_RM
F_RM
T_RM
TableCapital_Improvements_Milept
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Capital Improvement Projectlocations along milepoint routes
OBJECTID OID
MAJOR_PIN String Yes 6 Major project number
String Yes 9 The route the project occurs along
Single Yes 0 0 Starting milepoint reference
Single Yes 0 0 Ending milepoint reference
CENT_LN_MI Single Yes 0 0 Place a succinct description of the field in this text
PROJ_TITLE String Yes 60 Description of the project
LET_DATE String Yes 11 The date the project was let out for construction
PSE_ESTIMATE Double Yes 0 0 Project supervisor cost estimate
PSE_DATE String Yes 11 Project supervisor estimate date
PROJ_EST Double Yes 0 0 Project cost estimate
CONST_COST Double Yes 0 0 Construction Cost
PROJ_MGR_F String Yes 15 Project Manager (first)
PROJ_MGR_L String Yes 18 Project Manager (last)
WORK_TYPE String Yes 60 Type of project work
SUB_WRK_TYPE String Yes 60 More detailed project classification
PROJ_STUS_ String Yes 60 Project status
REGION_NUM String Yes 2 DOT Region number for the project
LASTUPDATE String Yes 11 Last date the information was updated
LET_QUARTE Small Integer Yes 0 0 2 The quarter the project was let for construction
FISC_YEAR Small Integer Yes 0 0 2 The fiscal year for the project
CAL_YEAR Small Integer Yes 0 0 2 The calendar year for the project
ROUTE
BGN_MILEPT
END_MILEPT
TableHAL_Refmkr
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Statistically High Accident sectionsalong reference marker routes andintersections
OBJECTID OID
String Yes 13 The GIS route the accident location is referenced to
Small Integer Yes 0 0 2 The start point along the route
Small Integer Yes 0 0 2 The end point along the route
HAL_YR String Yes 4 The year for which the High Accident Location data exists
RT_NUM String Yes 4 A number assigned to a highway by either federal or state governments
SEG_LEN Double Yes 0 0 The count of the number of reference markers multiplied by 1/10th
HAL_TYPE String Yes 3 Identifies whether the High Accident Location is a (PIL), (SDL) or a (PII).
REG_CO String Yes 2 Code that identifies the county within a region
REGION String Yes 1 The DOT region for the HAL
AVG_VOL String Yes 6 Computed total average volume
EXPOSURE Double Yes 0 0 The Million Vehicle Mile count for the section of road
CLSF_CDE String Yes 3 Calculated classifications for accident related rates, percentages and costs
NUM_FAT_ACC Double Yes 0 0 Number of fatal accidents
NUM_INJ_ACC Double Yes 0 0 Number of injury accidents
NUM_PDO_ACC Double Yes 0 0 Number of property damage only accidetns
NUM_INT_ACC Double Yes 0 0 Number of intersection accidents
UCL Double Yes 0 0 Upper limit of statistical confidence for HAL type
RED_IND Double Yes 0 0 Accident reductions required to obtain normal accident status
SEV_RANK Double Yes 0 0 Severity rank of the High Accident Location
ROUTE_GIS
From_RM
To_RM
TableSufficiency_Ratings_Milept
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Pavement Sufficiency data file for2000
OBJECTID OID
String Yes 9 The GIS route referenced
Single Yes 0 0 The from mile along the route
Single Yes 0 0 The to mile along the route
Sufficiency String Yes 1 Year 2000 surface score
STMP String Yes 4 Start milepost location
SHNUM String Yes 5 State highway number
RES String Yes 3 Residency code
RD String Yes 1 Number of roadways
LN String Yes 1 Number of lanes
PWD String Yes 2 Pavement width
SHWD String Yes 2 Shoulder width
SHT String Yes 1 Shoulder type
CYS String Yes 1 Current year surface score
MWD String Yes 1 Road median width
MT String Yes 1 Road median type
SURFT String Yes 1 Surface type
BASET String Yes 1 Base type
SUBBT String Yes 1 Sub-base type
TERA String Yes 1 Terrain
AREA String Yes 1 Area type
CULT String Yes 1 Culture
PARK String Yes 1 Percent Parking
PASS String Yes 2 Passing sight distance
TRK String Yes 2 Percent of trucks
TRYR String Yes 2 Traffic count year (2 digits)
DHV String Yes 4 Design hour volume (*10)
AADT String Yes 5 AADT volume (*10)
FC String Yes 2 Functional Class
HCC String Yes 1 Highway control code
YS String Yes 1 Year scored (current year)
YLW String Yes 2 Year of latest work
ACC String Yes 1 Access control
ARC String Yes 3 Adjusted rated capacity
VC String Yes 4 Volume-capacity rating
NHS String Yes 1 National highway system
DOMDIS String Yes 6 Dominant distress
REC String Yes 1 Record code = 1
TRRT String Yes 1 Tandem truck
TRKYR String Yes 2 Truck classification year
WRKT String Yes 1 Work type
OLAP String Yes 1 Route status - overlap code
PVT String Yes 1 Pavement type
GISRTE
FMILE
TMILE
Simple feature classRefmkrRoute Contains Z values
Contains M valuesGeometry Polyline
YesNo
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Routes with measures that correspondto reference marker locations alongroads
OBJECTID OID
Shape Geometry Yes
String Yes 9 The route number
Shape_Length Double Yes 0 0
ROUTE
Simple feature classMileptHistRoute Contains Z values
Contains M valuesGeometry Polyline
YesNo
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Historical layer of Milepost routes
OBJECTID OID
Shape Geometry Yes
ROUTE String Yes 9
ACTIVE String Yes 1
YEAR_ACTIVATED Small Integer Yes 0 0 2
YEAR_RETIRED Small Integer Yes 0 0 2
Shape_Length Double Yes 0 0
Route Identifier
If the route status is active
The year the route was activated
The year the route was retired
Simple feature classOffstateRoute Contains Z values
Contains M valuesGeometry Polyline
YesNo
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Routes along non-state roads
OBJECTID OID
Shape Geometry Yes
ROUTE String Yes 9
ACTIVE String Yes 1
YEAR_ACTIVATED Small Integer Yes 0 0 2
YEAR_RETIRED Small Integer Yes 0 0 2
Shape_Length Double Yes 0 0
Route Identifier
If the route status is active
The year the route was activated
The year the route was retired
Simple feature classThruwayRoute Contains Z values
Contains M valuesGeometry Polyline
YesNo
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
New York Thruway maintained byThruway Authority
OBJECTID OID
Shape Geometry Yes
ROUTE String Yes 12
Route NumberShape_Length Double Yes 0 0
Simple feature classCoupletRoute Contains Z values
Contains M valuesGeometry Polyline
YesNo
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Divided highways separated by morethan 200 feet
OBJECTID OID
Shape Geometry Yes
ROUTE String Yes 9 Route Identifier
ACTIVE String Yes 1 If the route status is active
YEAR_ACTIVATED Small Integer Yes 0 0 2 The year the route was activated
YEAR_RETIRED Small Integer Yes 0 0 2 The year the route was retired
Shape_Length Double Yes 0 0
Simple feature classAlbReferencePoint Contains Z values
Contains M valuesGeometry Point
NoNo
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Albany area Reference Points, simulatesNSDI Framework transportationreference points (FTRP)
OBJECTID OID
Shape Geometry Yes
FTRP_ID String Yes 17 Unique national reference point identifier
Simple feature classAlbReferenceLine Contains Z values
Contains M valuesGeometry Polyline
NoNo
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Albany area Reference Lines, simulatesNSDI Framework transportationreference segments (FTSeg)
OBJECTID OID
Shape Geometry Yes
CATEGORY String Yes 12 Category of road
NAME String Yes 32 Name of road
Shape_Length Double Yes 0 0
FTSEG_ID String Yes 17 Unique national road identifier
Simple feature classReferencePoint Contains Z values
Contains M valuesGeometry Point
NoNo
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
OBJECTID OID
Shape Geometry Yes
FTRP_ID String Yes 17
State DOT Reference Points, simulatesNSDI Framework transportationreference points (FTRP)
Unique national reference point identifier
Simple feature classReferenceLine Contains Z values
Contains M valuesGeometry Polyline
NoNo
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
OBJECTID OID
Shape Geometry Yes
Shape_Length Double Yes 0 0
FTSEG_ID String Yes 17
State DOT Reference Lines, simulatesNSDI Framework transportationreference segments (FTSeg)
Unique national road identifier
Coded value domain
ACCD_TYPEDescription
Field type
Split policy
Merge policy
ACCD_TYPE
String
Default Value
Default Value
DescriptionCode
01 Collision With Motor Vehicle
02 Collision With Pedestrian
03 Collision With Bicyclist
04 Collision With Animal
05 Collision With RailRoad Train
06 Collision With In-Line Skater
10 Collision With Other
11 Collision With Light/Support Utility
12 Collision With Guard Rail
13 Collision With Crash Cushion
14 Collision With Sign Post
15 Collision With Tree
16 Collision With Building/Wall
17 Collision With Curbing
18 Collision With Fence
19 Collision With Bridge/Structure
20 Collision With Culvert/Head Wall
21 Collision With Median/Barrier
22 Collision With Snow Embankment
23 Collision With Earth Element/Rock Cut/Ditch
24 Collision With Fire Hydrant
25 Collision With Guiderail End
26 Collision With Median Barrier End
27 Collision With Other Barrier
30 Collision With Other Fixed Object
31 Overturned
32 Fire/Explosion
33 Submersion
34 Ran Off Road Only
40 Other Non-Collision
?? Invalid Code
ZZ Not Reported
Coded value domain
COLL_TYPEDescription
Field type
Split policy
Merge policy
COLL_TYPE
String
Default Value
Default Value
DescriptionCode
0 Left Turn (With Other Car)
1 Rear End
2 Overtaking
3 Left Turn (Against Other Car)
4 Right Angle
5 Right Turn (Against Other Car)
6 Right Turn (With Other Car)
7 Head On
8 Side Swipe
9 Other
? Invalid Code
Z Not Reported
Coded value domain
COUNTYDescription
Field type
Split policy
Merge policy
COUNTY
String
Default Value
Default Value
DescriptionCode
11 Albany
Coded value domain
EXT_INJURYDescription
Field type
Split policy
Merge policy
EXT_INJURY
String
Default Value
Default Value
DescriptionCode
1 Apparent Death
2 Unconscious
3 Semi-Conscious
4 Incoherent
5 Shock
6 Conscious
? Invalid Code
A Incapacitating Injury
B Non-Incapacitating Injury
C Possible Injury
K Killed
X Unknown
Coded value domain
LIGHT_CONDDescription
Field type
Split policy
Merge policy
LIGHT_COND
String
Default Value
Default Value
DescriptionCode
1 Daylight
2 Dawn
3 Dusk
4 Dark Road Lighted
5 Dark Road Unlighted
? Invalid Code
Z Not Reported
Coded value domain
LOCATIONDescription
Field type
Split policy
Merge policy
LOCATION
String
Default Value
Default Value
DescriptionCode
1 First Event Occurred On Road
2 First Event Occured Off Road
? Invalid Code, Not Reported
Coded value domain
PED_ACTIONDescription
Field type
Split policy
Merge policy
PED_ACTION
String
Default Value
Default Value
DescriptionCode
00 Pedestiran Not Involved/Unreported
01 Crossing With Signal
02 Crossing Against Signal
03 Crossing, No Signal, Marked Crosswalk
04 Crossing, No Signal or Crosswalk
05 Along Highway With Traffic
06 Along Highway With Traffic
07 Along Highway Against Traffic
08 Child Getting On/Off Schoolbus
09 Getting On/Off Vehicle
10 Pushing/Working On Car
11 Working in Roadway
12 Playing in Roadway
13 Other Action in Roadway
14 Not in Roadway
?? Invalid Code
Coded value domain
PED_LOCDescription
Field type
Split policy
Merge policy
PED_LOC
String
Default Value
Default Value
DescriptionCode
0 Pedestrian Not Involved/Unreported
1 Pedestrian At Intersection
2 Pedestrian Not At Intersection
? Invalid Code
Coded value domain
ROAD_CHARDescription
Field type
Split policy
Merge policy
ROAD_CHAR
String
Default Value
Default Value
DescriptionCode
1 Straight And Level
2 Straight/Grade
3 Straight At Hillcrest
4 Curve And Level
5 Curve And Grade
6 Curve And Hillcrest
? Invalid Code
Z Not Reported
Coded value domain
ROAD_SURFDescription
Field type
Split policy
Merge policy
ROAD_SURF
String
Default Value
Default Value
DescriptionCode
0 Other
1 Dry
2 Wet
3 Muddy
4 Snow/Ice
5 Slush
? Invalid Code
Z Not Reported
Coded value domain
ROAD_SYSDescription
Field type
Split policy
Merge policy
ROAD_SYS
String
Default Value
Default Value
DescriptionCode
- Interstate
0 Parking Lot, Other Non-Traffic
1 State
2 County
3 Town
4 City Street
5 Parkway
6 Thruway
7 Northway
8 Limited Access
9 Unknown
? Invalid Code
Z Not Reported
Coded value domain
TRAF_CNTLDescription
Field type
Split policy
Merge policy
TRAF_CNTL
String
Default Value
Default Value
DescriptionCode
+ Stopped School Bus
& Stopped School Bus
- Other
0 RR Crossing Gates
1 None
2 Traffic Signal
3 Stop Sign
4 Flashing Light
5 Yield Sign
6 Officer/Flagman/Guard
7 No Passing Zone
8 RR Crossing Sign
9 RR Crossing Flash Light
C Highway Work Area (Construction)
D Maintenance Work Area
E Utility Work Area
? Invalid Code
Z Not Reported
Coded value domain
WEATHERDescription
Field type
Split policy
Merge policy
WEATHER
String
Default Value
Default Value
DescriptionCode
0 Other
1 Clear
2 Cloudy
3 Rain
4 Snow
5 Sleet/Hail/Freezing Rain
6 Fog/Smoke/Smog
? Invalid Code
Z Not Supported
Simple feature classMileptRoute Contains Z values
Contains M valuesGeometry Polyline
YesNo
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Routes with measure definedaccording to milepost markers alongroads
OBJECTID OID
Shape Geometry Yes
String Yes 9
ACTIVE String Yes 1
YEAR_ACTIVATED Small Integer Yes 0 0 2
YEAR_RETIRED Small Integer Yes 0 0 2
Shape_Length Double Yes 0 0
Route Identifier
If the route status is active
The year the route was activated
The year the route was retired
ROUTE
FromMeasure
Name
ToMeasure
FromMeasure
Name
ToMeasure
FromMeasure
Name
ToMeasure
Y coordinate
X coordinate
TableIncidents_XY
Data typeField namePrec-ision Scale LengthDomain
Defaultvalue
Allownulls
Incidents with an absolute X/Y value
OBJECTID OID
INC_ID Integer Yes 0 Unique incident identifier
EST_DURATI Double Yes 0 0 Estimated duration of the accident
INCIDENT_S String Yes 17 Place a succinct description of the field in this text
INC_TYPE String Yes 20 Type of incident
LANES_BLOC String Yes 15 Number of lanes blocked by the incident
DATE_ Date Yes 0 0 8 Date the incident occurred
Double Yes 0 0 X coordinate in UTM
Double Yes 0 0 Y Coordinate in UTM
X_COOR
Y_COOR
Line event table
Line event table
Line event table
Line event table
Point event table
Point event table
Route event source
Route event source
Key
Topology
R1Route_TopologyCluster tolerance 0.006185288
Participating feature classes and ranks
Topology rules
ReferenceLIne
ReferenceLIne
ReferenceLIne
ReferenceLIne
ReferenceLIne
Comparision feature class
RouteMPHist
RouteOffState
RouteRefmkr
RouteMilept
ReferenceLine
ReferencePoint
RouteCouplet
Feature class
RouteThruway
5
5
5
5
1
5
5
Rank
5
ReferencePoint
ReferenceLIne
RouteOffState
RouteRefmkr
RouteMilept
RouteMPHist
ReferenceLine
ReferenceLine
RouteCouplet
Origin feature class
ReferenceLine
RouteThruway
Must be covered by feature class of
Must be covered by feature class of
Must be covered by feature class of
Must be covered by feature class of
Must not over
Must not intersect or touch interior
Must be covered by feature class of
Topology rule
Endpoint must be covered by
Must be covered by feature class of
The geodatabase structure
Feature dataset
R1Route Topology
R1Route_Topology
Geodatabase
Line feature classReferenceLine
Point feature class
ReferencePoint
Line feature classRouteCouplet
Line feature class
RouteMilept
Line feature classRouteMPHist
Line feature class
RouteOffState
Line feature classRouteRefmkr
Line feature class
RouteThruway
Table
Accidents_Refmkr
TableCapital_Improvements_Milept
Table
HAL_Refmkr
TableIncidents_XY
Table
PMS_Refmkr
TableSufficiency_Ratings_Milept
Table
Transform_Output
Feature dataset
Imlications
Line feature class
albroad_arc
Line feature class
r1route_arc
Geodatabase
Table
Accidents_Refmkr
Feature dataset
Implications
Line feature class
albroad_arc
Line feature class
r1route_arc
Feature dataset
R1Route
Line feature class
ReferenceLine
Line feature class
ReferencePoint
Topology
R1Route_Topology
Line feature class
RouteCouplet
Line feature class
RouteMilept
Line feature class
RouteMPHist
Line feature class
RouteOffState
Line feature class
RouteRefmkr
Line feature class
RouteThruway
Table
Capitol_Improvements_Milept
Table
HAL_Refmkr
Table
Incidents_XY
Table
PMS_Refmkr
Table
Sufficiency_Ratings_Milept
Table
Transform_Output
Event layer
Event layer
Event layer
Event layer
The Catalog view
tHE aRCgis tRANSPORTATION dATA MODEL
The thematic layers
Layer
Map use
Data source
Representation
Spatial relationships
Map scale and accuracy
Symbology and annotation
Line events
Display and analyze DOT assets, activities, and incidents
Department of Transportation departmental systems
Linear-referenced line events
Line events are coincident with routes
Based on route geometry and measures
Typically drawn as thick lines colored by single attribute
Layer
Map use
Data source
Representation
Spatial relationships
Map scale and accuracy
Symbology and annotation
Routes
Used to display events on DOT maintained roads
State Department of Transportation
Polylines with measures
Should share geometry with base maps and navigation
Typical map scales range from 1:24 000 to 1:250 000
Typically drawn as thick lines colored by single attribute
Layer
Map use
Data source
Representation
Spatial relationships
Map scale and accuracy
Symbology and annotation
Point events
Display and analyze DOT assets, activities, and incidents
Department of Transportation departmental systems
Linear-referenced point events
Point events occur along routes
Based on route geometry and measures
Typically drawn as circles colored by single attribute
Layer
Map use
Data source
Representation
Spatial relationships
Map scale and accuracy
Symbology and annotation
Digital orthophoto
Map background
Aerial photogrammetry and satellite sources
Raster
Raster cells cover the image area
1 to 2.5 meter cell size
Tone, contrast, and balance of gray scale or color presentation
Layer
Map use
Data source
Representation
Spatial relationships
Map scale and accuracy
Symbology and annotation
Reference layer
A common underlying geometry for all transportation users
Multiple agencies, could be a national dataset
Lines and points
Could share geometry with routes
Typical map scales range from 1:24 000 to 1:250 000
Simple gray lines as background reference
Layer
Map use
Data source
Representation
Spatial relationships
Map scale and accuracy
Symbology and annotation
Basemap
Map background
Topographic maps and other cartographic data sources
Raster or vector maps
Should share geometry with routes and navigation
Typical map scales range from 1:24 000 to 1:250 000
Detailed transportation symbolized by class such as bridges, overpasses
Layer
Map use
Data source
Representation
Spatial relationships
Map scale and accuracy
Symbology and annotation
Navigation
For routing, navigation, and logistics
Basemap features plus navigation properties
Edges, transfers, turns, travel costs
Topology networks, share geometry with routes and base maps
Typical map scales range from 1:24 000 to 1:250 000
Varies with the source data product
A sample geodatabase data model document showing the various datasets and associated attributes, as well as the links between tables.
2 • Geographic Data Management
85
ArcCatalog lets you find and connect to data stored on your computer or another computer on your network, on a CD or
DVD, in a database management system, or on a GIS server on your local network or the Internet. Once connected, you
can browse or search for data across the connections.Establishing a data connectionWhile you can add data directly to a map from your local disk drive without setting up a connection, establishing the
connection allows you to preview the data, review the metadata, and more easily manage your data sources.
Finding and connecting to data
You manage all the data connections from ArcCatalogThe Connect to
Folder button lets you create a
connection to data stored on a local disk or network (Connect
to Folder is also available from the
File menu)
Double-click an option under GIS Servers to add a connection to an ArcGIS Server, an ArcIMS Server, a web mapping server (WMS), or a server on the Geography Network.
Double-click an option under Database Connections to add a connection to an OLE database or data stored in an RDBMS.
Double-click Add Database Server to connect to a Personal or Workgroup ArcSDE geodatabase.
