-
Notifications
You must be signed in to change notification settings - Fork 7
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
Consider adding tax block/lot to recommended or optional fields #73
Comments
On second thought, required might be too stringent, perhaps recommended or optional. |
a.k.a. Assessor's parcel number, Assessor's identification number, Property identification number, Property Account number, tax id number, parcel identification number, sidwell number, borough block lot (NYC), etc. |
In Philadelphia, its referred to as OPA or BRT number (OPA = Office of Property Assessment, BRT = Board of Revision of Taxes [deprecated]). |
Some proposed language for adding a new Recommended
|
Related to this issue about multi-parcel permits. |
What about this expanded description? "Primary unique identifier for a land parcel within a jurisdiction used for tax assessment purposes. The identifier may be colloquially referred to as assessor's ID, tax ID, parcel number, etc." |
Makes sense to me. Will wait to hear if others offer suggestions and update here when the change is finalized. |
How is this different than the "PIN" field in the Recommended list which is for "Parcel Identification Number" |
@bettin: Hmm, perhaps we should update the existing PIN field with the description provided by @jqnatividad. I missed that when I reviewed this issue. I think the intent in including it was to address the kinds of issue Joel raised, but the description as is isn't very helpful. Thoughts? |
Closed with this change. |
as this is often a more stable identifier that can also be used to crosswalk other jurisdiction datasets (i.e. property tax)
The text was updated successfully, but these errors were encountered: