Name: GDB_PUB.RIVCO.DRAINAGEFEE

Display Field: MAPNAME

Type: Feature Layer

Geometry Type: esriGeometryPolygon

Description: The Subdivision Map Act requires that agencies imposing fees have a general drainage plan for the fee area, a special fund for the fees and an equitable distribution of the fees prior to implementation. Since the District does not have land use authority, it cannot implement drainage fees directly. The District must therefore request that the County and/or local cities adopt drainage fees within their jurisdictions for the District. The District generally agrees to create the special funds for the fees and to prepare an ADP. The ADP is a document specifically prepared for the County and cities to adopt. The Area Drainage Plan is essentially the Master Drainage Plan with additional language supporting the costs and distribution of the fee within the plan area. To ensure the equitable distribution of fees, the ADP/MDP boundaries are generally based on watersheds. The total costs of facilities within the watershed are first calculated. The watershed area is then adjusted to discount publicly owned lands and areas on steep slopes not likely to develop. Finally, the total facility cost is divided by the revised watershed area to determine a per acre fee for the plan area. Due to State Law, the collection of drainage fees varies depending on the type of development. Developments falling under the Subdivision Map Act (those requiring a division of lands) pay fees on a per acre basis. Developments falling outside of the Subdivision Map Act (known as discretionary developments) can only be assessed fees based on their impacts to the watershed. The ADP Rules and Regulations state that these impacts can be related to the amount of impervious surface area that the development creates. Therefore, discretionary developments are charged not on a gross acreage basis, but on the total impervious acreage created by their development.

Definition Expression: N/A

Copyright Text: Credit for this material belongs solely to the Riverside County Flood Control and Water Conservation District.

Default Visibility: true

MaxRecordCount: 1000

Supported Query Formats: JSON, AMF, geoJSON

Min Scale: 1000000

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:

XMin: 6148875.126011103
YMin: 2117693.4204365164
XMax: 6464658.461962864
YMax: 2322158.72836861
Spatial Reference: 102646  (2230)

Drawing Info:

Renderer:
Simple Renderer:
Symbol:
Style: esriSFSSolid
Color: [199, 210, 242, 255]
Outline:
Style: esriSLSSolid
Color: [110, 110, 110, 255]
Width: 0
Label:
Description:
Transparency: 0
Labeling Info:

Advanced Query Capabilities:

Supports Statistics: true
Supports OrderBy: true
Supports Distinct: true
Supports Pagination: true
Supports TrueCurve: true
Supports Returning Query Extent: true
Supports Query With Distance: true
Supports Sql Expression: true
Supports Query With ResultType: false
Supports Returning Geometry Centroid: false

HasZ: false

HasM: false

Has Attachments: false

HTML Popup Type: esriServerHTMLPopupTypeAsHTMLText

Type ID Field: null

Fields:

• OBJECTID ( type: esriFieldTypeOID , alias: OBJECTID )
• MAPNAME ( type: esriFieldTypeString , alias: MAPNAME , length: 40 )
• FEE ( type: esriFieldTypeInteger , alias: FEE )
• PLAN_COST ( type: esriFieldTypeDouble , alias: PLAN_COST )
• ACRES ( type: esriFieldTypeDouble , alias: ACRES )
• AMEND_NO ( type: esriFieldTypeDouble , alias: AMEND_NO )
• ORIG_ADOPT ( type: esriFieldTypeDate , alias: ORIG_ADOPT , length: 8 )
• EFFECTIVE_DATE ( type: esriFieldTypeDate , alias: EFFECTIVE_DATE , length: 8 )
• Shape ( type: esriFieldTypeGeometry , alias: Shape )
• Shape.STArea() ( type: esriFieldTypeDouble , alias: Shape.STArea() )
• Shape.STLength() ( type: esriFieldTypeDouble , alias: Shape.STLength() )

Supported Operations:   Query   Generate Renderer   Return Updates

  Iteminfo   Thumbnail   Metadata