kflog-project / KFLog

Flight planning and analysis software
Other
17 stars 8 forks source link

Threshold #1.. should be named in Map Elements #28

Closed Ventusfahrer closed 10 years ago

Ventusfahrer commented 10 years ago

threshholddetail

we should show the number and unit of the single threshold instead of the abstract name Threshold #1, Threshold#2...

speed-axel commented 10 years ago

I tried to improve the current situation by adding the desired values to the window. Maybe it is helpful...

image

Ventusfahrer commented 10 years ago

If one could get the current dpi solution of the display device (screen ?), one would be able to calculate the scale of the map and present this number.

That's a number everybody is used to (or should we better say: should be used to)?

[?]

2014-09-16 11:44 GMT+02:00 Axel Pauli notifications@github.com:

I tried to improve the current situation by adding the desired values to the window. Maybe it is helpful...

[image: image] https://cloud.githubusercontent.com/assets/7580233/4285358/d3495e04-3d85-11e4-84fe-066e40b58fc5.png

— Reply to this email directly or view it on GitHub https://github.com/kflog-project/KFLog/issues/28#issuecomment-55719680.

Ventusfahrer commented 10 years ago

sorry I was talking about the screen _re_solution in dpi (not screen solution [?])

2014-09-16 12:32 GMT+02:00 Peter Simon psimon.kflog@gmail.com:

If one could get the current dpi solution of the display device (screen ?), one would be able to calculate the scale of the map and present this number.

That's a number everybody is used to (or should we better say: should be used to)?

[?]

2014-09-16 11:44 GMT+02:00 Axel Pauli notifications@github.com:

I tried to improve the current situation by adding the desired values to the window. Maybe it is helpful...

[image: image] https://cloud.githubusercontent.com/assets/7580233/4285358/d3495e04-3d85-11e4-84fe-066e40b58fc5.png

— Reply to this email directly or view it on GitHub https://github.com/kflog-project/KFLog/issues/28#issuecomment-55719680.

speed-axel commented 10 years ago

I don't know how to do it to calculate the map scale from the screen dpiX resolution. I found a method which said the screen dpiX resolution of my paint device is 96 dpi. If my projection scale is 5m per pixel what is then the map scale do you want to see?

Please help me and give me a hint.

Ventusfahrer commented 10 years ago

Mann, was machen wir denn da, wir sind am Mailen - da geht's doch gerade noch in deutsch! oder?

Ich bin gerade mal am phantasieren:

http://qt-project.org/doc/qt-5/qscreen.html#physicalDotsPerInch-prop

Man kennt ja noch die gute alte Formel für die ICAO Karten: 1:500000 = 1 cm auf der Karte sind 500000cm in Natura = 5000m = 5 km

Wenn wir jetzt einen Bildschirmauflösung von 97 PPI (PixelPerInch) haben, dann müsste doch ein Pixel 25,4mm/97=0.26 mm groß sein.

10 m / Pixel würden doch dann 0,26 mm auf dem Bildschirm entsprechen --> d.h. auf 1:xxxxx normiert, würde bzw. 10 * 1000 mm / 0,26 mm --> 1:38416.

Unter einem Maßstab 1:50 000, 1:500 000, 1:1 000 000 kann ich mir mehr vorstellen als unter dieser kryptischen Zahl m/Pixel mit der man sicher als Programmierer als Einheit designed und codiert. Ein Pixel ist halt keine Maßeinheit[?]...

Ich weiß, ich weiß. Kann man so vielleicht machen, muss man aber nicht...

Gruß

Peter

2014-09-16 14:54 GMT+02:00 Axel Pauli notifications@github.com:

I don't know how to do it to calculate the map scale from the screen dpiX resolution. I found a method which said the screen dpiX resolution of my paint device is 96 dpi. If my projection scale is 5m per pixel what is then the map scale do you want to see?

Please help me and give me a hint.

— Reply to this email directly or view it on GitHub https://github.com/kflog-project/KFLog/issues/28#issuecomment-55737526.

speed-axel commented 10 years ago

That is the modified solution with real map scales. But I'm unsure, if that all is correct now.

image

image