Check out this thing which I just got working again:
>>> Long Names of OpenStreetMap <<<
So that’s elements with a name tag, where the name seems to be very long. It’s a full list of the longest names in the planet (>150 chars)
I just found this old code and dusted it off. I made it originally back in May 2010 when Richard Weait ran a “Project of the week” looking at long names. I called it “namecheck” at the time, but I’m renaming it “longnames”.
A crazy long name is probably a data bug to be fixed. It certainly looks like a bug when we try to render it.
But… well taking that example. Here we have a few university buildings, each with a name, which list several departments. Can we class this as wrong? I think so, yes, but I’ll have to make a hand-wavy non-scientific judgement: I’d say it ceases to be a name of the building and becomes more of a “description” when it gets that long…. in this case. And maybe that’s a problem for a lot of them.
But in general this is not going to be a clear case of “these are all bugs. Here’s how to fix them”. Because of that I think I would stop short of saying this could be a MapRoulette challenge, or a new class of bugs for KeepRight or Osmose. For the moment I’m just going to put this list out there, and suggest some careful interpretation (but feel free to suggest other actions / tagging policies in the comments)
On the other hand some of these definitely are bugs with clear fixes. I saw somebody adding a load of space characters and then repeating the name again within the name tag, presumably in attempt to control label placement on a road (Yeah no we don’t do that)
The other caveat, in case it wasn’t clear, the username listed there is ‘last editing user’. It’s not necessarily the person who added the very long name, but it is a person who didn’t fix it :-) That and the last edit timestamp are really just to see if there’s any interesting patterns in the list.
My planet crunching script to find long names is here along with SQLite, CSV, and mangled OSM XML output files. I will re-run it again in a week, but the display also has a (slightly odd) feature to let you “rescan” an element after you’ve made a fix.
[Update: I mentioned “feel free to suggest other actions / tagging policies in the comments”. But also this discussion on the wiki might be a good place to discuss debate what the policies should be]
[Update: New diary entry. Updated data for 2019]
Comment from Boston Logan Taxi on 31 August 2016 at 18:14
Hmnn the display is kind of stuffy. In a small space they can look real ugly. But for single name displays or for Address purposes they will be very handy. thank you for the good work Harry. We are a taxi company in Boston and we rely on Map data for distance and traffic calculation. Our fares and timing are based on the maps. So I might give this a try and see if it helps us.
Comment from Wynndale on 31 August 2016 at 19:18
Is there ever a good reason to have multiple spaces, or is that something we should disallow?
Comment from Harry Wood on 1 September 2016 at 00:10
Yeah I was pondering the same thing. I certainly can’t think of a reason. Also HTML tags within names seems like something which is always a bad idea and could be blocked (or at least a new bug type in QA tools)
Comment from Alan Trick on 5 September 2016 at 23:46
I believe the name is supposed to be what a thing is typically called by typical people. While an official name (there is a separate tag for official names) for a thing might be ridiculously long, it would be unusual for that to be also how people typically refer to the thing.
Comment from Wynndale on 21 September 2016 at 17:26
There is a mailing list discussion about using the name tag for descritions of route relations.
Comment from Marián Kyral on 22 November 2016 at 06:04
At the other side - we should not do mapping for render. It is not my fault that renders does not render it better.
Comment from *Martin* on 22 November 2016 at 09:00
That’s my job. I was also limited by maximum value length of 255 ;-). There are several departments in the single building. I couldn’t find a better tagging for this, but if you suggest something then I can rework it. Names separated with “;” could be split to several nodes. It would be nice if there was a tag for university department.
Comment from Harry Wood on 16 January 2017 at 23:02
I put reply to this on the wiki here: https://wiki.openstreetmap.org/wiki/Talk:Names#Very_long_names._bad_practice.2Fbug.3F mainly because my osm account was weirdly broken for a while, and I couldn’t reply here … but also it’s good to discuss ‘name’ issues there
Comment from Warin61 on 13 October 2017 at 07:36
Boo … I was looking forward to a nice list of Welsh names! :)
Some names have more than one word so need a space or three. If the name ‘CSIRO Molecular Science and Food Science’ were full expanded out the name would be Commonwealth Scientific and Industrial Research Organization Molecular Science and Food Science… some 10 spaces. I use CSIRO myself - still some 5 spaces.
If something is a description .. then use the ‘description=’ tag? And I’m also using a ‘comment=’ tag instead of the note tag .. the note tag gets some prominence with some editors that I don’t want with some of my ‘comments’.
Comment from dieterdreist on 19 October 2017 at 19:25
many of these stem from compositing (e.g. adding the name of the university before the name of the faculty, on the faculty) or from combining (several businesses or doctors mapped as a single osm object rather than an object for each).
Comment from I_G on 23 December 2017 at 22:30
Lots of them are intercity bus route relations describing main destinations like “Bus #207 Town1 > Town2 > Town3”… Is that bad practice?
Comment from Warin61 on 24 December 2017 at 00:07
@ I_G Yes, putting a description in a name tag is bad practice.
“name=* tag is supposed to contain solely name, not to describe the type or location of the object or one of its other properties (such as height, elevation, operator, access restrictions, classification/certification/quality labels…).” from http://wiki.openstreetmap.org/wiki/Key:name#Additional_data
Use the description tag http://wiki.openstreetmap.org/wiki/Key:description !
Comment from I_G on 24 December 2017 at 16:29
@Warin61 I do know that the name is only for the name, sometimes people reference routes like “the Town1 to Town2 bus” maybe that caused this unpleasantness to occur. Anyways I never tagged bus routes and I don’t plan to do either, public transit mapping is a mess.
Comment from wille on 23 February 2018 at 13:54
We’ve added a filter in OSMCha to get features with very long names: http://bit.ly/2osjHCX