Re: [Talk-us] Talk-us Digest, Vol 114, Issue 9

2017-05-15 Per discussione Valerie Anderson
I live in Florida and this sort of thing is pretty common. We have rampant
development on a boom-and-bust cycle but probably if this was planned it
will be built eventually unless it is intentionally protected. I just
checked and it looks like part of the ranch was protected with Florida
Forever money in a straight-up purchase and the part that has the roads by
Eraque22 is going to be developed into a giant subdivision called Babcock
Ranch Community. Here the Fish and Wildlife website about it:
http://myfwc.com/viewing/recreation/wmas/cooperative/babcock-ranch-preserve

I've added the preserve boundaries in osm so you guys can see them.

On Mon, May 15, 2017 at 8:00 AM,  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. Help needed, Babcock Ranch near Fort Myers, FL (Frederik Ramm)
>2. Re: Help needed, Babcock Ranch near Fort Myers, FL (Eric Ladner)
>
>
> --
>
> Message: 1
> Date: Mon, 15 May 2017 09:58:00 +0200
> From: Frederik Ramm 
> To: OpenStreetMap US Talk 
> Subject: [Talk-us] Help needed, Babcock Ranch near Fort Myers, FL
> Message-ID: <610ed3a3-9369-00c2-b04c-28be3be76...@remote.org>
> Content-Type: text/plain; charset=utf-8
>
> Hi,
>
>DWG recently had a complaint from a property developer about a series
> of fictional roads South of Lake Babcock. I have removed them after
> checking with aerial imagery and after giving the original mapper a
> chance for comment. However, the whole "Babcock Ranch" area is
> cris-crossed with streets in OSM that are not even remotely visible on
> any of the available aerial images (and other roads that are on these
> images, are not in OSM).
>
> This is the area:
>
> https://www.openstreetmap.org/#map=14/26.7888/-81.7157
>
> Maybe someone in the area fancies a fact-finding mission ;)
>
> I'll also ask the property developer if they have better information but
> of course nothing beats a field survey.
>
> Bye
> Frederik
>
> --
> Frederik Ramm  ##  eMail frede...@remote.org  ##  N49°00'09" E008°23'33"
>
>
>
> --
>
> Message: 2
> Date: Mon, 15 May 2017 11:37:24 +
> From: Eric Ladner 
> To: Frederik Ramm , OpenStreetMap US Talk
> 
> Subject: Re: [Talk-us] Help needed, Babcock Ranch near Fort Myers, FL
> Message-ID:
>  mail.gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> On Mon, May 15, 2017 at 2:59 AM Frederik Ramm  wrote:
>
> > Hi,
> >
> >
> > Maybe someone in the area fancies a fact-finding mission ;)
> >
> >
> Some of it actually shows up in the Charlotte county GIS system[1] (the
> stuff south of Lake Timber), and construction on the round-a-bout is
> visible on other *cough*Google[2]*cough* satellite imagery (just below Lake
> Babcock).  Construction on the now deleted roads to the left of Lake
> Babcock is also visible (as of Feb imagery).
>
> Most likely it's not vandalism or somebody using OSM for urban fantasy but
> some very early county GIS or planning data that was uploaded.  It likely
> should have been tagged at least as "proposed," though.  Some of it is at
> least a solid "construction" now.
>
> The imagery availble in JOSM via Bing looks pixel-for-pixel identical to
> imagery available elsewhere from 2010.
>
> [1] http://agis.charlottecountyfl.gov/ccgis/
> [2] https://www.google.com/maps/@26.7872318,-81.7380132,2180m/
> data=!3m1!1e3
>
> Bye
> > Frederik
> >
>
> Eric
> -- next part --
> An HTML attachment was scrubbed...
> URL:  attachments/20170515/5b361f7c/attachment-0001.html>
>
> --
>
> Subject: Digest Footer
>
> ___
> Talk-us mailing list
> Talk-us@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
>
> --
>
> End of Talk-us Digest, Vol 114, Issue 9
> ***
>
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] Talk-us Digest, Vol 108, Issue 18

2016-11-23 Per discussione Valerie Anderson
Hello talk-us!
This is the area in question: http://www.openstreetmap.org/#map=13/28.2
929/-81.2331

I'm wondering why this building that I input into OSM: http://www.opens
treetmap.org/way/405322404 thinks that it's in New Eden
(http://www.openstreetmap.org/node/154079502) and not Narcoossee (http:
//www.openstreetmap.org/node/154104172). New Eden and Narcoossee are
two nearby hamlets (unincorporated cities). The mailing address of the
building is in Saint Cloud, the closest incorporated city to the
building that's in the same county. I entered the tag
addr:hamlet=Narcoossee yet when you search for the address in the
search bar it says Building 2886, Absher Road, New Eden, Osceola
County, Florida
(http://www.openstreetmap.org/search?query=2886%20absher%20rd#map=20/28
.33281/-81.19943=H).

Why?

Thanks,

Val___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


[Talk-us] Tree Survey

2016-09-28 Per discussione Valerie Anderson
Hey Bryce,

I recommend existing data collection software for standard municipal
tree surveys. iTree is free and is good for mobile collection. The
downside is it requires a windows computer to handle all the data and
run the simulations. It's easy to export data from iTree and I think
setting up an import script to osm would be totally cool and easily
reusable. I know there are other software but I know the most about
iTree.

Good luck! I am advising my local tree committee about what to do with
an old arcgis tree survey.

Cheers,

Valerie
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us


Re: [Talk-us] What should we do for wildfires?

2016-06-30 Per discussione Valerie Anderson
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 +, 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 
> To: OpenStreetMap talk-us list 
> Subject: [Talk-us] WeeklyOSM 310
> Message-ID:
>    .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 
> -- next part --
> An HTML attachment was scrubbed...
> URL:  160630/2fcc1058/attachment-0001.html>
> 
> --
> 
> Message: 2
> Date: Thu, 30 Jun 2016 12:24:35 +
> From: Josh Spencer 
> To: "talk-us@openstreetmap.org" 
> Subject: Re: [Talk-us] What should we do for wildfires?
> Message-ID:
>    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:  160630/a630ad57/attachment-0001.html>
> 
> --
> 
> Message: 3
> Date: Thu, 30 Jun 2016 08:14:36 -0600
> From: "Russell 

Re: [Talk-us] New MapRoulette now in early public beta

2016-05-25 Per discussione Valerie Anderson
Martijn,

It looks great on Chromium and Firefox/Iceweasel.

Cheers,

Val

On Wed, 2016-05-25 at 20:29 +, 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. Re: Odd road / odd structure (Paul Johnson)
>2. Re: Proposed import cleanup: NYSDEClands (Kevin Kenny)
>3. New MapRoulette now in early public beta (Martijn van Exel)
>4. Re: New MapRoulette now in early public beta (Rihards)
>5. Re: New MapRoulette now in early public beta (Kevin Kenny)
>6. Re: New MapRoulette now in early public beta (Martijn van Exel)
> 
> 
> --
> 
> Message: 1
> Date: Wed, 25 May 2016 13:12:57 -0500
> From: Paul Johnson 
> To: OpenStreetMap talk-us list 
> Subject: Re: [Talk-us] Odd road / odd structure
> Message-ID:
>   
> Content-Type: text/plain; charset="utf-8"
> 
> On Wed, May 25, 2016 at 8:55 AM, Steve Friedl  wrote:
> >
> > The Irvine GIS guy told me that Paisley Place also servers as a utility
> > easement, which may have impacted some of the design.  These are quite
> > pretty little walkways, with a nice gate to enter, it’s just odd that it’s
> > a street.
> >
> 
> Huh?  The only thing I could see that could be remotely construed as a
> through walkway is the concrete gutter, which would make a natural break at
> the planter that for all practical purposes breaks up the street as a
> traffic calming measure, and appears to have barely slowed down the Google
> car, much less anyone on foot.
> 
> 
> > But regarding the big water catchment surface:
> >
> >
> >
> > Ø  Depending on the cant and the surface, it could actually be some sort
> > of French drain or infiltration pad designed as potentially an emergency
> > helipad.  I, personally, would make no assumption as to what it was without
> > at least cursory knowledge of the region's drainage and/or rescue tropes …
> >
> >
> >
> > I have some of that cursory knowledge, plus I actually hiked up there and
> > checked it out myself – there’s no question that it’s there to collect
> > water, drain it into the two cisterns to the southeast, and there’s a water
> > tap a little farther to the southwest.
> >
> >
> >
> > What you can’t see from the satellite imagery is that it’s at the top of a
> > hill, the only water it can possibly collect is rainwater.  It’s also clear
> > that this isn’t being used any more, but back in the forties I’m certain it
> > was a great place to water your horse.
> >
> >
> >
> > I think it would serve as a fine helipad, though these were constructed
> > before helicopters were in widespread enough use to be considered for
> > that.  I’m going to ask the local fire agency if they have records of using
> > that spot for helo.
> >
> 
> Very interesting edge case; I'd honestly be surprised based on aerial
> imagery if the cisterns aren't still in use as at least an emergency water
> supply, given that particular stretch of hills' propensity for fire.  It
> has a dry climate, some plants that depend on fire for reproduction, and
> eucalyptus, which the AU crowd can testify sets itself on fire for like, no
> reason.
> -- next part --
> An HTML attachment was scrubbed...
> URL: 
> 
> 
> --
> 
> Message: 2
> Date: Wed, 25 May 2016 14:47:48 -0400
> From: Kevin Kenny 
> To: "talk-us@openstreetmap.org" 
> Subject: Re: [Talk-us] Proposed import cleanup: NYSDEClands
> Message-ID:
>