Uh oh!
There was an error while loading. Please reload this page.
Predict on new addresses - #5
Merged
Merged
Conversation
geneorama
commented
Dec 21, 2017
Member
Just reviewed the changes with @potash, everything looks good. This should help with new addresses that fall into geographies that we have not previously seen with the model. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This updates the saved feature matrix ("address_data_today") to include a row for a new address in each geography tuple (intersection of a community area, ward, and census block-- there are ~60k such tuples). This gets used by the API whenever we get an address that geocodes but was not in any of our address datasets, we simply grab the row corresponding to its geography tuple.