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 all DOR parcels into Engine and match spatially to PWD #81

Open
bertday opened this issue Dec 16, 2016 · 0 comments
Open

Allow all DOR parcels into Engine and match spatially to PWD #81

bertday opened this issue Dec 16, 2016 · 0 comments

Comments

@bertday
Copy link
Contributor

bertday commented Dec 16, 2016

Currently there are a number of DOR parcels that are missing from AIS because they don't meet the requirements for an addressable parcel (no street name, house number, etc.) As a result when you click on those parcels in Atlas you get an error message that no addresses were found. This probably isn't the ideal user experience and we'll need those parcels in order to replicate the functionality of apps like Parcel Explorer, so for now I think we should let those parcels into AIS and continue to flag any hygiene issues in the dor_parcel_error table.

Then in load_addresses, intersect DOR parcels with PWD and write rows to address_parcel using the PWD parcel address and a match type of pwd_spatial.

That way (almost) all DOR parcels should have a good address and will be queryable via the API.

Good test case: Reading Terminal Market (3 remainder parcels with no addresses).

@bertday bertday changed the title Allow all DOR parcels in Engine and match spatially to PWD Allow all DOR parcels into Engine and match spatially to PWD Jan 4, 2017
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

1 participant