Re: [Talk-us] Road abbreviations
Sounds like you fixed this quickly. Would you mind explaining the steps in detail you took to achieve this? Thanks On Thu, Aug 14, 2014 at 9:04 PM, Nick Hocking nick.hock...@gmail.com wrote: stevea wrote, though there are problems in the west, like Las Vegas Ok - I think I've fixed all of these in Las Vegas (there were a few thousand). It's amazing how simple they are to find using the overpass api (and overpass turbo). Nick ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Keith wrote
Sounds like you fixed this quickly. Would you mind explaining the steps in
detail you took to achieve this? Thanks
I decided to use a set of common abbreviations of
Ct
St
Ave
Dr
Ln
Pl
Pkwy
Cl
Cir
Rd
In Australia I'd propably add Cct (Circuit) to the list.
Then for the first Ct which is Court I went to overpass-turbo.eu and
ran the query of
query type=way
has-kv k=name regv= [Cc][Tt]$/
bbox-query {{bbox}}/!--this is auto-completed with the
current map view coordinates.--
/query
union
item/
recurse type=down/
/union
print/
This shows all the ways whose name ends in a space followed by ct (in any
capitalization).
With this map in one window and JOSM in another window, I then located the
first Ct in the Josm window and edited it manually to be Court
Often there was a *nest* of abbreviations (St Ln Pl etc...) in the same
neighbourhood, so having fixed one way I would hav a quick look around that
area. and fix any other abbreviations I found. Then on to the next Ct.
I generally worked my way west to east and north to south.
Once I had cleared up all the Ct (rerunning the operpass query verifies
this) I then started on the St (Streets). About30 or 40 hours later Las
Vegas was fixed.
What I will now do I export to CSV all the Las Vegas Road names, then grep
out all the good ones (I.E Court, Street, Road) and see what's left.
Any typos I've made while editing (E.G Ctourt) and any ways without
suffixes will be left and I can investigate if they can be improved or not
(from TIGER 2013).
You'll notice that no bots were run in the making of these fixes. This is
for two reasons. Firstly I'm not a fan of bots since they make assumptions
which may not always be true. Secondly, manual editing in JOSM with the
TIGER 2013 and OSM data showing, means that I found quite a few missing
road names in OSM. Also I found quite a few missing roads and If both TIGER
and Bing imagery agreed about the road then I added in the road.
I also found a few typos along the way which I could fix as well.
Ie always found that desk checking against another source (like TIGER) and
entire city results in massive improvements. Any city I've mapped I always
desk check against another source and inevitably find lots of typos to fix.
Nick
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Nick,
I have been following the discussion about road name abbreviations and wanted
to chime in.
I agree with you that bots miss stuff AND goof up in silly ways. A CLASSIC
example of a bot mistake is “Street Joseph Street”. This example has been fixed
by a participant in a MapRoulette name fixing challenge. But as you can see
below, a bot updated the street name from “St Joseph St” to “Street Joseph
Street”. Example below:
http://www.openstreetmap.org/way/13597392/history
For sure fixing names automatically can save time. But you can only correct so
much with the implemented bot logic and sometimes make mistakes (what you’re
analyzing might not be what you’re expecting). As my co-worker has said,
humans are the best pattern, spelling error catchers.
It’s pleasing to know you’re taking the time to expand abbreviations and
correct other data errors along the way. Keep it up!
Best,
Kristen
---
Kristen Kam
OSM Profile -- http://www.openstreetmap.org/user/KristenK
From: Nick Hocking [mailto:nick.hock...@gmail.com]
Sent: Friday, August 15, 2014 2:14 PM
To: talk-us@openstreetmap.org
Subject: Re: [Talk-us] Road abbreviations
Keith wrote
Sounds like you fixed this quickly. Would you mind explaining the steps in
detail you took to achieve this? Thanks
I decided to use a set of common abbreviations of
Ct
St
Ave
Dr
Ln
Pl
Pkwy
Cl
Cir
Rd
In Australia I'd propably add Cct (Circuit) to the list.
Then for the first Ct which is Court I went to
overpass-turbo.euhttp://overpass-turbo.eu and ran the query of
query type=way
has-kv k=name regv= [Cc][Tt]$/
bbox-query {{bbox}}/!--this is auto-completed with the
current map view coordinates.--
/query
union
item/
recurse type=down/
/union
print/
This shows all the ways whose name ends in a space followed by ct (in any
capitalization).
With this map in one window and JOSM in another window, I then located the
first Ct in the Josm window and edited it manually to be Court
Often there was a *nest* of abbreviations (St Ln Pl etc...) in the same
neighbourhood, so having fixed one way I would hav a quick look around that
area. and fix any other abbreviations I found. Then on to the next Ct. I
generally worked my way west to east and north to south.
Once I had cleared up all the Ct (rerunning the operpass query verifies this)
I then started on the St (Streets). About30 or 40 hours later Las Vegas was
fixed.
What I will now do I export to CSV all the Las Vegas Road names, then grep out
all the good ones (I.E Court, Street, Road) and see what's left.
Any typos I've made while editing (E.G Ctourt) and any ways without suffixes
will be left and I can investigate if they can be improved or not (from TIGER
2013).
You'll notice that no bots were run in the making of these fixes. This is for
two reasons. Firstly I'm not a fan of bots since they make assumptions which
may not always be true. Secondly, manual editing in JOSM with the TIGER 2013
and OSM data showing, means that I found quite a few missing road names in OSM.
Also I found quite a few missing roads and If both TIGER and Bing imagery
agreed about the road then I added in the road.
I also found a few typos along the way which I could fix as well.
Ie always found that desk checking against another source (like TIGER) and
entire city results in massive improvements. Any city I've mapped I always
desk check against another source and inevitably find lots of typos to fix.
Nick
___
Talk-us mailing list
Talk-us@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
stevea wrote, though there are problems in the west, like Las Vegas Ok - I think I've fixed all of these in Las Vegas (there were a few thousand). It's amazing how simple they are to find using the overpass api (and overpass turbo). Nick ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
The United States Postal Service prefers addresses to be written with abbreviations used, and they maintain a list of official abbreviations. I suppose they really only care about addresses written on physical mail, but then again this is the primary purpose of mail addresses. I know of multiple examples of places where the street name in the official addresses of houses on a street does not exactly match the name of the street itself. There is therefore no reason to insist these values should match. My conclusion is that address data should appear in the data as it properly does on a piece of mail, which includes using USPS standard abbreviations, and deviating from the road name in other ways where the postmaster has prescribed such deviation. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
I would say the primary use of address data in OSM is geocoding, not mail delivery. There may be legitimate differences between a street name and the address of a house along that street but abbreviations are not a legitimate difference. The Census Bureau also has a list of 503 official abbreviations[1]. Which one should we use? The answer is: Neither. It is always easier to go from full names to abbreviations for display than to go the other way around. (See Mapquest tiles - they abbreviate street names) Therefore we should always store things un-abbreviated. No ambiguity, no questions about which list of abbreviations, no one making their own abbreviations. Everything is explicit. [1] https://github.com/ToeBee/ogr2osm-translations/blob/master/tiger2012_abbrv.csv Toby On Wed, Aug 6, 2014 at 1:22 PM, David K vidthe...@gmail.com wrote: The United States Postal Service prefers addresses to be written with abbreviations used, and they maintain a list of official abbreviations. I suppose they really only care about addresses written on physical mail, but then again this is the primary purpose of mail addresses. I know of multiple examples of places where the street name in the official addresses of houses on a street does not exactly match the name of the street itself. There is therefore no reason to insist these values should match. My conclusion is that address data should appear in the data as it properly does on a piece of mail, which includes using USPS standard abbreviations, and deviating from the road name in other ways where the postmaster has prescribed such deviation. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
On Wed, Aug 6, 2014 at 12:08 PM, Toby Murray toby.mur...@gmail.com wrote: The answer is: Neither. It is always easier to go from full names to abbreviations for display than to go the other way around. (See Mapquest tiles - they abbreviate street names) Therefore we should always store things un-abbreviated. No ambiguity, no questions about which list of abbreviations, no one making their own abbreviations. Everything is explicit. +1 -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Afternoon, I concur with Toby+Clifford. I had a discussion with a coworker about road name abbreviations in OSM. He came across an existing OSM wiki page that contains a lookup table that maps the full word (street type or general place) to an abbreviation (mostly USPS): · http://wiki.openstreetmap.org/wiki/Name_finder:Abbreviations#English Additionally, the USPS publishes their official abbreviations: · https://www.usps.com/send/official-abbreviations.htm These accepted and documented abbreviation practices can be used by end-users when processing the OSM data for display purposes. Best, Kristen --- Kristen Kam OSM Profile -- http://www.openstreetmap.org/user/KristenK From: Clifford Snow [mailto:cliff...@snowandsnow.us] Sent: Wednesday, August 06, 2014 1:14 PM To: Toby Murray Cc: talk-us Subject: Re: [Talk-us] Road abbreviations On Wed, Aug 6, 2014 at 12:08 PM, Toby Murray toby.mur...@gmail.commailto:toby.mur...@gmail.com wrote: The answer is: Neither. It is always easier to go from full names to abbreviations for display than to go the other way around. (See Mapquest tiles - they abbreviate street names) Therefore we should always store things un-abbreviated. No ambiguity, no questions about which list of abbreviations, no one making their own abbreviations. Everything is explicit. +1 -- @osm_seattle osm_seattle.snowandsnow.ushttp://osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
On Aug 6, 2014 3:09 PM, Toby Murray toby.mur...@gmail.com wrote: I would say the primary use of address data in OSM is geocoding, not mail delivery. And in far too many other contexts as well. Except for the fact that so much collective effort has already been made (yet much remains) toward perfecting the task of geocoding by mail address, one might as well geocode by telephone number. I can accept that this is how it is, but I'll never agree that this is how it should be. ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Stecea wrote though there are problems in the west, like Las Vegas Hi, I've just come back from a holiday to Las Vegas where I surveyed as many unamed streets and new neighbourhoods (that are not named in TIGER 2013) as I could find. Hopefully this means that OSM now has the best road data of Las Vegas on the planet, although some gated communities still have unnamed streets. Now that I am reduced back to armchair mapping, I may as well get started on expanding all the abbreviated street names in Las Vegas from Paul's excellent overlay. Should keep me busy for a couple on months!! Cheers Nick ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
On 2014-08-01 00:23, Paul Norman wrote: A bit of PostgreSQL and CartoCSS later, and I have an overlay showing all the abbreviated roads: http://tile.paulnorman.ca/demo/abbreviated.html. This layer is *not* live updated. Most of the roads are in the eastern United States, with small clusters around some cities in the West. Great resource. I have fixed most of the cluster around South San Francisco/San Bruno, CA /Stellan ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Once again, Paul: nice overlay! It is very impressive what can be whipped up (and rather quickly!) with OSM data and clever use of tools. Such visualizations give the OSM community an excellent method to identify, prioritize and potentially assign/do fixups in our data. I encourage others to look at Paul's overlay and make suggestions, especially if you are local to or map in one of the areas with red lines representing road name abbreviations. Looking at San Diego, I see fewer than a dozen red roads, most around the Marine Corps base, but not bad at all. Yes, it seems worst in the east (ern USA) in clusters, though there are problems in the west, like Las Vegas, SW of Eugene, Oregon, around Denver and other parts of Colorado, and NE Wyoming (?!). I realize that this is a quick(er) solution and that more thought might need to go into any bot's logic that identifies problematic street names, but this overlay/visualization is a great initial result and should be pursued further. Thanks for everybody's efforts! SteveA California On 7/30/2014 6:18 PM, Serge Wroclawski wrote: Paul, Yeah, I'm just trying to figure out where the problems are- not trying to dig deeply into them yet- I'm looking for clusters of problems (ie San Diego), or I heard about a problem in Michigan where someone decided to revert a bunch of the bot-mode changesets because he didn't like the way they rendered, so in this case, I'd just look for some known contractions at the end. We may change that later, but that's where I'd start. A bit of PostgreSQL and CartoCSS later, and I have an overlay showing all the abbreviated roads: http://tile.paulnorman.ca/demo/abbreviated.html. This layer is *not* live updated. Strictly speaking, this is not road only, and may include other features. It has names ending in rd, st, bvld, ave or av, with the first letter lower-case or upper case and with or without a period at the very end. This is a total of about 69000 roads. Most of the roads are in the eastern United States, with small clusters around some cities in the West. Places outside the US with noticable numbers of abbreviated roads include: Vancouver, BC; Trinidat and Tobago; Philippines; Chennai, India. Technical note: The layer is generating 500 errors for tiles with nothing on them. This shouldn't impact its use. From a Vancouver perspective, a lot of the abbreviated roads will require a ground survey, because the rest of their name is frequently wrong (e.g. three roads named 22 av instead of 22 Avenue, 22A Avenue and 22B Avenue). ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
On 7/30/2014 6:18 PM, Serge Wroclawski wrote: Paul, Yeah, I'm just trying to figure out where the problems are- not trying to dig deeply into them yet- I'm looking for clusters of problems (ie San Diego), or I heard about a problem in Michigan where someone decided to revert a bunch of the bot-mode changesets because he didn't like the way they rendered, so in this case, I'd just look for some known contractions at the end. We may change that later, but that's where I'd start. A bit of PostgreSQL and CartoCSS later, and I have an overlay showing all the abbreviated roads: http://tile.paulnorman.ca/demo/abbreviated.html. This layer is *not* live updated. Strictly speaking, this is not road only, and may include other features. It has names ending in rd, st, bvld, ave or av, with the first letter lower-case or upper case and with or without a period at the very end. This is a total of about 69000 roads. Most of the roads are in the eastern United States, with small clusters around some cities in the West. Places outside the US with noticable numbers of abbreviated roads include: Vancouver, BC; Trinidat and Tobago; Philippines; Chennai, India. Technical note: The layer is generating 500 errors for tiles with nothing on them. This shouldn't impact its use. From a Vancouver perspective, a lot of the abbreviated roads will require a ground survey, because the rest of their name is frequently wrong (e.g. three roads named 22 av instead of 22 Avenue, 22A Avenue and 22B Avenue). ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
[Talk-us] Road abbreviations
I just came across a import of address data in San Diego. I checked the data and all of it is using road abbreviations. Is that normal? *Regards,* *Hans* *OpenStreetMapper - TheDutchMan13* ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
On Wed, Jul 30, 2014 at 12:22 AM, Hans De Kryger hans.dekryge...@gmail.com wrote: I just came across a import of address data in San Diego. I checked the data and all of it is using road abbreviations. Is that normal? Not normal nor acceptable. I would suggest sending a message to the importer asking them to stop and fix what they imported. As Serge suggested, send a link an area in San Diego with the bad formating. Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
I believe this was an import done in 2009. Here is an example changeset that is obviously an address import in the area: http://www.openstreetmap.org/changeset/3407483 The import is documented on the import catalog page[1] on the wiki and mentioned on the California imports page[2] as well. It isn't a recent rogue import so please don't send angry messages. This was done before the first TIGER name expansion bot was run (in 2010) so I'm not really sure if the no abbreviations consensus had been solidified at that point. But yeah, it should be fixed and it will take a bot to do so. Toby [1] http://wiki.openstreetmap.org/wiki/Import/Catalogue [2] http://wiki.openstreetmap.org/wiki/California/Import On Wed, Jul 30, 2014 at 9:32 AM, Clifford Snow cliff...@snowandsnow.us wrote: On Wed, Jul 30, 2014 at 12:22 AM, Hans De Kryger hans.dekryge...@gmail.com wrote: I just came across a import of address data in San Diego. I checked the data and all of it is using road abbreviations. Is that normal? Not normal nor acceptable. I would suggest sending a message to the importer asking them to stop and fix what they imported. As Serge suggested, send a link an area in San Diego with the bad formating. Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Toby, Thanks for the pointer. I think you're right that in this case especially, there's no reason to admonish anyone, but perhaps we can examine the data and see if there's a safe way to expand it, like we did the TIGER data. That may also explain some large portion of the contractions I found. Maybe it's worth trying to map them I'll have to spend some time with tilemill to get a visualization. - Serge On Wed, Jul 30, 2014 at 12:30 PM, Toby Murray toby.mur...@gmail.com wrote: I believe this was an import done in 2009. Here is an example changeset that is obviously an address import in the area: http://www.openstreetmap.org/changeset/3407483 The import is documented on the import catalog page[1] on the wiki and mentioned on the California imports page[2] as well. It isn't a recent rogue import so please don't send angry messages. This was done before the first TIGER name expansion bot was run (in 2010) so I'm not really sure if the no abbreviations consensus had been solidified at that point. But yeah, it should be fixed and it will take a bot to do so. Toby [1] http://wiki.openstreetmap.org/wiki/Import/Catalogue [2] http://wiki.openstreetmap.org/wiki/California/Import On Wed, Jul 30, 2014 at 9:32 AM, Clifford Snow cliff...@snowandsnow.us wrote: On Wed, Jul 30, 2014 at 12:22 AM, Hans De Kryger hans.dekryge...@gmail.com wrote: I just came across a import of address data in San Diego. I checked the data and all of it is using road abbreviations. Is that normal? Not normal nor acceptable. I would suggest sending a message to the importer asking them to stop and fix what they imported. As Serge suggested, send a link an area in San Diego with the bad formating. Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
On Wed, Jul 30, 2014 at 9:48 AM, Serge Wroclawski emac...@gmail.com wrote: Thanks for the pointer. I think you're right that in this case especially, there's no reason to admonish anyone, but perhaps we can examine the data and see if there's a safe way to expand it, like we did the TIGER data. That may also explain some large portion of the contractions I found. Maybe it's worth trying to map them I agree with Serge and Toby's post - this is old data that should be fixed. I pulled the data from a Mapzen city extract (San Diego Tijuana). There are 488,571 address points. Looking at OSMI, the whole area has addresses with abbreviated street names. Serge, anything I can do to help you with the expansion bot, just let me know. Knowing how to do this would help me down the road as we try to figure out how to update address info from my local county. Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Clifford, I think the thing right now is to really understand the problem in depth. The issues the community gets into and complains about regarding automated edits is when they come out wrong. For example, the expansion that was run before that was turning all E's into East. That's very bad and we need to make sure that doesn't happen. We have to make some tradeoffs between what we can reasonably assume and what we know absolutely to be true. For example, if I see Rd at the end of a highway=residential way, I'm pretty sure that is a contraction for Road. Of course if there's a street somewhere named Main Saint rather than Main Street, well, it will be wrong, and that will be bad, but hopefully this kind of problem can be minimized if we, for example, try to match the roads up with newer TIGER data road names and use the TIGER metadata, or any local street address data which we can use to validate against. This is why I want to map this problem visually, to see if there are localized clusters of problems and to see if we can reduce the problems by using local data sources alongside the software's educated guesses. And we also need to realize, as a community, that automated edits, like manual edits, will never be 100% correct. I'd be happy with 99.5% correct. That's better than the rate of typos and other problems we see with our normal mappers. The remaining .5% will be something that either local community members will fix, or some further iteration of a tool will fix. So if you have expertise in Tilemill, I'd love the help in setting up some tiles that show probable abbreviations. - Serge On Wed, Jul 30, 2014 at 3:44 PM, Clifford Snow cliff...@snowandsnow.us wrote: On Wed, Jul 30, 2014 at 9:48 AM, Serge Wroclawski emac...@gmail.com wrote: Thanks for the pointer. I think you're right that in this case especially, there's no reason to admonish anyone, but perhaps we can examine the data and see if there's a safe way to expand it, like we did the TIGER data. That may also explain some large portion of the contractions I found. Maybe it's worth trying to map them I agree with Serge and Toby's post - this is old data that should be fixed. I pulled the data from a Mapzen city extract (San Diego Tijuana). There are 488,571 address points. Looking at OSMI, the whole area has addresses with abbreviated street names. Serge, anything I can do to help you with the expansion bot, just let me know. Knowing how to do this would help me down the road as we try to figure out how to update address info from my local county. Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
On Wed, Jul 30, 2014 at 1:45 PM, Serge Wroclawski emac...@gmail.com wrote: So if you have expertise in Tilemill, I'd love the help in setting up some tiles that show probable abbreviations. Sorry, I've only created tiles from shapefiles, not from OSM data. I did look at the address data. It does contain lots of variation. EAst, WEst, Ro, Rd, suite numbers in addr:street, There are 20K distinct street names in the db. Some are variations of the same name, for example 4th Av and 4th Avenue. If anyone wants to look at the data, https://www.dropbox.com/s/51dy31ivgkar89m/sandiego.csv There does appear to be an E Avenue but no W (Avenue)|(Road)|(Street)|(etc.) What would be especially helpful if we had some local mappers involved. Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Hi Clifford Thanks for diving into the data. I'm going to look into the data. On Jul 30, 2014 4:53 PM, Clifford Snow cliff...@snowandsnow.us wrote: On Wed, Jul 30, 2014 at 1:45 PM, Serge Wroclawski emac...@gmail.com wrote: So if you have expertise in Tilemill, I'd love the help in setting up some tiles that show probable abbreviations. Sorry, I've only created tiles from shapefiles, not from OSM data. I did look at the address data. It does contain lots of variation. EAst, WEst, Ro, Rd, suite numbers in addr:street, There are 20K distinct street names in the db. Some are variations of the same name, for example 4th Av and 4th Avenue. If anyone wants to look at the data, https://www.dropbox.com/s/51dy31ivgkar89m/sandiego.csv There does appear to be an E Avenue but no W (Avenue)|(Road)|(Street)|(etc.) What would be especially helpful if we had some local mappers involved. Clifford -- @osm_seattle osm_seattle.snowandsnow.us OpenStreetMap: Maps with a human touch ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Clifford Snow writes: What would be especially helpful if we had some local mappers involved. In addition to OSM-mapping part of Seattle (Magnolia) a few years ago I've already mentioned to Clifford, I wanted to say I grew up in San Diego, visit often and know the area very well. I've been lurking on this thread, but I wanted to offer my help in San Diego if I am able to do so. My TileMill is still basic-to-intermediate, but I have done some professional work with it (made a map for a book that is due to be published later this year). If Serge can sharpen up exactly what he needs it to do (either on-list or off-list) we can likely get closer to the goal. TileMill experts: you might chime in here, too. SteveA California ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
On 7/30/2014 1:45 PM, Serge Wroclawski wrote: So if you have expertise in Tilemill, I'd love the help in setting up some tiles that show probable abbreviations. I have the databases to do this, but it's not clear to me how to visualize this. Just color roads in that have abbreviations? ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
Re: [Talk-us] Road abbreviations
Paul, Yeah, I'm just trying to figure out where the problems are- not trying to dig deeply into them yet- I'm looking for clusters of problems (ie San Diego), or I heard about a problem in Michigan where someone decided to revert a bunch of the bot-mode changesets because he didn't like the way they rendered, so in this case, I'd just look for some known contractions at the end. We may change that later, but that's where I'd start. - Serge On Wed, Jul 30, 2014 at 8:31 PM, Paul Norman penor...@mac.com wrote: On 7/30/2014 1:45 PM, Serge Wroclawski wrote: So if you have expertise in Tilemill, I'd love the help in setting up some tiles that show probable abbreviations. I have the databases to do this, but it's not clear to me how to visualize this. Just color roads in that have abbreviations? ___ Talk-us mailing list Talk-us@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-us
