You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.
Reporter: bubaya [Submitted to the original trac issue database at 6.55pm, Friday, 9th November 2012]
Given the following example: [http://parent.tile.openstreetmap.org/cgi-bin/export?bbox=5.0,50.0,5.1,50.016666&scale=10500&format=pdf]
This map extract is 1' lat high, this is 1852m. The scale is 1:10500. Hence, the exported pdf should be 17,64cm high. In fact, it is 34,6cm high; that means a scale of 1:5353.
The same problem if I export images: When I export the same area as a PNG image, the image is 981px high, and has a resolution of 72ppi. That means a height of 34,6cm, the same as the PDF. To match the 1:10500 scale, the image would have to have a resolution of 141.3ppi. If I play around, I do not get a constant resolution that would match the scale, but always value between 140 and 145ppi.
The text was updated successfully, but these errors were encountered:
Reporter: bubaya
[Submitted to the original trac issue database at 6.55pm, Friday, 9th November 2012]
Given the following example: [http://parent.tile.openstreetmap.org/cgi-bin/export?bbox=5.0,50.0,5.1,50.016666&scale=10500&format=pdf]
This map extract is 1' lat high, this is 1852m. The scale is 1:10500. Hence, the exported pdf should be 17,64cm high. In fact, it is 34,6cm high; that means a scale of 1:5353.
The same problem if I export images: When I export the same area as a PNG image, the image is 981px high, and has a resolution of 72ppi. That means a height of 34,6cm, the same as the PDF. To match the 1:10500 scale, the image would have to have a resolution of 141.3ppi. If I play around, I do not get a constant resolution that would match the scale, but always value between 140 and 145ppi.
The text was updated successfully, but these errors were encountered: