Yup, that's where I was going with the USNG use.
Separate dataset bound to addresses where needed/desired for detailed locating. And where no address is present, the
USNGbecomes the address.
Bobb
-----Original Message-----
From: Rich Shepard <rshepard@appl-ecosys.com>
Sent: Wednesday, May 13, 2020 9:01 AM
To: pgsql-general@lists.postgresql.org
Subject: RE: Enforcing uniqueness on [real estate/postal] addresses
Think Before You Click: This email originated outside our organization.
On Wed, 13 May 2020, Basques, Bob (CI-StPaul) wrote:
> Was wondering if you ever thought about binding the textual address to
> a USNG location. https://usngcenter.org/
Bobb, et al.:
Why not have a 'parent' table with entries such as 'Foo Farm' and a 'child'
table with rows for sub-parts of the parent; e.g., 'Barn', 'Field'?
Rich
