We have a challenge to list all address info for a building unit (subUnit) of an apartment.
In the EU Inspire model we have several means to 'locate' that place (Inspire use the concept of address locator with a level & designator), either by:
- physical access with the info of floor, apartment number or name indicated on that floor
- indicating the postal delivery point with the info of a (postal) box number or (postal) box name often in the entrance of the building
We don't see a straightforward full 100% mapping between the EU Inspire Place/Address and the TMF673 one, the approaches are a bit too different, although a mapping between the two models would be desired in the future we think.
Looking at the current TMF673, we wonder if the best construction would not be to pass the info as several geographicSubAddresses by defining a new value for "subAddressType"="postalDeliveryPoint" and extending with a field "poBox" (postal delivery point identifier) for use with this type of sub address.
The idea is equally that in the validation of a geographicaAddress one could choose between the two subAddress types.
This way we could provide both info's like:
"geographicSubAddress" :
[{
"subaddressType":"SubUnit",
"subUnitType":"FLAT",
"levelNumber":"5",
"levelType":"FLOOR",
"subUnitNumber":"501"
},
{
"subaddressType":" postalDeliveryPoint",
"poBox":"5A"
}
]
Looking for your advice & feedback.
------------------------------
Peter Broucke
Proximus SA
------------------------------