All Layers and Tables (survey123_d8c79e4cf71e40c387b4ccac2bf7c1df

Layers:

Layer: Basin_Level_Flooding_Assessment_Form (0)

Name:

Display Field:

Type:

Geometry Type:

Is View:

Is Updatable View:

Source Schema Changes Allowed:

Description:

Copyright Text:

Min. Scale:

Max. Scale:

Default Visibility:

Max Record Count:

Supported query Formats:

Use Standardized Queries:

Extent:

Drawing Info:

{"labelingInfo":null,"renderer":{"description":"Survey Data Locations","label":"Basin-Level Flooding Assessment Form","symbol":{"angle":0,"color":[255,0,0,255],"outline":{"color":[255,255,0,255],"width":1},"size":8,"style":"esriSMSCircle","type":"esriSMS","xoffset":0,"yoffset":0},"type":"simple"},"transparency":0}

HasZ:

HasM:

Has Attachments:

Has Geometry Properties:

HTML Popup Type:

Object ID Field:

Unique ID Field:

Global ID Field:

Type ID Field:

Fields:

objectid (type: esriFieldTypeOID, alias: ObjectID, SQL Type: sqlTypeOther, length: 0, nullable: false, editable: false)
globalid (type: esriFieldTypeGlobalID, alias: GlobalID, SQL Type: sqlTypeGUID, length: 38, nullable: false, editable: false)
District_Name (type: esriFieldTypeString, alias: Name of Special District or Water Management District:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
Disctrict_Responsibilities (type: esriFieldTypeString, alias: Please indicate whether your special district is responsible for any of the following:, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true)
District_Conduct_Assessments (type: esriFieldTypeString, alias: 1. Does the district currently conduct basin-level flooding assessments / watershed flood risk studies (i.e., modeling of flood risk at the watershed-level)?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [Yes: Yes], [No: No])
District_Provide_Funding (type: esriFieldTypeString, alias: 2. Does the district provide funding assistance to local partners to conduct similar flood studies in addition to, or in lieu of, district efforts?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [Yes: Yes], [No: No])
Guidelines_Scale (type: esriFieldTypeString, alias: a. Scale of boundary/watershed, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Guidelines_Spatial (type: esriFieldTypeString, alias: b. Spatial data, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Guidelines_Topographic (type: esriFieldTypeString, alias: c. Topographic data, including LiDAR and ground surveys, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Guidelines_Hydrologic (type: esriFieldTypeString, alias: d. Hydrologic features, including rainfall data and soils, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Guidelines_Hydraulic (type: esriFieldTypeString, alias: e. Hydraulic features, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Guidelines_Floodplain_Delinea (type: esriFieldTypeString, alias: f. Floodplain delineation, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Guidelines_Future_Conditions (type: esriFieldTypeString, alias: g. Future condition projections, including rising sea levels, increased rainfall and compound flooding, and changes in land use, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Guidelines_Floodplain_Analysis (type: esriFieldTypeString, alias: h. Floodplain analysis and H&H model development, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Guidelines_Flood_Protection (type: esriFieldTypeString, alias: i. Flood protection level of service (FPLOS), SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Guidelines_Critical_Infrastruc (type: esriFieldTypeString, alias: j. Critical infrastructure access, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Guidelines_Incorporated_Doc (type: esriFieldTypeString, alias: 5. Are the above technical guidelines incorporated into a guidance document?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [Yes: Yes], [No: No])
Flood_Assessment_Study_HH (type: esriFieldTypeString, alias: 6. Are the flood assessments / risk studies based on hydrologic and hydraulic (H&H) modeling?, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true, Coded Values: [Yes: Yes], [No: No])
Basins_Prioritization (type: esriFieldTypeString, alias: 7. How are basins / watersheds prioritized for flood studies? Is there initial screening to prioritize where more granular modeling should be done?, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Modeling_Validation_Process (type: esriFieldTypeString, alias: 8. What processes (including peer or external review) are used to validate the results of the modeling?, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Public_Outreach (type: esriFieldTypeString, alias: 9. Is public outreach a component of the district's process for conducting flood assessments?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [Yes: Yes], [No: No])
Public_Outreach_Description (type: esriFieldTypeString, alias: a. Please describe., SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
FEMA_Technical_Coop (type: esriFieldTypeString, alias: 10. Is the district a technical cooperative partner with FEMA?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [Yes: Yes], [No: No])
FEMA_Technical_Used (type: esriFieldTypeString, alias: a. Are any FEMA requirements and standards built into the studies?, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
District_Other_Work_Relevant (type: esriFieldTypeString, alias: a. Is there other work the district does relevant to flooding and flood risk?, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Additional_Context (type: esriFieldTypeString, alias: 11. Is there any additional context for your answers that you'd like to share?, SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
CreationDate (type: esriFieldTypeDate, alias: CreationDate, SQL Type: sqlTypeOther, length: 8, nullable: true, editable: false)
Creator (type: esriFieldTypeString, alias: Creator, SQL Type: sqlTypeOther, length: 128, nullable: true, editable: false)
EditDate (type: esriFieldTypeDate, alias: EditDate, SQL Type: sqlTypeOther, length: 8, nullable: true, editable: false)
Editor (type: esriFieldTypeString, alias: Editor, SQL Type: sqlTypeOther, length: 128, nullable: true, editable: false)
Guidelines_Description (type: esriFieldTypeString, alias: 4. What guidelines are put into place to ensure technical consistency for the following types of data? (Examples of types of data include scale or boundary/watershed; spatial data; topographic data, including LiDAR and ground surveys; hydrologic features, including rainfall and soils; hydraulic features; floodplain delineation; future condition projections, including sea level rise, increased rainfall, compound flooding, and land use changes; floodplain analysis and H&H model development; flood protection level of service; and access to critical assets.), SQL Type: sqlTypeOther, length: 3000, nullable: true, editable: true)
Have_GIS_Files (type: esriFieldTypeString, alias: 3. Do you have GIS files for your service area?, SQL Type: sqlTypeOther, length: 255, nullable: true, editable: true, Coded Values: [Yes: Yes], [No: No])
District_Type (type: esriFieldTypeString, alias: District Type, SQL Type: sqlTypeOther, length: 500, nullable: true, editable: true)

Templates:

Relationships:

Basin_Level_Flooding_Assessment_Form_Basin_Information (1) -- Related To: Basin_Information (1)

Is Data Versioned:

Has Contingent Values:

Supports Rollback On Failure Parameter:

Last Edit Date:

Schema Last Edit Date:

Data Last Edit Date:

Tables:

Basin_Information (1)