First let me say that don't worry about the "goof". FTM and other software products are not helpful in this regard.
Unfortunatelly FTM goofed in that they do not support the GEDCOM address structure properly. In my primary DB tool I put full addresses in the address tags within the RESI "fact" and to support FTM (and mapping to Google or Bing) I also use the PLAC tag to support complete addreses (minus the zipcode for USA). In other countries I do enter the city code.
So my GEDCOM before it goes to FTM for USA residences looks like this:
1 RESI
2 DATE FROM ... TO ...
2 PLAC address, city, county, state, country
2 ADDR address line1
2 CONT address line2
2 CONT address line3
2 OBJE pointer to media
2 SOUR pointer to source
I don't use the FTM description field because the GEDCOM standard does not allow a "description" value for a RESI fact. Again FTM goofed here as well :-(
At this time I do not remember if FTM supports the media here, but I think it does.
Unfortunatelly FTM goofed in that they do not support the GEDCOM address structure properly. In my primary DB tool I put full addresses in the address tags within the RESI "fact" and to support FTM (and mapping to Google or Bing) I also use the PLAC tag to support complete addreses (minus the zipcode for USA). In other countries I do enter the city code.
So my GEDCOM before it goes to FTM for USA residences looks like this:
1 RESI
2 DATE FROM ... TO ...
2 PLAC address, city, county, state, country
2 ADDR address line1
2 CONT address line2
2 CONT address line3
2 OBJE pointer to media
2 SOUR pointer to source
I don't use the FTM description field because the GEDCOM standard does not allow a "description" value for a RESI fact. Again FTM goofed here as well :-(
At this time I do not remember if FTM supports the media here, but I think it does.