Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cairo PDF output misplaces shield of ShieldSymbolizer #737

Closed
artemp opened this issue Oct 11, 2011 · 5 comments
Closed

Cairo PDF output misplaces shield of ShieldSymbolizer #737

artemp opened this issue Oct 11, 2011 · 5 comments

Comments

@artemp
Copy link
Member

artemp commented Oct 11, 2011

Today I upgraded the main OSM tile server to Mapnik2 SVN trunk and the road shields are now being placed incorrectly in the Cairo PDF output (from the /export tab). The PNG output looks fine.

The machine is running with the latest versions of the Cairo chain:

  • cairo-1.10.2
  • cairomm-1.9.8
  • pixman-0.21.6
@artemp
Copy link
Member Author

artemp commented Oct 11, 2011

[Ldp] The cairo chain places the shield origin at the text center, instead of moved half width/height to the left/top. This patch is the most notable difference between the cairo and agg chains.

@artemp
Copy link
Member Author

artemp commented Oct 11, 2011

[Ldp] Patch applied in r2652

@artemp
Copy link
Member Author

artemp commented Oct 11, 2011

[rcoup] @Ldp also brought up:
[11:23] <Ldp__> what about the missing floor() on x,y a few lines earlier?
[11:23] <Ldp__> should we synch that to agg as well?
[11:24] <rcoup> Ldp__: which lines?
[11:24] <rcoup> (the missing floor())
[11:24] <Ldp__> http://trac.mapnik.org/browser/trunk/src/agg/process_shield_symbolizer.cpp#L220
[11:25] <Ldp__> vs http://trac.mapnik.org/browser/trunk/src/cairo_renderer.cpp#L1251

Will keep this open until @tcollett has a chance to review.

artemp pushed a commit that referenced this issue Oct 11, 2011
…han top-left in cairo output. re #737 - thanks @jburgess for testing and @Ldp for the patch.
@springmeyer
Copy link
Member

@rcoup - can this be closed now? /cc @thjc

@springmeyer
Copy link
Member

assuming this can be closed, so closing it. In master (upcoming 2.1.x release) there has been much refactoring so if this persists it will be re-addressed separately.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants