Re: [Talk-us] Requesting to remove stoplines in San Jose

2017-09-18 Thread Shawn K. Quinn
On 09/18/2017 08:39 PM, Vivek Bansal wrote:
> Hey, I noticed pfliers has added lots of unconnected ways w/
> `highway=stopline` all over San Jose. It’s really been cluttering up our
> workflows in iD, and now it’s triggering JOSM’s validator as we’re
> adding sidewalks. Can we remove them in one big mechanical edit? Even if
> the concept is good, they’d have to be remapped in order to be useful
> anyways. Maybe they should be a node along the centerline.  Or instead
> they should be a road_marking.

Ideally, the position of the highway=stop/yield node should convey this
information. In the case of a nearby highway=traffic_signals I could
maybe see road_marking=stopline, but not under highway=*.

-- 
Shawn K. Quinn 
http://www.rantroulette.com
http://www.skqrecordquest.com

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


[Talk-us] Requesting to remove stoplines in San Jose

2017-09-18 Thread Vivek Bansal
Hey, I noticed pfliers has added lots of unconnected ways w/
`highway=stopline` all over San Jose. It’s really been cluttering up our
workflows in iD, and now it’s triggering JOSM’s validator as we’re adding
sidewalks. Can we remove them in one big mechanical edit? Even if the
concept is good, they’d have to be remapped in order to be useful anyways.
Maybe they should be a node along the centerline.  Or instead they should
be a road_marking.

This also affects Phoenix, Arizona.

Here is a link to pfliers history:
https://www.openstreetmap.org/user/pflier/history#map=6/38.882/-117.411

Here is pfliers proposal:
http://wiki.openstreetmap.org/wiki/Proposed_features/stop_line

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


[Talk-us] Virtual Mappy Hours reboot

2017-09-18 Thread Martijn van Exel
Hey all, 

I decided to give the Virtual Mappy Hours another go. The first one will be 
next Wednesday at 5:30 pacific. We’ll talk about State of the Map US. I hope 
you can join! Details are in this diary entry: 
https://www.openstreetmap.org/user/mvexel/diary/42318 


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


Re: [Talk-us] Edits in Phoenix, Arizona

2017-09-18 Thread Greg Morgan
On Mon, Sep 18, 2017 at 1:49 AM, Horea Meleg 
wrote:

> Hi Greg,
>
> We are editing in Maricopa and Pinal counties area, where we have tiger
> and approved local data. Thanks for all input and advice. We already talked
> with Hans about highway tags when we had some concerns. We talked with some
> mappers in Phoenix about signpost and the tag destination:street, which we
> used before in other areas but in Phoenix it’s not used. Could you give us
> some pointers: why do you not use it? Could we?
>

http://www.openstreetmap.org/way/60547575
http://www.openstreetmap.org/node/756209453

Look at the history on these to objects.  Was name, ref, exit_to, or
destination the tag to use or now is it destination:street?  Do you put the
tags on the node or the way? In my case, freeway exit numbers and mileposts
are important.  I put in many of the exit numbers.  I found something
better to do that keep up with all the "shall we do it this way
discussions".  Go right ahead and make the changes.  Your changes will be a
model for other future exits or exits left unchanged.

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


Re: [Talk-us] Edits in Phoenix, Arizona

2017-09-18 Thread Horea Meleg
Hi Greg,
We are editing in Maricopa and Pinal counties area, where we have tiger and 
approved local data. Thanks for all input and advice. We already talked with 
Hans about highway tags when we had some concerns. We talked with some mappers 
in Phoenix about signpost and the tag destination:street, which we used before 
in other areas but in Phoenix it’s not used. Could you give us some pointers: 
why do you not use it? Could we?
Thanks,
Horea Meleg

From: Greg Morgan [mailto:dr.kludge...@gmail.com]
Sent: Monday, September 11, 2017 6:01 PM
To: Horea Meleg 
Cc: talk-US@openstreetmap.org
Subject: Re: [Talk-us] Edits in Phoenix, Arizona



On Mon, Sep 11, 2017 at 4:31 AM, Horea Meleg 
> wrote:

Hi everyone!

This is Horea and I am part of the mapping team at Telenav.

To make OpenStreetMap more navigable and accurate in guidance, our mapping team 
is planning to start editing in Phoenix.

Do you mean the City of Phoenix or the metro Phoenix area?  There is plenty of 
work to do in both.  However, I'd like your team to stay awhile and work on the 
metro area.  ;-)


In the next weeks we will focus on road geometry, road name, oneways, signpost, 
speed limit, lanes and turn lanes.

This is where you come in! Beside the general OSM mapping guidelines 
(http://wiki.openstreetmap.org/wiki/Main_Page, 
http://wiki.openstreetmap.org/wiki/Map_Features), do you have any local mapping 
guidelines for us? Also, we appreciate any hints regarding available local or 
government data that we might be able to us.

We'd love any input and advice!


 On Tue, Aug 29, 2017 at 3:15 PM, Martijn van Exel 
> wrote:
turn restrictions, missing roads (if any), one-way roads, traffic signals, some 
carto features such as parks.

Hans Dekryger is a mapping force.  I think he maps all those features except 
turn restrictions. Hans has done a great job of adding dual carriage ways to 
metro Phoenix.  Most of the turn restriction and traffic flow entries are false 
positives.  I see many no left turns suggestions where a dual carriage way 
comes together. Only a few drivers make the u-turn.  It would be incorrect to 
add those restrictions.

As always we will respect local mappers’ work above everything.
Thank you for your concern.

Sources will be Bing / DG, OpenStreetCam, Mapillary,
 https://www.openstreetmap.org/way/109740061
Bing is your best bet.  Digital Globe is not even competitive.
If you look at the new ASU Law building, you can see that Bing has the building 
under construction. DG premium show the area as a green parking lot. DG 
standard shows the footing being dug.  DG is great for rural areas but not 
here.  Bing is actual airplane flyovers around 2014 .  The new ESRI imagery is 
newer but it does not let you overzoom.  Bing will still give you tiles to zoom 
20.  ESRI has newer data to zoom 17 and then shows the same DG standard for 18. 
Overzooming only provides white tiles.

ImproveOSM (GPS based detections) augmented with government data where possible 
(which is where Horea’s question came from).



Where possible we will publish MapRoulette / Tasking Manager jobs for anyone to 
participate.
The Phoenix area was hit hard by the chdr changes.  Fredrick lists affected 
streets as Arizona but there are only three small outliers: Yuma, a few along 
Mexico, and Tucson.  The rest were sub-prime rate subdivisions that chdr either 
added the geometry and name or just the name.  The tiger2015 layer is more than 
adequate to cover these names.  I have set all  name tags to 
chdr_USA_AZ_name_fixup_required because the rest of the metro Phoenix are 
pockets.  You can use any number of tools to search and repair the name.  Other 
than this issue I cannot think of any potential MapRoulette challenges.


If you have any (other) specific insights to share, like locally specific 
mapping practices, things on the ground that are different / specific to the 
area, data you’ve worked with, let us know. Thanks!
 Remove all the tiger tags when you are done with a street.  Add surface tags 
and lanes if you can. I use surface tag of dirt verses tracks.  I started using 
the dirt surface tag when the town of Tonopah disappeared on 
http://tripmaker.randmcnally.com/
 . Tripmaker will let you route over dirt but tracks do not display.

You really cannot use blue tiles like you would else where.  Most all of our 
flood plains are recreation areas such as golf courses, and area mini parks.  
Most of the small neighborhood green looking mini-park areas are dual use.  
They are a catch basin during heavy rains but function as a park.  Here is an 
example