TrekBuddy

[guest]

Could we have automatic map datum selection from .map/gmi files ?
(when it isn't possible, ie. map datum is not available in TB, just use manualy selected datum).

Ranger

[kruch]

That would be nice - anyone has a list of datums names used in .map/.gmi?

[guest]

You need something like this ?

Subset of names for .map file
Adindan
Arc 1950
Arc 1960
Australian Geodetic 1966
Australian Geodetic 1984
Austrian
CH-1903
Djakarta (Batavia)
European 1950
European 1950 (Mean France)
European 1950 (Spain and Portugal)
European 1979
Easter Island 1967
Egypt
Finland Hayford
Geodetic Datum 1949
Hermannskogel
Hong Kong 1963
Indian Bangladesh
Indian Thailand
Israeli
Ireland 1965
Liberia 1964
Luzon Mindanao
Luzon Philippines
NAD27 Alaska
NAD27 Bahamas
NAD27 Canada
NAD27 Canal Zone
NAD27 Caribbean
NAD27 Central
NAD27 CONUS
NAD27 Cuba
NAD27 Greenland
NAD27 Mexico
NAD27 San Salvador
NAD83
Nahrwn Masirah Ilnd
Nahrwn Saudi Arabia
Nahrwn United Arab
NGO1948
Norsk
Oman
Puerto Rico
Ord Srvy Grt Britn
Potsdam Rauenberg DHDN
Pulkovo 1942 (2)
Pulkovo 1942 HUN
Pulkovo 1942 POL
Pulkovo 1942 CZH
Pulkovo 1942 LAT
Pulkovo 1942 KAZ
Pulkovo 1942 ALB
Pulkovo 1942 ROM
Qatar National
Rome 1940
RT 90
S-JTSK
South American 1969
South Asia
Tokyo
WGS 72
WGS 84
Yacare
Zanderij

Default list is in OziE Trial (Menu View, Datum list) except user defined.
The names are case sensitive. But probably better solution for automatic setting is use currently defined datums in TB only.

Ranger

[kruch]

I think of something like a file (property file format) in /resources, with lines like this:

AGD66(ELLIPSOID_AUSTRALIAN,-133,-48,148)=map:Australian Geodetic 1966,gmi:"do not know:)"

That is:

NAME_IN_TB(reference ellipsoid,dx,dy,dz)=CALIBRATION_FILE_EXT:NAME_IN_GIVEN_CALIBRATION,...

[guest]

Good idea.

I don't use .gmi, so I couldn't help.

One more about ellipsoid numbers and names used in OziE.
There is a list:
0 : 'Airy 1830'; a : 6377563.396; invf : 299.3249646
1 : 'Modified Airy'; a : 6377340.189; invf:299.3249646
2 : 'Australian National'; a : 6378160.0; invf: 298.25
3 : 'Bessel 1841'; a : 6377397.155; invf:299.1528128
4 : 'Clarke 1866'; a : 6378206.4; invf: 294.9786982
5 : 'Clarke 1880'; a : 6378249.145; invf:293.465
6 : 'Everest (India 1830)'; a : 6377276.345; invf:300.8017
7 : 'Everest (1948)'; a : 6377304.063; invf:300.8017
8 : 'Modified Fischer 1960'; a : 6378155.0; invf: 298.3
9 : 'Everest (Pakistan)'; a : 6377309.613; invf:300.8017
10 : 'Indonesian 1974'; a : 6378160.0; invf: 298.247
11 : 'GRS 80'; a : 6378137.0; invf: 298.257222101
12 : 'Helmert 1906'; a : 6378200.0; invf: 298.3
13 : 'Hough 1960'; a : 6378270.0; invf: 297.0
14 : 'International 1924'; a : 6378388.0; invf: 297.0
15 : 'Krassovsky 1940'; a : 6378245.0; invf: 298.3
16 : 'South American 1969'; a : 6378160.0; invf: 298.25
17 : 'Everest (Malaysia 1969)'; a : 6377295.664; invf:300.8017
18 : 'Everest (Sabah Sarawak)'; a : 6377298.556; invf:300.8017
19 : 'WGS 72'; a : 6378135.0; invf: 298.26
20 : 'WGS 84'; a : 6378137.0; invf: 298.257223563
21 : 'Bessel 1841 (Namibia)'; a : 6377483.865; invf:299.1528128
22 : 'Everest (India 1956)'; a : 6377301.243; invf:300.8017
23 : 'Clarke 1880 Palestine'; a: 6378300.789; invf:293.466
24 : 'Clarke 1880 IGN'; a: 6378249.2; invf:293.466021
25 : 'Hayford 1909'; a: 6378388.0; invf:296.959263
26 : 'Clarke 1858';a:6378350.87;invf:294.26
27 : 'Bessel 1841 (Norway)' ; a:6377492.0176;invf:299.1528
28 : 'Plessis 1817 (France)'; a: 6376523.0 ; invf:308.6409971
29 : 'Hayford 1924'; a : 6378388.0; invf: 297.0

Without such information it is difficult to know which ellipsoid can be used in custom datum or not (when implemented

Ranger

[guest]

Kruch,

It seems that for gmi files this is not possible, Map Calibrator doesn't write map datum information to the file. Probably this is manual setting in MC only.

Ranger

[kruch]

You're right, I've just tried it, datum is not saved in .gmi

[guest]

So I propose for this moment:

NAME_IN_TB(reference_ellipsoid_number,dx,dy,dz)=CALIBRATION_FILE_EXT:NAME_IN_GIVEN_CALIBRATION

Ranger

[guest]

Kruch,
I found a little trick to have map datum in .gmi
If you do something like this below (use blank line) MC is still working


Map Calibration data file v2.0
\World.jpg
1815
911
752;455;-29.95;0
903;152;-0.05;60

European (ETRS89)


Ranger

[guest]

... and I tested such file in TB too. It works.

Did you try it ?

Ranger

[guest]

Sorry for overposting, but no answer.

I looked a little at names convention used in MC.
In the definition file (datums.csv) they are using names for:
"datum+projection"
so it can't be the same as datum name only.
But file structure is rather clear, ellipsoid parameters followed by semi 7p (Bursa-Wolf) type transformation + projection, 3 pts can be used too, so for test I added S-42 and it works.
Conclusion. It is not so difficult to have the same set of datums in TB and MC, cause any names can be defined in many to one relation.
Names from such defined set, known for TB, can be manually inserted to gmi as I needed (I explained this earlier).
I really don't know why MC designers doesn't put this info to gmi, map without datum has no value for GPS.

Ranger

[kruch]

I have this in my TODO list, definitely, let's say for v0.9.4. But my priority #1 for v0.9.3 is now "last-10-meters-guide screen" for geocachers (see my recent post if you are interested).

[kruch]

[guest]

[kruch]

I meant that Ozi .map files already contain projection parameters, so there's no need to use user's definition (which may be even wrong).