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

Map Composer Map Item Rotation Other than Whole Degrees #14533

Closed
qgib opened this issue Dec 11, 2011 · 4 comments
Closed

Map Composer Map Item Rotation Other than Whole Degrees #14533

qgib opened this issue Dec 11, 2011 · 4 comments

Comments

@qgib
Copy link
Contributor

qgib commented Dec 11, 2011

Author Name: Larry Shaffer (Larry Shaffer)
Original Redmine Issue: 4632


When using the map print composer, the option for rotating a placed map item increments in whole degrees. It would be advantageous to have this increment to at least hundredths of a degree (e.g. 0.87).

I found it impossible to rotate from UTM grid north to true north when composing my UTM map for print output. Is it a limitation imposed solely by the composer GUI input field, or does the rotation code require (at this time) whole degrees for rotation?

Larry


Related issue(s): #14699 (duplicates)
Redmine related issue(s): 4871


@qgib
Copy link
Contributor Author

qgib commented Dec 16, 2011

Author Name: Giovanni Manghi (@gioman)


  • category_id was configured as 33

@qgib
Copy link
Contributor Author

qgib commented Dec 16, 2011

Author Name: Giovanni Manghi (@gioman)


  • fixed_version_id was configured as Version 1.7.4

@qgib
Copy link
Contributor Author

qgib commented Dec 19, 2011

Author Name: Marco Hugentobler (@mhugent)


Changed precision in master (will be backported to 1_7 and 1_8)


  • status_id was changed from Open to Resolved

@qgib
Copy link
Contributor Author

qgib commented Dec 19, 2011

Author Name: Werner Macho (Werner Macho)


backported to 1_7 and 1_8 for upcoming release 1.7.4 and possible 1.8.0 in commit 2001cc6
so closing for now


  • resolution was changed from to fixed
  • status_id was changed from Resolved to Closed

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

1 participant