Closed GoogleCodeExporter closed 8 years ago
It is a Swampex bug and can not no be fixed. It happens commonly to maps with
only 2 calibration points. So the workaround is to add 2 more calibration
points to the corners of the map where they are missing.
Original comment by novikov
on 9 Oct 2010 at 8:24
I have the problem that the map stays on the corner with ozfx3 map created for
oziexplorer.
I don't understand "It is a Swampex bug and can not no be fixed." What is
Swampex ? Will you fix the problem or it cannot be fixed ? It is major issue
for me as I have so many map created for oziexplorer and that are not working
with your soft.
I have exactly the same problem with the software "yozi".
Original comment by ben....@gmail.com
on 4 Nov 2010 at 10:32
Also it seems that I have 4 calibration points on my maps. See example of .map
in attachment.
Original comment by ben....@gmail.com
on 4 Nov 2010 at 5:16
Attachments:
Can you please attach ozf3 file, so I can look at what happens with it?
Original comment by novikov
on 4 Nov 2010 at 8:53
Here is a new litle example that I made to be small.
Original comment by ben....@gmail.com
on 5 Nov 2010 at 7:36
Attachments:
Did you test with my file ? Any solution ?
Original comment by ben....@gmail.com
on 6 Nov 2010 at 7:50
I've looked at your file, unfortunately there is now solution - it uses France
Zone II projection which is not implemented in the projection transformation
library that I use. I've also looked at other geodesic libraries - none of them
support this projection.
Original comment by novikov
on 8 Nov 2010 at 6:36
Thanks for your tests. So i should try to convert my .map files ?
Original comment by ben....@gmail.com
on 9 Nov 2010 at 5:15
Yes, you should try to convert it to another projection, one of these:
http://code.google.com/p/swampex/wiki/ListOfProjections
Original comment by novikov
on 9 Nov 2010 at 8:03
Fixed (in terms of two calibration points) in 0.9.7b
Original comment by novikov
on 12 Dec 2010 at 8:15
Issue 5 has been merged into this issue.
Original comment by novikov
on 12 Dec 2010 at 8:16
Original issue reported on code.google.com by
novikov
on 9 Oct 2010 at 8:22