Le 02/11/2014 16:29, Nicolai Hess a écrit :
> 2014-11-02 15:22 GMT+01:00 Thierry Goubier <
[hidden email]
> <mailto:
[hidden email]>>:
>
> Le 02/11/2014 15:15, stepharo a écrit :
>
>
> I gave up on zoomability (with the idea to revisit after
> Athens is
> integrated),
>
>
> Athens is integrated. Now if the community does not help
> redefining the
> drawnOn: methods using athens then it will not happen.
>
>
> And, speaking of infinite zoomability, you have a few surprises
> waiting for you in Athens :( (some are from Athens design, others
> may be linked to Cairo).
>
>
> ?
> What exactly?
(1) Precisions issues: Athens/Cairo seems only precise at 0.001 points
in Roassal space (independently of the scaling of the canvas, i.e. even
if you camera scaling is 10 pixels for 0.001).
(2) Limits: if your Athens coordinates are over a certain number (around
1e7, I believe), Athens stop displaying things (independently of the
scaling, again)
(3) Athens design: the idea of having a stroke width of 1 has strange
effects (polygons with scaling being 10 pixels wide, but with a border a
100 pixels wide: certainly not what you expect to see displayed)
(1) means that you can't zoom to a meter/pixel resolution without errors
on a earth map where your scale is at 1 in roassal / 1km at equator.
(2) means that nothing will be displayed on your map of earth if your
scale is at 1 in Roassal/1m on Earth (i.e., if you try to solve 1 by
increasing your scale, then you may end up with nothing displayed).
(3) is just plain annoying, because of (2).
For normal Roassal use, doesn't matter except if your unlucky with your
scaling. When you start to play with geo-referenced data with a meter
resolution, you are sure to hit them. I did ;) Luckily, at that stage I
knew I had proper projections and coordinate transforms, otherwise I
would have lost a lot of time.
Thierry
Locked
Nov 02, 2014; 2:18pm
