My company has a database with customer information (SQL Server 7.0).
My boss wants me to formalize the address (USA address).
The street address format is like this (city, state, zip are not my
concern).
(I know that there will be exceptions and I will ignore them if I can
recognize them to be exceptional.)
On Wed, Nov 24, 2004 at 02:38:02AM +0900, Sam Sungshik Kong scribed:
>
> Don't forget Utah adresses:
>
> 190 N 200 W
> Orem, UT 12345
>
> Usually misinterpreted as 190 N on 200 West Street.
> But it could also be 200 W on 190 North Street.
>
> The adresses are actually coordinates.
Although one is a street and one is a street address.
You just don't know which. It's _likely_ that the more
round number is the street, but without a street guide,
you can't be 100% sure. For instance, an address like:
1105 E 4800 S
is probably on the street "4800 S"
But luckily, you don't need to worry about it unless you're
trying to map things, since the coordinate statement _is_
the canonical form of the address.
I miss coordinate addresses and a grid system.
-Dave
···
--
work: dga@lcs.mit.edu me: dga@pobox.com
MIT Laboratory for Computer Science http://www.angio.net/
This is NOT 200 University St. #55, but 55 University St. #200.
-austin
···
On Wed, 24 Nov 2004 03:02:51 +0900, David G. Andersen <dga@lcs.mit.edu> wrote:
On Wed, Nov 24, 2004 at 02:38:02AM +0900, Sam Sungshik Kong scribed:
> > Don't forget Utah adresses:
> >
> > 190 N 200 W
> > Orem, UT 12345
> >
> > Usually misinterpreted as 190 N on 200 West Street.
> > But it could also be 200 W on 190 North Street.
> >
> > The adresses are actually coordinates.
Although one is a street and one is a street address.
You just don't know which. It's _likely_ that the more
round number is the street, but without a street guide,
you can't be 100% sure. For instance, an address like:
1105 E 4800 S
is probably on the street "4800 S"
But luckily, you don't need to worry about it unless you're
trying to map things, since the coordinate statement _is_
the canonical form of the address.