open-data-standards/permitdata.org

A Permit with multiple parcels

Opened this issue · 2 comments

How would a permit with multiple parcels be best handled in BLDS?

In an extreme example, a single permit for a pipeline that is several miles long crossing hundreds of properties. There really isn't a "primary" parcel that could be used, nor would we want people to think that the permit was only on one property.

Would something as simple as a separate optional PIN table work?

PermitNum |  PIN
B-1       | 10001
B-1       | 10002
B-1       | 10003
B-1       | 10004
B-2       | 14444
B-2       | 14445
B-3       | 10101

Could the PIN be an array?

@dvdhns What permit type, or - more accurately - what PermitTypeMapped value would such a project use?

Interested in how frequent an occurrence this would be for you.