{
 "currentVersion": 10.81,
 "serviceDescription": "Volusia County has well over two hundred layers of information in GIS format, most created in house but many are obtained from other sources. When data is created it might be \u201cbuilt\u201d for use at different scales. Think of a paper nationwide map of interstate highways, if you were to use that to create a layer of data in a digital format and overlay it on a local, more accurate, street map, it wouldn\u2019t fit. The scale at which data is created is important. \n\nWe have data, created or acquired, at several different scales. So if you use data automated at a scale of 1\u201d= 2000\u2019 and overlay it on a layer of data automated at a scale of 1\u201d=400\u2019 while you can make some visual associations the line work will not fit.  Data created by different agencies also might use different \u201cbases\u201d to map on, so even data nominally the same scale might be slightly different.\n\nAnother issue is maintenance. A case in point is shown below, where a County zoning line fits the corresponding parcel data. Each County Department maintains their own layers of data and store them in a centralized GIS library for everyone to use. These layers undergo maintenance as information changes. Many of our layers of data use one of our two common base maps, streets and parcels. As those layers undergo maintenance, layers built on them by other agencies require modification as well. If parcel data undergoes maintenance to improve the quality of the data (based on newly provided survey data for instance), then other layers predicated on it need to be adjusted to fit.  Our many data custodians take their responsibilities seriously and while some layers are updated weekly, others are only scheduled for maintenance quarterly or annually due to staffing constraints.   \n",
 "mapName": "Basemap",
 "description": "",
 "copyrightText": "",
 "supportsDynamicLayers": true,
 "layers": [
  {
   "id": 0,
   "name": "Parcels 2015",
   "parentLayerId": -1,
   "defaultVisibility": true,
   "subLayerIds": null,
   "minScale": 24000,
   "maxScale": 0,
   "type": "Feature Layer",
   "geometryType": "esriGeometryPolygon"
  },
  {
   "id": 1,
   "name": "Parcel Text Current",
   "parentLayerId": -1,
   "defaultVisibility": true,
   "subLayerIds": null,
   "minScale": 16000,
   "maxScale": 0,
   "type": "Feature Layer",
   "geometryType": "esriGeometryPolygon"
  },
  {
   "id": 2,
   "name": "Parcels Current",
   "parentLayerId": -1,
   "defaultVisibility": true,
   "subLayerIds": null,
   "minScale": 32000,
   "maxScale": 0,
   "type": "Feature Layer",
   "geometryType": "esriGeometryPolygon"
  },
  {
   "id": 3,
   "name": "BasemapChanges",
   "parentLayerId": -1,
   "defaultVisibility": true,
   "subLayerIds": null,
   "minScale": 800000,
   "maxScale": 0,
   "type": "Feature Layer",
   "geometryType": "esriGeometryPolygon"
  },
  {
   "id": 4,
   "name": "County Boundary",
   "parentLayerId": -1,
   "defaultVisibility": true,
   "subLayerIds": null,
   "minScale": 800000,
   "maxScale": 0,
   "type": "Feature Layer",
   "geometryType": "esriGeometryPolygon"
  }
 ],
 "tables": [],
 "spatialReference": {
  "wkid": 2881,
  "latestWkid": 2881
 },
 "singleFusedMapCache": false,
 "initialExtent": {
  "xmin": 373703.9416404334,
  "ymin": 1650853.9999802553,
  "xmax": 807334.1513595665,
  "ymax": 1866401.18025,
  "spatialReference": {
   "wkid": 2881,
   "latestWkid": 2881
  }
 },
 "fullExtent": {
  "xmin": 439158.16800000146,
  "ymin": 1555529.1239999998,
  "xmax": 741641.875,
  "ymax": 1851597.749,
  "spatialReference": {
   "wkid": 2881,
   "latestWkid": 2881
  }
 },
 "minScale": 800000,
 "maxScale": 0,
 "units": "esriFeet",
 "supportedImageFormatTypes": "PNG32,PNG24,PNG,JPG,DIB,TIFF,EMF,PS,PDF,GIF,SVG,SVGZ,BMP",
 "documentInfo": {
  "Title": "Amanda.mxd",
  "Author": "nchurch",
  "Comments": "Volusia County has well over two hundred layers of information in GIS format, most created in house but many are obtained from other sources. When data is created it might be \u201cbuilt\u201d for use at different scales. Think of a paper nationwide map of interstate highways, if you were to use that to create a layer of data in a digital format and overlay it on a local, more accurate, street map, it wouldn\u2019t fit. The scale at which data is created is important. \n\nWe have data, created or acquired, at several different scales. So if you use data automated at a scale of 1\u201d= 2000\u2019 and overlay it on a layer of data automated at a scale of 1\u201d=400\u2019 while you can make some visual associations the line work will not fit.  Data created by different agencies also might use different \u201cbases\u201d to map on, so even data nominally the same scale might be slightly different.\n\nAnother issue is maintenance. A case in point is shown below, where a County zoning line fits the corresponding parcel data. Each County Department maintains their own layers of data and store them in a centralized GIS library for everyone to use. These layers undergo maintenance as information changes. Many of our layers of data use one of our two common base maps, streets and parcels. As those layers undergo maintenance, layers built on them by other agencies require modification as well. If parcel data undergoes maintenance to improve the quality of the data (based on newly provided survey data for instance), then other layers predicated on it need to be adjusted to fit.  Our many data custodians take their responsibilities seriously and while some layers are updated weekly, others are only scheduled for maintenance quarterly or annually due to staffing constraints.   \n",
  "Subject": "Why don\u2019t these layers fit? \n\nPlease read the following document for more information:\nhttp://www.maps1.vcgov.org/DataDownload/Why_Doesn't_It_fit.pdf",
  "Category": "",
  "AntialiasingMode": "None",
  "TextAntialiasingMode": "Force",
  "Keywords": "Volusia County; Parcel; Changes"
 },
 "capabilities": "Map,Query,Data",
 "supportedQueryFormats": "JSON, geoJSON",
 "exportTilesAllowed": false,
 "referenceScale": 0,
 "datumTransformations": [
  {
   "geoTransforms": [
    {
     "wkid": 108001,
     "latestWkid": 1241,
     "transformForward": true,
     "name": "NAD_1927_To_NAD_1983_NADCON"
    }
   ]
  },
  {
   "geoTransforms": [
    {
     "wkid": 108001,
     "latestWkid": 1241,
     "transformForward": false,
     "name": "NAD_1927_To_NAD_1983_NADCON"
    }
   ]
  }
 ],
 "supportsDatumTransformation": true,
 "maxRecordCount": 1000,
 "maxImageHeight": 4096,
 "maxImageWidth": 4096,
 "supportedExtensions": ""
}