Re: [Talk-us] Newly tweaked TIGER road names tiles
Toby, We do have to be careful with these. An earlier effort created some incorrect tagging in the Four Corners area, where I map, --W Road (a county road in SW Colorado) ended up as West Road and S Road as South Road. --And, N36 (for Navajo 36) ended up as North 36, as did a lot of Navajo roads. It took me a while to figure out what was happening. Luckily I have a contact at Navajo Division of Transportation, who assured me they have no roads named North. I still find these from time to time, so a lot of incorrect tags were created. But, if you've got a good way to do it, great! It sure is tedious to do them manually. Charlotte At 01:40 PM 11/18/2012, you wrote: As we briefly discussed during the virtual mappy hour last week, I have managed to wrangle some TIGER data and do some automated expansion of abbreviated street names on the TIGER road name tiles. The results can be seen in a new tile layer. You can preview it here: http://tile.osm.osuosl.org/tiles/tiger2012_roads_expanded/preview.html#17/37.79816/-122.24627 I just added the appropriate URLs for the new layer to the TIGER 2012 page on the wiki so you can use them in JOSM and Potlatch as well: http://wiki.openstreetmap.org/wiki/TIGER_2012 Since this is a brand new tile layer, nothing is cached in the CDN so requests might be a little slower than normal at first. I am fairly certain about the accuracy of the process and the checks I have performed all came back with good results. But of course TIGER being such a large and varied data set, there might be an odd edge case lurking somewhere so it would be great if some people could check their areas and make sure they don't see anything odd. The other tweak I made after a suggestion from Ian was to draw the tiles in two layers. One drawn first with only lines and then another layer with only names on top of it. This means that road names will always appear on top of road lines. This avoids roads obscuring names and improves readability. Technical details: This was *not* done by doing simple string matching. I downloaded all of the Feature Names Relationship files which contain separate fields with codes for directional, type and qualifier prefixes/suffixes. Then I composed the name one element at a time from these fields. This gave me a mapping from TLID to expanded street name which I then imported into a new column in the existing table that is used to render the tiles. Then it was just a simple matter of telling the mapnik style to look at the new expanded name column. Toby ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us Charlotte Wolter 927 18th Street Suite A Santa Monica, California 90403 +1-310-597-4040 techl...@techlady.com Skype: thetechlady The Four Internet Freedoms Freedom to visit any site on the Internet Freedom to access any content or service that is not illegal Freedom to attach any device that does not interfere with the network Freedom to know all the terms of a service, particularly any that would affect the first three freedoms. ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Newly tweaked TIGER road names tiles
Oh, and they're flat out hosed in the Tulsa County area, particularly at the same latitude as Broken Arrow (TIGER carries Broken Arrow-specific street names into Tulsa City improperly). On Mon, Nov 19, 2012 at 9:23 AM, Charlotte Wolter techl...@techlady.comwrote: Toby, ****We do have to be careful with these. An earlier effort created some incorrect tagging in the Four Corners area, where I map, ****--W Road (a county road in SW Colorado) ended up as West Road and S Road as South Road. ****--And, N36 (for Navajo 36) ended up as North 36, as did a lot of Navajo roads. It took me a while to figure out what was happening. Luckily I have a contact at Navajo Division of Transportation, who assured me they have no roads named North. ****I still find these from time to time, so a lot of incorrect tags were created. ****But, if you've got a good way to do it, great! It sure is tedious to do them manually. Charlotte At 01:40 PM 11/18/2012, you wrote: As we briefly discussed during the virtual mappy hour last week, I have managed to wrangle some TIGER data and do some automated expansion of abbreviated street names on the TIGER road name tiles. The results can be seen in a new tile layer. You can preview it here: http://tile.osm.osuosl.org/tiles/tiger2012_roads_expanded/preview.html#17/37.79816/-122.24627 I just added the appropriate URLs for the new layer to the TIGER 2012 page on the wiki so you can use them in JOSM and Potlatch as well: http://wiki.openstreetmap.org/wiki/TIGER_2012 Since this is a brand new tile layer, nothing is cached in the CDN so requests might be a little slower than normal at first. I am fairly certain about the accuracy of the process and the checks I have performed all came back with good results. But of course TIGER being such a large and varied data set, there might be an odd edge case lurking somewhere so it would be great if some people could check their areas and make sure they don't see anything odd. The other tweak I made after a suggestion from Ian was to draw the tiles in two layers. One drawn first with only lines and then another layer with only names on top of it. This means that road names will always appear on top of road lines. This avoids roads obscuring names and improves readability. Technical details: This was *not* done by doing simple string matching. I downloaded all of the Feature Names Relationship files which contain separate fields with codes for directional, type and qualifier prefixes/suffixes. Then I composed the name one element at a time from these fields. This gave me a mapping from TLID to expanded street name which I then imported into a new column in the existing table that is used to render the tiles. Then it was just a simple matter of telling the mapnik style to look at the new expanded name column. Toby ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us ** ** Charlotte Wolter 927 18th Street Suite A Santa Monica, California 90403 +1-310-597-4040 techl...@techlady.com Skype: thetechlady *The Four Internet Freedoms* Freedom to visit any site on the Internet Freedom to access any content or service that is not illegal Freedom to attach any device that does not interfere with the network Freedom to know all the terms of a service, particularly any that would affect the first three freedoms. ___ 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] Newly tweaked TIGER road names tiles
THIS HAS NOTHING TO DO WITH EXPANDING NAMES ALREADY IN OSM! Please read my email again. All I did was update the TIGER 2012 road name tiles. I am not touching OSM data at all! But please do take a look at the road name tiles in the areas you have mentioned and see if they are correct. Cases that were incorrectly handled before are an interesting test for the new tiles. Toby On Mon, Nov 19, 2012 at 9:32 AM, Paul Johnson ba...@ursamundi.org wrote: Oh, and they're flat out hosed in the Tulsa County area, particularly at the same latitude as Broken Arrow (TIGER carries Broken Arrow-specific street names into Tulsa City improperly). On Mon, Nov 19, 2012 at 9:23 AM, Charlotte Wolter techl...@techlady.com wrote: Toby, We do have to be careful with these. An earlier effort created some incorrect tagging in the Four Corners area, where I map, --W Road (a county road in SW Colorado) ended up as West Road and S Road as South Road. --And, N36 (for Navajo 36) ended up as North 36, as did a lot of Navajo roads. It took me a while to figure out what was happening. Luckily I have a contact at Navajo Division of Transportation, who assured me they have no roads named North. I still find these from time to time, so a lot of incorrect tags were created. But, if you've got a good way to do it, great! It sure is tedious to do them manually. Charlotte At 01:40 PM 11/18/2012, you wrote: As we briefly discussed during the virtual mappy hour last week, I have managed to wrangle some TIGER data and do some automated expansion of abbreviated street names on the TIGER road name tiles. The results can be seen in a new tile layer. You can preview it here: http://tile.osm.osuosl.org/tiles/tiger2012_roads_expanded/preview.html#17/37.79816/-122.24627 I just added the appropriate URLs for the new layer to the TIGER 2012 page on the wiki so you can use them in JOSM and Potlatch as well: http://wiki.openstreetmap.org/wiki/TIGER_2012 Since this is a brand new tile layer, nothing is cached in the CDN so requests might be a little slower than normal at first. I am fairly certain about the accuracy of the process and the checks I have performed all came back with good results. But of course TIGER being such a large and varied data set, there might be an odd edge case lurking somewhere so it would be great if some people could check their areas and make sure they don't see anything odd. The other tweak I made after a suggestion from Ian was to draw the tiles in two layers. One drawn first with only lines and then another layer with only names on top of it. This means that road names will always appear on top of road lines. This avoids roads obscuring names and improves readability. Technical details: This was *not* done by doing simple string matching. I downloaded all of the Feature Names Relationship files which contain separate fields with codes for directional, type and qualifier prefixes/suffixes. Then I composed the name one element at a time from these fields. This gave me a mapping from TLID to expanded street name which I then imported into a new column in the existing table that is used to render the tiles. Then it was just a simple matter of telling the mapnik style to look at the new expanded name column. Toby ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us Charlotte Wolter 927 18th Street Suite A Santa Monica, California 90403 +1-310-597-4040 techl...@techlady.com Skype: thetechlady The Four Internet Freedoms Freedom to visit any site on the Internet Freedom to access any content or service that is not illegal Freedom to attach any device that does not interfere with the network Freedom to know all the terms of a service, particularly any that would affect the first three freedoms. ___ 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] Newly tweaked TIGER road names tiles
On 11/19/12 10:41 AM, Toby Murray wrote: THIS HAS NOTHING TO DO WITH EXPANDING NAMES ALREADY IN OSM! Please read my email again. All I did was update the TIGER 2012 road name tiles. I am not touching OSM data at all! But please do take a look at the road name tiles in the areas you have mentioned and see if they are correct. Cases that were incorrectly handled before are an interesting test for the new tiles. i have seen/repaired these expansion errors in the Nevada, Iowa area last year. i just double checked the expanded TIGER 2012 tiles for the area, and the expansion algorithm did the right thing. richard ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Feature proposal: proposed expanded address tagging scheme for US
* Steven Johnson sejohns...@gmail.com [2012-11-17 18:45 -0500]: http://wiki.openstreetmap.org/wiki/Proposed_features/House_numbers/UnitedStates From my perspective, addr:street_prefix and addr:street_type don't seem that useful, since I don't see how they add information that's useful to data consumers and they require extra work from data contributers. If I understand things, the proposal would take a way tagged with name=Old Frederick Road and add addr:street_prefix=Old, addr:street_type=Road. What benefit is there to that? (Put differently, what motivation can you give to convince mappers that it's worth their time to add those tags on every road whose name they modify?) It's also worth considering how a tagging scheme can be broken. It's not uncommon for contributors to edit one tag and fail to notice related tags on the same object. How would you suggest handling, say, name=Wentworh Avenue, addr:street_type=Road? I do think there's a use case for directional prefixes that are not strictly part of the road name, but are instead for addressing. Many parts of the US have roads with addresses of the form 10 North Something Street where the road signs emphasize Something Street and the North or South parts are less visible. (I've seen many roads in my area where the signs for such roads are not even consistent in terms of whather it's a prefix or suffix; adjacent signs might show both N Something St and Something St N.) In these cases, I think it would be beneficial to have tagging of the form name=Something Street, addr:direction=North so routers can tell people things like, Turn left on Something Street, which reflects the signage, but geocoders can figure out where addresses are likely to be even in the absence of complete address information. (This sort of usage would require proposing changes to address tagging, as well as road tagging.) ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Newly tweaked TIGER road names tiles
Looks good to me! Would it be possible to get this added to the list of default imagery layers in Potlatch? Or, ideally, to replace the TIGER 2011 layer? It's a pain to have to add it in manually every time I start up Potlatch... Ben ___ Talk-us mailing list Talk-us@openstreetmap.org http://lists.openstreetmap.org/listinfo/talk-us
