Re: [Talk-us] Edit-a-thon promotion
Indeed, I'll reach out to them. OSM NYC is planning on mapping Hurricane Sandy damage (I was planning on a trip to Wall Street to scope out locations). I'll reach out to these folks and see what they say. - Serge On Tue, Jul 9, 2013 at 9:48 PM, Jason Remillard remillard.ja...@gmail.com wrote: Hello, There is already a mapping party at NeighborLand, mapping seats in NYC! http://handbook.neighborland.com/nyc-mapping-party/ Bummer, they are not doing this on top of OSM! The site is using google for everything, even storing the raw data. https://www.google.com/fusiontables/DataSource?docid=1dpQr55ZhmgcExT2ldCYeI6jbejuAI0Nf4n9oGX0#rows:id=1 Jason. On Tue, Jul 9, 2013 at 9:19 PM, Martijn van Exel m...@rtijn.org wrote: Hey all, I found out about NeighborLand today and am using it as one of the channels to promote the SLC edit-a-thon -- https://neighborland.com/ideas/salt-lake-city-to-improve-openstreetmap Perhaps it's useful for you as well, either for promoting a local edit-a-thon or just to let people know about your local OSM group. At least the people on there are somehow concerned with what's happening around them, so they might be a good target demographic for your next mapping party or mappy hour! Martijn -- Martijn van Exel http://oegeo.wordpress.com/ http://openstreetmap.us/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Future Interstate Relations
Is there picture proof of how they are signing it? -James Date: Wed, 10 Jul 2013 21:43:47 -0400 From: kken...@nycap.rr.com To: talk-us@openstreetmap.org Subject: Re: [Talk-us] Future Interstate Relations On Wed, Jul 10, 2013 at 7:40 AM, Phil! Gold phi...@pobox.com wrote: Given that previous list consensus was for tagging of the form: network=US:I:Future ref=number modifier=Future and that only one person offered a variant opinion this time around, I'd recommend tagging as above. Also, from your earlier emails, I have future interstates 26, 73, 74, and 840. Are there any others? 86 in New York, so signed for various segments of NY 17. https://www.dot.ny.gov/regional-offices/multi/i-86 ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
I know that there is a US 1-9 in NJ, but this error is showing up in NC. ;) -James Date: Wed, 10 Jul 2013 10:07:17 -0500 From: toby.mur...@gmail.com CC: talk-us@openstreetmap.org Subject: Re: [Talk-us] Update on highway shield rendering On Wed, Jul 10, 2013 at 9:44 AM, James Mast rickmastfa...@hotmail.com wrote: Well, I've found a bug in the rendering engine. What's up with these US 1-9 shields? http://elrond.aperiodic.net/shields/?zoom=16lat=35.52081lon=-79.18442layers=B This is a real thing. Welcome to the insane variety of how we do highways in this country :)http://www.alpsroads.net/roads/nj/us_1-9/n46.jpg Phil actually mentioned this in his sotm-us talk which everyone in this discussion might find interesting:http://vimeopro.com/openstreetmapus/state-of-the-map-us-2013/video/68097487 Toby ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
Well, it is ONLY posted in the field as US-21 Bypass, and it was that way last month. (I was down in Charlotte for the Coca-Cola 600, so I traveled on that segment of I-77.) I don't know who added that segment to the main US-21 relation, but might have been NE2, but can't be sure. Anyways, here's a quick link to StreetView showing this: http://goo.gl/maps/DiSfn. Just chock it up to one of those NCDOT quirks. I mean, they have a Bypass, Business, Alternate, and vanilla US-70 in the same area (Smithfield, NC)! -James Date: Wed, 10 Jul 2013 16:15:44 -0400 From: phi...@pobox.com To: talk-us@openstreetmap.org Subject: Re: [Talk-us] Update on highway shield rendering * James Mast rickmastfa...@hotmail.com [2013-07-10 10:44 -0400]: http://www.openstreetmap.org/browse/way/172380289 There are some interesting things going on here. Is this road really part of both US 21 and US 21 Bypass? That seems weird to me, but if someone says that's how the road's signed I'll believe it (see: US 1-9 signage...). Also, the map really ought to show bypass shields for the roads that are part of US 21 Bypass.[0] My rendering is not doing so because US 21 Bypass has network=US:US (not network=US:US:Bypass), so it's treated as mainline US 21. [0] Like US 341 Bypass here: http://elrond.aperiodic.net/shields/?lat=32.4739lon=-83.7315zoom=14 ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
direction is not part of the name and shouldn't be tagged in the name. I know especially NE2 has done that everywhere but it doesn't make sense. Signs usually say east,west,north,south not (*bound). The wiki is not consistent itself on the interstate relations page. It's important information and often signed with an additional shield. So I think best is to remove it from the name and put it in a extra tag called direction or something more specific since this is a US specific thing and direction is often different from a geographic direction on certain segments. Thought we had this tag at some time documented but right now it's not in the wilki. This makes also more sense if a routing software needs to announce correct instructions. It's a lot easier to have a clearly defined tag instead the need to parse complicated names. On Jul 10, 2013, at 1:24 PM, Phil! Gold phi...@pobox.com wrote: * Paul Johnson ba...@ursamundi.org [2013-07-10 10:28 -0500]: On Wed, Jul 10, 2013 at 2:18 AM, James Mast rickmastfa...@hotmail.comwrote: Also, do you guys think for the PA Turnpike XXX routes, that the network tag for them should be US:PA:Turnpike That's how I've been handling the Oklahoma situation: US:OK:Turnpike. Yep: http://elrond.aperiodic.net/shields/?lat=34.55064lon=-96.94071zoom=13 :) I only see two US:OK:Turnpike routes in the database at the moment, and the Cherokee Turnpike suffers from the same issue as the PA Turnpike has currently; my rendering doesn't understand name=Cherokee Turnpike (eastbound). I'm still not sure what the best way to handle that is. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
* James Mast rickmastfa...@hotmail.com [2013-07-11 14:02 -0400]: I know that there is a US 1-9 in NJ, but this error is showing up in NC. ;) Oh, wow. That *is* a bug. I've got to figure out how to handle it, but here's what's going on: Those ways (take http://www.openstreetmap.org/browse/way/11177 as an example) are members of three relations: NC Strategic Highway Corridor 34, US 1, and US 1 Bypass. (Like the other case that came up recently, I question whether it's *really* both US 1 and US 1 Bypass.) US 1 Bypass is tagged as network=US:US, ref=1, modifier=Bypass, so the rendering treats it as a duplicate of US 1. The consolidation algorithm I wrote for US 1-9 is a little naive; it matches against US 1 and US 9 and if it gets two matches, it substitutes in US 1-9. The duplicate US 1 relations give it two matches, so it does the substitution. I'll have to think a bit about how I want to address this bug. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
Just so you know Phil, I've fixed up US-21 and it's children in the Elkin/Jonesville area a few minutes ago. I removed US-21's relation from the US-21 Bypass route and added a note=* tag explaining the gap. Hopefully that will prevent anybody else from re-adding it again. I also took the chance to add in the :Business and :Bypass to the two children of US-21 there (but kept the modifier tag). So, those will now render properly on your renderer. -James Date: Wed, 10 Jul 2013 16:15:44 -0400 From: phi...@pobox.com To: talk-us@openstreetmap.org Subject: Re: [Talk-us] Update on highway shield rendering * James Mast rickmastfa...@hotmail.com [2013-07-10 10:44 -0400]: http://www.openstreetmap.org/browse/way/172380289 There are some interesting things going on here. Is this road really part of both US 21 and US 21 Bypass? That seems weird to me, but if someone says that's how the road's signed I'll believe it (see: US 1-9 signage...). Also, the map really ought to show bypass shields for the roads that are part of US 21 Bypass.[0] My rendering is not doing so because US 21 Bypass has network=US:US (not network=US:US:Bypass), so it's treated as mainline US 21. [0] Like US 341 Bypass here: http://elrond.aperiodic.net/shields/?lat=32.4739lon=-83.7315zoom=14 ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
On 7/11/13 4:20 PM, James Mast wrote: Just so you know Phil, I've fixed up US-21 and it's children in the Elkin/Jonesville area a few minutes ago. I removed US-21's relation from the US-21 Bypass route and added a note=* tag explaining the gap. Hopefully that will prevent anybody else from re-adding it again. if i seriously want people to read something, i find that README= works well because both JOSM and Potlatch sort it to the top, and the all caps make it really noticeable. note= is technically correct, but likely to be buried in the tags. richard ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
* Phil! Gold phi...@pobox.com [2013-07-11 15:32 -0400]: * James Mast rickmastfa...@hotmail.com [2013-07-11 14:02 -0400]: I know that there is a US 1-9 in NJ, but this error is showing up in NC. ;) Oh, wow. That *is* a bug. And now it's fixed. :) The replacement code will only kick in if both parts of the precondition are met. This does raise a thought for me. I'm going to see if I can convince my code to spit out a shield for every relation, even if two of them are duplicates of each other. That will better highlight cases like this where two overlapping routes have the same apparent definitions. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
Done. Changed it to README=*. Thanks for that suggestion. -James Date: Thu, 11 Jul 2013 16:30:06 -0400 From: rwe...@averillpark.net To: talk-us@openstreetmap.org Subject: Re: [Talk-us] Update on highway shield rendering On 7/11/13 4:20 PM, James Mast wrote: Just so you know Phil, I've fixed up US-21 and it's children in the Elkin/Jonesville area a few minutes ago. I removed US-21's relation from the US-21 Bypass route and added a note=* tag explaining the gap. Hopefully that will prevent anybody else from re-adding it again. if i seriously want people to read something, i find that README= works well because both JOSM and Potlatch sort it to the top, and the all caps make it really noticeable. note= is technically correct, but likely to be buried in the tags. richard ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Future Interstate Relations
Here's someone's picture of a Future 86 shield from a few years ago: http://www.flickr.com/photos/iccdude/5516141266/ And also some band by that name with nonstandard FUTURE lettering on the shield: http://www.flickr.com/photos/89048316@N00/1815241606/ Eric On Thu, Jul 11, 2013 at 10:57 AM, James Mast rickmastfa...@hotmail.comwrote: Is there picture proof of how they are signing it? -James Date: Wed, 10 Jul 2013 21:43:47 -0400 From: kken...@nycap.rr.com To: talk-us@openstreetmap.org Subject: Re: [Talk-us] Future Interstate Relations On Wed, Jul 10, 2013 at 7:40 AM, Phil! Gold phi...@pobox.com wrote: Given that previous list consensus was for tagging of the form: network=US:I:Future ref=number modifier=Future and that only one person offered a variant opinion this time around, I'd recommend tagging as above. Also, from your earlier emails, I have future interstates 26, 73, 74, and 840. Are there any others? 86 in New York, so signed for various segments of NY 17. https://www.dot.ny.gov/regional-offices/multi/i-86 ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] tile.openstreetmap.us down tomorrow
Hi folks, We're installing some hardware upgrades in the server running tile.openstreetmap.us, so some of the tile layers in the editors will be unavailable for the day. The layers that might not work: - TIGER 2012 Road Names - USGS Topo Maps - USGS Large Scale Aerials - some other layers that are used less frequently Please let me know if you have any questions, Ian ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
