Re: [Talk-us] Highway Shield Rendering
Ngày 2012-04-11 4:23 PM, Phil! Gold viết: * Minh Nguyen [2012-04-04 11:54 -0700]: More requests: in addition to its circular-shield state highway system, Kentucky also has an ad-hoc "parkway" network. At least some of them are tagged `network=US:KY:Parkway` with a shield URL in `symbol`. Since I've now got shields rendering larger at higher zoom levels, I made some shields for the Kentucky Parkways. They are indeed pretty unreadable until you get to about z17, but at that point you can mostly make out what they are (or you can also just read the name on the road...). At least there's something on the motorways so they don't just look naked. Even if the parkway shields are mostly illegible, they're still quite an improvement over Google Maps (which uses the parkways' unsigned 900x route numbers) and Bing and MapQuest (nothing other than the road name at higher zoom levels). Thanks for your attention to detail! We're putting the shield images in the public domain (well, we're putting them under a CC0 waiver, which amounts to the same thing semantically), so I don't think the "Kentucky Unbridled" image would be compatible with that. I just went with an italic font. (It's not like you can tell at these resolutions, anyway.) One way to simplify them would be to use the routes' two-letter abbreviations. NE2 suggested this for New York's parkways, too. I want to see how the current shields are received now that you can zoom in and see more detail on them, but using the routes' initials is certainly a possibility if no one likes their current incarnation. On second thought, some of the Kentucky parkways' abbreviations require a little guessing anyways, so maybe the spelled-out images are good enough. Someone who tries to navigate based on this map will say "that blue and white sign with tiny text", which is exactly how they'll see it on guide signs. Adding to the mess, the AA Highway is a special case that I *think* belongs in `network=US:KY` as `ref=AA`. I've added that, too. The network=US:KY, ref=AA relation does not appear to include all of the ways with the name "AA Highway" (it looks like the relation ends somewhere around KY 2828). I'll get right to it. By the way, four-digit circle shields appear to have broken over the last day or two: http://elrond.aperiodic.net/mtiles/cutouts/12/1081/1569.png -- Minh Nguyen AIM: trycom2000; Jabber: m...@1ec5.org; Blog: http://notes.1ec5.org/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] importing bus stops
Hey guys sorry I haven't been paying more attention to this of late, but I wanted to help as I did do a rather large bus import in the Massachusetts area that seemed go off fine (nobody complained to me at least). First I would recommend looking at the Google transit feed files for the UTA rather then the state gis layer. If Utah gis is anything like massgis then the their official gis layer is just based on an out of date gtfs, you can grab the most up to date uta gtfs here http://www.gtfs-data-exchange.com/agency/utah-transit-authority/latest.zip and it's from 4/6/12. The main advantage of this was that it gave ref tags that could theoretically be hooked in to the real time transport data. If your interested I can give you slightly more details about how I did that import. -- Calvin Metcalf Massachusetts Department of Transportation Office of Transportation Planning 617.973.7027 >-Original Message- >From: Paul Norman [mailto:penor...@mac.com] >Sent: Wednesday, April 11, 2012 12:52 AM >To: 'Martijn van Exel'; 'OpenStreetMap US Talk' >Subject: Re: [Talk-us] importing bus stops > >> From: Martijn van Exel [mailto:mve...@gmail.com] >> Subject: [Talk-us] importing bus stops >> >> Hi, >> >> Anyone here with experience importing bus stops? Any particular >> considerations? >> >> To make it more concrete, I have permission to import all UTA stops. >> They come in a shapefile similar to the one available for >download here: >> >> http://gis.utah.gov/sgid-vector-download/utah-sgid-vector-gis-data- >> layer-download-index?fc=BusStops_UTA >> >> (That particular set of files is out of date, though) >> >> There's a number of properties that would map to OSM nodes pretty >> nicely: >> MAILBOX -> create a separate node amenity= LIGHT -> lit=yes >SHELTER -> >> shelter=yes BENCH -> bench=yes (?) > >Unfortunately, all of these attributes are null. > >> >> I was planning to just use what I know which is >highway=bus_stop for the >> bus stops, and railway=tram_stop for the light rail stops. > >What differentiates them in the shapefile? I don't know the >area so I don't >know where there are any light rail stops > >> >> To get back on topic, if anyone wants to help out devise a >mapping from >> UTA stops file to OSM, I'd welcome some help. I've never done a local >> import before, and I'm not a particularly big fan of >imports, so I want >> to proceed with caution. > >I threw together a draft translation file at >https://github.com/pnorman/ogr2osm-translations/blob/master/utahbus.py > >To go farther, a local would need to provide some knowledge. > >1. Are there unique ref numbers on the stops? Every bus stop here has a >unique ID on its sign. If so, do these correspond to LOCATIONID? > >2. What are the names of some bus stops? If they're named by the street >they're on and the cross-street it should be possible to >construct a name >from the shapefile for each stop. (e.g. northbound far side >1st ave and main >street) > >3. The shapefile appears to have address data for each stop. Should the >addr:*=* information be added? > >I also noticed a couple of other things when looking at the data. > >The spatial accuracy is decent. Some stops are a few meters >off and on the >road, not the sidewalk, but they're all near the shelters that >I can see. > >Conflating this data with the existing data will be the hard >part. If there >hasn't been too much manual mapping of bus stops this could be >done by hand. >If there has, then you need to look at how to conflate the data. > > > >___ >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] Network tag Re: Highway Shield Rendering
* Paul Johnson [2012-04-11 17:33 -0700]:
> On Apr 11, 2012 11:48 AM, "Phil! Gold" wrote:
> > From what I've read, all US highways in California should get similar
> > treatment, in that they're signed with different shields than the standard
> > ones. Are there other regional sign variants for broader road networks in
> > the US (or elsewhere)?
>
> Some US highways (segments of US 75A for sure) and many state highways
> feature generic white circle state route signage, though it's not clear to
> me if this was deliberate or a case of sign shop error, or older signs not
> yet replaced, respectively.
I think I'd prefer to ignore unusual or one-off sign variations like
those. Let me put it this way: Are there any other places where a local
organization responsible for making and placing signs along a route has an
official policy of placing signs that differ significantly in appearance
from the signs used along the rest of the network? US Business routes in
Maryland meet these criteria. Where else is this true?
--
...computer contrarian of the first order... / http://aperiodic.net/phil/
PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2
--- --
main(a){printf(a="main(a){printf(a=%c%s%c,34,a,34);}",34,a,34);}
--- --
___
Talk-us mailing list
Talk-us@openstreetmap.org
http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Highway Shield Rendering
* Minh Nguyen [2012-04-12 00:09 -0700]: > Thanks for your attention to detail! You're welcome. :) > By the way, four-digit circle shields appear to have broken over the > last day or two. Indeed they were. It should be fixed now, pending a rerender. (A few days ago, I changed the shield generating mechanism from pregenerating every shield and every known cluster (in every possible orientation) and saving them in directories--to only pregenerating every individual shield (which is still almost 45,000 images), storing them in the database, and letting the database generate the clusters on demand. With the old system, we'd been cheating a little with the circle- and lozenge-style shields by generating two sets of images (one with circles for all numbers from 1 to , and one with circles for 1 to 99 and lozenges for 100 to ) and then symlinking states to those as appropriate. With the new setup, we have to generate all the shields for each state individually and I just didn't go high enough for Kentucky. I've now generated shields for Kentucky up to 3999, which should cover everything I see in the database. Wikipedia lists 9006 and 9008, but it looks like those are unsigned reference numbers for some of the parkways.) -- ...computer contrarian of the first order... / http://aperiodic.net/phil/ PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 --- -- You know you're really somebody in the software world when Richard Stallman complains about you having a gratuitous patent -- Source unknown --- -- ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Highway Shield Rendering
You need to create shields up to at least in the 6000 range for Kentucky. The reason I'm saying this is that the have a 6000 series for small service roads. 99% of the them they aren't posted, but there are a few that I discovered while working on overhauling my Kentucky files for the CHM project (my personal KY page here - http://cmap.m-plex.com/stat/region.php?u=rickmastfan67&c=usa&rg=ky&du=mi&sort=ra). I can't seem to find my list that I compiled that listed all of the posted 6000 series routes right now, but I do know that at least KY-6011 is posted (Streetview - http://g.co/maps/23mpe). So, on the safe side for the KY routes, I would create shields up to at least 6299 so that when people get around to properly tagging the 6000 series, they will be rendered when necessary. -- James > Date: Thu, 12 Apr 2012 08:29:22 -0400 > From: phi...@pobox.com > To: talk-us@openstreetmap.org > Subject: Re: [Talk-us] Highway Shield Rendering > > * Minh Nguyen [2012-04-12 00:09 -0700]: > > Thanks for your attention to detail! > > You're welcome. :) > > > By the way, four-digit circle shields appear to have broken over the > > last day or two. > > Indeed they were. It should be fixed now, pending a rerender. (A few > days ago, I changed the shield generating mechanism from pregenerating > every shield and every known cluster (in every possible orientation) and > saving them in directories--to only pregenerating every individual shield > (which is still almost 45,000 images), storing them in the database, and > letting the database generate the clusters on demand. With the old > system, we'd been cheating a little with the circle- and lozenge-style > shields by generating two sets of images (one with circles for all numbers > from 1 to , and one with circles for 1 to 99 and lozenges for 100 to > ) and then symlinking states to those as appropriate. With the new > setup, we have to generate all the shields for each state individually and > I just didn't go high enough for Kentucky. I've now generated shields for > Kentucky up to 3999, which should cover everything I see in the database. > Wikipedia lists 9006 and 9008, but it looks like those are unsigned > reference numbers for some of the parkways.) > > -- > ...computer contrarian of the first order... / http://aperiodic.net/phil/ > PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 > --- -- > You know you're really somebody in the software world when Richard > Stallman complains about you having a gratuitous patent >-- Source unknown > --- -- > > ___ > 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] Highway Shield Rendering
* James Mast [2012-04-12 09:40 -0400]: > You need to create shields up to at least in the 6000 range for > Kentucky. The reason I'm saying this is that the have a 6000 series for > small service roads. [snip] > So, on the safe side for the KY routes, I would create shields up to at > least 6299 so that when people get around to properly tagging the 6000 > series, they will be rendered when necessary. Are there any roads in the 4000s or 5000s? If not, I can skip those and just do the range from 6000 to 6299. -- ...computer contrarian of the first order... / http://aperiodic.net/phil/ PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 --- -- I think... I think it's in my basement... Let me go upstairs and check. -- Escher --- -- ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Network tag Re: Highway Shield Rendering
On Thu, Apr 12, 2012 at 5:01 AM, Phil! Gold wrote: > * Paul Johnson [2012-04-11 17:33 -0700]: >> On Apr 11, 2012 11:48 AM, "Phil! Gold" wrote: >> > From what I've read, all US highways in California should get similar >> > treatment, in that they're signed with different shields than the standard >> > ones. Are there other regional sign variants for broader road networks in >> > the US (or elsewhere)? >> >> Some US highways (segments of US 75A for sure) and many state highways >> feature generic white circle state route signage, though it's not clear to >> me if this was deliberate or a case of sign shop error, or older signs not >> yet replaced, respectively. > > I think I'd prefer to ignore unusual or one-off sign variations like > those. Let me put it this way: Are there any other places where a local > organization responsible for making and placing signs along a route has an > official policy of placing signs that differ significantly in appearance > from the signs used along the rest of the network? That's what I wasn't clear about above. Though Wikipedia's articles and the actual ground truth seems to show that what is signed as US 75A is actually OK 75A, since it seems Oklahoma considers US bannered/lettered routes as state highways and may not consistently sign it wholly as a state or US highway. Another highway with confusing inconsistencies would be US 412. Parts of it include: - Cherokee Turnpike (signed as Cherokee Turnpike, not signed as US412). - US 412 Scenic (old US 412, a loop bypassing the Cherokee Turnpike, the "last free exit" in both directions where the turnpike starts; signed as US 412S or US 412 Scenic). - OK 412A (not sure of signage, but is definitely related to US 412; may actually be US 412 Alternate) - OK 412B (not sure of signage, but is definitely related to US 412; may actually be US 412 Business) - OK 412P (signed as OK 412P, definitely a spur of US 412 at the Arkansas River Navigation System; may actually be US 412 Port) Arkansas seems to have similar quirks to Oklahoma on US highways between the Cherokee border and Bentonville; not sure if this is regionalistic signage issues or if the business/alternate/port/scenic roads are really state highways as a result. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Highway Shield Rendering
There's an ALT I-75 that needs its own sequence file: http://www.openstreetmap.org/browse/relation/2118037 It'd look like this: http://roadfan.com/altn75c.JPG -- Minh Nguyen AIM: trycom2000; Jabber: m...@1ec5.org; Blog: http://notes.1ec5.org/ ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Highway Shield Rendering
* Minh Nguyen [2012-04-12 10:06 -0700]: > There's an ALT I-75 that needs its own sequence file I had no idea there were alternate Interstates. I added it under network=US:I:Alternate, ref=75. (Right now, it's rendering as regular I-75.) -- ...computer contrarian of the first order... / http://aperiodic.net/phil/ PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 --- -- Hydrogen is a colorless, odorless gas which, given enough time, turns into people. -- Henry Hiebert --- -- ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Highway Shield Rendering
On 4/12/2012 2:59 PM, Phil! Gold wrote: * Minh Nguyen [2012-04-12 10:06 -0700]: There's an ALT I-75 that needs its own sequence file I had no idea there were alternate Interstates. I added it under network=US:I:Alternate, ref=75. (Right now, it's rendering as regular I-75.) Sounds like a bug in the rendering. However, I wouldn't necessarily oppose a separate network tag in this case, since it's clearly not part of the Interstate Highway System. (The same would apply to business Interstates.) Michigan has some 'emergency' Interstates that are essentially detours, but are permanently signed: http://www.stopandgo.org/gallery/trafficsigns/Emergency_plaque.html There's also an I-278 Truck in New York City that avoids a piece of the Grand Central Parkway that's closed to large trucks: http://www.openstreetmap.org/browse/relation/2131889 ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Highway Shield Rendering
On Thu, Apr 12, 2012 at 03:52:35PM -0400, Nathan Edgars II wrote: > On 4/12/2012 2:59 PM, Phil! Gold wrote: > >* Minh Nguyen [2012-04-12 10:06 -0700]: > >>There's an ALT I-75 that needs its own sequence file > > > >I had no idea there were alternate Interstates. I added it under > >network=US:I:Alternate, ref=75. (Right now, it's rendering as regular > >I-75.) > > Sounds like a bug in the rendering. > > > However, I wouldn't necessarily oppose a separate network tag in > this case, since it's clearly not part of the Interstate Highway > System. (The same would apply to business Interstates.) > > Michigan has some 'emergency' Interstates that are essentially > detours, but are permanently signed: > http://www.stopandgo.org/gallery/trafficsigns/Emergency_plaque.html Yeah, those are odd. What the description on that page fails to mention is that I-94 also passes by the Cook Nuclear Power Plant at Bridgman, so it's not just snow MDOT is worried about :-) -- Kristian M Zoerhoff ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Highway Shield Rendering
On 4/12/2012 3:52 PM, Nathan Edgars II wrote: There's also an I-278 Truck in New York City that avoids a piece of the Grand Central Parkway that's closed to large trucks: http://www.openstreetmap.org/browse/relation/2131889 Also I-270 Spur in Maryland, which *is* part of the Interstate Highway System and thus belongs in network=US:I: http://www.openstreetmap.org/browse/relation/1685926 ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Highway Shield Rendering
On Thu, Apr 12, 2012 at 1:02 PM, Kristian M Zoerhoff wrote: > On Thu, Apr 12, 2012 at 03:52:35PM -0400, Nathan Edgars II wrote: >> On 4/12/2012 2:59 PM, Phil! Gold wrote: >> >* Minh Nguyen [2012-04-12 10:06 -0700]: >> >>There's an ALT I-75 that needs its own sequence file >> > >> >I had no idea there were alternate Interstates. I added it under >> >network=US:I:Alternate, ref=75. (Right now, it's rendering as regular >> >I-75.) >> >> Sounds like a bug in the rendering. >> >> >> However, I wouldn't necessarily oppose a separate network tag in >> this case, since it's clearly not part of the Interstate Highway >> System. (The same would apply to business Interstates.) >> >> Michigan has some 'emergency' Interstates that are essentially >> detours, but are permanently signed: >> http://www.stopandgo.org/gallery/trafficsigns/Emergency_plaque.html > > Yeah, those are odd. What the description on that page fails to mention is > that I-94 also passes by the Cook Nuclear Power Plant at Bridgman, so it's > not just snow MDOT is worried about :-) How should we tag routes like this? Oregon has a few "Detour I-5" routes on smaller (often two-lane county roads) roads where all lanes get sent the same direction when some dork talking on their cellphone while driving gets creamed on the motorway route that are posted (and often have some normally gated routes that round off what would normally be a four-way stop). ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Excellent progress, u.s.
Hey, us, vaguely northamerican OSMers: nice work so far! I see excellent progress in California during the recent eight days of re-mapping. If you are an editing maniac (like me in the last few days) you have discovered that BADMAP lag makes you move onto another region. I have chased myself over much of San Diego and patched up the old home town. Its freeways now emerge as navigable. The Bay Area shapes up nicely. Greater Southern California shows vast improvement, and yet there is still so much more to do. We are so many people, loving what we do so hard. Just a pat on the back and bit of cheer-leading. Now get back to work! (Oops, I mean the fun of OSM). SteveA California ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Excellent progress, u.s.
On Thu, Apr 12, 2012 at 7:36 PM, stevea wrote: > Hey, us, vaguely northamerican OSMers: nice work so far! > > I see excellent progress in California during the recent eight days of > re-mapping. If you are an editing maniac (like me in the last few days) you > have discovered that BADMAP lag makes you move onto another region. I have > chased myself over much of San Diego and patched up the old home town. Its > freeways now emerge as navigable. The Bay Area shapes up nicely. Greater > Southern California shows vast improvement, and yet there is still so much > more to do. > > We are so many people, loving what we do so hard. > > Just a pat on the back and bit of cheer-leading. Now get back to work! > (Oops, I mean the fun of OSM). +1 I have noticed several people's remapping efforts in my live edit viewer. Over towards the east, I see long stretches of interstate around Columbia, SC have vanished from badmap. Thanks to Paul's efforts on highlighting coastline problems, that is mostly clean now. There is still a bit of work to do in Washington. The Pacific coastline should be clean now (I reimported most of it from NHD) but some bays and Puget Sound in particular are still problematic. It's kind of disconcerting not actually knowing when the license bot will be set loose. Before April 1 I was going all out. Now I have relaxed a little but am still doing a few edits each night. We'll get there eventually. Whether or not it happens before or after the bot does its work remains to be seen :) Toby ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Highway Shield Rendering
I couldn't find any Kentucky State Routes that are in the 4000's and 5000's. So, you should be able to get away with just doing the 6000-series shields. As far as I can tell, currently, they only go up to KY-6334 (per http://bunkerblast.info/roads/sric.html). Now, not all of these 6000-series highways are posted, so, I would just create shields in the range of 6000-6500. I don't see them ever going over 6500 to be honest any time in the future. -- James > Date: Thu, 12 Apr 2012 10:10:26 -0400 > From: phi...@pobox.com > To: talk-us@openstreetmap.org > Subject: Re: [Talk-us] Highway Shield Rendering > > * James Mast [2012-04-12 09:40 -0400]: > > You need to create shields up to at least in the 6000 range for > > Kentucky. The reason I'm saying this is that the have a 6000 series for > > small service roads. > [snip] > > So, on the safe side for the KY routes, I would create shields up to at > > least 6299 so that when people get around to properly tagging the 6000 > > series, they will be rendered when necessary. > > Are there any roads in the 4000s or 5000s? If not, I can skip those and > just do the range from 6000 to 6299. > > -- > ...computer contrarian of the first order... / http://aperiodic.net/phil/ > PGP: 026A27F2 print: D200 5BDB FC4B B24A 9248 9F7A 4322 2D22 026A 27F2 > --- -- > I think... I think it's in my basement... Let me go upstairs and check. >-- Escher > --- -- > > ___ > 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] Excellent progress, u.s.
> Date: Thu, 12 Apr 2012 21:56:49 -0500 > From: toby.mur...@gmail.com > To: stevea...@softworkers.com > CC: talk-us@openstreetmap.org > Subject: Re: [Talk-us] Excellent progress, u.s. > > I have noticed several people's remapping efforts in my live edit > viewer. Over towards the east, I see long stretches of interstate > around Columbia, SC have vanished from badmap. I don't know who's doing that work in Columbia on the Interstates, but they are doing it wrong unfortunately. While the ways aren't "tainted" anymore, all of the nodes are still. Meaning that once the bot gets unleashed, the highways will still get "fucked-up". It seems that they are just starting a new way and connecting each old node to the new way without at least moving the old node, which means if Lar created the node and nobody has moved it since, it still will get deleted and mess up the highway alignment. -- James ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
