Avagene Moore: On behalf of Amy and myself, welcome to the EIIP Virtual Forum! Today we will be discussing Standardizing Map Symbols: An Initiative to Improve Communication. Avagene Moore: We all have ideas on standards in various areas of the disaster business. Today we will see that definite work has been done and more is underway. Avagene Moore: Before we introduce our speaker, we will go over the order of business. We will begin today's session with a presentation, and then we will proceed to your questions. Avagene Moore: We will provide further instructions just before we begin the Q&A section, but you may wish to jot down your questions or comments as we go along. Avagene Moore: Please do not send private messages to our speakers or the moderator, as we will be busy with the presentation. If you need assistance, you may send a private message to Amy Sebring, my partner in EIIP work. Avagene Moore: Please note our speaker will be using a few URLs in his presentation. When you see a blue hyperlink such as http://www.emforum.org , click on the link and the page will come up in your browser. Look at it briefly and then come back to the chat screen. Avagene Moore: The first time, your chat screen may disappear from your desktop. You will find it at the bottom of your screen, click on it and you will be back in the action and discussion. Avagene Moore: The transcript of today's session will be available by this evening -- just check back on our home page. Avagene Moore: It is a pleasure to introduce today's speaker, Scott McAfee. I heard Scott speak in a meeting in Baton Rouge last spring and decided then that we needed him in the EIIP Virtual Forum. Avagene Moore: Scott is the Gis coordinator for the DHS/FEMA Mitigation Division. He helps develop policy and coordinate the geospatial information aspects of a number of FEMA activities and programs, .... Avagene Moore: including HazardMaps.gov; Emergency Management Map Symbology; HAZUS; and Multihazard Flood Map Modernization. Please see the background page after the session for more details and related links. Avagene Moore: Welcome Scott, and thank you for joining us today. I now turn the floor over to you to start us off, please. Scott McAfee: Thanks Ava, and hello and welcome to all! Scott McAfee: Before I give the background to this project I'd like to officially announce that the symbols themselves are available for review. This review is not an official step in an accredited standards process, but more to give us some feedback from the user community. Scott McAfee: I'll give you the website URL now, but before you all run off to that website to check it out, I should mention that it will take some time to digest, so you might just take a quick look at the different sections. Scott McAfee: To get to the different sections, click on the boxes in the header, such as "Incidents Evaluation." Scott McAfee: Note: I don't know what the server's capacity is. If it is too slow or crashes with everyone going there at once, we have backup slides. Scott McAfee: I'll give you a couple of minutes to explore The website, http://www.fgdc.gov/HSWG Scott McAfee: Slowed down a little bit, but worked for me! Scott McAfee: I wish I could look out and see your faces, but I guess I'll just have to assume that you're all smiling and glued to your monitors in anticipation of hearing about "standardized map symbols for emergency management." Scott McAfee: It's certainly a topic that has interested me. The seed for this initiative was planted back when I worked for the California Office of Emergency Services and responded to a number of disaster incidents. Scott McAfee: Then, as now, it was typically up to the GIS analysts to choose which symbols from a limited symbol set to use for planning, preparedness, response, and recovery maps. Scott McAfee: At the incident level, at least you had a (limited) standard set of Incident Command System (ICS) symbols to choose from, but many of those symbols weren't part of the standard GIS programs. Some extensions and customized applications did incorporate them, though. Scott McAfee: For the mapmakers to pick the symbols on the fly causes a few problems. First, it's a waste of time to have to be creative in a disaster situation. Scott McAfee: Picking symbols means you have to think like the end-user of the map, choose a simple symbol that communicates as much as possible, and avoid symbols that might be in poor taste. Scott McAfee: Then you have to think about color, size, transparency, labels. . .don't get me started about labels. Scott McAfee: Second, you typically have to choose this symbol from a number of true-type font sets that usually are limited to a particular area of interest. Say you were an emergency manager that needed to map how landslides affected power generation facilities. Scott McAfee: The symbol for these facilities in the UTILITY symbol set might make complete sense to utility employees, but be completely unintuitive to emergency managers. Scott McAfee: So I chatted with other emergency managers about how nice it would be to have a comprehensive, standardized set of symbols for the emergency management map maker to choose from. Scott McAfee: This was a difficult project to undertake from a state agency, but when I took a job with FEMA a few years ago, I had the opportunity to foster the development of such a standard from a national perspective. Scott McAfee: Through our contract with Michael Baker Jr. Corporation, FEMA's Mitigation Divison requested a draft report that identified existing symbols and suggested ideal symbols. Scott McAfee: The report was done (under subcontract from Michael Baker) by Dr. Ute Dymon of Kent State University. It was important to me that a specialist in cartography was involved in the analysis, so I was confident in the approach. Scott McAfee: I'd also like to note that Jeff Booth of Michael Baker has done a great job coordinating and supporting this initiative as the project manager. Scott McAfee: After the September 11 attacks, a Homeland Security Working Group (HSWG) was formed by the Federal Geographic Data Committee. This group looked at a draft report put together by Dr. Dymon, and thought it would be an appropriate standard to pursue. Scott McAfee: At that point, my involvement in the initiative became a smaller part of a much larger, well-coordinated effort. Scott McAfee: The HSWG decided this was an important enough effort to form a subgroup devoted to the development of these symbols. This subgroup has worked very hard and been very productive. The subgroup decided to pursue this initiative on three tracks: Scott McAfee: 1) Develop graphical symbols to represent various features of Natural Events, Operations, Infrastructures, and Damage or Operational Status; Scott McAfee: 2) Guide the symbols through an accredited standards process, such as FGDC, ANSI, ISO, etc; and Scott McAfee: 3) Explore the interoperability of emergency map symbology. Scott McAfee: I will address these one-by-one. Scott McAfee: First off: Graphics Scott McAfee: The graphic symbols that Ute Dymon of Kent State had drafted have gone through a number of iterations. The following link breaks down the hierarchy of how the symbols are categorized. Scott McAfee: http://www.emforum.org/vforum/symbols.htm Scott McAfee: So, there are categories, themes within the categories, and features within the themes. Each get symbols. We could have done more than three tiers, but decided for the sake of sanity to cut off there. Scott McAfee: Any additional information can be captured as attributes of the feature, at the users discretion. Those attributes can then be applied as labels, for example. Scott McAfee: The Symbology Subgroup was very active in vetting all of the symbols, and cartographers at the Census Bureau, with support from University of Maryland, Baltimore Campus, did a fabulous job of interpreting the subgroup's ideas and graphically improving upon the original symbols. Scott McAfee: The next link shows ways in which an individual symbol can be put in a frame to show the status of that symbol in terms of damage to the facility or at what level it is functioning. Scott McAfee: Oops. Don't have that link. I'll show it later. Amy Sebring: I have the slide Scott. Scott McAfee: http://www.fgdc.gov/HSWG/#startDamage_Operational Amy Sebring: (scroll down slightly) Scott McAfee: Using this method, for example, we might show a power generation facility as non-operational by putting the level four frame around the power generation facility symbol. Scott McAfee: At this point I should note that the website was designed by the Bureau of Census, and hosted by the FGDC. Comments provided through the site will be analyzed by Ute Dymon of Kent State University, and those comments will be taken into consideration and the symbols revised as necessary. Scott McAfee: Census did the graphics, as well. Scott McAfee: We've always figured that there needs to be a review of the symbols by emergency managers and first responders at the state and local levels, and this site is the manifestation of that requirement. There will likely be another chance to review the symbols as part of the official standardization process. Scott McAfee: Our period for review of the symbols through this website is December 8th 2003 through January 31st 2004. Scott McAfee: For outreach, we will be notifying a number of organizations such as the National Emergency Managers Association, the International Association of Emergency Managers, the Open GIS Consortium, and others. If you have ideas for other groups, please forward them to me at my e-mail address: scott.mcafee@dhs.gov . Scott McAfee: Here is an example of these symbols on a map that the state of Maryland put together: http://www.fgdc.gov/HSWG/eval_maps/AnnapolisPhotoMap01.jpg Scott McAfee: Next Section: Choosing a Standards Process Scott McAfee: This has been a difficult part of the process, since there are so many paths to choose from. Choices include FGDC, ANSI, ISO, Industry, and variations and combinations of these. Scott McAfee: We are still evaluating what to do here, but one of the most promising avenues is to bring this standard through ANSI by way of an existing U.S. Army Corps of Engineers sponsored standard known as "Spatial Data Standards for Facilities, Infrastructure, and Environment." Scott McAfee: Among other advantages, SDSFIE is FGDC and ANSI INCITS L1 compliant. It also has an annual update process that might facilitate incorporation of the symbols. Scott McAfee: Final Section: Interoperability Scott McAfee: Let's use my previous example and say that you're a utility worker sent to work a disaster. The emergency management symbol for the feature: "power generation station" is not one that you're familiar with being used in the industry. Scott McAfee: Is there a way to generate different symbols for such a feature based on the symbol that a person might be used to? Scott McAfee: It would take a system of internet registries, catalogs, style descriptions, graphic descriptions, and standard, cross discipline, feature definitions. Scott McAfee: The Open GIS Consortium is undertaking a project known as Emergency Mapping Symbology (EMS) that will explore this issue. Scott McAfee: The goals of the project are to mature a number of specifications of the Open GIS Consortium and explore their application for two symbol sets: Those of this FGDC group as well as the set from a Department of Defense application known as Geospatial Symbols for Digital Display (Geosym). Scott McAfee: FEMA is co-sponsoring this project with the National Geospatial- Intelligence Agency (NGA, formerly NIMA). Scott McAfee: A Request for Quotations and Call for Participation are available for this initiative from http://www.opengis.org , with the deadline of December 16th. Scott McAfee: Forgot to credit the other agencies and organizations that are involved. I believe they are on the background page. Scott McAfee: That's all I have for the presentation portion of today's activities. I'm now available to answer any questions you'd like to post! I turn the floor back to our Moderator. Avagene Moore: Thank you very much, Scott. Our protocol for audience questions is to enter a question mark ? to indicate you wish to ask a question or make a comment. ... Avagene Moore: Then go ahead and compose your question or comment to have it ready, but do NOT hit your Enter key or click on the Send button until you are recognized by name. Please WAIT your turn. ... Avagene Moore: We will take questions in the order the question marks are sent to the screen. One question at at time please. If you have a follow up, please get back on line with a ? ... Avagene Moore: There is a system limitation on length of one entry, so if necessary, you may need to break your question into parts. We are ready to begin now. Avagene Moore: Input your ? mark at any time. Jason Moats: ? Avagene Moore: Jason, please compose your question and send it to the screen when ready. Jason Moats: Can we get these symbols to use currently? Joanna Grossman: ? Scott McAfee: Good question. We haven't yet discussed when to officially release the symbols . . . Scott McAfee: It at least won't be until we've gone through this review process to see what the community thinks. . . Scott McAfee: We don't want people to adopt the symbols only to have them change significantly. Jason Moats: ? addition to the first Avagene Moore: Joanne Grossman, please. Rodney Rogers: ? Joanna Grossman: Often symbols have to be small. These are so detailed, I'm worried the wouldn't be legible. Mike Morrow: ? Scott McAfee: Great point, Joanna. . . Scott McAfee: A lot of emergency maps use shape symbols such as circles or squares . . . Scott McAfee: If your maps are too small for the symbols to be legible, just use the shape of the category. . . Scott McAfee: That way at least you'll know whether it's an incident, infrastructure, etc. . . Scott McAfee: And you can label it how you wish. Avagene Moore: Jason, you have another question - please input. Jason Moats: I have the possible availability of a test bed to get some real application evaluation. If I could get them to use in a training project, we'll put them throught the paces. Jason Moats: Is the project open for something like this? Scott McAfee: Jason, go ahead and send me an e-mail and we can discuss. Jason Moats: will do Avagene Moore: Rodney, your turn, please. Rodney Rogers: City of Portland, OR officials have determined a major earthquake will seperate the region into 5 area, knocking out all bridges. Will symblols indicate vulnerable stuctures such as these? Avagene Moore: (Input your ? if you have a question for Scott.) Ingrid Aldridge: ? Scott McAfee: The context of your map will be the important part of that communication, I suspect. You can use the symbols for any purpose, and indicate levels of vulnerability as you like. Avagene Moore: Mike Morrow, next. Mike Morrow: What are your plans, if any, for standardization of lines and polygons to represent things like evacuation areas? Scott McAfee: I knew someone would ask that, Mike . . . Scott McAfee: We really wanted to keep it simple, so we steadfastly stuck to point symbols . . . Scott McAfee: If we are successful with points, and have funding to continue, we will do lines, polygons, and symbols for other communities of homeland security. Avagene Moore: Ingrid, your question, please. Ingrid Aldridge: What timeline are you looking at for finishing the project to the point where you will have the symbols available? Amy Sebring: ? Avagene Moore: (We need more questions, folks. Input a ? if you have a question or comment for Scott.) Ingrid Aldridge: ? Scott McAfee: I suspect the symbols won't be officially available until they are an official standard. . . Scott McAfee: This might take some time, and the Working Group might have to discuss how we handle unofficial releases of the symbols. Avagene Moore: Amy, your turn, please. Amy Sebring: Scott, have you considered changing the background colors as opposed to changing frames to indicate levels? I would think that might show up better? Avagene Moore: ? Scott McAfee: Kaile, want to take that one? Kaile is from Census, and handled the graphics. Joe Sukaskas: ? Kaile Bower: Sure... Kaile Bower: We decided on using color only in the frames in order to facilitate the use of the symbology... Kaile Bower: in both color and black and white. Because the frames have both a texture and a color they work in both realms. Avagene Moore: Ingrid, please. Ingrid Aldridge: What format will the symbols be in? Useful for multiple GIS software? Scott McAfee: Kaile can correct me if I'm wrong . . . Scott McAfee: But I think they're in CGM now, and we plan to do True Type fonts and SVG. Avagene Moore: Kaile, any additional comment? Scott McAfee: Also. . . Kaile Bower: We will also be providing symbol sets in a couple of popular GIS software package formats. Scott McAfee: We're hopeing that the GIS vendors will step up and incorporate the symbols into their applications. Avagene Moore: Scott, have you fielded the symbols with any user groups yet, even on a limited basis? If so, what type of reactions are you getting? Scott McAfee: Kaile can again help on this . . . Avagene Moore: (We have time for a few more questions - input your ? now.) Scott McAfee: We had a limited pilot in Maryland and Los Angeles last month to test the website. Scott McAfee: The LA folks were busy with fires, of course . . . Kaile Bower: In our initial sniff test we had a total of 49 responses that were overwhelmingly positive. Scott McAfee: That covers it. Jim McConnell: ? Avagene Moore: Great! Jim, your question, please. Jim McConnell: might a concurrent project be standarized abbeviations since labels may always be needed? Scott McAfee: We have a catchall category for attributes. . . Scott McAfee: You can use any attributes you wish, including abbreviations . . . Scott McAfee: A larger question you might be leading to is standardizing a data structure for these symbols Avagene Moore: I overlooked Joe Sukaskas. Joe, please ask your question now. Joe Sukaskas: Some of the symbols are defined as Themes, others as types of Features -- Are the features simply subsets of themes, or are there other reasons or applications for the differentiation? Scott McAfee: Which may happen in the future. Question answered? Scott McAfee: Good question, Joe. . . Amy Sebring: ? Chuck Zechman: ? Scott McAfee: Features are substes of themes, but you can use a generic theme symbol if you like . . . Scott McAfee: Themes are contained in categories. Avagene Moore: Amy, please. Amy Sebring: Scott, are you aware of any fora specifically for folks interested in GIS for emergency management, either formal or informal? Such as a mailing list? Amy Sebring: If not, do you think it would be useful? Scott McAfee: None that I'm aware of. . . Scott McAfee: There are usually Tracks at GIS conferences devoted to Emergency Management (or Homeland Security) Scott McAfee: So a forum would probably be popular. Avagene Moore: Chuck, your question, sir. Chuck Zechman: Are there plans to track incidents using maps & symbles real time on regional, state, and national level? Avagene Moore: (Other questions? Please input your ? now.) Lauren McLane: Some areas do have these GIS in EM groups. Try contacting your GIS Coordinator at the FEMA Regions - Scott can probably help with that Scott McAfee: I think that's a good question for our audience. Anyone doing that (thanks Lauren)? Lauren McLane: We are in New England - informally (Sorry to jump in late) Rodney Rogers: ? Scott McAfee: I think that's the ultimate goal that's in every GIS savvy emergency managers mind. Isabel McCurdy: ? Scott McAfee: And I think the interoperability piece will be helpful for the future success of that. Avagene Moore: Anything else on Chuck's question, Scott, before we go on to the next question? Johanna Meyer: ? Bob Bilder: ? Scott McAfee: Nope. Avagene Moore: Rodney, please. Rodney Rogers: More & more of our Red Cross volunteers are using GIS to find accommodations for displaced clients in the field. We are currently installing satilite networking for communcation. Scott McAfee: I will say that Lauren is with our FEMA Region 1 office in New England. Thanks Rodney! Avagene Moore: Isabel, please. Isabel McCurdy: Will these standard GIS symbols transcend over to signage internationally? Scott McAfee: We've talked about ISO for an international standard . . . Scott McAfee: But feel we really need to focus on the US first. We can evolve to ISO later . . . Scott McAfee: As far as signs, Kaile can tell you that signs work different from map symbols. . . Scott McAfee: The DOT Hazmat placards don't work well as map symbols, for example. Scott McAfee: But maybe? Scott McAfee: (done.) Avagene Moore: Johanna, you are next, please. Johanna Meyer: Is there going to be symbology for (MEDS) building foot prints or will point symbols be the standard? Scott McAfee: You mean the HSIP features? Johanna Meyer: yes Scott McAfee: Great question. Scott McAfee: One of the advantages of using the SDSFIE standard . . . Scott McAfee: Is that there is some exploration of incorporation of HSIP into SDSFIE. . . Scott McAfee: So harmonizing the HSIP features with the symbol features would be made easier (but not easy). Avagene Moore: Bob, please. (Time for one more question after this one - now is your chance to ask your question.) Bob Bilder: I don t see map symbols for biological issues like amount or types of populations (animals, people) affected, disease types or a way to track the density of the ill in a biological outbreak. Scott McAfee: Good point, Bob. . . Scott McAfee: Please visit the website, give the symbols your review, and put those comments in at the end. They will be considered. Kaile Bower: Scott, if I may, I see these things coming into play when we get o areal features. Since you can't have density without area. Scott McAfee: Right, Good point Kaile. Avagene Moore: That's all we have time for today. Thank you very much, Scott. Excellent presentation and very good information. Please stand by a moment while we make some quick announcements .... Scott McAfee: Thanks for having me. Avagene Moore: If you are not currently on our mailing list, and would like to get program announcements and notices of transcript availability, please see the Subscribe link on our home page. Avagene Moore: Again, the transcript will be posted later this afternoon and you will be able to access it from our home page. Avagene Moore: If your organization is interested in becoming an EIIP Partner, please see the Partnership link on our home page. Avagene Moore: Thanks to everyone for participating today. Our session is adjourned but before you go, please help me show our appreciation to our speaker, Scott McAfee, for a fine job. Avagene Moore: Yes, thanks to Kaile and Lauren for being here and adding to the discussion. Kaile Bower: Thank you. I look forward to seeing all the responses to the evaluation!