Markers may overlap slightly when rendered from SVG even if allow-overlap=false #1754

springmeyer opened this Issue Mar 12, 2013 · 4 comments


None yet
1 participant

springmeyer commented Mar 12, 2013

This is either because the bbox width/height calculations are not correct (perhaps related to #1122, or more specifically because the stroke thickness is not taken into account like in #1354 ) or because of some incorrect calculation of the collision box.

Screen Shot 2013-03-12 at 11 19 49 AM


springmeyer commented Mar 12, 2013

not seeing any fix immediately actionable here because:

  • dynamically determining the impact of stroke width used in the svg would be overly complicated
  • because the user can set stroke, but not all aspects of the stroke are boost::optional - we cannot predictably pad the bbox by user supplied stroke - we would need to be able to distinguish between the user providing only a non-width based attribute like stroke-opacity/color vs also providing a stroke-width.

Needs a simple, comprehensive solution, like requiring svg provide a value viewbox for collision or something like that.


springmeyer commented Mar 13, 2013

see also #1538


springmeyer commented Nov 22, 2013

assigning to harfbuzz milestone as this appears fixed:
screen shot 2013-11-21 at 8 34 45 pm


springmeyer commented Nov 22, 2013

nevermind: only thing fixed was collision box for markers with scale_factor != 1

@springmeyer springmeyer added this to the Mapnik 3.x milestone Jan 7, 2015

@springmeyer springmeyer removed this from the Mapnik 3.x milestone May 14, 2015

@dgaubert dgaubert referenced this issue in CartoDB/grainstore Jan 26, 2017


[mapnik-3] mapnik-reference #118

11 of 12 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment