ArcGIS REST Services Directory Login | Get Token
Home > services > AvonCT > AvonEngineeringScans (MapServer) > Engineering Map Extents API Reference
JSON

Layer: Engineering Map Extents (ID: 0)

Name: Engineering Map Extents

Display Field: filename

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: This dataset represents the spatial extents of all Town of Avon, CT Engineering maps and plans stored in drawers and created in the years 1990-2019, most of the maps created in the 1980s, plus a few older maps. Its intended use is help users find Engineering maps that cover an area of interest. It is only intended to be a guide, it does not depict the actual locations of property boundaries.Originally compiled during Summer 2019 by Jeffrey Lyle (GIS intern) for Larry Baril (Town Engineer) – Town of Avon, CT Engineering, Sewer, and GIS Department. Map extents were located primarily by comparing the Enginnering map with the Cadastral_MDB_Parcelsdataset from the Town of Avon internal GIS server and identifying parcel(s) with the correct size and shape. Other supplementary data was used as well, such as 2016 ORTHO, 2016 Hillshade, and 2016 Contours datasets from CT ECO; and Buildings83_poly, Sewer_Net and Road_centerline83 from internal Town of Avon GIS data.Once the location was identified, a polygon was drawn enclosing all of the important information shown on the Engineering map. If it was a parcels map, the polygon was drawn approximately 10-20 feet beyond the parcels’ boundaries as shown in the Parcels GIS data to ensure that the boundaries were included within the map extent polygon. If a boundary was not shown on the Parcels GIS data then the coordinate geometry information from the map was used to estimate the boundary’s location.I considered topographic information to be important information that should be included in the extent polygon, so I included the full extent of topo maps instead of just the parcels that the map focuses on. Therefore, most of the extents of topographic maps were plotted as rectangles. I also plotted extents as rectangles for series of maps that collectively describe a large subdivision, such as Buckingham or Weatherstone.Many maps were road or sewer plan & profiles. In general, the segment of road or sewer line was treated as the parcel and extent polygons were traced about ~ 10-20 feet beyond the parcel boundary as shown on the Parcels GIS data, just as any other parcel map would be treated. However, there was often other valuable information on the map that needed to be encompassed by the extent polygon (such as topography), so I drew some road or sewer profile polygons as rectangles or other larger polygons.Description of Fields:drawer: Drawer that the physical copy of the map was stored in.file: File numberfilename: Name of the scanned map on the computer. Format goes like: drawer + “-“ + file + “.pdf”fileyear: Date when the map was published. If only the month was available, the first day of the month was assumed.type: General type of map. See below for descriptions of the types:parcels: The map primarily shows parcel boundarieshighway: The map primarily shows a road, but does not include a profile.profile: The map primarily shows a road and its profile. It may also show utilities.sewer: The map primarily shows a sewer line, usually with a profile included.drainage: The map primarily shows a drainage easement or structure.stream profile: The map primarily shows a stream or river with its profile.culvert: The map primarily shows a culvert.as-built: As-built survey that is not included in the other categories.ng: The map primarily shows a natural gas pipeline.planting plan: Planting plan or other Landscape Architecture drawingtopo map: The map shows topography and is not included in other categories.site plan: A plan for a site (not including planting plan). Includes site development plans, erosion control plans, etc.water: The map primarily shows a water line.Revised_copy: Does this map include any revisions? "y" if yes, "n" if no.cogo: Was any part of this extent polygon plotted using coordinate geometry information? "y" if yes, "n" if no.created_date: Date the polygon was created.created_user: First initial and last name of the user who created the polygon.

Copyright Text:

Default Visibility: true

MaxRecordCount: 2000

Supported Query Formats: JSON, geoJSON, PBF

Min Scale: 0

Max Scale: 0

Supports Advanced Queries: true

Supports Statistics: true

Has Labels: false

Can Modify Layer: true

Can Scale Symbols: false

Use Standardized Queries: true

Supports Datum Transformation: true

Extent:
Drawing Info: Advanced Query Capabilities:
HasZ: false

HasM: false

Has Attachments: true

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:
Supported Operations:   Query   Query Attachments   Query Analytic   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata