That’s nothing. Addresses here are based on landmarks:
De donde fue Texaco Viejo 1/2 C al E, 2 c al S
City Name, Department name (sometimes), Nicaragua
Break that one up.
(literal translation is: From where the old texaco USED TO BE (it’s a
petronic
now), 1/2 a block to the east and 2 blocks to the south) That is just
how
addresses are here.
And the only problems arise when one or both of paterno or materno is
itself composite and non hyphenated. Right, Gerardo?
In France, not only you can receive either your father’s or mother’s
family name, but you can change your family when you marry, divorce
remarry and so on.
And what’s the point of storing that in different fields?
I’m working on a system that interfaces with a GIS mainframe system
(global information system?). It does street address / keymap ops for
police/fire. It requires that all fields are separate, including things
like street prefix, postfix, type, yada yada. A real pain.
e.g. 123 N. NESTOR LANE RD. SE #10B
(literal translation is: From where the old texaco USED TO BE (it’s a petronic
now), 1/2 a block to the east and 2 blocks to the south) That is just how
addresses are here.
(literal translation is: From where the old texaco USED TO BE (it’s a petronic
now), 1/2 a block to the east and 2 blocks to the south) That is just how
addresses are here.
And when you’re geocoding it gets even worse. In the Rural US
you find lots of places where the mailboxes are at a different
location than the buildings (say, all mailboxes for a set of
farms centrally located for a group of farms); so geocoding for
emergency services should give different results than geocoding
for mail deliveries.
Nothing really on topic here, except re-iterating that the
original poster’s request is a non-trivial problem.