how should we handle ranges of addresses?

[hughstimson]

It's pretty common to see a range of addresses as either the primary geographic component of an application, or in addition to discrete street addresses.

E.g. "506 West 60th Avenue and 7645-7675 Cambie Street"

How should ranges be stored?

Should there be a distinct data type for that, with two components?

- addresses
- - address range
- - - start address
- - - - street 1
...
- - - - postal code
- - - stop address
- - - - street 1
...
- - - - postal code

or is that getting too complex, with now 3 address types (address, geo object, address range) and a bunch of non-intuitive field name (address range, start address, stop address)?