Subbasins_Dissolve_WebApp
<DIV STYLE="text-align:Left;"><DIV><DIV><P><SPAN>This data shows the sewerage subbasins in Pierce County Sewer Service area. </SPAN><SPAN>A sewerage basin represents the existing and planned areas from which wastewater is collected and sent to specific wastewater treatment plants. Sewerage basins are often confused with watersheds or drainage basins. Because most sewer pipelines are designed for gravity flow, a sewerage basin is primarily defined by the topography of the watershed or drainage basin where it is located. The sewer subbasin are smaller areas within the </SPAN><SPAN STYLE="font-size:12pt">sewerage basin</SPAN><SPAN>. Currently there are 24 basin (including Fircrest, Stelacoom, and Western Slopes) and 168 subbasins (including the same). This data will be used to create the following layers:</SPAN></P><UL><LI><P><SPAN>Sewer_Subbasin</SPAN></P></LI><LI><P><SPAN>Sewer_Basin_Facility_Charge</SPAN></P></LI><LI><P><SPAN>Sewer_Pump_Maintenance_Districts (Used by crews)</SPAN></P></LI></UL><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN>Sewer_Subbasin:</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>The symbology is based on GROUP_ as shown in the layer file, Sewer_Subbasin.lyr</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>Fields to be visible: GROUP_, SUB_GROUP</SPAN></P><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN>Sewer_Basin_Facility_Charge:</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>The symbology is based on BASIN_ as shown in the layer file, Sewer_Basin_Facility_Charge.lyr</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>There is a definition query to change the visibility of the layer: BFC = ‘Y’</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>Fields to be visible: BASIN, BASIN_NAME, BASIN_AREA_CHARGE, CAPACITY_CHARGE, USAGE_CHARGE_MONTHLY_PER_RE</SPAN></P><P /><P STYLE="font-weight:bold;margin:0 0 0 0;"><SPAN>Sewer_Pump_Maintenance_Districts</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>The symbology is based on PUMP_DISTRICT_NAME as shown in the layer file, Sewer_Pump_Maintenance_Districts.lyr</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>There is a definition query to change the visibility of the layer: PUMP_MNT_DISTRICTS &lt;&gt; ‘’</SPAN></P><P STYLE="margin:0 0 0 0;"><SPAN>Fields to be visible: PUMP_MNT_DISTRICTS, PUMP_DISTRICT_NAME</SPAN></P><P /><P STYLE="margin:0 0 0 0;"><SPAN>For all of the above new datasets, subbasin_reporting is used for any result boxes and reporting tools in GIS applications.</SPAN></P><P /><P><SPAN /></P><P><SPAN /></P><P><SPAN /></P><P><SPAN /></P><P><SPAN /></P><P><SPAN /></P><P><SPAN /></P><P><SPAN /><SPAN /></P><P><SPAN /></P></DIV></DIV></DIV>
nan
[{'name': 'OBJECTID', 'type': 'esriFieldTypeOID', 'alias': 'OBJECTID', 'sqlType': 'sqlTypeOther', 'nullable': False, 'editable': False, 'domain': None, 'defaultValue': None}, {'name': 'BASIN_NAME', 'type': 'esriFieldTypeString', 'alias': 'BASIN_NAME', 'sqlType': 'sqlTypeOther', 'length': 100, 'nullable': True, 'editable': True, 'domain': None, 'defaultValue': None}, {'name': 'Shape__Area', 'type': 'esriFieldTypeDouble', 'alias': 'Shape__Area', 'sqlType': 'sqlTypeDouble', 'nullable': True, 'editable': False, 'domain': None, 'defaultValue': None}, {'name': 'Shape__Length', 'type': 'esriFieldTypeDouble', 'alias': 'Shape__Length', 'sqlType': 'sqlTypeDouble', 'nullable': True, 'editable': False, 'domain': None, 'defaultValue': None}]
[{'name': 'PK__BASINCON__F4B70D85D53895F2', 'fields': 'OBJECTID', 'isAscending': True, 'isUnique': True, 'description': '', 'indexType': 'Attribute'}, {'name': 'user_7812.BASINCONNECTIONCHARGES_SUBBASINS_DISSOLVE_WEBAPP2_Shape_sidx', 'fields': 'Shape', 'isAscending': True, 'isUnique': False, 'description': '', 'indexType': 'Spatial'}, {'name': 'Shape__Area_Index', 'fields': 'Shape__Area', 'isAscending': True, 'isUnique': False, 'description': '', 'indexType': 'Attribute'}, {'name': 'Shape__Length_Index', 'fields': 'Shape__Length', 'isAscending': True, 'isUnique': False, 'description': '', 'indexType': 'Attribute'}]
nan
{'renderer': {'type': 'simple', 'symbol': {'type': 'esriSFS', 'style': 'esriSFSSolid', 'color': [0, 76, 115, 0], 'outline': {'type': 'esriSLS', 'style': 'esriSLSSolid', 'color': [110, 110, 110, 0], 'width': 0.7}}}, 'scaleSymbols': True, 'transparency': 30, 'labelingInfo': [{'labelExpression': '[BASIN_NAME]', 'labelPlacement': 'esriServerPolygonPlacementAlwaysHorizontal', 'removeDuplicates': 'all', 'removeDuplicatesDistance': 0, 'multiPart': 'labelLargest', 'deconflictionStrategy': 'static', 'repeatLabel': False, 'allowOverrun': True, 'stackLabel': False, 'useCodedValues': True, 'maxScale': 0, 'minScale': 0, 'name': 'Default', 'priority': 3, 'symbol': {'type': 'esriTS', 'color': [0, 0, 0, 255], 'backgroundColor': None, 'borderLineColor': None, 'borderLineSize': None, 'verticalAlignment': 'bottom', 'horizontalAlignment': 'center', 'rightToLeft': False, 'angle': 0, 'xoffset': 0, 'yoffset': 0, 'kerning': True, 'haloColor': [255, 255, 255, 255], 'haloSize': 1, 'font': {'family': 'Arial', 'size': 6, 'style': 'normal', 'weight': 'normal', 'decoration': 'none'}}}]}
[]
[{'name': 'Subbasins_Dissolve_WebApp', 'description': '', 'drawingTool': 'esriFeatureEditToolPolygon', 'prototype': {'attributes': {}}}]