Flood Map Desktop™<br />Case Studies<br />
Background<br />FEMA’s DFIRM Tools will be decommissioned July 31, 2010.<br />Several FEMA Lunch & Learn sessions hosted t...
Premise<br />Many AWRA members engaged in FEMA flood mapping projects<br />To date, many users have transferred FEMA proje...
transfer data from DFIRM Tools to FMD<br />Case Study #1 – Sherburne, MN<br />
Case Study #1 - Sherburne, MN<br />42 Printed FEMA Maps<br />312 Cross Sections<br />3 detailed streams<br />7,375 Transpo...
Case Study #1 - Sherburne, MN<br />
Case Study #1 - Sherburne, MN<br />Font Transfer<br />Issue: FMD contains FEMA symbology, but DFIRM Tools system dependent...
Case Study #1 - Sherburne, MN<br />Example of with and without MapText font results<br />
Case Study #1 - Sherburne, MN<br />Example of with and without MapText font results<br />
Case Study #1 - Sherburne, MN<br />Import DFIRM Tools data to multi-user format<br />Issue: After data import, user wants ...
Case Study #1 - Sherburne, MN<br />ELM<br />Disconnected multi-user cartography<br />Connected multi-user cartography<br />
Case Study #1 - Sherburne, MN<br />
Case Study #1 - Sherburne, MN<br />Import DFIRM Tools data to FMD<br />Issue: Data transfer is large – “out of memory” err...
Case Study #1 - Sherburne, MN<br />
Case Study #1 - Sherburne, MN<br />Data transfer quality control<br />Issue: Transferring data from one system to another ...
Case Study #1 - Sherburne, MN<br />
Case Study #1 - Sherburne, MN<br />Error discovery results:<br />6 layers containing significant topology errors<br />Viol...
Case Study #1 - Sherburne, MN<br />Final Steps: Review Cartography & MIP Upload<br />Some minor issues discovered in carto...
Case Study #1 - Sherburne, MN<br />
Case Study #1 - Sherburne, MN<br />
Case Study #1 - Sherburne, MN<br />
distributed processing using non-enterprise tools<br />Case Study #2 – Marion, IN<br />
Case Study #2 – Marion, IN<br />Highly urbanized area - contains the City of Indianapolis<br />97 Printed panels<br />914 ...
Case Study #2 – Marion, IN<br />Data Edits<br />Cartography w/ ELM file type<br />Reconcile GRF into ELM<br />Final Export...
Case Study #2 – Marion, IN<br />Custom Workflow Explained<br />Non-enterprise system desired<br />Very fast client deadlin...
Case Study #2 – Marion, IN<br />ELM & GRF file types<br />ELM: Element database. MS Access based w/out MS locks, multi-use...
Case Study #2 – Marion, IN<br />MS Access personal geodatabase is locked to multi-user editing.<br />ELM element database ...
Case Study #2 – Marion, IN<br />
Case Study #2 – Marion, IN<br />
Case Study #2 – Marion, IN<br />Conclusions<br />Low IT investment v. enterprise system<br />effective method for multi-us...
distributed processing using enterprise tools<br />Case Study #3 – Recreation of ArcSDE environment<br />Case study slides...
Case Study #3 – Recreation of ArcSDE environment<br />User desired to re-create ArcSDE experience w/out DFIRM Tools<br />M...
Case Study #3 – Recreation of ArcSDE environment<br />Issue: labor intensive creation of schema to extensive FEMA database...
Issue: Custom workflow used for production<br />Solution: Self-customization of the imported schema.<br />Case Study #3 – ...
In this example, we added the “Supplemental” feature dataset to meet custom data management procedures. </li></ul>Case stu...
Case Study #3 – Recreation of ArcSDE environment<br /><ul><li>Issue: Efficiency and slow data editing speeds
Solution: WAN connections too slow for production but LAN connections had minimal speed loss</li></ul>Disconnected databas...
Case Study #3 – Recreation of ArcSDE environment<br />Conclusions<br />Centrally stored database<br />Tightly managed work...
extend FMD tools to include user-specific needs<br />Case Study #4 – Extend FMD Tools<br />Case study slides provided by C...
Case Study #4 – Custom Tools<br />Issue:  High-volume producer for FEMA needs rapid software change and custom tools<br />...
Case Study #4 – Custom Tools<br />Solution<br />Our developers design a stand alone ArcGIS Toolbar which pulls data from t...
Case Study #4 – Custom Tools<br />Solution<br />Export selected files – no need to re-export entire database for a correct...
Case Study #4 – Custom Tools<br />Conclusions<br />Simple interface written in VBA using existing ArcGIS capabilities<br /...
CDM Contact Info<br />Mike Schultz, GISP, CFM – schultzmd@cdm.com<br />Gaston Cabanilla, PE, CFM – cabanillaga@cdm.com<br />
Conclusions<br />
Conclusions<br />Importing data from DFIRM Tools is a simple process, but requires quality control measures for minor adju...
Upcoming SlideShare
Loading in...5
×

Flood Map Desktop Case Studies - AWRA 2010

893

Published on

Flood Map Desktop for ArcGIS 9.3 is an ESRI software extension to create FEMA flood hazard maps, databases, metadata, LOMRs, and profiles. This presentation presents 4 case studies in different uses of the software for different projects and client applications.

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
893
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
0
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Data types and storage are simple.
  • On each panel, tools to export and import the GRF file type which reconciles with the ELM database in the workflow.
  • Project easily ported to another location with tools to establish data connections.
  • Transcript of "Flood Map Desktop Case Studies - AWRA 2010"

    1. 1. Flood Map Desktop™<br />Case Studies<br />
    2. 2. Background<br />FEMA’s DFIRM Tools will be decommissioned July 31, 2010.<br />Several FEMA Lunch & Learn sessions hosted to guide users.<br />Alternatives to DFIRM Tools are needed to produce flood hazard mapping for FEMA.<br />FMD is a tool available as a DFIRM Tools replacement.<br />
    3. 3. Premise<br />Many AWRA members engaged in FEMA flood mapping projects<br />To date, many users have transferred FEMA projects from DFIRM Tools to FMD<br />Review a few use cases highlighting user experiences transferring between the systems and creating new products for FEMA<br />
    4. 4. transfer data from DFIRM Tools to FMD<br />Case Study #1 – Sherburne, MN<br />
    5. 5. Case Study #1 - Sherburne, MN<br />42 Printed FEMA Maps<br />312 Cross Sections<br />3 detailed streams<br />7,375 Transportation Features<br />Provided with an ESRI personal geodatabase containing all spatial layers, non-spatial tables, annotation feature classes <br />
    6. 6. Case Study #1 - Sherburne, MN<br />
    7. 7. Case Study #1 - Sherburne, MN<br />Font Transfer<br />Issue: FMD contains FEMA symbology, but DFIRM Tools system dependent on custom MapText fonts for features such as cross sections and road shields<br />Solution: Download MapText fonts from FEMA’s MIP website and load into local PC c:windowsfonts. Resolves all symbol and font transfer issues from DFIRM Tools.<br />
    8. 8. Case Study #1 - Sherburne, MN<br />Example of with and without MapText font results<br />
    9. 9. Case Study #1 - Sherburne, MN<br />Example of with and without MapText font results<br />
    10. 10. Case Study #1 - Sherburne, MN<br />Import DFIRM Tools data to multi-user format<br />Issue: After data import, user wants to retain multi-user cartographic production in a personal geodatabase<br />Solution: DFIRM Tools annotation layers imported to a FMD ELM annotation database type.<br />
    11. 11. Case Study #1 - Sherburne, MN<br />ELM<br />Disconnected multi-user cartography<br />Connected multi-user cartography<br />
    12. 12. Case Study #1 - Sherburne, MN<br />
    13. 13. Case Study #1 - Sherburne, MN<br />Import DFIRM Tools data to FMD<br />Issue: Data transfer is large – “out of memory” errors generated for many computers.<br />Solution: Data imported to personal geodatabase in two stages:<br />Spatial and Non-Spatial FEMA layers<br />Annotation Feature Classes.<br />Solution: Compact final database.<br />
    14. 14. Case Study #1 - Sherburne, MN<br />
    15. 15. Case Study #1 - Sherburne, MN<br />Data transfer quality control<br />Issue: Transferring data from one system to another can introduce error from: tolerances, topology rules, user errors, and other database settings.<br />Solution: Discover and solve errors with database queries, topology rules, and error reports.<br />
    16. 16. Case Study #1 - Sherburne, MN<br />
    17. 17. Case Study #1 - Sherburne, MN<br />Error discovery results:<br />6 layers containing significant topology errors<br />Violating 21 topology rules<br />49,720 total topology errors discovered<br />54,542 total database errors discovered<br />
    18. 18. Case Study #1 - Sherburne, MN<br />Final Steps: Review Cartography & MIP Upload<br />Some minor issues discovered in cartographic placement as result of system transfer. Manually review time approximately 5 minutes per FEMA map, total of 3.5 hours for this case.<br />MIP upload produced no errors.<br />
    19. 19. Case Study #1 - Sherburne, MN<br />
    20. 20. Case Study #1 - Sherburne, MN<br />
    21. 21. Case Study #1 - Sherburne, MN<br />
    22. 22. distributed processing using non-enterprise tools<br />Case Study #2 – Marion, IN<br />
    23. 23. Case Study #2 – Marion, IN<br />Highly urbanized area - contains the City of Indianapolis<br />97 Printed panels<br />914 Lettered Cross Sections<br />47 detailed streams<br />26,000 transportation features<br />26 LOMRs to be incorporated<br />Less than 1 month from start of panel production to QR3 submission<br />
    24. 24. Case Study #2 – Marion, IN<br />Data Edits<br />Cartography w/ ELM file type<br />Reconcile GRF into ELM<br />Final Export and FEMA MIP Delivery<br />QA<br />Loc #1<br />Data Copy<br />Cartography w/ GRF file type<br />Loc #2<br />
    25. 25. Case Study #2 – Marion, IN<br />Custom Workflow Explained<br />Non-enterprise system desired<br />Very fast client deadline<br />Multi-location, multi-user functions desired<br />Internet/WAN connection speeds inadequate<br />
    26. 26. Case Study #2 – Marion, IN<br />ELM & GRF file types<br />ELM: Element database. MS Access based w/out MS locks, multi-user ability for cartographic elements, data stored as blob type.<br />GRF: Exported Graphics File. Integrated with ELM data type. Exported from project, imported to ELM.<br />The files work in concert to facilitate a cartographic workflow.<br />
    27. 27. Case Study #2 – Marion, IN<br />MS Access personal geodatabase is locked to multi-user editing.<br />ELM element database for cartographics is not locked .<br />
    28. 28. Case Study #2 – Marion, IN<br />
    29. 29. Case Study #2 – Marion, IN<br />
    30. 30. Case Study #2 – Marion, IN<br />Conclusions<br />Low IT investment v. enterprise system<br />effective method for multi-user multi-location processing<br />Custom workflow must be created per-project, documented, and distributed to project team<br />Processing speed is very fast to meet tight client deadlines<br />Assign data manager (and a back-up) – similar to DBA<br />Consider multi-location access to data instead of copies if technologically/financially feasible<br />Can be some cartographic overlaps – QA process resolves.<br />
    31. 31. distributed processing using enterprise tools<br />Case Study #3 – Recreation of ArcSDE environment<br />Case study slides provided by CDM<br />Contact Mike Schultz or Gaston Cabanilla for further info<br />
    32. 32. Case Study #3 – Recreation of ArcSDE environment<br />User desired to re-create ArcSDE experience w/out DFIRM Tools<br />Multi-user data editing<br />Single datastore w/ multiple users and locations<br />Higher degree of workflow standardization<br />Centralized quality control<br />Case study slides provided by CDM<br />Contact Mike Schultz or Gaston Cabanilla for further info<br />
    33. 33. Case Study #3 – Recreation of ArcSDE environment<br />Issue: labor intensive creation of schema to extensive FEMA database specifications.<br />Solution: FMD schema imported with ArcCatalog<br />Case study slides provided by CDM<br />Contact Mike Schultz or Gaston Cabanilla for further info<br />
    34. 34. Issue: Custom workflow used for production<br />Solution: Self-customization of the imported schema.<br />Case Study #3 – Recreation of ArcSDE environment<br /><ul><li>Alteration of schema does not interfere with FMD functions.
    35. 35. In this example, we added the “Supplemental” feature dataset to meet custom data management procedures. </li></ul>Case study slides provided by CDM<br />Contact Mike Schultz or Gaston Cabanilla for further info<br />
    36. 36. Case Study #3 – Recreation of ArcSDE environment<br /><ul><li>Issue: Efficiency and slow data editing speeds
    37. 37. Solution: WAN connections too slow for production but LAN connections had minimal speed loss</li></ul>Disconnected databases offer an excellent solution. Data may be shared between offices without losing SDE identity. This allows data to be “checked in” and conflicts will be detected.<br />Case study slides provided by CDM<br />Contact Mike Schultz or Gaston Cabanilla for further info<br />
    38. 38. Case Study #3 – Recreation of ArcSDE environment<br />Conclusions<br />Centrally stored database<br />Tightly managed workflow<br />Increased QC efficiency as all edits are posted to a single database <br />Customized to our process, not someone else’s process to maximize our production efficiency<br />Disconnected editing, while an effective solution, requires additional coordination efforts<br />Case study slides provided by CDM<br />Contact Mike Schultz or Gaston Cabanilla for further info<br />
    39. 39. extend FMD tools to include user-specific needs<br />Case Study #4 – Extend FMD Tools<br />Case study slides provided by CDM<br />Contact Mike Schultz or Gaston Cabanilla for further info<br />
    40. 40. Case Study #4 – Custom Tools<br />Issue: High-volume producer for FEMA needs rapid software change and custom tools<br />FEMA replaces old QA/QC Pro database validation tool with the DVT.<br />The DVT introduces new requirements, some of which are not contained in the existing FMD export tool. <br />FEMA is not allowing exceptions for legacy data and is resistant to extending deadlines<br />Mapping partners need to get creative<br />Case study slides provided by CDM<br />Contact Mike Schultz or Gaston Cabanilla for further info<br />
    41. 41. Case Study #4 – Custom Tools<br />Solution<br />Our developers design a stand alone ArcGIS Toolbar which pulls data from the FMD ArcSDE database, automatically reformats and exports to the required submittal formats<br />Process is kept simple and effective<br />Connect to database<br />Render (optional)<br />Add layers<br />Export<br />Case study slides provided by CDM<br />Contact Mike Schultz or Gaston Cabanilla for further info<br />
    42. 42. Case Study #4 – Custom Tools<br />Solution<br />Export selected files – no need to re-export entire database for a correction in one file<br />Export to Basemap, Floodplain and Final DFIRM deliverables<br />Export shapefiles only for DVT test run<br />Case study slides provided by CDM<br />Contact Mike Schultz or Gaston Cabanilla for further info<br />
    43. 43. Case Study #4 – Custom Tools<br />Conclusions<br />Simple interface written in VBA using existing ArcGIS capabilities<br />Highly effective – first round DVT pass rate is nearly100%<br />Does not interfere with FMD functions<br />Development costs have been recovered many times over. <br />Case study slides provided by CDM<br />Contact Mike Schultz or Gaston Cabanilla for further info<br />
    44. 44. CDM Contact Info<br />Mike Schultz, GISP, CFM – schultzmd@cdm.com<br />Gaston Cabanilla, PE, CFM – cabanillaga@cdm.com<br />
    45. 45. Conclusions<br />
    46. 46. Conclusions<br />Importing data from DFIRM Tools is a simple process, but requires quality control measures for minor adjustments post-import.<br />Multi-user multi-location project processing is possible, fast, and inexpensive, but custom workflows and a cohesive team are required.<br />ArcSDE schema and custom tool development for organizational change improves unique processes and no FMD interference.<br />
    47. 47. Contact<br />floodmapdesktop@pbsj.com<br />www.floodmapdesktop.com<br />Free downloads, forum, product information<br />Twitter: @floodmapdesktop<br />Facebook: Flood Map Desktop<br />Joshua Price, PBS&J<br />303.221.7275, jpprice@pbsj.com<br />
    48. 48. www.floodmapdesktop.com<br />Questions.<br />

    ×