FFMP Basin Customization Webinar #1 Stream Name Verification and Editing & Introduction to the Customization Repository Thursday, November 5, :00 PM – 3:30 PM EST

Agenda  Review of three-tiered FFMPA shapefile processing  Review of how stream names were originally included in the FFMP datasets  Stream name verification and editing Stream name data sourcesStream name data sources DEMO - example procedureDEMO - example procedure  Introduction to the Basin Customization Repository DEMO – navigating the repository websiteDEMO – navigating the repository website Submitting customized filesSubmitting customized files  Wrap-up/Q&A

**Reminder about access to the repository websites**  Access to the FFMP Basin Repository and the FFMP Basin Customization Repository is restricted by IP address.  You can still access these sites from the same IP address you used during the Tier I processing.  If you need to access these sites from a new IP address, please send it to:  Original basin repository:  Customization repository:

Three-Tiered FFMPA Shapefile Processing  Tier I (completed) All WFOs completed this prior to OB8.3 All WFOs completed this prior to OB8.3 Involved download and basic processing of shapefilesInvolved download and basic processing of shapefiles Completed for your FFMPA domain (your CWA plus the CWA(s) for which you have flash flood backup responsibility, plus a 25-km buffer)Completed for your FFMPA domain (your CWA plus the CWA(s) for which you have flash flood backup responsibility, plus a 25-km buffer) The result of Tier I processing was an AWIPS/FFMPA-ready set of basin and stream shapefiles The result of Tier I processing was an AWIPS/FFMPA-ready set of basin and stream shapefiles  Tier II (the topic for today’s webinar) This tier is OPTIONAL This tier is OPTIONAL Must be completed if you plan to use the basin names in WarnGenMust be completed if you plan to use the basin names in WarnGen Involves verifying and adding stream names to the post-processed shapefiles resulting from Tier I Involves verifying and adding stream names to the post-processed shapefiles resulting from Tier I Stream names should be modified only for basins within your CWA Stream names should be modified only for basins within your CWA The customized shapefile should be submitted for inclusion in the Basin Customization Repository The customized shapefile should be submitted for inclusion in the Basin Customization Repository  Tier III (will be covered in subsequent webinars) This Tier is OPTIONAL This Tier is OPTIONAL Involves more extensive customization tasks such as editing basin boundaries, subdividing basins, clipping out lakes, etc. Involves more extensive customization tasks such as editing basin boundaries, subdividing basins, clipping out lakes, etc. Tier III customization should only be done for basins within your CWA Tier III customization should only be done for basins within your CWA The customized shapefile should be submitted for inclusion in the Basin Customization Repository The customized shapefile should be submitted for inclusion in the Basin Customization Repository

Why Verify/Edit Stream Names?  Provides additional information for FFMP users  Optional inclusion of basin names in WarnGen Currently MANY names included Currently MANY names included Working to develop a solution to make this functionality more usable Working to develop a solution to make this functionality more usable  Can be used for communicating site specific information to emergency managers

Original Stream Name Assignment Stream names were assigned from the NHD reach files. Stream names were assigned from the NHD reach files. Names were assigned based on the most prevalent name within a basin (based on stream length). Names were assigned based on the most prevalent name within a basin (based on stream length). Thus, the name assigned may not be the name of the main stem. Thus, the name assigned may not be the name of the main stem. ***Important***: These names are a starting point--they MUST be checked for accuracy and changes/additions should be made as necessary. There may be more than one NHD reach corresponding to each DEM-derived stream reach. Not all NHD reaches are named (red reaches show those with names).

Stream Name After Aggregation Cedar Creek Little Bear tributary Aggregated basin name: Cedar Creek (should be Cedar Creek w/ Little Bear trib) During automated aggregation, the aggregated basin was attributed with the main stem stream segment name.

Stream Name Verification & Editing Tips:  Only need to work on basins/streams in your CWA (not backups) NOTE: No need to separate out your CWA though (better for FFMPA toolbox scripts if you do not) NOTE: No need to separate out your CWA though (better for FFMPA toolbox scripts if you do not) Neighboring WFOs can share verified names via the Basin Customization Repository Neighboring WFOs can share verified names via the Basin Customization Repository  FFMP shows the names that are included in the FFMP_aggr_basins shapefile Recommend verifying names in both the FFMP_aggr_basins and FFMP_ref_sl shapefiles Recommend verifying names in both the FFMP_aggr_basins and FFMP_ref_sl shapefiles

Stream Name Verification & Editing Tips (continued):  Strive for consistency Before you begin, decide on rules for your naming convention and abbreviations Before you begin, decide on rules for your naming convention and abbreviations Example: Bear Creek / Bear Cr / Bear creek / BearCreek  Tedious process Bite off small chunks at a time Bite off small chunks at a time Student/intern help Student/intern help

Data Sources  There are MANY GIS data sources that may be useful for name verification and editing  Today we will discuss two that can be used together easily for simple verification of many stream names ArcGIS Online Standard Map Service ArcGIS Online Standard Map Service Geographic Names Information System (GNIS) Geographic Names Information System (GNIS)  Please use other sources as well!! Stream Name Verification & Editing

 ArcGIS Online Standard Map Service Base maps and reference maps available at no cost for internal use and noncommercial external use.Base maps and reference maps available at no cost for internal use and noncommercial external use. Satellite and aerial imagery, topographic maps, street maps, shaded relief, boundaries/places, transportation, elevation Satellite and aerial imagery, topographic maps, street maps, shaded relief, boundaries/places, transportation, elevation Can be used with ArcGIS 9.2, 9.3, and 9.3.1Can be used with ArcGIS 9.2, 9.3, and NOTE: Use of Premium Map Services requires purchase of an annual subscription.NOTE: Use of Premium Map Services requires purchase of an annual subscription. Two ways to download:Two ways to download: Ready-to-use basemap (.mxd file to open in ArcGIS) Ready-to-use basemap (.mxd file to open in ArcGIS) View service (add.lyr file in ArcGIS) View service (add.lyr file in ArcGIS) Stream Name Verification & Editing

 Geographic Names Information System (GNIS) Developed by the USGS in cooperation with the U.S. Board on Geographic NamesDeveloped by the USGS in cooperation with the U.S. Board on Geographic Names Text files of federally recognized names for ~2 million physical and cultural geographic features in the U.S.Text files of federally recognized names for ~2 million physical and cultural geographic features in the U.S. Located by state, county, and geographic coordinates Located by state, county, and geographic coordinates Can be manipulated to a comma delimited format for import as point features in ArcView Can be manipulated to a comma delimited format for import as point features in ArcView Stream, Canal, Channel, and Swamp feature class points have been extracted for each state and are available via hyperlinks on the Basin Customization Repository websiteStream, Canal, Channel, and Swamp feature class points have been extracted for each state and are available via hyperlinks on the Basin Customization Repository website  DEMO – example procedure Stream Name Verification & Editing

 DEMO – navigating the repository website  Submitting customized files Make sure they are uniquely identifiable (zip file with your WFO ID)Make sure they are uniquely identifiable (zip file with your WFO ID) Upload to ftp://ftp.nssl.noaa.gov/incoming/aarthur/Upload to ftp://ftp.nssl.noaa.gov/incoming/aarthur/ftp://ftp.nssl.noaa.gov/incoming/aarthur/ Send me an to let me know you have uploaded them and what type of changes you have madeSend me an to let me know you have uploaded them and what type of changes you have made Metadata will be created for each submitted dataset to track versions and changes Metadata will be created for each submitted dataset to track versions and changes Introduction to the Basin Customization Repository

Wrap-up/Q&A Upcoming Webinars Thu 19 Nov - The Basin Customization Repository: How to Share Your Customization and Incorporate Your Neighbor's Customization Thu 3 Dec - Merging and Subdividing Basins and Manual Editing Thu 17 Dec - Clipping Lakes/Reservoirs and Wide River Polygons If you have any problems or questions, please contact me: Questions?