Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow users to view identify results for stacked parcels #131

Open
rkelson opened this issue Dec 8, 2022 · 4 comments
Open

Allow users to view identify results for stacked parcels #131

rkelson opened this issue Dec 8, 2022 · 4 comments
Assignees

Comments

@rkelson
Copy link
Member

rkelson commented Dec 8, 2022

In some counties condo and apartment parcels might be a stack of parcels with the same geometry. In Utah county, south of the Vineyard Connector Rd., there are good examples of this:
https://parcels.utah.gov/#/location/-12440666.900157992,4910819.476840503,1128.497176
image

I can see Utah Co is dealing with this a few different ways however, stacked parcels exist. It would be an improvement if the app allowed users to click through the multiple parcels with identical geometries in the identify results:
image

@steveoh
Copy link
Member

steveoh commented Dec 8, 2022

Interesting. So a parcel isn't only a piece of land, it could be a floor or room in a building?

@rkelson
Copy link
Member Author

rkelson commented Dec 8, 2022

Not exactly. Think of it for tax purposes; that geometry represents 3 unique parcel IDs, 3 address, and 3 tax payers
image

@steveoh
Copy link
Member

steveoh commented Dec 8, 2022

Yeah that's a much better way to think about it. Taxes.

@steveoh steveoh self-assigned this Dec 8, 2022
@rkelson
Copy link
Member Author

rkelson commented Dec 8, 2022

yeah parcels are more than just a boundary. For me they are a boundary with a unique ID that can be linked to all sorts of attributes across multiple offices and organizations.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants