GIS Data Catalog
Control Other Line
Learn how to use GIS Open Data 🗺
Summary
A stormwater management feature or best management practice (BMP) that provides Flow Control and/or Water Quality, but does not fit in one of the other Control Components.
Description
Control Other Line Component Type---Infiltration Trench: 2-5’ wide trench designed to infiltrate stormwater below the ground They feature perforated distribution pipes that is topped with filter fabric to prevent dispersal to the ground ---Bioretention Swale: May have rocks in the swale, various plantings with a landscaped feature look.
---Dispersal Trench: 2.5’ or greater trench designed to disperse stormwater to the ground They feature perforated distribution pipes and a filter fabric trench liner to prevent infiltration.
---Basic Dispersion: Basic dispersion is the application of dispersion devices that utilize any available capacity of onsite vegetated areas to mitigate the runoff quantity and quality impacts from developed surfaces (i.e., impervious and non-native pervious surfaces).
The requirements for basic dispersion are less restrictive than full dispersion in that any type of vegetation cover is allowed, the flowpath lengths through the vegetation are shorter, and there is no requirement to preserve native vegetated surface (e.g., forested surface) or minimize developed As such, its mitigation of runoff impacts is significantly lower than that of full dispersion.---Full Dispersion: Features a native vegetated flowpath segment of at least 100ft (25ft for sheet flow.
from a non-native pervious surface) along the flowpath that runoff would follow upon discharge.
The flowpath segment must be either onsite or in an offsite tract or easement area reserved for dispersion and should be designated as a “native growth retention area” on the flow control BMP site plan attached to the required declaration of covenant and grant of easement.
Full dispersion involves use of splash blocks, rock pads, gravel filled trenches or sheet flow.
Layer information
| Layer Name | sw_ctrl_other_line_line |
| Subject Category | Utilities |
| Title | Control Other Line |
| Feature Count | 1082 |
| Feature Type | Line |
| Next Update | Continually |
| Spatial reference | EPSG:2926 |
| Control ID | 2512 |
| Place Keywords | Pacific NW, King County, WA, Washington State |
| Theme Keywords | Utility, MS4, Stormwater, Drainage, Municipal Separate Stormwater Sewer System, NPDES Municipal Stormwater Permit, Utilitiescommunication |
| Supplemental Information | None |
Table Preview
Attribute information
|
OBJECTID
From Esri |
Description
Internal feature number. DomainSequential unique whole numbers that are automatically generated. |
|
Shape
From King County |
Description
Feature geometry. DomainCoordinates defining the features. |
|
DBAssetID
From SOP Chapter 2: Database Design |
Description
DBAssetID is the unique identifier that is used to tie to Cityworks, MIS, or some other database. The DBAssetID is unique for each feature class and is generated by a script that runs nightly. Users should not modify the DBAssetID. DomainNot Found |
|
ComponentType
From SOP Chapter 2: Database Design |
Description
Within the Puget Sound Stormwater Infrastructure Framework, Component Type is the finest classification for a structure. DomainBioretention Swale - Bioretention Swale: Bioretention Swale: May have rocks in the swale, various plantings with a landscaped feature look. Infiltration Trench - Infiltration Trench: 2-5’ wide trench designed to infiltrate stormwater below the ground surface. They feature perforated distribution pipes that is topped with filter fabric to prevent dispersal to the ground surface. Basic Dispersion - Basic Dispersion: Basic dispersion is the application of dispersion devices that utilize any available capacity of onsite vegetated areas to mitigate the runoff quantity and quality impacts from developed surfaces (i.e., impervious and non-native pervious surfaces). The requirements for basic dispersion are less restrictive than full dispersion in that any type of vegetation cover is allowed, the flowpath lengths through the vegetation are shorter, and there is no requirement to preserve native vegetated surface (e.g., forested surface) or minimize developed surface. As such, its mitigation of runoff impacts is significantly lower than that of full dispersion. Full Dispersion - Full Dispersion: Full Dispersion: Features a native vegetated flowpath segment of at least 100ft (25ft for sheet flow from a non-native pervious surface) along the flowpath that runoff would follow upon discharge. The flowpath segment must be either onsite or in an offsite tract or easement area reserved for dispersion and should be designated as a “native growth retention area” on the flow control BMP site plan attached to the required declaration of covenant and grant of easement. Full dispersion involves use of splash blocks, rock pads, gravel filled trenches or sheet flow. |
|
Intent
From SOP Chapter 2: Database Design |
Description
Intent tracks whether the infrastructure was designed primarily to convey stormwater or a natural water body. DomainNot Found |
|
Underdrain
From SOP Chapter 2: Database Design |
Description
Underdrain tracks if the Control feature has an underdrain. DomainNo, Yes |
|
FCBMPType
No Source Noted |
Description
Not Found DomainNot Found |
|
PipeMaterial
From SOP Chapter 2: Database Design |
Description
Pipe Material tracks the material the underdrain pipe is made of. DomainNot Found |
|
PipeDiameter
From SOP Chapter 2: Database Design |
Description
Pipe Diameter is the average inner diameter of the Connect structure, not the opening (cover frame or slab). DomainNot Found |
|
Liner
From King County |
Description
Material type of low permeability liner or treatment liner that is located underneath the stormwater control feature. DomainNot Found |
|
OwnerEntity
From SOP Chapter 2: Database Design |
Description
OwnerEntity tracks the owner of the particular feature. DomainPrivate, WLRD |
|
Jurisdiction
From SOP Chapter 2: Database Design |
Description
Jurisdiction tracks the jurisdiction that governs the land that the asset resides in. DomainKing County |
|
XYSource
From SOP Chapter 2: Database Design |
Description
XYSource tracks the method in which the geographic location of the asset was recorded. DomainPicked from aerial |
|
KingCountyMS4
No Source Noted |
Description
Not Found DomainNot Found |
|
FieldVisitDate
From SOP Chapter 2: Database Design |
Description
FieldVisiteDate tracks the date that staff last visited the feature in the field. DomainNot Found |
|
LastEditDate
From SOP Chapter 2: Database Design |
Description
LastEditDate tracks the date that staff last edited the feature. DomainNot Found |
|
DataStage
From SOP Chapter 2: Database Design |
Description
DataStage tracks the status of the data as it moves through the QAQC process. DomainAcquire, Process |
|
CurrentStatus
From SOP Chapter 2: Database Design |
Description
CurrentStatus tracks the status of the data as it moves through the lifecycle of an asset. DomainActive |
|
DataSource
From SOP Chapter 2: Database Design |
Description
DataSource tracks the group, program, or process that added the data. DomainSWSS Mapping |
|
FacilityID
From SOP Chapter 2: Database Design |
Description
FacilityID tracks the FacilityID number that the feature is a part of. DomainNot Found |
|
PlanLink
From SOP Chapter 2: Database Design |
Description
When digital plans are available, PlanLink provides a hyperlink to plan files. DomainNot Found |
|
GlobalID
From ESRI |
Description
GlobalID is a 36 character string that ArcGIS uses to uniquely identify features or table rows within a geodatabase and across geodatabases. DomainNot Found |
|
AssetID
From SOP Chapter 2: Database Design |
Description
AssetID is the unique identifier that is used to tie to Cityworks, MIS, or some other database. The AssetID is unique for each feature class and is generated by a script that runs nightly. Users should not modify the AssetID. Domain5740, 5741, 5742, 5923, 5924, 5954, 5992, 6358, 6476, 6480, 6778, 7134, 7641, 7642 |
|
PAA
From SOP Chapter 2: Database Design |
Description
PAA tracks which Potential Annexation Area an asset intersects, if applicable. DomainNot Found |
|
CCTVInspectionDate
From King County |
Description
Most Recent CCTV Inspection tracks the date of the most recent CCTV inspection. DomainNot Found |
|
Shape.STLength()
From ESRI |
Description
Shape is used by ArcGIS to store the geometry of a feature. DomainNot Found |
Contact information
| Maintained by | DNRP - Water and Land Resources |
| Primary |
Harkeerat Kang
Harkeerat.Kang@kingcounty.gov |
Terms of Use
| License | Terms of use and copyright |
Use this Data
|
Links
How to use in ArcGIS Pro |
|
| Sharing Status | Public |
Summary
A stormwater management feature or best management practice (BMP) that provides Flow Control and/or Water Quality, but does not fit in one of the other Control Components.
Description
Control Other Line Component Type---Infiltration Trench: 2-5’ wide trench designed to infiltrate stormwater below the ground They feature perforated distribution pipes that is topped with filter fabric to prevent dispersal to the ground ---Bioretention Swale: May have rocks in the swale, various plantings with a landscaped feature look.
---Dispersal Trench: 2.5’ or greater trench designed to disperse stormwater to the ground They feature perforated distribution pipes and a filter fabric trench liner to prevent infiltration.
---Basic Dispersion: Basic dispersion is the application of dispersion devices that utilize any available capacity of onsite vegetated areas to mitigate the runoff quantity and quality impacts from developed surfaces (i.e., impervious and non-native pervious surfaces).
The requirements for basic dispersion are less restrictive than full dispersion in that any type of vegetation cover is allowed, the flowpath lengths through the vegetation are shorter, and there is no requirement to preserve native vegetated surface (e.g., forested surface) or minimize developed As such, its mitigation of runoff impacts is significantly lower than that of full dispersion.---Full Dispersion: Features a native vegetated flowpath segment of at least 100ft (25ft for sheet flow.
from a non-native pervious surface) along the flowpath that runoff would follow upon discharge.
The flowpath segment must be either onsite or in an offsite tract or easement area reserved for dispersion and should be designated as a “native growth retention area” on the flow control BMP site plan attached to the required declaration of covenant and grant of easement.
Full dispersion involves use of splash blocks, rock pads, gravel filled trenches or sheet flow.
Contact information
| Maintained by | DNRP - Water and Land Resources |
| Primary |
Harkeerat Kang
Harkeerat.Kang@kingcounty.gov |
Terms of use and copyright
| License | Terms of use and copyright |
Change history
| 10/16/2015 |
Data imported from KC Roads and other sources. |