Data format: SDE Feature Class
File or table name: ROPA.TRANS_ROAD_RTE_SV
Coordinate system: Lambert Conformal Conic
Theme keywords: transportation, forest roads, forest practices, transportation
| TRANS ROAD ROUTE Spatial View | |
|
|
Data format: SDE Feature Class File or table name: ROPA.TRANS_ROAD_RTE_SV Coordinate system: Lambert Conformal Conic Theme keywords: transportation, forest roads, forest practices, transportation |
|
Abstract:
The Transportation (TRANS) data layer represents road, railroad, and other land and water transportation routes existing within the state of Washington.
TRANS_ROAD_RTE_SV is an ArcSDE read-only spatial view that joins the TRANS spatial data to both the TRANS_ROAD table (road characteristics) using the TRANS_ARC_NO field, and to the TRANS_RTE table using the TRANS_RTE_REF_NO field. |
|
Metadata elements shown with blue text are defined in the Federal Geographic Data Committee's (FGDC) Content Standard for Digital Geospatial Metadata (CSDGM). Elements shown with green text are defined in the ESRI Profile of the CSDGM. Elements shown with a green asterisk (*) will be automatically updated by ArcCatalog. ArcCatalog adds hints indicating which FGDC elements are mandatory; these are shown with gray text.
The Transportation (TRANS) data layer represents road, railroad, and other land and water transportation routes existing within the state of Washington. TRANS_ROAD_RTE_SV is an ArcSDE read-only spatial view that joins the TRANS spatial data to both the TRANS_ROAD table (road characteristics) using the TRANS_ARC_NO field, and to the TRANS_RTE table using the TRANS_RTE_REF_NO field.
Forest practice regulation; Timber, Fish & Wildlife (TFW) planning and analysis applications, natural resource planning and general mapping reference.
While these data represent our best estimate of the location of transportation routes in the state, they should not be considered a complete inventory of these routes. There are many transportation routes that exist but are not represented in the data. There are also many routes that are depicted in the data that no longer serve as transportation routes, such as abandoned forest roads and trails. There has never been a thorough accuracy assessment of the Transportation data layer, so under-representation vs. over-representation cannot be quantified. Additionally, many routes are not correctly typed as railroad vs. road vs. trail. Caution should be exercised when assessing the results of GIS analysis involving these data.
Within DNR, TRANS, TRANS.ROAD, TRANS.RTE, TRANS_ROAD_RTE_SV, TRANS.ROAD_SV, and TRANS_RTE_SV are available through ROPA.
TRANS_ROAD_SV is a read-only ArcSDE spatial view that joins the TRANS layer and the TRANS_ROAD table using the TRANS.ARC.NO field. All transportation features from TRANS, including roads, trails, railroads, etc. are included. However, only roads (trans_rte_ty = 10) have associated attribute information from the TRANS_ROAD table.
TRANS_RTE_SV is a read-only ArcSDE spatial view that joins the TRANS layer and the TRANS_RTE table using the TRANS.RTE.REF.NO field.
TRANS_ROAD_RTE_SV is a read-only ArcSDE spatial view that joins the TRANS layer with the TRANS_ROAD and TRANS_RTE tables. All transportation features from TRANS, including roads, trails, railroads, etc. are included. However, only roads (trans_rte_ty = 10) have associated attribute information from the TRANS_ROAD table.
Within DNR, TRANS is also available through /database/covers as an ARC/INFO arc/node topology coverage. The TRANS spatial file has two associated INFO files (located at /database/state): (1) TRANS.ROAD (road use and characteristics) is related to the .aat file by TRANS.ARC.NO. The relate is named road. (2) TRANS.RTE (route names and ids) is related to the .aat file by TRANS.RTE.REF.NO. The relate is named rte.
Externally, TRANS, TRANS.ROAD, TRANS.RTE and metadata are available for download through the DNR website as a zipped file. The data can be imported from the ARC/INFO export files (.e00). See http://www3.wadnr.gov/dnrapp6/dataweb/dmmatrix.html#Transportation.
TRANS_ROAD_RTE_SV can be re-created from the downloaded data by joining TRANS to both the TRANS.ROAD table using the TRANS.ARC.NO field and the TRANS.RTE table using TRANS.RTE.REF.NO field.
This select statement is used to create the view:
AS
SELECT /*+ FIRST_ROWS */ --distinct
A.OBJECTID,
A.TRANS_ID,
A.TRANS_ARC_NO,
A.TRANS_RTE_REF_NO,
A.TRANS_INP_METH,
A.TRANS_RTE_TY,
A.TOWN_TILE_NM,
A.SHAPE,
B.ROAD_SUR_TY,
B.ROAD_CLASS_CD,
B.ROAD_ACT_STAT_CD,
B.ROAD_MAINT_PGM,
B.ROAD_USER_PGM_1,
B.ROAD_USER_PGM_2,
B.ROAD_USER_PGM_3,
B.ROAD_RESP_FLG,
B.ROAD_ACC_CD,
B.ROAD_MAINT_CD,
C.TRANS_RTE_ID,
C.TRANS_RTE_NM
FROM ROPA.TRANS A,
ROPA.TRANS_ROAD B,
ROPA.TRANS_RTE C
WHERE A.TRANS_ARC_NO = B.TRANS_ARC_NO(+)
AND A.TRANS_RTE_REF_NO = C.TRANS_RTE_REF_NO(+)
/
ground condition
1111 Washington ST SE
PO BOX 47012
Some data item fields contain no data (until funding is available for additional data collection), some fields are not in use, and other fields are only partially populated due to incomplete source data.
Some fields contain no data, some fields are not in use, and other fields are only partially populated due to incomplete source data. Initial data compilation was completed May 1994. Focus of data collection for initial phase was on forested state and private lands within the state of Washington. Through a multi-agency agreement (Data96) the layer was extended to cover remaining portions of the state, which became available February 1996. Starting in 1996, updates to the data were entered on a site-by-site basis, primarily on DNR managed lands for proprietary road management purposes. No updates were made to the data set between February 2000 and October 2003. Updates are currently on-going on a site-by-site basis. The following attributes are not in use: ROAD_MAINT_PGM, ROAD_USER_PGM_1, ROAD_USER_PGM_2, ROAD_USER_PGM_3.
+/- 40 feet
n/a
DNR Transportation and Hydrographic data layers were created as part of the Timber Fish and Wildlife (TFW) Agreement during a five year period beginning in 1987. There were approximately $1.7 million invested in the initial dedevelopment of the DNR Trans/Hydro database. The work was accomplished for Forest Practices Division cooperatively by DNR Photogrammetry and Resource Mapping staff. These data were created in order to: (1) Replace the manual, hardcopy water typing process with more complete, accurate, current, and more easily accessible digital hydrographic data; (2) Provide computer readable TRANS and HYDRO information for use in Forest Practices regulation and implementation of TFW, for access by the TFW participants, and later, for use in the MAPS system (MAPS was the precursor to the current FPARS - Forest Practices Application and Review System, an ArcIMS internet mapping system); and (3) Make digital TRANS and HYDRO data part of the DNR corporate GIS database for use in a wide variety of DNR programs. (Curtis 1994) Initial data compilation covering state and private forested lands in Washington was completed May 1994. The multi-agency DATA96 project was an effort to add the remainder of the state. Subsequent to the completion of this project in February 1996, updates to the data were entered on a site-by-site basis, primarily on DNR managed lands for proprietary road management purposes. No updates were made to the data set between February 2000 and October 2003. Updates are currently on-going on a site-by-site basis.
Created as ArcSDE spatial view from /database/state.
CREATE OR REPLACE VIEW ROPA.TRANS_ROAD_RTE_SV (OBJECTID,
TRANS_ID,
TRANS_ARC_NO,
TRANS_RTE_REF_NO,
TRANS_INP_METH,
TRANS_RTE_TY,
TOWN_TILE_NM,
SHAPE,
ROAD_SUR_TY,
ROAD_CLASS_CD,
ROAD_ACT_STAT_CD,
ROAD_MAINT_PGM,
ROAD_USER_PGM_1,
ROAD_USER_PGM_2,
ROAD_USER_PGM_3,
ROAD_RESP_FLG,
ROAD_ACC_CD,
ROAD_MAINT_CD,
TRANS_RTE_ID,
TRANS_RTE_NM
)
AS
SELECT /*+ FIRST_ROWS */ --distinct
A.OBJECTID,
A.TRANS_ID,
A.TRANS_ARC_NO,
A.TRANS_RTE_REF_NO,
A.TRANS_INP_METH,
A.TRANS_RTE_TY,
A.TOWN_TILE_NM,
A.SHAPE,
B.ROAD_SUR_TY,
B.ROAD_CLASS_CD,
B.ROAD_ACT_STAT_CD,
B.ROAD_MAINT_PGM,
B.ROAD_USER_PGM_1,
B.ROAD_USER_PGM_2,
B.ROAD_USER_PGM_3,
B.ROAD_RESP_FLG,
B.ROAD_ACC_CD,
B.ROAD_MAINT_CD,
C.TRANS_RTE_ID,
C.TRANS_RTE_NM
FROM ROPA.TRANS A,
ROPA.TRANS_ROAD B,
ROPA.TRANS_RTE C
WHERE A.TRANS_ARC_NO = B.TRANS_ARC_NO(+)
AND A.TRANS_RTE_REF_NO = C.TRANS_RTE_REF_NO(+)
/
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Internal feature number.
ESRI
Unique identifier for each arc. Used as a relate item to relate the Roads Table to the TRANS spatial data.
Transportation route reference number: Number used to uniquely represent a transportation route segment. Use as a relate or join item to link to the TRANS_RTE table.
The TRANS.ROAD table (road use and characteristics) can be joined or related to the TRANS spatial data with the TRANS.ARC.NO field.
Photogrammetrically derived
Machine scanned
Contractor digitized from USGS 7.5' separate
Contractor digitized from USGS 7.5' separate
Contractor digitized from USGS 7.5' separate
Contractor digitized from USGS 7.5' separate
Contractor digitized from USGS 7.5' separate
Contractor digitized from USGS 7.5' separate
Contractor digitized from USGS 7.5' separate
Contractor digitized from USGS 7.5' separate
DNR digitized from DNR Water Type Maps
DNR digitized from National Wetlands Inventory
DNR digitized from National Wetlands Inventory
DNR digitized from National Wetlands Inventory
Type of transportation route the linear feature represents. Classification of a transportation route is based on the primary mode of transportation on the route.
Road
Trail
Railroad
Railroad grade
Ferry crossing
Unspecified transportation route
Identifies the township tile that contains the TRANS arc.
Feature geometry.
ESRI
Road surface type
Paved road
Unpaved road
Crushed rock
Gravel
Native material
unknown
Road classification code. These code definitions are based on generalized USGS road classification codes.
Primary highway/all-weather/hard surface
Secondary highway/ all-weather/ hard surface
Light-duty road/ all-weather/ improved surface
Unimproved road/ fair or dry weather
Unkown road classification
Road activity status classification. This code refers to the status of forest roads as defined by the Washington Forest Practices Rules. See WAC 222-16-010 and WAC 222-24-052. Railroad activity status is not included.
Active
Inactive
Abandoned
Orphan
Planned
Unspecified
DNR Program Index to which a road construction or maintenance activity is charged. Applicable only to roads. NOT IN USE.
DNR Program Index of primary road user. NOT IN USE.
DNR Program Index of secondary road user. NOT IN USE
DNR Program Index of additional road user. NOT IN USE.
Flag identifying that DNR has full or partial maintenance responsibility for a road segment.
Road segment in the DNR road system.
Road segment not part of the DNR road system.
Code describing the level of physical access intended for the public on the road segment.
Road segment with year-round public access - no gates
Road segment temporarily gated to limit public access
Road segment intended for management access only.
Not driveable by four-wheeled highway vehicles.
Code describing the intensity level at which road maintenance activities occur along the road segment.
Road segment receiving annual maintenance.
Road segment receiving only minimal maintenance.
Road segment has been decommissioned.
Transportation route identifier in common use.
Full textual name of transportation route.
Data collected with focus on the type, condition, and drivability of forest roads. The source of the spatial data is also included for each arc. Minimal information exists for other transportation route types including trails, railroads, and ferry crossings.
PO BOX 47012
Data and metadata are available for download at http://fortress.wa.gov/dnr/app1/dataweb/dmmatrix.html#Transportation
The Washington State Department of Natural Resources (DNR) provides these geographic data "as is." DNR makes no guarantee or warranty concerning the accuracy of information contained in the geographic data. DNR further makes no warranties, either expressed or implied as to any other matter whatsoever, including, without limitation, the condition of the product, or its fitness for any particular purpose. The burden for determining fitness for use lies entirely with the user. Although these data have been processed successfully on DNR computers, no warranty, expressed or implied, is made by DNR regarding the use of these data on any other system, nor does the fact of distribution constitute or imply any such warranty. In no event shall DNR have any liability whatsoever for payment of any consequential, incidental, indirect, special, or tort damages of any kind, including, but not limited to, any loss of profits arising out of use of or reliance on the geographical data or arising out of the delivery, installation, operation, or support by DNR.
Download the Transportation data from http://fortress.wa.gov/dnr/app1/dataweb/dmmatrix.html#TransportationTransportation. The zipped file includes ARC/INFO export files (.e00) of the TRANS spatial data and the ROAD and ROUTE tables and the metadata.
1111 Washington ST SE
PO BOX 47012