{
 "currentVersion": 10.71,
 "cimVersion": "2.4.0",
 "id": 0,
 "name": "Numeric Nutrient Criteria",
 "type": "Group Layer",
 "description": "The Numeric Nutrient Criteria are established to set allowable surface limits on nutrients (nitrogen, phosphorus, and floral response) in Florida's waters. The Rule's hierarchical approach gives preference to site-specific analyses that result in a numeric interpretation of the NNC. Site specific interpretations are generally deemed superior to more broadly applicable interpretations of the NNC because of the many natural factors affecting the expression of nutrient loadings on a given waterbody. If there is a site specific interpretation of the narrative, such as a Total Maximum Daily Load, Site Specific Alternative Criterion, Water Quality Based Effluent Limitation, or other Department-approved action that numerically interprets the narrative criterion (e.g., Reasonable Assurance derived values), that numeric interpretation is the applicable nutrient criterion. These numeric interpretations of the narrative criterion must establish the total allowable load or ambient concentration for at least one nutrient that represents achievement of a healthy, well balanced aquatic community. Each nutrient (nitrogen and phosphorus) is interpreted independently using this hierarchical approach; if the site-specific interpretation only addresses one nutrient, then the generally applicable numeric interpretations will apply for the other nutrient.If a site specific interpretation is not available, the Rule\u2019s hierarchical approach then gives preference to numeric nutrient values based on quantifiable stressor-response relationships between nutrients and biological response (i.e., springs and lakes). If no quantifiable stressor-response relationship has been established, such as is the case for Florida streams, reference-based Nutrient Thresholds, in conjunction with biological information, are used to determine the applicable interpretation of the NNC. For those waters without a numeric interpretation under any of these approaches, the NNC continues to apply to the waterbody.",
 "geometryType": null,
 "copyrightText": "FDEP, DEAR, Standards Development Section",
 "parentLayer": null,
 "subLayers": [
  {
   "id": 1,
   "name": "Coastal Nutrient Regions"
  },
  {
   "id": 2,
   "name": "Narrative Nutrient Criteria Waters"
  },
  {
   "id": 3,
   "name": "Numeric Nutrient Criteria (NNC) - Estuary Nutrient Regions"
  },
  {
   "id": 4,
   "name": "Site Specific Interpretations of the Narrative Nutrient Criterion"
  },
  {
   "id": 5,
   "name": "Stream Nutrient Regions"
  }
 ],
 "minScale": 0,
 "maxScale": 0,
 "defaultVisibility": false,
 "extent": {
  "xmin": 52666.37589999923,
  "ymin": 41211.68589999899,
  "xmax": 799725.4853999994,
  "ymax": 781568.6295000017,
  "spatialReference": {
   "wkid": 3087,
   "latestWkid": 3087,
   "xyTolerance": 0.001,
   "zTolerance": 0.001,
   "mTolerance": 0.001,
   "falseX": -19550100,
   "falseY": -7526400,
   "xyUnits": 2.2574321067916927E8,
   "falseZ": -100000,
   "zUnits": 10000,
   "falseM": -100000,
   "mUnits": 10000
  }
 },
 "hasAttachments": false,
 "htmlPopupType": "esriServerHTMLPopupTypeNone",
 "displayField": "",
 "typeIdField": null,
 "subtypeFieldName": null,
 "subtypeField": null,
 "defaultSubtypeCode": null,
 "fields": null,
 "geometryField": {},
 "indexes": [],
 "subtypes": [],
 "relationships": [],
 "canModifyLayer": false,
 "canScaleSymbols": false,
 "hasLabels": false,
 "capabilities": "Map,Query",
 "supportsStatistics": false,
 "supportsAdvancedQueries": false,
 "supportedQueryFormats": "JSON, geoJSON, PBF",
 "isDataVersioned": false,
 "ownershipBasedAccessControlForFeatures": {"allowOthersToQuery": true},
 "useStandardizedQueries": true,
 "advancedQueryCapabilities": {
  "useStandardizedQueries": true,
  "supportsStatistics": false,
  "supportsHavingClause": false,
  "supportsOrderBy": false,
  "supportsDistinct": false,
  "supportsCountDistinct": false,
  "supportsPagination": false,
  "supportsTrueCurve": true,
  "supportsReturningQueryExtent": true,
  "supportsQueryWithDistance": true,
  "supportsSqlExpression": false
 },
 "supportsDatumTransformation": true,
 "dateFieldsTimeReference": null,
 "hasMetadata": true,
 "isDataArchived": false,
 "archivingInfo": {
  "supportsQueryWithHistoricMoment": false,
  "startArchivingMoment": -1
 },
 "supportsCoordinatesQuantization": true,
 "supportsDynamicLegends": false
}