1 / 24

North Carolina CTS Committee Meeting #4

North Carolina CTS Committee Meeting #4. January 16, 2001. Today’s Agenda. Status updates Demonstration of scoping tool Information Management System “NCFloodmaps.com” demo Working Group reports/updates Discussion Items Agenda items for CTS Meeting #5. Status Updates.

ranger
Download Presentation

North Carolina CTS Committee Meeting #4

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. North Carolina CTS Committee Meeting #4 January 16, 2001

  2. Today’s Agenda • Status updates • Demonstration of scoping tool • Information Management System • “NCFloodmaps.com” demo • Working Group reports/updates • Discussion Items • Agenda items for CTS Meeting #5

  3. Status Updates • Contract/Delivery Order Negotiations (John Dorman) • Basin Plans/Flood Data Delivery Order Development (Abdul Rahmani) • LIDAR DO and QA/QC(Gary Thompson) • Community needs/scoping (Ken Taylor)

  4. Status Updates • Coordination with Federal Agencies (John Dorman) • January 8-11, 2001, trip toWashington, D.C. • FEMA and State Staff: • Participated in FGDC Coordination Group meeting • Met with USACE, HUD, DOT, USGS, and NASA about funding and mapping activities • Also briefed/updated NC Congressional and key Committee staff

  5. GIS-Enabled Scoping Tool

  6. GIS-Enabled Scoping Tool • Provides centralized database of initial research data • Provides immediate access to flood map data during community scoping meetings • Enables user to visualize data and recommendations for multiple communities and flooding sources • Assists in scoping out mapping activities on a basin-wide basis (continued)

  7. GIS-Enabled Scoping Tool • Data collected from wide range ofsources, including: • CIS/Status • Library research • MNUSS • State and Federal GIS data sets • Census Bureau • Community Input (Meetings and Questionnaires) • Q3 • FIA (continued)

  8. GIS-Enabled Scoping Tool • Data stored on two levels: • Community basis • Flooding source basis • GIS display provides link to bothtypes of data

  9. Information Management System

  10. Status of IT System • DO negotiations finalized/notice to proceed • Major tasks: • Requirements analysis • Preliminary system design • Work plan for implementation • ESRI is IT provider (part of WC Team) • Work began week of Jan. 8-12, 2001

  11. Schedule for IT System

  12. NCFloodmaps.com

  13. NCFloodmaps.com • Public Web site providing: • Description of Statewide flood mapping program • News about the program • Status and progress reports • Public documents, such as project fact sheets, presentations, etc., for download • Important links to other Web sites

  14. NCFloodmaps.com • Will go “live” by 1/19/01 • Descriptions of Federal Agency partners included in your notebook • Please provide comments about Agency writeups to Jerry Sparks at jsparks@dewberry.com by 1/23/01 • Provide comments on Web site to Bart Alligood at Bart.Alligood@ncmail.net • Demo

  15. Working Group Reports/Status Updates

  16. Working Group Reports/Status Updates • Future Conditions — Gavin Smith • Coastal — Abdul Rahmani • Post-Flood HazardVerification — Gavin Smith

  17. Discussion Items

  18. Conflicts between State and Local Priorities Issue: • Flood data update needs for basin plans based on variety of methods: • Community surveys and input at initial scoping meetings • Historical flood data, such as post-Floyd gage records and inundation mapping • Flood insurance and repetitive loss claims data • Engineering assessments of effective FIS and FIRM analyses • Mapping deficiencies documented in FEMA’s archives • Community response to FEMA’s MNUSS survey • Some communities may not agree with all needs identified by State and FEMA

  19. Conflicts between State and Local Priorities Proposed Policy/Process: • All needs ranked/scored using “Selecting Technical Methods and Assigning Scores” procedures • If ranked high enough, will be included in the Draft Basin Plan • Communities will have opportunity to provide input at Final Scoping Meeting • Technical justification will be required for removing from Basin Plan

  20. “Approximate” Flood Elevations Issue: • Zone A areas on FIRMs do notshow BFEs • Typically not based on computations • Zone A areas for NC’s program will be based on H&H analyses/models (albeit less detailed than full detailed study) • Computed 1% annual chance flood elevations useful for floodplain management • Can also be used to rate flood insurance policies

  21. “Approximate” Flood Elevations Proposed Policy/Process: • How to best disseminate this elevation information? • FIRMs? • FIS Reports? • Online IT System? • Other mechanisms? • What do we call them?

  22. Flood Insurance and Mortgage Determinations Issue: • NC flood maps will be official FIRMs • Will be used for flood insurance and mortgage determinations Proposed Policy/Process: • Should other interested parties(i.e., insurance agents, determination companies) be proactively engaged?

  23. Issues for Discussion at CTS Committee Meeting #5 Scheduled for February 13, 2001

  24. Action Items/Wrap Up

More Related