Data format: ArcInfo Coverage
File or table name: road065
Coordinate system: Universal Transverse Mercator
Theme keywords: transportation
| Clinch County Roads | |
|
|
Data format: ArcInfo Coverage File or table name: road065 Coordinate system: Universal Transverse Mercator Theme keywords: transportation |
|
Abstract:
Road Segment: A section of road providing an open way for the passage of vehicles. |
|
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.
Road Segment: A section of road providing an open way for the passage of vehicles.
Inventory maintenance. This dataset contains Georgia's most up-to-date GIS Road information in an ESRI ArcInfo Interchange (.e00) file format. The attribute updates contained in this file are the result of the Ga. DOT's DLG-F/RC Reconciliation project. This project is engaged in transferring the attribute information residing in the DOT's Road Characteristics (RC) Files to the existing, spatially accurate DLG-F Road files. While many enhancements have taken place, more work is required. All of the counties posted on the Clearinghouse have 95% of the records present in the RC File represented in the GIS data. The DLG-F/RC Reconciliation project is currently undergoing initial reconciliation with maintenance starting immediately. The updates here available for download are, therefore, part of a WORK IN PROGRESS.
Capture conditions: capture all inventoried roads. Delineation rule: The limit of ROAD SEGMENT is the extent of the passage surface, excluding shoulders and curbs. Representation Rule: Segments are defined from intersection to intersection, intersection to endpoint, or endpoint to endpoint. End points are defined as county line or end of jurisdiction. The only exception to road segment line splits will occur when the maximum number of vertices has been reached in the Arc/Info coverage data model. The data set has a complete set of routes, as implied by the inclusion of the complete set of attribute tables: .pat(point), .aat, .nat, and .ratdot.
ground condition
[To be completed by Georgia Department of Transportation].
Inventory Routes Not Currently Present in GIS: Inv_route_id Reason for absence 06511049TA no point of reference 0651104900 imagery not recent enough Inventoried Routes present in GIS but unbuilt: Inv_route_id Comments 0651003800 GDOT Error 0651008900 GDOT Error 0651009400 unbuilt contingent upon SR 089 0651018700 GDOT Error 0652012800 GDOT Error 0652024400 Imagery not recent enough 0653050105 GDOT Error 0653050205 GDOT Error 0653050305 GDOT Error 0653050405 GDOT Error 0653050505 GDOT Error 0653051905 GDOT Error 0653052305 GDOT Error 0653052405 GDOT Error 0653055705 GDOT Error
The Inventoried Routes in this transportation dataset were built using an iterative process that compared the GIS with the RC file. With each successive iteration of this process, errors were discovered and corrected where the GIS did not match the RC file. Errors found included inconsistancies in both the GIS and the RC file. The RC file was the overall authority and the GIS was made to match in every case possible. Exceptions included areas where available imagery was not sufficiently up to date to correctly represent the RC file or where the RC file was in conflict with itself.
Completeness will be measured by correspondence to RC Next records.
Horizontal accuracy meets or exceeds National Map Accuracy Standards for 1:24,000-scale data. The DLG-F transportation dataset was photorevised using 1:12000 DOQQ's from the USGS. Accuracy is dependant upon the DOQQ'S. This transportation dataset underwent a visual QC at a 1:6000 scale using the DOQQ's.
Since this data is built for aerial photography that is at a scale of 1:12,000 the following National Map Accuracy Standards apply. For maps on publication scales larger than 1:20,000, not more than 10 percent of the points tested shall be in error by more than 1/30 inch, measured on the publication scale; for maps on publication scales of 1:20,000 or smaller, 1/50 inch. These limits of accuracy shall apply to positions of well-defined points only. Well-defined points are those that are easily visible or recoverable on the ground, such as the following: monuments or markers, such as bench marks, property boundary monuments; intersections of roads and railroads; corners of large buildings or structures (or center points of small buildings). In general, what is well-defined will also be determined by what is plottable on the scale of the map with-in 1/100 inch. Thus, while the intersection of two roads or property lines meeting at right angles would come within a sensible interpretation, identification of the intersection of such lines meeting at an acute angle would not be practicable within 1/100 inch. Similarly, features not identifiable upon the ground within close limits are not to be considered as test points within the limits quoted, even though their positions may be scaled closely upon the map. This class would cover timber lines and soil boundaries.
Photorevised road centerlines built from Georgia Department of Transportation data.
I. GPS Integration
A. GPS data provided by GDOT will be integrated into the DLG-F data so that:
1. Any unknown roads that already exist in the DLG-F and represent the new GPS roads shall be correctly attributed from the GPS roads.
2. Any GPS road that does not currently exist in the DLG-F data shall be integrated in and photorevised using the most current imagery available for that county.
II. RC Verification
A. All inv_route_id's that exist in the new RC file provided by GDOT must have corresponding arcs that represent them in the DLG-F. This will be accomplished through the following steps:
1. Using ArcView, summary lists will be made of both the RC file and the DLG-F .AAT. The discrepancy between these two lists will show which inv_route_id's need to be added to the DLG-F.
2. An editor will use the list of missing inv_route_id's and the RC File to find and calc the unknown roads with the correct attribution in ArcView.
3. For those records that don't already exist as an unknown road, a shapefile will be created that includes the inv_route_id number so that the road can be added using DLG_EDIT.
4. The new arcs will be added and attributed in DLG_EDIT using the shapefile (converted into a coverage) generated in ArcView.
III. Geometry QC
A. After the new arcs have been added through GPS integration and RC verification, there will need to be QC and correction of errors. Errors that must be addressed include:
1. All arcs with the same inv_route_id must go in the same direction
2. All arcs must be snapped together properly
3. All nodes not occurring at an intersection of at least two or more roads must be removed unless the node fits the following criteria:
a. separates two arcs with differing inv_route_id's
b. separates jurisdictional boundaries (i.e. County boundaries)
c. serves as the termination point for the route. (i.e. dead end)
IV. Feature_id's for the .AAT
A. Unique Feature_id's must be calculated for all features in the .AAT that do not currently have one. They must be maintained for features that already have them.
V. Routes
A. Routes must be built for this dataset based upon inv_route_id. Tasks in this step to be completed by script are as follows:
1. Routes will be built and calibrated to match the intersection file.
2. Calibration points will be created for each intersection that denotes its milepoint along the route.
3. Each arc shall have its from and to mile field populated with the correct measures from the intersection file.
4. Arcs shall be flipped so that they are in the direction of inventory.
B. Tasks in this step to be completed by editors are as follows:
1. Inv_route_id's that did not get built programmatically will be reviewed by an editor for potential errors that can be fixed in order for the route to be built when run through the program again.
2. Fixable errors will be corrected.
3. Complex loop routes will be built by editors.
4. A common route table will be created and populated for arcs that belong to more than one inv_route_id.
VI. Feature_id's for .PAT, .RATDOT, .SECDOT.
A. Feature_id's will be calculated for all of the above feature attribute tables.
VII. Final QC
A. A QC process will be implemented. It will check for the following:
1. The arc length and calibrated distance will be compared for each inv_route_id to check for discrepancies.
2. We will check again to see that we have all inv_route_id numbers accounted for from the new RC file.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Metadata imported.
Dataset copied.
Internal feature number.
ESRI
Feature geometry.
ESRI
Area of feature in internal units squared.
ESRI
Perimeter of feature in internal units.
ESRI
Internal feature number.
ESRI
User-defined feature number.
ESRI
Inventoried Route ID: Georgia DOT assigned ID number for the associated route.
None
Mile Point
None
Source data from which the feature was captured.
None
The name of the DLG-F feature
None
Unique permanent feature ID.
None
Feature Association: The corresponding feature ID from source database that intersects at the node.Blank = self
None
State FIPS Code: FIPS code of the state containing the feature.
None
County FIPS Code: FIPS code of the county containing the feature.
None
Entity that performed feature updates.
None
Date when feature was last updated.
None
Date of the source data.
None
Internal feature number.
ESRI
Feature geometry.
ESRI
Internal node number for the beginning of an arc (from-node).
ESRI
Internal node number for the end of an arc (to-node).
ESRI
Internal node number for the left polygon.
ESRI
Internal node number for the right polygon.
ESRI
Length of feature in internal units.
ESRI
Internal feature number.
ESRI
User-defined feature number.
ESRI
The name of the DLG-F feature.
None
Unique permanent feature ID
None
The type of road segment.
None
State FIPS Code: FIPS code of the state containing the feature.
None
County FIPS Code: FIPS code of the county containing the feature.
None
Inventoried Route ID: Georgia DOT assigned ID number for the associated route.
None
Georgia DOT Road Type: A one-character code used by Georgia DOT to identify the road type.
None
Type: Interstate. Description: A road that is designated as a State Route by resolution of the Georgia DOT Transportation Board, and is also part of the Interstate Highway System.
None
Type: State Highway. Description: A road that is designated as a State Route by resolution of the Georgia DOT Transportation Board, but is not part of the Interstate Highway System.
None
Type: County Road. Description: A road that is designated by a county as part of its county road system.
None
Type: City Street. Description: A road that is designated by a city as part of its city street system.
None
Type: County Road. Description: A road where the county line follows the right of way of the road instead of going down the centerline.
None
Type: Unofficial Road. Description: A nontabulating road used to identify railway crossings or bridges that are inaccessible by other means.
None
Type: Ramp. Description: A road providing access to and/or from a limited access road.
None
Type: Private Road. Description: A road which remains in private ownership and for which the owner is responsible for maintenance. Includes new subdivision roads that the builder intends to be taken over by the county or city for maintenance purposes.
None
Type: Public Road. Description: A road that is open to the public but that has not been accepted by GaDOT?, the county, or the city as part of their official system. Includes State Hospital roads, State Park roads, Corp of Engineer roads, and Forest Service roads.
None
Type: Collector-Distributor. Description: A road within the limits of access of interstate highways which collects and/or distributes traffic to and/or from interstate highways and ramps of adjoining roads.
None
Type: DOT Proposed. Description: A road that is not in the Georgia DOT inventory but is collected by the Georgia Forestry Commission for fire control maps. GFC has identified the road as a proposed GaDOT? route.
None
Type: State Property. Description: A road that is not in the Georgia DOT inventory but is collected by the Georgia Forestry Commission for fire control maps. Although the road is not in GaDOT? inventory, GFC has identified the road as State property.
None
Type: Forest Service. Description: A road that is not in the Georgia DOT inventory but is collected by the Georgia Forestry Commission for fire control maps. GFC has identified the road as a Forest Service road.
None
Type: Forest Company. Description: A road that is not in the Georgia DOT inventory but is collected by the Georgia Forestry Commission for fire control maps. GFC has identified the road as a private road owned by a company in the forest products industry.
None
Type: Private Road. Description: A road that is not in the Georgia DOT inventory but is collected by the Georgia Forestry Commission for fire control maps. GFC has identified the road as a private road not owned by a forest products company.
None
Type: Unknown Road. Description: A road that is not in the Georgia DOT inventory, and is also not collected by the Georgia Forestry Commission.
None
Georgia DOT Road Number: The route number assigned by Georgia DOT.
None
Georgia DOT Road Suffix: A two-character code used by Georgia DOT to identify the municipality or special designation associated with the road segment.
None
Type: State Route or County Route. Description: Standard state or county route. No suffix is assigned.
None
Type: North. Description: Direction of travel is north. Primarily used for one-way streets.
None
Type: South. Description: Direction of travel is south. Primarily used for one-way streets.
None
Type: East. Description: Direction of travel is east. Primarily used for one-way streets.
None
Type: West. Description: Direction of travel is west. Primarily used for one-way streets.
None
Type: Alternate. Description: An alternate routing having the same route number as the main route which eventually merges back to the main route.
None
Type: Bypass. Description: The portion of a route that bypasses a town, city, or other congested area.
None
Type: Spur. Description: A departure from the main route, having the same route number as the main route, but which never merges back again.
None
Type: Connector. Description: Connects two or more state routes.
None
Type: Loop. Description: Similar to a bypass. The portion of a route that bypasses a town, city, or other congested area, eventually merging back with itself to form a closed loop.
None
Type: Toll. Description: A road for which a toll is levied for travel.
None
Type: Bypass Connector. Description: A road that connects a bypass with a state route.
None
Type: Northbound Lane. Description: The northbound travel lanes of a divided, limited access highway.
None
Type: Southbound Lane. Description: The southbound travel lanes of a divided, limited access highway.
None
Type: Eastbound Lane. Description: The eastbound travel lanes of a divided, limited access highway.
None
Type: Westbound Lane. Description: The westbound travel lanes of a divided, limited access highway.
None
Type: Northbound Lane Dual. Description: A departure from the main route, having the same route number as the main route, and typically connecting with a state route. Direction of travel is north.
None
Type: Southbound Lane Dual. Description: A departure from the main route, having the same route number as the main route, and typically connecting with a state route. Direction of travel is south.
None
Type: Eastbound Lane Dual. Description: A departure from the main route, having the same route number as the main route, and typically connecting with a state route. Direction of travel is east.
None
Type: Westbound Lane Dual. Description: A departure from the main route, having the same route number as the main route, and typically connecting with a state route. Direction of travel is west.
None
Type: City Suffix Number. Description: For city streets, a two digit code which identifies the incorporated municipality. City suffixes are only unique with a particular county.
None
Road Name: The local name of the corresponding road segment
None
Source data from which the feature was captured.
None
Entity that performed feature updates.
None
Date of the source data.
None
Date when feature was last updated.
None
Order of arcs in Common and Loop routes. Used to recreate Common and Loop routes.
None
User Specified Tolerance for difference between ArcLength and RC Calibrated length.
None
Tolerance used by Route Builder program to build route.
None
From milepoint of arc. Value derived from GDOT
None
To milepoint of arc. Value derived from GDOT RC_FILE.
None
Internal feature number.
ESRI
Feature geometry.
ESRI
Internal feature number.
ESRI
Internal feature number.
ESRI
User-defined feature number.
ESRI
Identifies node as bridge or underpass intersection for calibration purposes.
None
Bridge or Underpass intersection
None
Feature: The name of the DLG-F feature.
None
Feature ID: Unique permanent feature ID.
None
Feature Association: The corresponding feature ID from source
None
Route ID: Georgia DOT assigned ID number for the associated route.
None
State FIPS Code: FIPS code of the state containing the feature.
None
County FIPS Code: FIPS code of the county containing the feature.
None
Mile point
None
Internal feature number.
ESRI
Feature geometry.
ESRI
Internal feature number.
ESRI
User-defined feature number.
ESRI
Inventoried Route ID: Georgia DOT assigned ID number for the associated route.
None
Feature: The name of the DLG-F feature.
None
Feature ID: Unique permanent feature ID.
None
Feature Association: The corresponding feature ID from source database that intersects at the node.Blank = self
None
State FIPS Code: FIPS code of the state containing the feature.
None
County FIPS Code: FIPS code of the county containing the feature.
None
Entity that performed feature updates.
None
Date when feature was last updated.
None
Mile Point
None
1180 E. Broad Street, Suite 2058
Although these data have been processed successfully on a computer system at the Georgia GIS Data Clearinghouse no warranty expressed or implied is made by Georgia GIS Data Clearinghouse regarding the utility of the data on any other system, nor shall the act of distribution constitute any such warranty. Georgia GIS Data Clearinghouse will warrant the delivery of this product in computer-readable format and will offer appropriate adjustment of credit when the product is determined unreadable by correctly adjusted computer input peripherals, or when the physical medium is delivered in damaged condition. Requests for adjustments of credit must be made within 90 days from the date of this shipment from the ordering site.
Information Technology Outreach Services
Chicopee Complex
Suite 2076