Support rendering of "label" member of relation

[joakimfors]

Administrative boundaries can have a "label" node member. It would be nice if the stylesheet rendered the name of the relation at the position of the label member node.

Related: #103 #104

[pnorman]

Is sufficient information in a standard osm2pgsql database to render this?

[gravitystorm]

It's entirely the wrong concept to put a "label" node in the database, and I'll not be using it for rendering.

The geodatabase is for geodata. Rendering decisions are made by the renderer. If the renderer isn't sufficiently advanced to place a label to your desire, then lets improve the renderer.

[Dimitar5555]

@gravitystorm Mappers work with what Carto offers them. You can't expect them to not put label (or admin_centre which is practically the same) elements when the relation's name is not rendered. After all they want to create some relationship between the area and the label/place center (which is usually not the same point as the centroid). Of course it would be fine to render names on the centroid if no label/admin center nodes are available.

If the name of the relation were rendered ignoring label nodes, the name would be in seemingly random places and mappers would not create relations for those objects. Also, I think it's important to note that mappers currently determine the label location by placing place=* nodes, so I don't see how having the same node with label role and no tags is a problem.