For static locations, using Civic Address location descriptions would be the easiest method. As stated earlier though, you and your partners must agree on which description formats are acceptable.
The following tables list the IANA registered element names that are currently accepted. The complete list of codes is defined in:
The country is identified by the two-letter ISO 3166 code.
national subdivisions (state, region, province, prefecture)
county, parish, gun (JP), district (IN)
city, township, shi (JP)
city division, borough, city, district, ward, chou (JP)
Leading street direction
Trailing street direction
Avenue, Platz, Street
House number, numeric part only
House number suffix
Landmark or vanity address
Additional location information
Name (residence, business or office occupant)
These codes were added in RFC5139
Unit (apartment, suite)
Postal community name
Post office box (P.O. box)
Seat (desk, cubicle, workstation)
Primary road or street
These codes were added in RFC6848
Post number that is attributed to a lamp post or utility pole.
Milepost: a marker indicating distance to or from a place (often a town)
Street Type Prefix.
House Number Prefix.
Simple Example 1
In geolocation.conf, we can define a location that describes a building and profiles for Bob and Alice that add floor and room. We're assuming here that Bob's and Alice's phones don't send any location information themselves.
PIDF-LO XML Examples
Here's what Alice's PIDF-LO would look like:
Here's what Bob's PIDF-LO would look like:
Note that the only civicAddress difference between the two are the