The LGIM Site Address Schema doesn't explicitly parse out address components and I'm curious as to why. One of our key uses of address point data is for geocoding, and current locators work best when the PrefixDirection, StreetName, SuffixDirection and Streetype are parsed out. (Look at the US Address Single House and/or US Address Single House Subaddress locator styles for specifics.) Another field lacking in the LGIM is the Altname JoinID field that I simply cannot live without. The schema does provide PREADDRNUM and ADDRNUMSUF that could (should?) be used as surrogates. However, at one time storing a Suffix Direction in the same field as a Street Type was considered bad practice. Perhaps that has changed.
I realize that the any of the schemas can be viewed more less as guidelines instead of hard fast rules, but as new tools are developed with LGIM-centricity, too much modification to the original schema will negate the utility in using it. Admittedly, I'm very new to using the LGIM, and deep in the trough of it's learning curve, so if this is a topic that has been already ridden hard and put up wet, I apologize in advance.
