#997 Handling of _PLAC_DEFN

[Veit]

A lots of new program versions like Legacy 7 handle additional place information in the tag _PLAC_DEFN at level 0. This includes also the map coordinates.

It would be fine if phpGedView could import and export this data to gedcom and use it for google map module.

Sample record:
0 _PLAC_DEFN
1 PLAC Meisdorf, Aschersleben-Staßfurt, Sachsen-Anhalt, Deutschland
2 ABBR Meisdorf, Meisdorf, , SA, DEU
2 NOTE http://de.wikipedia.org/wiki/Meisdorf
2 MAP
3 LATI N51.7
3 LONG E11.3
>

[Anonymous]

Logged In: YES
user_id=1910459
Originator: NO

Viet, this is one of the most discussed issues here, and on the genealogical web generally.
The problem is that "...lots of new program versions..." do NOT use the _PLAC_DEFN tag for this. As far as my research indicates, only Legacy does.

Cumberland 3 uses '3 NOTE' tags for lat and long
Lifelines uses a Xref like 0 @PL96@ PLDF
Legacy, as you say, uses 0 _PLAC_DEFN
RootsMagic uses 0 _PLAC

The official GEDCOM spec 5.5 has no provision for LATI/LONG tags.
The DRAFT 5.5.1 has +1 MAP / +2 LATI, +2 LONG tags, which PGV does recognise.

This shows there is no standard for these 'non-standard' tags.

It would be great if there was a standard, but why pick Legacy's (or anyone else's) - its a long way from being a market leader.

If PGV could do anything, my preference is described in this existing RFE:
http://sourceforge.net/tracker/index.php?func=detail&aid=1770716&group_id=55456&atid=477082

[KosherJava]

Logged In: YES
user_id=634811
Originator: NO

Veit ,
This is totally of topic here, but how does the GEDCOM output of the new SourceWriter templates in Legacy 7 look?
Thanks