Hey all, I'm a current wildland firefighter but all I do are prescribed fires here in Florida. In terms of getting ICs using OSM your best bet would be to get they guys who do fire every week to start using and contributing to OSM. They're usually the ones tapped for local and remote wildfires. They also have a ton of data for firelines, land cover, escape routes, and wetlands. I think you probably won't be able to get anyone to use OSM for incidents in the US until it's a lot better, but a better first step would be to get local governments to quit using their own data/proprietary programs to manage their roads, streetlights, and routing emergency vehicles and get a few to switch to OSM. That would make an IC much more likely to rely on OSM for a future wildfire, particularly if a local burn boss was already familiar with it.
Cheers, Val On Thu, 2016-06-30 at 14:58 +0000, talk-us-requ...@openstreetmap.org wrote: > Send Talk-us mailing list submissions to > talk-us@openstreetmap.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.openstreetmap.org/listinfo/talk-us > or, via email, send a message with subject or body 'help' to > talk-us-requ...@openstreetmap.org > > You can reach the person managing the list at > talk-us-ow...@openstreetmap.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Talk-us digest..." > > > Today's Topics: > > 1. WeeklyOSM 310 (Jinal Foflia) > 2. Re: What should we do for wildfires? (Josh Spencer) > 3. Re: What should we do for wildfires? (Russell Deffner) > 4. Re: Join us for another import party at the L.A. Times J > une > 25 (Michael Reichert) > > > ------------------------------------------------------------------- > --- > > Message: 1 > Date: Thu, 30 Jun 2016 19:11:32 +0530 > From: Jinal Foflia <fofliaji...@gmail.com> > To: OpenStreetMap talk-us list <talk-us@openstreetmap.org> > Subject: [Talk-us] WeeklyOSM 310 > Message-ID: > <CAC2+iy0BkvEzfiVRVCkrU3n3_B8fBiwsHETmNihzAjJikwY_FQ@mail.gmail > .com> > Content-Type: text/plain; charset="utf-8" > > The weekly round-up of OSM news, issue #310, is now available online > in > English, giving as always a summary of all things happening in the > OpenStreetMap world: > > http://www.weeklyosm.eu/archives/7765 > > Cheers, > > Jinal Foflia <https://twitter.com/fofliajinal> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20 > 160630/2fcc1058/attachment-0001.html> > > ------------------------------ > > Message: 2 > Date: Thu, 30 Jun 2016 12:24:35 +0000 > From: Josh Spencer <joshua.spen...@zurichna.com> > To: "talk-us@openstreetmap.org" <talk-us@openstreetmap.org> > Subject: Re: [Talk-us] What should we do for wildfires? > Message-ID: > <a14a67e217764dda8267892d7596e...@zursrvres785.zurmws.cscmws.co > M> > Content-Type: text/plain; charset="utf-8" > > I work for a large insurance company and stumbled upon open street > maps and their humanitarian mapping for some international > catastrophe events. Ironically, I've just switched email programs > and my mail rule didn't transfer, so I have been paying more > attention to this subscription. > > I've always been curious about this and have been trying to see how > all of this works. I used a lot of public data as we planned for > Fort McMurray response. Any sort of mapping that confirms damaged > buildings would be a great resource as every time something like this > happens, the information flow is different. I'm hoping that once I > figure out how the maps and updates work, I can share them with some > of the others I work with and contribute more. I've got a few other > industry contacts that would probably be up for the same as well. > > If anyone can send me the best place to get started on fully > understanding all of this, I would appreciate it. > > > Josh Spencer > > > > ******************* PLEASE NOTE ******************* > This message, along with any attachments, is for the designated > recipient(s) only and may contain privileged, proprietary, or > otherwise confidential information. If this message has reached you > in error, kindly destroy it without review and notify the sender > immediately. Any other use of such misdirected e-mail by you is > prohibited. Where allowed by local law, electronic communications > with Zurich and its affiliates, including e-mail and instant > messaging (including content), may be scanned for the purposes of > information security and assessment of internal compliance with > company policy. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20 > 160630/a630ad57/attachment-0001.html> > > ------------------------------ > > Message: 3 > Date: Thu, 30 Jun 2016 08:14:36 -0600 > From: "Russell Deffner" <russdeff...@gmail.com> > To: "'Jonathan Schleuss'" <jschle...@me.com>, > <talk-us@openstreetmap.org> > Subject: Re: [Talk-us] What should we do for wildfires? > Message-ID: <00d201d1d2d9$bc000870$34001950$@gmail.com> > Content-Type: text/plain; charset="utf-8" > > Hi all, > > > > I coordinated that Colorado Wildfire mapping effort in 2013. I am > also a HOT > voting member and volunteer coordinator for our Disaster Mapping > program. > Would be happy to talk directly with folks about this stuff. To try > and put > the key points in an email - it can be something HOT does, but as > with most > response efforts in the United States, Canada and Europe - those > response > agencies (such as the USFS) typically are not going to use > OpenStreetMap. I > had some minimal success talking with the Incident Command team for > the > Waldo Canyon fire in 2012 and that's what inspired my efforts in > 2013. > However, as Incident Command teams are 'temporary' and change with > each > incident, not sure those talks/efforts ever made it 'up the chain'. > > > > Of course getting and keeping the map up-to-date is ideal and as a > former > wildland firefighter I can say, it's really only helpful to those > 'on-the-line' if the map is ready in advance; but of course the > aftermath is > helpful for insurance, recovery, etc. I was just looking over the > Waldo > Canyon burn area a few weeks back as I noticed Mapbox imagery had > been > updated in the area (now I think Bing has as well), but I was > completely > surprised because almost every one of the 346 homes destroyed have > been > built back, exactly the same as before - wasn't sure I was seeing > things > correctly until I did find a few lots that are empty and 1 or 2 homes > that > were built back slightly different. > > > > Guess my main point here is that we can and should map as much as we > can, > but unless there are some locals who want to survey once the area is > safe, > then tracing the buildings pre-disaster is maybe all that needs > done. I do > notice however it seems the imported landuse around Lake Isabella has > an > offset to Bing and road network. > > > > =Russ > > > > From: Jonathan Schleuss [mailto:jschle...@me.com] > Sent: Wednesday, June 29, 2016 10:53 PM > To: talk-us@openstreetmap.org > Subject: [Talk-us] What should we do for wildfires? > > > > The Erskine Fire <http://inciweb.nwcg.gov/incident/4806/> [1] has > burned > more than 46,000 acres and killed two. It destroyed 200 structures. > The > perimeter of the fire is huge. > > > > What's the right response from OpenStreetMap? > > > > Should we go in and check roads? Add buildings? What if they've been > destroyed? Addresses? Shelters? Other items? Is this more a role for > the HOT > group? I checked the talk-us archives, but didn't find a lot of > "wildfire" > discussion and I'd love to know what you all think is an appropriate > response. There's some good background on the 2013 Colorado Wildfire > Season > [3]. There's also a preemptive take with Portuguese Wildfire Mapping > [4]. We > could probably find places inside the U.S. that are at a high risk > and task > those areas out. California has a shapefile. [5] > > > > I figured I'd open it up for discussion. Please reply with your > thoughts. > > > > cheers, > > Jon Schleuss > > > > I'm a reporter and graphic artist at the Los Angeles Times. I got > into > OpenStreetMap about a year ago thanks to at MaptimeLA event taught by > techlady <https://www.openstreetmap.org/user/techlady> and Data411 > <https://www.openstreetmap.org/user/Data411> . I use maps in my work > almost > every day. Currently, hacking on the Great L.A. County Building > Import > <http://labuildingsimport.com> [5]. > > > > [1] http://inciweb.nwcg.gov/incident/4806/ > > [2] > http://www.fire.ca.gov/fire_prevention/fire_prevention_wildland_state > wide > > [3] http://wiki.openstreetmap.org/wiki/2013_Colorado_Wildfire_Season > > [4] http://wiki.openstreetmap.org/wiki/Portuguese_Wildfire_Mapping > > [5] http://labuildingsimport.com/ > > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20 > 160630/f2db50e2/attachment-0001.html> > > ------------------------------ > > Message: 4 > Date: Thu, 30 Jun 2016 14:58:43 +0000 (UTC) > From: Michael Reichert <naka...@gmx.net> > To: talk-us@openstreetmap.org > Subject: Re: [Talk-us] Join us for another import party at the L.A. > Times June 25 > Message-ID: <nl3c32$da3$1...@ger.gmane.org> > Content-Type: text/plain; charset=UTF-8 > > Hi, > > Am Fri, 17 Jun 2016 22:20:46 +0000 schrieb Jonathan Schleuss: > > The Los Angeles Times will host another import party to push the > > "Great > > L.A. County Import" forward. We've imported more than half a > > million > > buildings with the great help of locals and the folks from Mapbox. > > Did each participant use a separate account for this import? > > > My focus is to use this import strengthen the Southern California > > OSM > > community. But, the project is open to all. If you're in the area, > > please join us. > > Do you really believe that this helps the local community? A healthy > map > has a strong community and a strong community consists out of people > who > look after their neighbourhood on the map (i.e. keep data up to > date). > > > Meetup even page Import guidelines Tasking manager I've also been > > working to improve our language on why we're doing this. Feedback > > and > > more ideas would be greatly appreciated! > > > > Why are we doing this? > > > > • To improve our map! More data will allow more users to create > > projects > > and do analysis on a variety of things. How many units are located > > within 1,000 feet of a freeway? What's the average building age in > > a > > neighborhood? What's the tallest building on Sunset Boulevard? The > > data > > will tell you. > > > > • To catch up with other cities! New York has buildings. Seattle > > has > > buildings. San Francisco. Portland. Even Bakersfield has buildings. > > L.A. > > County should too! > > > > • Because a big earthquake is coming. Free and open data will > > assist > > first responders. And later it will allow folks to update the > > buildings > > with tags showing whether they have been destroyed, are dangerous > > or > > have been red-tagged. > > Why do buildings have to be at OSM? Is there any problem which > prevents > you and others to use a free-licensed third party source for > building > data if you have/want to create an emergency map? > > > • To encourage more edits. Once buildings are in the map, people > > will be > > able to orient themselves to the shapes, making it easier to add > > more > > data, like names or businesses. > > Adding POIs also works without buildings on the map. You still have > aerial imagery (i.e. Bing). Apart from offline editors like OsmAnd > and > MAPS.ME, you have an aerial image available at all those editors. > > Best regards > > Michael > > > > > ------------------------------ > > Subject: Digest Footer > > _______________________________________________ > Talk-us mailing list > Talk-us@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-us > > > ------------------------------ > > End of Talk-us Digest, Vol 103, Issue 41 > **************************************** _______________________________________________ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
