search

alankwok / androzic

Automatically exported from code.google.com/p/androzic
GNU General Public License v3.0
0 stars 0 forks source link

MSF map calibration parameter not honored #79

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?

1. Datums.dat file is not recognized, maps with custom datum dispalyed at wrong 
position with or without datums.dat file in Androzic folder.

What version of the product are you using? On what operating system?

0.9.13.4b

Sample of map file is attached.

Original issue reported on code.google.com by prim...@gmail.com on 17 Jan 2011 at 6:19

Attachments:

GoogleCodeExporter commented 8 years ago 
datums.dat filename should be all lovercase. Try using example datums.dat from 
downloads section - it contains your datum.

Original comment by novikov on 17 Jan 2011 at 9:31

GoogleCodeExporter commented 8 years ago 
Tried everything, small, caps in androzic and maps folder, also with example 
file, no difference. Maybe it has something to do with UTM projection? Maps 
wtih standard WGS84 datum only work OK with latest version.

Original comment by prim...@gmail.com on 18 Jan 2011 at 6:46

GoogleCodeExporter commented 8 years ago 
Can you share the image file, so I can check it?

Original comment by novikov on 18 Jan 2011 at 11:00

GoogleCodeExporter commented 8 years ago 
Ljubljana in okolica.ozf2 is 17M and can not be attached here.
Instead I attached one other file, which also gives wrong position, same datum.

Original comment by prim...@gmail.com on 18 Jan 2011 at 11:26

Attachments:

GoogleCodeExporter commented 8 years ago 
As I thought datums file was correctly processed. The map contained incorrect 
XY coordinates and map dimensions. When I fixed it using OziExplorer map 
recalibration tool (just opened and saved it without changing anything) it 
started to open correctly in Androzic. Unfortunately I currently depend on 
correct calibration of an image file. I will fix it in the future to correspond 
with OziExplorer behavior but not very soon.

See attached file for what have changed.

Original comment by novikov on 25 Jan 2011 at 8:46

Attachments:

GoogleCodeExporter commented 8 years ago 
Thanks. If I understand correctly, it is not a problem with datum, but with MSF 
(map scale factor) in line 6 of map file. It is not interpreted by your 
application and in that case I can rewrite all my map files in a simple batch 
operation. If you decide to inlude interpretation of MSF, here is a post on 
this topic:
http://tech.groups.yahoo.com/group/OziUsers-L/message/12484

Original comment by prim...@gmail.com on 28 Jan 2011 at 10:54

GoogleCodeExporter commented 8 years ago 
Fixed in 1.4.1

Original comment by novikov on 15 Feb 2012 at 10:21