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

resolve geoclient-pluto mismatches #23

Open
wstlabs opened this issue Apr 15, 2017 · 1 comment
Open

resolve geoclient-pluto mismatches #23

wstlabs opened this issue Apr 15, 2017 · 1 comment
Labels

Comments

@wstlabs
Copy link
Collaborator

wstlabs commented Apr 15, 2017

Sometimes Geoclient and Pluto don't seem to agree on a BIN for a building (even for a single-building lot). As a result, a lot with a building shows up without its building (and sometimes being described as "a vacant lot"). Related to issue/14.

Example (1): "1461 Pennsylvania Avenue, Brooklyn, NY, United States"

Geoclient resolves this address to (3044520325,3098300).
However pluto says that bbl = 3044520325 has one building, 3398314.
And bin = 3098300 matches only one lot, 3044520300.

Example (2): 39 Eldridge St / 89 Canal St
Geoclient resolves to (1003010013,1081957) in agreeance with PAD. However in the shapefiles, that BIN is attached to 1003010001 (along with the buildings on several adjacent lots). In any case it currently shows up as a vacant lot.

@wstlabs wstlabs added the bug label Apr 15, 2017
@wstlabs
Copy link
Collaborator Author

wstlabs commented Jul 11, 2017

select * from omni.building_origin where bin = 3098300;
bbl | bin | in_adr | in_pluto | bbltype | bintype | total_adr | total_pluto
------------+---------+--------+----------+---------+---------+-----------+-------------
3044520300 | 3098300 | f | t | 1 | 1 | | 1
3044520325 | 3098300 | t | f | 1 | 1 | 2 |

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

No branches or pull requests

1 participant