[Talk-us] Talk-us Digest, Vol 102, Issue 38

Will Skora skorasaurus at gmail.com
Mon May 23 19:44:02 UTC 2016


These types of roads (portions of roads are somewhat common in the City of
Cleveland - for example, here's a selection of them -
http://overpass-turbo.eu/s/goF ) I've done Martijn's #2 option but as Jack
Burke noted, I used alt_name instead since it's less ambiguous as name_1.

Regards,
Will



On Mon, May 23, 2016 at 1:12 PM, <talk-us-request at openstreetmap.org> wrote:

> Send Talk-us mailing list submissions to
>         talk-us at 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-request at openstreetmap.org
>
> You can reach the person managing the list at
>         talk-us-owner at 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 (Martijn van Exel)
>    2. 'Honorary' street name conflicts with posted name - how   to
>       decide (Martijn van Exel)
>    3. Re: 'Honorary' street name conflicts with posted name -   how
>       to decide (Jack Burke)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 23 May 2016 10:53:44 -0600
> From: Martijn van Exel <m at rtijn.org>
> To: Steve Friedl <steve at unixwiz.net>
> Cc: OSM Talk US <talk-us at openstreetmap.org>
> Subject: Re: [Talk-us] Odd road / odd structure
> Message-ID: <CB119D28-9590-47B3-941B-C063DC63B16E at rtijn.org>
> Content-Type: text/plain; charset="utf-8"
>
> Hi Steve,
>
> It looks like there is garage access, so I would tag it highway=service,
> possibly with an appropriate access= tag if access is restricted.
> https://bit.ly/1WNyjdd <https://bit.ly/1WNyjdd>
>
> If you are referring to the foot access to the west of that, I’d do
> highway=footway (perhaps with bicycle=yes if appropriate) and name it
> Paisley Place as well, if that name refers to that side of the homes also.
>
> Martijn
>
> > On May 23, 2016, at 10:41 AM, Steve Friedl <steve at unixwiz.net> wrote:
> >
> > Hi all,
> >
> > I have two things that I just don’t quite know how to map.  Sorry that I
> have to provide Google Maps views to demonstrate.
> >
> > 1)      How does one represent a named street which is really a
> greenbelt: never been drivable, was assigned a name just to allow attaching
> a street name to the houses on either side.
> >
> > Example: In Irvine California there’s a residential area shown here:
> >
> > https://www.google.com/maps/@33.7298257,-117.7572128,19z <
> https://www.google.com/maps/@33.7298257,-117.7572128,19z>
> >
> > I’m referring to Paisley Place, which is shown as a named alley
> connecting Garden Gate Lane and Winslow Lane.
> >
> > After surveying the area and seeing that the City of Irvine GIS showed
> Paisley as that greenbelt, I reported it as an error (as I’ve done dozens
> of times for other things), but the very helpful GIS manager reported that
> this is correct (but certainly odd), and the two street-like things on
> either side of it are just unnamed alleys.
> >
> > How do I represent this in OSM?  It’s not a street that doesn’t allow
> access, it’s not really even a street!
> >
> > 2)      How do I represent a parking-lot-sized area that’s intended to
> collect rainwater that fills a cistern?
> >
> > In the Santa Ana Mountains in Southern California, the satellite views
> show something that looks exactly like a helipad:
> >
> > https://www.google.com/maps/@33.7875181,-117.5805174,419m/data=!3m1!1e3
> <https://www.google.com/maps/@33.7875181,-117.5805174,419m/data=!3m1!1e3>
> >
> > But it’s not. That whole huge surface – paved in asphalt – is tilted
> slightly so that rainwater water will collect and fill the two cisterns to
> the left (zooming in you can barely see the pipe from the big pad to the
> cisterns.
> >
> > I cannot find anything that’s even close to describing what this is, but
> it’s so prominent on the maps (and interesting to visit) that I seems like
> it should be there even if to make note that it’s not a helipad.
> >
> > Thanks,
> >
> > Steve – who hopes the links above work.
> > ---
> > Stephen J Friedl  | Security Consultant | UNIX Wizard | 714 345-4571
> > steve at unixwiz.net <mailto:steve at unixwiz.net> | Southern California |
> Windows Guy |  unixwiz.net <http://unixwiz.net/>
> >
> > _______________________________________________
> > Talk-us mailing list
> > Talk-us at openstreetmap.org <mailto:Talk-us at openstreetmap.org>
> > https://lists.openstreetmap.org/listinfo/talk-us <
> https://lists.openstreetmap.org/listinfo/talk-us>
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.openstreetmap.org/pipermail/talk-us/attachments/20160523/b702dc0a/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 2
> Date: Mon, 23 May 2016 11:03:15 -0600
> From: Martijn van Exel <m at rtijn.org>
> To: OSM Talk US <talk-us at openstreetmap.org>
> Subject: [Talk-us] 'Honorary' street name conflicts with posted name -
>         how     to decide
> Message-ID: <AD2C0506-AE1C-483C-8247-EF4762A652C7 at rtijn.org>
> Content-Type: text/plain; charset="utf-8"
>
> Salt Lake City just renamed a part of 900 South to ‘Harvey Milk
> Boulevard’. This is a so-called ‘honorary designation’. But now I see a
> conflict.
>
> 1) The common tagging practice is that posted names rule. The signs
> changed to show the new honorary name:
> https://goo.gl/photos/xqAxQCwCmPRUGWkm9 <
> https://goo.gl/photos/xqAxQCwCmPRUGWkm9> . So that would suggest I change
> the name to ‘Harvey Milk Boulevard’ and demote ‘900 South’ to name_1 or
> loc_name.
> 2) Addressing and geocoding. People will continue to refer to this street
> as 900 South. Official addresses will not change. That would suggest that I
> leave the name=900 South in place and add name_1=Harvey Milk Boulevard.
>
> I went with option 2, here is a segment —>
> https://www.openstreetmap.org/way/418190301 <
> https://www.openstreetmap.org/way/418190301>
>
> Opinions?
>
> Martijn
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.openstreetmap.org/pipermail/talk-us/attachments/20160523/bd3ed342/attachment-0001.html
> >
>
> ------------------------------
>
> Message: 3
> Date: Mon, 23 May 2016 13:12:14 -0400
> From: Jack Burke <burkejf3 at gmail.com>
> To: Martijn van Exel <m at rtijn.org>,OSM Talk US
>         <talk-us at openstreetmap.org>
> Subject: Re: [Talk-us] 'Honorary' street name conflicts with posted
>         name -  how     to decide
> Message-ID: <001979D0-965E-456E-A1A4-BA134D387621 at gmail.com>
> Content-Type: text/plain; charset="utf-8"
>
> I concur. You could also put Harvey as an alt_name tag.
>
> --
> Typos courtesy of fancy auto spell technology
>
> On May 23, 2016 1:03:15 PM EDT, Martijn van Exel <m at rtijn.org> wrote:
> >Salt Lake City just renamed a part of 900 South to ‘Harvey Milk
> >Boulevard’. This is a so-called ‘honorary designation’. But now I see a
> >conflict.
> >
> >1) The common tagging practice is that posted names rule. The signs
> >changed to show the new honorary name:
> >https://goo.gl/photos/xqAxQCwCmPRUGWkm9
> ><https://goo.gl/photos/xqAxQCwCmPRUGWkm9> . So that would suggest I
> >change the name to ‘Harvey Milk Boulevard’ and demote ‘900 South’ to
> >name_1 or loc_name.
> >2) Addressing and geocoding. People will continue to refer to this
> >street as 900 South. Official addresses will not change. That would
> >suggest that I leave the name=900 South in place and add name_1=Harvey
> >Milk Boulevard.
> >
> >I went with option 2, here is a segment —>
> >https://www.openstreetmap.org/way/418190301
> ><https://www.openstreetmap.org/way/418190301>
> >
> >Opinions?
> >
> >Martijn
> >
> >------------------------------------------------------------------------
> >
> >_______________________________________________
> >Talk-us mailing list
> >Talk-us at openstreetmap.org
> >https://lists.openstreetmap.org/listinfo/talk-us
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <
> http://lists.openstreetmap.org/pipermail/talk-us/attachments/20160523/3c643490/attachment.html
> >
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> Talk-us mailing list
> Talk-us at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-us
>
>
> ------------------------------
>
> End of Talk-us Digest, Vol 102, Issue 38
> ****************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk-us/attachments/20160523/4e472409/attachment.html>


More information about the Talk-us mailing list