Opened 13 years ago

Closed 13 years ago

#6143 closed enhancement (wontfix)

[patch] Use place_name as the name for place multipolygons

Reported by: Zverikk Owned by: team
Priority: normal Milestone:
Component: Core Version: latest
Keywords: place Cc:


Although there are only 680 uses of place_name tag on relations (according to taginfo), it is widely used in western Russia. But the name formatter in JOSM only supports name, ref etc. for naming. We'd like to have place_name shown as well, when name is absent.

Attachments (1)

place-name.patch (872 bytes ) - added by Zverikk 13 years ago.
Add place_name to the list of naming tags

Download all attachments as: .zip

Change History (8)

by Zverikk, 13 years ago

Attachment: place-name.patch added

Add place_name to the list of naming tags

comment:1 by mjulius, 13 years ago

I would not encourage the use of place_name. Why not use name instead? That it already exists so many time is not enough of an argument to support it when a better solution exists.

comment:2 by anonymous, 13 years ago

-1. Unless there's some compelling reason why the name of the place can't be in name= instead of place_name= this is a data error, not a rendering error.

comment:3 by Zverikk, 13 years ago

It's not a data error, but a common mapping practice, at least in Russia. I agree that it's a bit ugly workaround, but can easily be fixed sometime. And it would not hurt community to support this tag — I doubt there are no other deprecated or country-specific tags in JOSM presets.

comment:4 by mjulius, 13 years ago

If there are country specific tags that take care of certain circumstances in that country it might be a good idea if JOSM supports them (If there are a lot of them they might be better taken care of in a plugin.). If there are ugly workarounds that happen to be used in some country JOSM should not treat them in any special way and the workarounds should be fixed, IMHO.

comment:5 by Zverikk, 13 years ago

Isn't finger-pointing and name-calling the validator plugin's task? Does this patch break anything?

Users who didn't use place_name won't use it, because in the wiki it's marked as deprecated, and nothing in the interface mentions this tag. But editing data which already has that tag would be much easier.

comment:6 by mjulius, 13 years ago

Hey, the "ugly workaround" was your's.

The patch probably doesn't break anything, but, from my POV it is bloat. JOSM can not account for every tagging scheme someone might be using.

In the concrete example the better solution would be to be able to define in the rendering style which tags are to be used for labelling an object instead of hard-coding that into JOSM. Then, you could define your own style if you want to see place_name.

comment:7 by stoecker, 13 years ago

Resolution: wontfix
Status: newclosed

I still see no sense for this. When somebody want to use it, it can be changed in josms advanced preferences, but it should not be default.

Modify Ticket

Change Properties
Set your email in Preferences
as closed The owner will remain team.
as The resolution will be set.
The resolution will be deleted. Next status will be 'reopened'.

Add Comment

E-mail address and name can be saved in the Preferences .
Note: See TracTickets for help on using tickets.