When your mission goes into multiple operational periods and/or starts to incorporate outside teams or agencies, things can get complicated.
CalTopo has integrated tools for managing large amounts of data, and there are best practices that have come through trial and error as we use the program and run missions. In this chapter, you’ll practice.
Topics on this Page:
Basic large mission management starts at the map level with good organization. Folders, labeling and data management all contribute to this. As the mission grows and outside organizations get involved, you use an Event to incorporate those additional resources. Finally, when the incident reaches the level of being enormous, you start using multiple maps for field ops versus planning operations. Each of these builds on the assumption that the previous was managed and executed well.
Good labeling, organization via folders, and map cleanliness are the three key tools to keeping your mission map under control.
The segment-assignment approach covered earlier will go a long way towards keeping your mission well organized. In the last chapter we covered using a folder for the tracks for each operational period, but folders can serve many purposes. Your range rings can go in a folder. Other folder ideas include one for any hazards, for clues that were exploited and determined to be not relevant, for landing zones, for ingress and egress routes, for important mission objects such as the ICP and the PLS, for notes and reminders, for things that still need to be organized, and more.
Different types of assignments get their own folders. Air ops assignments do not fit into the normal segmenting model, and usually overlay quite a few ground assignments. Separating these out of the assignments folder and putting them in their own folder is a good practice.
Air ops tracks also get their own folders. Air tracks will obliterate the usefulness of the map if you leave all of them turned on all the time or if they are overlaid with ground tracks. Furthermore for aircraft tracks, using bulk ops to make the lines narrower and change the color can help them be less intrusive.
Maps with large amounts of data operate slowly. Several tips here will help you work on these maps that may run into performance issues.
1. Folders Off: Make use of the feature that allows you to set folders to not display when you reload the page. It’s much easier to turn on folders to see data when you need it rather than to wait for the page to catch up to or to have to turn off a bunch of folders to find what you need.
2. Labels Off: In the settings menu, set labels to "by folder" then at the bottom of each folder, choose whether or not to display the labels for that folder. Fewer labels = better performance, and also easier to view critical map items.
3. Use Caution with Special Line Types: Use all the line colors and weights that you want, but switching to dashed lines or anything else leads to slower maps.
4. Watch your Layers: Stacking layers is a great tool for planning and analysis. However, leaving those layers stacked and panning the map around means that each of those layers needs to load, even if the opacity is set to 0%. Turn them off if you don't need them.
5. Computer and Browser Memory: Remember your computer only has so much memory, and your browser may only be allocated part of that. If you have 80 tabs open, that could affect how much memory you have for your map. If you're working with a really large map, empower your browser to have its best chance at working well for you, and close some of those other tabs and processes.
When your mission starts to involve mutual aid and searchers or others from outside your own team, with your team account you can scale up your team for a limited time to include additional users. There are three basic components to incorporating mutual aid users into your team account:
Events are a powerful way to quickly integrate other responding agencies into your team. This allows them to view premium layers and download offline base layers - a critical component of backcountry searching. They also gain the ability to share their location with you live, if a cell network is available.
All responders should have some level of access to the map. This improves situational awareness and adaptability while in the field. You may want to give most field-based responders update-only access to the map. This allows them to add markers and their tracks to the map, without letting them edit the objects any other user adds to the map. A. Create an event in your admin tool. B. Create a mission map. C. Move that map to your event folder. D. Set up your ICP in a place with cellular network service, OR, send information to responders before they arrive at the base. Some teams now have two ICPs - an initial one at a location that has cellular service and a second one at the final deployment site, such as a trailhead. This allows for everyone to get connected on the same map and thus have access to the relevant search data, assignments, and more. They can also get base maps downloaded to their device before heading into areas without service. If the callout is for the following operational period (next day), having team members get this data before they leave home is the best option.
Refer to the reference guides (demo images below) or the user guide page for events for full instructions for using CalTopo events.
Responders will need to download the app, join the event, and find their assignment. They may also need to download base layers for offline use. If responders are new to SARTopo, they will need some help to learn their way around the app and find their assignment and record a track.
Should they be recording a track directly to the map via the mobile app? Should they be sharing their location live? Should they have the shared locations overlay turned on so they can see where other searchers are located?
With the above steps, you’ll be able to connect multiple agencies to a single map or set of maps, and gather the data you need from them.
As your mission grows in size - whether geographically, from adding personnel, or a very long series of OP periods - you can consider using multiple copies of the map to help manage data. With this method, you maintain one primary map that contains the full data set of the mission. This primary map would only get updated occasionally with data that is clean and processed, so it becomes the record of the full mission. By using the “copy to a new map” function in the export menu, you can create a working map for each day that has the relevant set of information for that operational period.
Let’s consider a situation where we might use this technique, and look at how it would play out. Consider the case of a small plane that went down during a winter storm, and the resulting search requires a wide search area of hundreds of square miles and hundreds of ground searchers over many days. Searchers need to be able to access the mission map in their mobile app, and to record tracks to the map so we don’t have to download as many gps units later. If we give them access to the entire set of data for the search, their app could be overwhelmed by all the map objects.
The ground teams need to have a complete representation of the mission and the day's objectives, any important clues, and ingress and egress routes. They probably do not need to see the last 8 operational periods worth of tracks. By making a daily operational map, we give ground teams a map they can work with without being overwhelmed.
Teams can record to the OP map and not the primary mission map. Meanwhile, the plans team can be working on a map that does not have active tracks being recorded to it. At the end of the day, a mapping team can clean up the recorded tracks, trimming them, renaming them, and making sure the data is clean before moving it to the primary incident map.
Now that you’ve reached the end of the course, it’s time to revisit all the skills you’ve learned and practice applying them to a new operational period, OP 3, which we will scale up to a larger size. For this exercise, assume you are requesting 35 ground searchers, 3 dog teams, and other resources such as OHVs and a helicopter.
To complete the exercise, you will work through the whole series from drawing additional segments to importing and cleaning tracks:
You have now completed all the tasks in this course!
You can submit the link to your Wally Sinclair mission map via NASAR's online learning platform. Then we will review it and provide feedback and issue your certificate if your map meets the basic criteria! Please note that reviews could take up to 4 weeks, but we hope to get back to you within one week of submission.
You have put a lot of time and effort into your Wally Sinclair map at this point. Follow these tips to help be sure that you do not get a rejection email!
Large missions are complicated by nature. Don’t panic! Stay as organized as you can. Practice your systems before a mission so you know how you want to label segments, keep track of operation periods, and assign teams. Get everyone on the same map, even if that isn’t your final or full mission map. Record tracks, and communicate as much as you can to your ground teams.
Good maps require organization, and that starts with good labeling of map objects and folders for organizing them. From there, you can scale up as much as necessary to meet your needs.