{ "currentVersion": 10.71, "serviceDescription": "The Systematic Signs Workplan application was developed to assist the County Forces and Capital Programs sections with planning systematic sign replacement projects. The Capital programmed Systematic Signs projects are programmed in ELLIS and mapped out using the ELLIS work location layer. The in-house force account systematic sign project locations are not in ELLIS and will need to be populated in the COUNTY_SSRP feature class.\n\nThis application will help County Management enter planned systematic sign locations into the COUNTY_SSRP feature class, displaying the routes planned for Systematic Sign replacement and when that replacement is happening. Over time this information will help as systematic sign projects are completed, we will be able to see when the route was last completed and plan systematic sign replacement projects in the future to get on a 15-year cycle. \n\nFor more information or changes to the map/data, please contact the ODOT District 3 TAM Coordinator Kenny Krise at (419)-207-7052 or Kenneth.Krise@dot.ohio.gov\n\nTerms of Use\n\nNo warranties, expressed or implied, concerning the accuracy, reliability or suitability of this data have been made by the Ohio Department of Transportation or any other State Agency. Any use of this information is at the recipient's own risk.\n", "mapName": "Layers", "description": "", "copyrightText": "TAMC Collector", "supportsDynamicLayers": true, "layers": [ { "id": 0, "name": "County SSRP - Viewer", "parentLayerId": -1, "defaultVisibility": true, "subLayerIds": null, "minScale": 0, "maxScale": 0, "type": "Feature Layer", "geometryType": "esriGeometryPolyline" } ], "tables": [], "spatialReference": { "wkid": 102100, "latestWkid": 3857 }, "singleFusedMapCache": false, "initialExtent": { "xmin": -6.2892594048875034E7, "ymin": 7538676.403176144, "xmax": 3.822056218393496E7, "ymax": 4.201625939392574E7, "spatialReference": { "wkid": 102100, "latestWkid": 3857 } }, "fullExtent": { "xmin": -9252037.1328, "ymin": 4946216.734099999, "xmax": -9017153.9111, "ymax": 5131552.826800004, "spatialReference": { "wkid": 102100, "latestWkid": 3857 } }, "minScale": 0, "maxScale": 0, "units": "esriMeters", "supportedImageFormatTypes": "PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP", "documentInfo": { "Title": "", "Author": "", "Comments": "The Systematic Signs Workplan application was developed to assist the County Forces and Capital Programs sections with planning systematic sign replacement projects. The Capital programmed Systematic Signs projects are programmed in ELLIS and mapped out using the ELLIS work location layer. The in-house force account systematic sign project locations are not in ELLIS and will need to be populated in the COUNTY_SSRP feature class.\n\nThis application will help County Management enter planned systematic sign locations into the COUNTY_SSRP feature class, displaying the routes planned for Systematic Sign replacement and when that replacement is happening. Over time this information will help as systematic sign projects are completed, we will be able to see when the route was last completed and plan systematic sign replacement projects in the future to get on a 15-year cycle. \n\nFor more information or changes to the map/data, please contact the ODOT District 3 TAM Coordinator Kenny Krise at (419)-207-7052 or Kenneth.Krise@dot.ohio.gov\n\nTerms of Use\n\nNo warranties, expressed or implied, concerning the accuracy, reliability or suitability of this data have been made by the Ohio Department of Transportation or any other State Agency. Any use of this information is at the recipient's own risk.\n", "Subject": "The Systematic Signs Workplan application was developed to assist the County Forces and Capital Programs sections with planning systematic sign replacement projects. The Capital programmed Systematic Signs projects are programmed in ELLIS and mapped ", "Category": "", "AntialiasingMode": "None", "TextAntialiasingMode": "Force", "Keywords": "TAMC,TAMC Collector,Signs,ODOT" }, "capabilities": "Map,Query,Data", "supportedQueryFormats": "JSON, geoJSON", "exportTilesAllowed": false, "supportsDatumTransformation": true, "maxRecordCount": 10000000, "maxImageHeight": 4096, "maxImageWidth": 4096, "supportedExtensions": "KmlServer" }