20170516
15421400
1.0
North American Profile of ISO19115 2003
FALSE
SidewalkCenterlines
3072938.467300
3095495.135113
1679626.607604
1711781.745721
1
0.000
002
Projected
GCS_North_American_1983
Linear Unit: Foot_US (0.304801)
NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet
<ProjectedCoordinateSystem xsi:type='typens:ProjectedCoordinateSystem' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:xs='http://www.w3.org/2001/XMLSchema' xmlns:typens='http://www.esri.com/schemas/ArcGIS/10.6'><WKT>PROJCS["NAD_1983_StatePlane_Colorado_Central_FIPS_0502_Feet",GEOGCS["GCS_North_American_1983",DATUM["D_North_American_1983",SPHEROID["GRS_1980",6378137.0,298.257222101]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Lambert_Conformal_Conic"],PARAMETER["False_Easting",3000000.000316083],PARAMETER["False_Northing",999999.999996],PARAMETER["Central_Meridian",-105.5],PARAMETER["Standard_Parallel_1",38.45],PARAMETER["Standard_Parallel_2",39.75],PARAMETER["Latitude_Of_Origin",37.83333333333334],UNIT["Foot_US",0.3048006096012192],AUTHORITY["EPSG",2232]]</WKT><XOrigin>9.0811409950524066e-316</XOrigin><YOrigin>1.9575685275696325e-280</YOrigin><XYScale>3048.0060960121914</XYScale><ZOrigin>0</ZOrigin><ZScale>1</ZScale><MOrigin>0</MOrigin><MScale>1</MScale><XYTolerance>0.0032808333333333335</XYTolerance><ZTolerance>2.0000000000000002e-05</ZTolerance><MTolerance>2.0000000000000002e-05</MTolerance><HighPrecision>true</HighPrecision><WKID>102654</WKID><LatestWKID>2232</LatestWKID></ProjectedCoordinateSystem>
20190618
10300700
20190618
10300700
FGDC
Josh Pendleton
Denver Regional Council of Governments (DRCOG)
GIS Specialist
geospatial@drcog.org
1290 Broadway, Suite 700
Denver
CO
80203-5606
U.S.
303 455-1000
303 480-6790
8am to 5pm US Mountain Time
20190618
https://gis.cityofgolden.net/arcgis/rest/services/OpenData/SidewalkCenterlines/MapServer
https://gis.cityofgolden.net/arcgis/rest/services/OpenData/SidewalkCenterlines/MapServer
DRCOG Paved Sidewalks and Paved Trails Centerlines Line Feature (2014)
Geodatabase
ArcGIS 10.1
ESRI
Josh Pendleton
Denver Regional Council of Governments (DRCOG)
GIS Specialist
geospatial@drcog.org
1290 Broadway, Suite 700
Denver
CO
80203-5606
U.S.
303 455-1000
303 480-6790
8am to 5pm US Mountain Time
Contact resellers
Order from either Map Mart or Colorado Aerial Photo Service
Feature Class
SidewalkCenterlines
2015-01-01
1.0
Orthoimagery – 2014
DRCOG Denver Region Urbanized Project Area
vector digital data
City of Golden GIS
gis@cityofgolden.net
1445 10th Street
Golden
Colorado
80401
US
303-384-8000
City of Golden Colorado sidewalk centerlines for general planning collected from digital orthophotography. Used for general planning and mapping purposes only; not survey accurate.
City of Golden Colorado sidewalk centerlines for general planning
Capture criteria: If the sidewalk widens and the centerline shifts, create a "jig" to keep the centerline connected. The sidewalk does not stop at intersections or at parking aprons or at driveways, BUT these areas should be separate segments within the line feature and attributed differently (see attribution:Type). The main goal of this feature dataset is connectivity; it will be used for routing and modeling of pedestrian trips. When connecting "sidewalk"segments with an "other crossing" segment (see attribution: Type), only connect with there is visible access between the two sidewalk segments. Access means that a wheelchair can traverse it (so stairs do not constitute a connection). For sidewalk centerlines meeting parking apron, the portion of sidewalk centerline within the apron always breaks into a different line segment, and has a type of "other crossing" unless the sidewalk crossing the parking lot is readily visually apparent, in which case the sidewalk centerline simply continues unbroken. For sidewalk centerlines meeting driveway apron, the sidewalk continues as with the polygon sidewalks. This layer includes all public sidewalks (e.g. adjacent to a public building, schools, or roads, adjacent to commercial buildings, maintained by a public entity) and trails (e.g. in public parks, maintained by a public entity). The sidewalks layers will not include private sidewalks (i.e. serving individual residences, contained within campuses, mails or commercial complexes) EXCEPT where the sidewalk maintains connectivity with the public sidewalk network. In these instances, if the private sidewalk is too complex (i.e. multiple, indirect paths, or with many branches), a best-fit line may be drawn to maintain connectivity with the public sidewalks. Break all sidewalk and trail centerlines at line intersections.
City of Golden, Colorado
Version 6.2 (Build 9200) ; Esri ArcGIS 10.6.1.9270
Sidewalk
Transportation
Golden
GIS
Infrastructure
transportation
paved sidewalks and paved trails centerlines
Golden
Colorado
2014-03-05
2014-07-03
Ground condition
-105.240788
-105.160199
39.698886
39.787362
City of Golden
gis@cityofgolden.net
1445 10th Street
Golden
Colorado
80401
US
303-384-8000
<p style='margin-top:0in;margin-right:0in;margin-bottom:
0in;margin-left:.25in;margin-bottom:.0001pt;mso-add-space:auto;line-height:
normal'><span style='font-family:"Arial",sans-serif;color:#4C4C4C;background:
white'>Licensed under a Creative Commons Attribution 4.0 International License.
The City of Golden presents the information on this site as a service to the
public. Every effort has been made to ensure that the information is correct,
however, Golden makes no warranty or guarantee concerning the completeness,
accuracy or reliability of the content at this or any other site to which we
link or to the information contained in any document, dataset, website or
application on or downloaded from the site. Assessing accuracy and reliability
of information is the sole responsibility of the user and shall be used and
relied upon only at the risk of user.</span></p>
Contact the City of Golden GIS
1
-105.240788
-105.160199
39.787362
39.698886
Editing of compiled features takes place in VrOne environment. Editing consists of layering validation, duplicate point removal, trimming lines, closing of lines, etc. Vectors are compared to ortho product to validate geometric accuracy. All compilation is cut to project boundary. Where lines intersect project boundary the lines are trimmed at the boundary.
2015-01-01
New digital aerial imagery is collected concurrently with the lidar data and triangulated to provide stereo coverage of the project area in the desired coordinate system and datums. See orthoimage metadata for collection and processing details.
2015-01-01
VrOne files translated to DWG format.
2015-01-01
Planimetric feature collection is performed in one or more of BAE SocetSet, ZI SSK, Cardinal VROne softcopy digital stereoscopic compilation workstations.
2015-01-01
DWG files translated to ESRI Geodatabase format.
2015-01-01
The aerial imagery was captured with Leica Geosystems ADS40 and ADS80 digital sensors, sensor heads SH104, SH140 and SH1318. The ADS40 and ADS80 use a pushbroom method of data collection with multiple linear array CCDs using forward, rearward and nadir orientations along planned flight lines. Each collects data in one of the pan, red, green, blue or NIR spectral bands. This results in one image per CCD for each flight line. Forward and rearward images allow for stereo viewing of the image strips. The aerial images are used for softcopy aerotriangulation of the project image strips and stereo compilation of surface features.
1200
Aerial imagery
2014-03-05
2014-07-03
Ground condition
Aerotriangulated digital aerial imagery is used to compile surface planimetric features in a softcopy stereo environment. Software used are BAE SocetSet, ZI SSK and Cardinal VROne.
1200
Aerial imagery
2014-03-05
2014-07-03
Ground condition
the map editing process performs the same two functions for the planimetric and topographic data, which is; 1. to check the data for accuracy, and 2. make the mapping more aesthetically pleasing and easy to work with. The various map features are assigned unique digital layers according to Kucera's general layering scheme (or a more "custom" layering scheme if specified by the client). "Layering" meaning the separation of like features to a unique digital level that can be viewed, located, counted or otherwise manipulated to the exclusion of other features/levels. Planimetrically, a good example of the layering system would be that all of the major buildings such as houses and commercial buildings be placed on their own layer named something like "BUILDINGS" so they can more easily be viewed or worked separately from more inconsequential structures such as small storage buildings or sheds that would be own their own layer named "MINOR BUILDINGS" or whatever the client would like those particular layers named. Other planimetric examples of the use of layering would be the use of separate digital layers to differentiate paved roads from unpaved roads, treelines from brushlines, ditches from streams, etc. The finished mapping is then usually gridded, the appropriate title block information is added (info regarding the scale, contour interval, mapping location, client name, date of photography or Lidar collection, etc...), translated from Kucera's in-house editing software – primarily VrOne – into the digital format and layering scheme requested by the client (usually AutoCAD and/or ESRI) and delivered to the client on a DVD or by means of electronic delivery (email or posting to the FTP site for the client to download).
Edited Planimetric/Topographic Mapping
2015-01-01
Ground condition
Compliance with the collection and accuracy standard was ensured by the placement of GPS ground control prior to the acquisition of aerial imagery. A softcopy aerotriangulation adjustment is performed on the aerial imagery is Leica XPro software. Accuracy of the stereo compiled features is a function of the aerotriangulation accuracy as summarized by the X, Y, Z RMSE statistics of the ground control points.
Completeness is ensured in the final vector editing process by comparison to the 2014 digital orthoimages as a backdrop to the paved sidewalks and paved trails centerlines vector features.
There are no Attributes in this data set.
The horizontal accuracy of the delivered paved sidewalks and paved trails centerlines features is a function of the aerotriangulation accuracy as expressed by the X and Y RMSE statistics of the ground control. DRCOG stated accuracy requirement (AppendixB_Feature Requirements_20151002.xlsx) is National Map Accuracy Standard (NMAS) for 1"=100' scale mapping. NMAS accuracy for map scales larger than 1:20000 horizontal tolerance is 1/30" for 90% of well defined points or, 3.0' horizontal accuracy. RMSE of the control is X = 0.108' and Y = 0.082'.
The Horizontal_Positional_Accuracy_Value was tested in accordance with Geospatial Positioning Accuracy Standards Part 3: National Standard for Spatial Data Accuracy (NSSDA), FGDC-STD-007.3-1998. NSSDA horizontal accuracy is 1.7308*RMSE_r or 1.7308*0.095 = 0.16'. NSSDA Horizontal accuracy of the aerotriangulated aerial imagery meets or exceeds the NMAS requirement of 1/30" for 1"100' scale mapping.
0.16
The paved sidewalks and paved trails centerlines were digitized in 2D from the aerial imagery and have no vertical attribute of accuracy value associated with X and Y values.
3352
SidewalkCenterlines
Centerline of paved sidewalks and paved trails.
DRGOG
Feature Class
3352
last_edited_date
last_edited_date
Date
8
0
0
CreateDate
Date attribute is created.
DRCOG
mm/dd/yyyy
Month, day and year the feature entity is created
DRCOG
CreateDate
Date
8
0
0
Type
The type of paved sidewalk or paved trail.
DRCOG
"Sidewalk", Crosswalk", Other crossing", Best fit line".
Type of path. A "sidewalk" is a paved path for pedestrians on the side of the road. A" crosswalk" is a marked part of the paved road where pedestrians have right of way to cross. An "other crossing" is a line segment that maintains connectivity within this layer but is not a sidewalk or crosswalk. The "other crossing" should be used to connect sidewalk and crosswalk features that are separated by an average city block or less (~650ft); this feature does not have to be paved; it will only be collected if there is visible and reasonable access (wheelchair accessible) or connection between the sidewalks/crosswalks to be connected.
DRCOG
Type
String
20
0
0
OBJECTID
Internal feature number.
Esri
Sequential unique whole numbers that are automatically generated.
OBJECTID
OID
4
10
0
last_edited_user
last_edited_user
String
255
0
0
Custodian
Custodian
String
50
0
0
created_user
created_user
String
255
0
0
Retired
Retired Date
Date
8
0
0
Shape.STLength()
Shape.STLength()
Double
0
0
0
CarteID
CarteID
String
50
0
0
created_date
created_date
Date
8
0
0
CreateUser
Kucera International, Inc.
DRCOG
Kucera International, Inc.
Name of vendor creating the entity feature
DRCOG
CreateUser
String
32
0
0
SHAPE
Feature geometry.
Esri
Coordinates defining the features.
Shape
Geometry
4
0
0
dataset
EPSG
5.3(9.0.0)
Simple
FALSE
3352
TRUE
FALSE