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

Add supported for blacklisted sources #224

Open
trescube opened this issue Jan 31, 2017 · 0 comments
Open

Add supported for blacklisted sources #224

trescube opened this issue Jan 31, 2017 · 0 comments

Comments

@trescube
Copy link
Contributor

trescube commented Jan 31, 2017

Occasionally OA sources just have terrible data. For example, Lamar County, TX has, more often than not, wildly incomplete data that extends beyond 0 house numbers:

  • 215 SE 33RD - no street type and directional should be post
  • 2 W PLAZA & 135 BONHAM - inexplicable house number with intersection
  • OLD BELK'S PARKING LOT - GIS admin is on drugs
  • 112 BONHAM ST - SHOE STORE - ibid
  • 2ND NE @ E KAUFFMAN - intersection
  • 800 BLK JACKSON ST - block address

It would be programmatically difficult to determine address validity on a per-row basis, so this solution would blacklist an entire source to reduce data pollution when the majority of a source is bad data.

@trescube trescube added this to the API Improvements milestone Jan 31, 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

2 participants