Re: [Talk-us] Update on highway shield rendering
On Sun, Jul 14, 2013 at 5:50 PM, Phil! Gold wrote: > I do support US:GA:Connector, but I didn't have an entry for Connector > 40. (I do now. :) ) I an effort to reduce the amount of time needed > for shield generation, I tend to specify only the specific bannered > routes I know about, either from personal experience, Wikipedia, or > looking at OSM data. I'm pondering a change to the bannering code > that would handle most cases more dynamically (but not for Georgia, > since they don't actually use banners for their bennered routes...). FWIW recent GDOT installations seem to be using real banners for bannered routes, either due to FHWA pressure or simply because the in-shield banners are basically unreadable at highway speeds. I haven't seen any on guide signs yet but examples on reassurance markers are popping up fairly regularly. Chris -- Chris Lawrence Website: http://www.cnlawrence.com/ ___ 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 [2013-07-15 00:36 -0400]: > Man, there are TONS of bannered routes in GA. It might take forever to > find out all of them, even with using GA's own maps to find them. Well, I wrote a tool[0] that looks at the rendering database and gives me a list of route relations without shields. In the worst case, someone would add a new bannered route and it would sit unrendered until I looked at the missing shields page and saw I needed to add it. [0] http://bazaar.launchpad.net/~asciiphil/osm-shields/trunk/view/head:/show_missing.py ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
Man, there are TONS of bannered routes in GA. It might take forever to find out all of them, even with using GA's own maps to find them. -James > Date: Sun, 14 Jul 2013 17:50:07 -0400 > From: phi...@pobox.com > To: talk-us@openstreetmap.org > Subject: Re: [Talk-us] Update on highway shield rendering > > * James Mast [2013-07-13 20:46 -0400]: > > In GA, it seems you're not supporting the "US:GA:Connector" network. > > I do support US:GA:Connector, but I didn't have an entry for Connector > 40. (I do now. :) ) I an effort to reduce the amount of time needed > for shield generation, I tend to specify only the specific bannered > routes I know about, either from personal experience, Wikipedia, or > looking at OSM data. I'm pondering a change to the bannering code > that would handle most cases more dynamically (but not for Georgia, > since they don't actually use banners for their bennered routes...). > > -- > ...computer contrarian of the first order... / http://aperiodic.net/phil/ > PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 > --- -- > The ring needs another token. >-- BOFH excuse #129 > --- -- > > ___ > 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 [2013-07-13 20:46 -0400]: > In GA, it seems you're not supporting the "US:GA:Connector" network. I do support US:GA:Connector, but I didn't have an entry for Connector 40. (I do now. :) ) I an effort to reduce the amount of time needed for shield generation, I tend to specify only the specific bannered routes I know about, either from personal experience, Wikipedia, or looking at OSM data. I'm pondering a change to the bannering code that would handle most cases more dynamically (but not for Georgia, since they don't actually use banners for their bennered routes...). -- ...computer contrarian of the first order... / http://aperiodic.net/phil/ PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 --- -- The ring needs another token. -- BOFH excuse #129 --- -- ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
Hey Phil. Found another little bug. That or you forgot to add this in, not sure. In GA, it seems you're not supporting the "US:GA:Connector" network. I just had added the ":Connector" part to a relation for GA-40 Connector, and then all the GA-40 shields disappeared from the way and weren't replaced by the connector shields. http://elrond.aperiodic.net/shields/?zoom=16&lat=30.83972&lon=-81.99971&layers=Bhttp://www.openstreetmap.org/browse/relation/2145405 Think you could get this fixed? -James ___ 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] Update on highway shield rendering
* Phil! Gold [2013-07-11 15:32 -0400]: > * James Mast [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
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
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 [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.4739&lon=-83.7315&zoom=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
* James Mast [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
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 wrote: > * Paul Johnson [2013-07-10 10:28 -0500]: >> On Wed, Jul 10, 2013 at 2:18 AM, James Mast wrote: >>> 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.55064&lon=-96.94071&zoom=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
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 [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.4739&lon=-83.7315&zoom=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
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 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=16&lat=35.52081&lon=-79.18442&layers=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
No ref unless it has a ref. If a renderer wants initials in absence of a ref, it can extrapolate that from the relation's name. On Jul 10, 2013 2:50 PM, "Phil! Gold" wrote: > * Richard Welty [2013-07-10 09:58 -0400]: > > an NJTP shield is probably appropriate. the turnpike is _not_ precisely > > I-95. > > I think I was unclear in my question. I have a New Jersey Turnpike shield > that I want to use. My question is: should the route relation for the New > Jersey Turnpike be tagged "ref=NJTP" or should it have no ref tag at all? > > ___ > 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
* Paul Johnson [2013-07-10 10:28 -0500]: > On Wed, Jul 10, 2013 at 2:18 AM, James Mast wrote: > > 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.55064&lon=-96.94071&zoom=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
Re: [Talk-us] Update on highway shield rendering
* James Mast [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.4739&lon=-83.7315&zoom=14 ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
* Richard Welty [2013-07-10 09:58 -0400]: > an NJTP shield is probably appropriate. the turnpike is _not_ precisely > I-95. I think I was unclear in my question. I have a New Jersey Turnpike shield that I want to use. My question is: should the route relation for the New Jersey Turnpike be tagged "ref=NJTP" or should it have no ref tag at all? ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
Let me take this opportunity to sollicit another round of feedback on http://maproulette.org/relationpages/ This is still updated every 4 hours. It needs a pretty index page, better filter options. I prefer it if you just file an issue at https://github.com/mvexel/relationpages/issues Martijn On Wed, Jul 10, 2013 at 8:28 AM, Paul Johnson wrote: > > On Wed, Jul 10, 2013 at 2:18 AM, James Mast wrote: > >> Also, do you guys think for the "PA Turnpike XXX" routes, that the >> "network" tag for them should be "US:PA:Turnpike" (also for the mainline PA >> Turnpike relation and NE Extension)? > > > That's how I've been handling the Oklahoma situation: US:OK:Turnpike. > > ___ > Talk-us mailing list > Talk-us@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-us > > -- 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
Re: [Talk-us] Update on highway shield rendering
On Wed, Jul 10, 2013 at 2:18 AM, James Mast wrote: > Also, do you guys think for the "PA Turnpike XXX" routes, that the > "network" tag for them should be "US:PA:Turnpike" (also for the mainline PA > Turnpike relation and NE Extension)? That's how I've been handling the Oklahoma situation: US:OK:Turnpike. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
On Wed, Jul 10, 2013 at 9:44 AM, James Mast 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=16&lat=35.52081&lon=-79.18442&layers=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
Re: [Talk-us] Update on highway shield rendering
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=16&lat=35.52081&lon=-79.18442&layers=B Is it because there are two different "US 1" relations tagged on those ways? http://www.openstreetmap.org/browse/way/11177 No idea why there are two there, maybe somebody thought that they needed to keep all of US-1 together in NC, even though some segments are Bypass/Business with no "vanilla" US-1? Then again, I know US-21 has this happen in Jonesville with the Business route going into town and the main route being a "Bypass" along I-77 and this rendering "bug" isn't happening there. http://elrond.aperiodic.net/shields/?zoom=14&lat=36.24215&lon=-80.83527&layers=B http://www.openstreetmap.org/browse/way/172380289 -James ___ 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/10/13 9:14 AM, Phil! Gold wrote: Also, I note that someone has added ref=NJTP to the New Jersey Turnpike, which breaks my rendering there. I do support ref= tags for some New York parkways, because that's basically how the signs look, but I'm not sure how reasonable it is for the New Jersey Turnpike. Anyone want to offer an opinion here? an NJTP shield is probably appropriate. the turnpike is _not_ precisely I-95. Delaware to exit 6 is unsigned NJ route 700 (all signage is NJTP), Exit 6 to the GWB is signed both I-95 and NJTP. I-95 is not yet complete in the Philadelphia/South Jersey area so all the traffic is on the NJTP. a typical shield is on the wikipedia page: https://en.wikipedia.org/wiki/New_Jersey_Turnpike in general, drivers on the NJTP think NJTP, not I-95 when they think about it at all. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
> Date: Wed, 10 Jul 2013 09:40:22 -0400 > From: phi...@pobox.com > To: talk-us@openstreetmap.org > Subject: Re: [Talk-us] Update on highway shield rendering > > * James Mast [2013-07-10 09:22 -0400]: > > I could "fix" the PA Turnpike relation with the "US:PA:Turnpike" network > > tag in a moment. Would that work instead of just "fixing" the name tags > > for both directions? > > That wouldn't affect my rendering as it currently stands. The rendering, > right now, will only make a shields for a relation with the exact name > "Pennsylvania Turnpike". Is it possible that it could take the "name" from > the "Super" relation for both directions? I didn't put the word "(super)" In > it.http://www.openstreetmap.org/browse/relation/270032 Also, how will you > deal with the PA Turnpike's NE Extension which also should have the shields > on it? Before today, it didn't have a relation (just the base I-476 one) > till I added it. However, I did split it up with a relation for each > direction, and then a super tying it up > together.http://www.openstreetmap.org/browse/relation/3075654 Or maybe you > could somehow tweak your script to "ignore" anything in "()" in the name tag? > That might be the best solution here, IMO. -James ___ 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 [2013-07-10 09:22 -0400]: > I could "fix" the PA Turnpike relation with the "US:PA:Turnpike" network > tag in a moment. Would that work instead of just "fixing" the name tags > for both directions? That wouldn't affect my rendering as it currently stands. The rendering, right now, will only make a shields for a relation with the exact name "Pennsylvania Turnpike". > I only split it up because it was getting close to 1,000 ways and > thought it would be easier to edit in the future having two smaller > relations, one for each direction. -James Yeah, the same reason we split national routes on a state-by-state basis. The practice of putting stuff like "I-95 (VA)" in the name tag on those doesn't interfere with my rendering because those relations have ref tags, even though that's not really the name of the route. What we really need is a tag like name:relation that the editing tools can use for labeling things in their UIs when we want something more descriptive than precise use of the name tag can give us. -- ...computer contrarian of the first order... / http://aperiodic.net/phil/ PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 --- -- "Well, what IS the song, then?" said Alice, who was by this time completely bewildered. "I was coming to that," the Knight said. "The song really IS 'A-SITTING ON A GATE': and the tune's my own invention." -- _Through the Looking-Glass_, Lewis Carroll ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
I could "fix" the PA Turnpike relation with the "US:PA:Turnpike" network tag in a moment. Would that work instead of just "fixing" the name tags for both directions? I only split it up because it was getting close to 1,000 ways and thought it would be easier to edit in the future having two smaller relations, one for each direction. -James > Date: Wed, 10 Jul 2013 09:14:40 -0400 > From: phi...@pobox.com > To: talk-us@openstreetmap.org > Subject: Re: [Talk-us] Update on highway shield rendering > > * James Mast [2013-07-10 03:18 -0400]: > > I'm just curious, but how are you going to add shields for all of the > > Turnpikes out there that have their shield posted alongside another > > route shield (like the PA Turnpike, New York Thruway, Ohio Turnpike as > > examples)? > > Yes. > > http://elrond.aperiodic.net/shields/?zoom=16&lat=41.23953&lon=-80.99077 > > I've got shields for the PA Turnpike, but a recent edit of yours broke the > rendering. :) See below. For all that I've got most (hopefully all) of > New York's parkways prepped, I seem to have missed the New York Thruway; > I'll have to add that. > > > Will there need to be some tweaks to the relations for those said routes > > so this can happen? > > The way I'm handling this at the moment (documented at > http://elrond.aperiodic.net/shields/supported.html ) is that the relation > needs: > > * an appropriate network tag, usually one matching the state's routes >(US:PA, US:NJ, etc.); > * the name tag set to the name of the route; and > * *no* ref tag > > The recent edit to the PA Turnpike added "(eastbound)" and "(westbound)" > to the name tag for the relations, which broke the rendering because it > just expects "name=Pennsylvania Turnpike". I'm not sure I want to change > this aspect of the rendering, because "Pennsylvania Turnpike" is the name > of the route and "Pennsylvania Turnpike (eastbound)" is merely the > designation for a partiular relation. > > Also, I note that someone has added ref=NJTP to the New Jersey Turnpike, > which breaks my rendering there. I do support ref= tags for > some New York parkways, because that's basically how the signs look, but > I'm not sure how reasonable it is for the New Jersey Turnpike. Anyone > want to offer an opinion here? > > > Also, do you guys think for the "PA Turnpike XXX" routes, that the > > "network" tag for them should be "US:PA:Turnpike" (also for the mainline > > PA Turnpike relation and NE Extension)? > > I've already got shields available for PA routes 43, 66, and 576 under the > US:PA:Turnpike network. (Also, the Pennsylvania Turnpike will get a > shield with either US:PA or US:PA:Turnpike, since I thought a reasonable > argument could be made for either case.) > > ___ > 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 [2013-07-10 03:18 -0400]: > I'm just curious, but how are you going to add shields for all of the > Turnpikes out there that have their shield posted alongside another > route shield (like the PA Turnpike, New York Thruway, Ohio Turnpike as > examples)? Yes. http://elrond.aperiodic.net/shields/?zoom=16&lat=41.23953&lon=-80.99077 I've got shields for the PA Turnpike, but a recent edit of yours broke the rendering. :) See below. For all that I've got most (hopefully all) of New York's parkways prepped, I seem to have missed the New York Thruway; I'll have to add that. > Will there need to be some tweaks to the relations for those said routes > so this can happen? The way I'm handling this at the moment (documented at http://elrond.aperiodic.net/shields/supported.html ) is that the relation needs: * an appropriate network tag, usually one matching the state's routes (US:PA, US:NJ, etc.); * the name tag set to the name of the route; and * *no* ref tag The recent edit to the PA Turnpike added "(eastbound)" and "(westbound)" to the name tag for the relations, which broke the rendering because it just expects "name=Pennsylvania Turnpike". I'm not sure I want to change this aspect of the rendering, because "Pennsylvania Turnpike" is the name of the route and "Pennsylvania Turnpike (eastbound)" is merely the designation for a partiular relation. Also, I note that someone has added ref=NJTP to the New Jersey Turnpike, which breaks my rendering there. I do support ref= tags for some New York parkways, because that's basically how the signs look, but I'm not sure how reasonable it is for the New Jersey Turnpike. Anyone want to offer an opinion here? > Also, do you guys think for the "PA Turnpike XXX" routes, that the > "network" tag for them should be "US:PA:Turnpike" (also for the mainline > PA Turnpike relation and NE Extension)? I've already got shields available for PA routes 43, 66, and 576 under the US:PA:Turnpike network. (Also, the Pennsylvania Turnpike will get a shield with either US:PA or US:PA:Turnpike, since I thought a reasonable argument could be made for either case.) ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
I'm just curious, but how are you going to add shields for all of the Turnpikes out there that have their shield posted alongside another route shield (like the PA Turnpike, New York Thruway, Ohio Turnpike as examples)? Will there need to be some tweaks to the relations for those said routes so this can happen? If so, I'd be more than willing to do some tweaking at least with the PA Turnpike's relation (right now I'm splitting it up into WB and EB for the main route) and adding a super relation to also tie in all of the sections that the PA Turnpike controls (PA Turnpike 43, PA Turnpike 66, PA Turnpike 576, NE Extension I-476, + a segment of the extended I-376 that use to be PA Turnpike 60). Also, do you guys think for the "PA Turnpike XXX" routes, that the "network" tag for them should be "US:PA:Turnpike" (also for the mainline PA Turnpike relation and NE Extension)? I know I would need to spilt up PA-66 and PA-43 relations since both have segments that aren't part of the PA Turnpike network. (Yes, there is a free segment of PA-43 posted with normal PA shields, which is between Exit #8 and US-40/US-119. Have pictures of it, but too tired to dig them up and resize to upload right now, so here's a StreetView link instead: http://goo.gl/maps/GeZzo) I was planning on changing them to that "network" when I split them from the non-Turnpike segments. -James ___ 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/1/2013 10:19 PM, Toby Murray wrote: For those interested in highway shields: Thanks for the update and for everyone's efforts! ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
This actually came up when we were talking about the shields last week. The
shields rendering is actually a full mapnik stylesheet, not just an
overlay. Phil pointed out that this is the only way to avoid conflicts. So
it is essentially a full osm.org mapnik stylesheet (from a few months ago
but it hasn't changed much recently) with the shields logic added in. It
could definitely be tweaked with more US-specific rules. Of course
osm.orgis about to move to a carto based stylesheet instead of the
hand-tweaked
XML that things are based on now. This is being done because the
hand-crafted XML is a pain to maintain. Not sure if we can port the shields
logic to that setup yet. But either way, yes there are definitely some
possibilities here.
Toby
On Mon, Jul 1, 2013 at 10:30 PM, stevea wrote:
> +1 to Martijn's excitement: I, too, find this a neat and appropriate
> front for the us-servers to be serving up specific tiles about. Good luck
> getting postgres technical glitches ironed out!
>
> While it sounds like Ian & Co. have your hands full, another "neat and
> appropriate front" which I believe was once discussed here for the
> us-servers were slightly altered versions of mapnik. They might have
> experimental and new render rules (I believe we were talking about
> boundary=national_park and related matters a few months back). I'm not
> banging the door down about this, and I'm not quite sure how to word a
> specific request (maybe participate in a discussion about some
> possibilities, though, YES!). More like "I'm still thinking about this"
> (funky mapnik renderers with cool new rules we agree would be neat to try).
>
> So, after highway shield rendering is solved and up, maybe this can move
> from back burner to front burner. Think about it, folks: experimental
> mapnik renderings to do cool stuff with park boundaries, perhaps
> admin_level boundaries...your imagination is the limit. We might start
> with a few small changes and see how that goes. Might be a way to propose
> world-wide changes (only if they are consensus-based improvements) into
> mapnik, if we even want to go to such a place.
>
> If we do, starting a new thread ("Experimental mapnik rendering rules"?)
> seems appropriate. If the us has servers (it appears we do), we just might
> have some interesting ideas to try out!
>
> Just (re-) throwing it out there,
>
> SteveA
> California
>
>
>
> For those interested in highway shields:
>>
>> Phil, Ian and myself put some more time in on getting shields working on
>> the OSM-US server last week. We actually got things mostly working but did
>> run into a brick wall. Unfortunately postgres 8.4 doesn't support how the
>> image data is being handled. The fix is to upgrade to a newer version of
>> postgres however that is a slightly complicated matter. Ian is planning
>> some hardware upgrades for the server in the near future which will
>> alleviate some of the issues. So as of now we are waiting on the server
>> changes/upgrades to happen before we start rendering shields.
>>
>> But the good news is I actually got an instance up and running on a VM I
>> have been using here at home. So it is definitely possible!
>>
>> 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
+1 to Martijn's excitement: I, too, find this a neat and appropriate
front for the us-servers to be serving up specific tiles about. Good
luck getting postgres technical glitches ironed out!
While it sounds like Ian & Co. have your hands full, another "neat
and appropriate front" which I believe was once discussed here for
the us-servers were slightly altered versions of mapnik. They might
have experimental and new render rules (I believe we were talking
about boundary=national_park and related matters a few months back).
I'm not banging the door down about this, and I'm not quite sure how
to word a specific request (maybe participate in a discussion about
some possibilities, though, YES!). More like "I'm still thinking
about this" (funky mapnik renderers with cool new rules we agree
would be neat to try).
So, after highway shield rendering is solved and up, maybe this can
move from back burner to front burner. Think about it, folks:
experimental mapnik renderings to do cool stuff with park boundaries,
perhaps admin_level boundaries...your imagination is the limit. We
might start with a few small changes and see how that goes. Might be
a way to propose world-wide changes (only if they are consensus-based
improvements) into mapnik, if we even want to go to such a place.
If we do, starting a new thread ("Experimental mapnik rendering
rules"?) seems appropriate. If the us has servers (it appears we
do), we just might have some interesting ideas to try out!
Just (re-) throwing it out there,
SteveA
California
For those interested in highway shields:
Phil, Ian and myself put some more time in on getting shields
working on the OSM-US server last week. We actually got things
mostly working but did run into a brick wall. Unfortunately postgres
8.4 doesn't support how the image data is being handled. The fix is
to upgrade to a newer version of postgres however that is a slightly
complicated matter. Ian is planning some hardware upgrades for the
server in the near future which will alleviate some of the issues.
So as of now we are waiting on the server changes/upgrades to happen
before we start rendering shields.
But the good news is I actually got an instance up and running on a
VM I have been using here at home. So it is definitely possible!
Toby
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Update on highway shield rendering
Thanks for the update, Toby. I am definitely excited about this. Let me know if there's anything I can do to help move this forward! On Mon, Jul 1, 2013 at 8:19 PM, Toby Murray wrote: > For those interested in highway shields: > > Phil, Ian and myself put some more time in on getting shields working on > the OSM-US server last week. We actually got things mostly working but did > run into a brick wall. Unfortunately postgres 8.4 doesn't support how the > image data is being handled. The fix is to upgrade to a newer version of > postgres however that is a slightly complicated matter. Ian is planning > some hardware upgrades for the server in the near future which will > alleviate some of the issues. So as of now we are waiting on the server > changes/upgrades to happen before we start rendering shields. > > But the good news is I actually got an instance up and running on a VM I > have been using here at home. So it is definitely possible! > > Toby > > ___ > Talk-us mailing list > Talk-us@openstreetmap.org > http://lists.openstreetmap.org/listinfo/talk-us > > -- 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] Update on highway shield rendering
For those interested in highway shields: Phil, Ian and myself put some more time in on getting shields working on the OSM-US server last week. We actually got things mostly working but did run into a brick wall. Unfortunately postgres 8.4 doesn't support how the image data is being handled. The fix is to upgrade to a newer version of postgres however that is a slightly complicated matter. Ian is planning some hardware upgrades for the server in the near future which will alleviate some of the issues. So as of now we are waiting on the server changes/upgrades to happen before we start rendering shields. But the good news is I actually got an instance up and running on a VM I have been using here at home. So it is definitely possible! Toby ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
