{ "culture": "en-US", "name": "", "guid": "", "catalogPath": "", "snippet": "Feature Class for Anne Arundel County snow map Hills.\nDensify in QGIS to create 100 meter segments of all AA County streets... 70660 records in the Streets shp after this step.\n2017 DEM used.\nInput 100m Streets and 2017 DEM into ArcGIS 3D Analyst > Add Surface > produces Avg Slope for all 100m road segments.\nChecked using basic slope formula: ( [Z_Max] - [Z_Min]) / [Shape_len] *100.\nGoogle Street View and Pictometry's Ground Slope also used to check slope accuracy.\n-------------------------------------------------------\nMethodology used for false positives with bridges and DEM: \nSelect by location all streets that intersect Bridges_and_Overpasses.shp.\nFrom this selection, now select all the ones with slopes greater than 3.5.\nIn this selection, change all selected's Avg_Slope to 2... these are the more or less flat bridges that have 2% with +- 1% discrepancies.\nUsed Google / Bing Street Views and Pictometry's Ground Slope to spot check about 50 of them and all looked correct.\nCounty maintained roads were extracted out.\n\nKnown caveats: \nWhere new streets have been planned but not built yet (or built after 2017) there will be erroneous slope values.\nBridges and overpasses produce false positives. Work around by setting all of them to slope = 2% which results in +- 1% discrepancies in most cases.\nSome of the smaller bridges (not listed in the Bridges shp) were not accounted for e.g. Buckingham Place, Patuxent River Rd, etc.\nThere are a few errors in the Bridges shp that result in \"select by location\" missing the target e.g. Conway Road at Little Patuxent 6.\n\"Shoreline\" values in Streams shp produced a few oddities in the cold spot streets.", "description": "

Feature Class for Anne Arundel County snow map Hills (Avg_Slope >= 9.0.)<\/SPAN><\/P><\/DIV><\/DIV><\/DIV>", "summary": "Feature Class for Anne Arundel County snow map Hills.\nDensify in QGIS to create 100 meter segments of all AA County streets... 70660 records in the Streets shp after this step.\n2017 DEM used.\nInput 100m Streets and 2017 DEM into ArcGIS 3D Analyst > Add Surface > produces Avg Slope for all 100m road segments.\nChecked using basic slope formula: ( [Z_Max] - [Z_Min]) / [Shape_len] *100.\nGoogle Street View and Pictometry's Ground Slope also used to check slope accuracy.\n-------------------------------------------------------\nMethodology used for false positives with bridges and DEM: \nSelect by location all streets that intersect Bridges_and_Overpasses.shp.\nFrom this selection, now select all the ones with slopes greater than 3.5.\nIn this selection, change all selected's Avg_Slope to 2... these are the more or less flat bridges that have 2% with +- 1% discrepancies.\nUsed Google / Bing Street Views and Pictometry's Ground Slope to spot check about 50 of them and all looked correct.\nCounty maintained roads were extracted out.\n\nKnown caveats: \nWhere new streets have been planned but not built yet (or built after 2017) there will be erroneous slope values.\nBridges and overpasses produce false positives. Work around by setting all of them to slope = 2% which results in +- 1% discrepancies in most cases.\nSome of the smaller bridges (not listed in the Bridges shp) were not accounted for e.g. Buckingham Place, Patuxent River Rd, etc.\nThere are a few errors in the Bridges shp that result in \"select by location\" missing the target e.g. Conway Road at Little Patuxent 6.\n\"Shoreline\" values in Streams shp produced a few oddities in the cold spot streets.", "title": "Highways.SDELOADER.Hills", "tags": [ "Anne Arundel County", "Department of Public Works", "Bureau of Highways", "DPW", "BOH", "Snow", "Hills" ], "type": "", "typeKeywords": [], "thumbnail": "", "url": "", "minScale": 500000, "maxScale": 5000, "spatialReference": "", "accessInformation": "Created by Paul Russel, GIS Technician in DPW Technical Engineering, in May 2019. Methodology approved by Carl Converso, Road Operations Supervisor.", "licenseInfo": "

Disclaimer<\/SPAN><\/P>

While efforts have been made to ensure the accuracy of this data, Anne Arundel County accepts no liability or responsibility for errors, omissions, or positional inaccuracies in the content of this data. Reliance on this data is at the risk of the user. This data is for illustration purposes only and should not be used for surveying, engineering, or site-specific analysis. For additional information view the <\/SPAN>GIS Disclaimer<\/SPAN><\/A>.<\/SPAN><\/P><\/DIV>", "portalUrl": "" }