Opened 6 years ago

Closed 6 years ago

#2466 closed defect (wontfix)

amenities rendered twice when applied to building and node inside building

Reported by: woidrick Owned by: osm@…
Priority: major Milestone:
Component: osmarender Version:
Keywords: twice, render, amenity Cc:


Mapnik do not render amenities applied to building (i think). Osmarenderer until last times too. There was some agreement somewhere to apply amenity=* both to building and to node somewhere inside building. (Break of mantra 'do not map for renderer').

Now, when it is rendered - same amenity rendered twice. Until very last times - sometimes close to each other, but now in some distance (great achievement in general!).

There is some good decision should be made to handle this twice (node and building) renders. After mapnik will render amenities for buildings the database slowly will be cleared of this bad things, but slowly... for that time map will be looking bad.

I ask to enhance algorithm to do not render amenity for building, if it is the same amenity (and same name+operator) for building, only for node inside.

This enhancing will work also as 'hint' to renderer, if default placing of amenity's icon is not good, and mappers can use it for it. (but still it will be somehow 'map for renderer').


Change History (1)

comment:1 Changed 6 years ago by bob@…

  • Resolution set to wontfix
  • Status changed from new to closed

Adding things twice to make them nicer in one renderer is bad data and should be fixed there.

Secondly it's quite expensive to have osmarender do this.

And for the hinting idea, see the label relation.

Note: See TracTickets for help on using tickets.