When you add a tag such as PROP or OCCU it doesn't actually check to see if you have entered data in the PROP or OCCU field in the record.
1 PROP
2 DATE 14 OCT 1852
2 PLAC Nicholas Co, WV, USA
If you re-import the GEDCOM, the sanity check will tell you that you have an error for that tag. I would like to see if the check could be made when you enter the tag using PHPGEDVIEW to comply with Gedcom 5.5.1 if you select that option.
I don't know if this applies to any other tags.
Thanks.
Logged In: YES
user_id=1466942
Originator: NO
The difficulty here is distinguishing valid gedcom (e.g. the example given) from invalid gedcom (e.g. as generated by Family Tree Maker).
1 PROP
2 DATE 14 OCT 1852
2 PLAC Family Bible
Had you put a value in the PROP field, the rewriting wouldn't have happened. e.g.
1 PROP Farmhouse
2 DATE 14 OCT 1852
2 PLAC Nicholas Co, WV, USA
I'm not sure the best way to fix this. One option might be to ignore PLAC records that contain a comma. This would be better, but still not perfect.
Better logic anyone?
Logged In: YES
user_id=399547
Originator: YES
I am not too concerned about imports, I think the sanity check is valid.
I realize after reading my request that I didn't make the issue clear enough.
PHPGEDVIEW allowed me to enter a PROP tag using the ADD (tag) entry form (not RAW GEDCOM)without checking to see if I added a value in the PROP or OCCU fields (the two I tested).
I later added different information to the GEDCOM file from another file and then re-imported it. The sanity check found PHPGEDVIEW's supposed error on items I previously entered several days prior.
It is sort of inconsistent that PHPGEDVIEW checks imports and not the input entry for correct format on these tags. That is why I made this a request.
Sorry for the misunderstanding.