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

Consider adding tax block/lot to recommended or optional fields #73

Closed
jqnatividad opened this issue Dec 8, 2015 · 10 comments
Closed

Comments

@jqnatividad
Copy link

as this is often a more stable identifier that can also be used to crosswalk other jurisdiction datasets (i.e. property tax)

@jqnatividad
Copy link
Author

On second thought, required might be too stringent, perhaps recommended or optional.

@mheadd mheadd changed the title Consider adding tax block/lot to required fields Consider adding tax block/lot to recommended or optional fields Feb 11, 2016
@jqnatividad
Copy link
Author

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.

https://en.wikipedia.org/wiki/Assessor%27s_parcel_number

@mheadd
Copy link
Member

mheadd commented Feb 12, 2016

In Philadelphia, its referred to as OPA or BRT number (OPA = Office of Property Assessment, BRT = Board of Revision of Taxes [deprecated]).

@mheadd mheadd added in progress and removed ready labels Feb 12, 2016
@mheadd
Copy link
Member

mheadd commented Feb 16, 2016

Some proposed language for adding a new Parcel ID filed to the list of recommended fields in the Core Permit Dataset.

Recommended

Field DataType Description
Parcel ID TEXT Unique identifier for a land parcel within a jurisdiction. The identifier may be colloquially referred to as assessor's ID, tax ID, parcel number, etc.

@mheadd mheadd added this to the Version 1.2 milestone Feb 16, 2016
@mheadd
Copy link
Member

mheadd commented Feb 17, 2016

Related to this issue about multi-parcel permits.

@jqnatividad
Copy link
Author

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."

@mheadd
Copy link
Member

mheadd commented Feb 19, 2016

Makes sense to me. Will wait to hear if others offer suggestions and update here when the change is finalized.

@bettin
Copy link

bettin commented Mar 8, 2016

How is this different than the "PIN" field in the Recommended list which is for "Parcel Identification Number"
https://github.com/open-data-standards/permitdata.org/wiki/Core-Permits-Dataset-Requirements#recommended

@mheadd
Copy link
Member

mheadd commented Mar 8, 2016

@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?

@mheadd
Copy link
Member

mheadd commented Apr 1, 2016

Closed with this change.

@mheadd mheadd closed this as completed Apr 1, 2016
@mheadd mheadd removed the in progress label Apr 1, 2016
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

3 participants