Skip to content

Comments

Location codes#2

Open
rbzargon wants to merge 32 commits intobonetrees:masterfrom
rbzargon:location_codes
Open

Location codes#2
rbzargon wants to merge 32 commits intobonetrees:masterfrom
rbzargon:location_codes

Conversation

@rbzargon
Copy link
Contributor

No description provided.

@rbzargon
Copy link
Contributor Author

Location code parsing, retrieval, and storage

Reset tinydb before write
Add TODO for alternative  save/db implementations
Performance improved thousands of times
@rbzargon
Copy link
Contributor Author

Improved performance with bulk-write operation

Move to model/location_codes.py
Move to model/location_codes.py
Having it in a separate file was over-engineering
Moved functionality to model/location_codes to simplify
Plan to create tinydb repo instead
LocationCodes can be greatly simplified since isn't too large to need to be saved to a repo, purpose is intermediary model to pass on to ValidCodes
Interface for repositories (e.g. databases)
Minimal implementation of a tinydb repo
@rbzargon
Copy link
Contributor Author

rbzargon commented Feb 3, 2019

Move files to realestate submodule dir
Repo dir
LocationCodes simplification, uses DataFrame

  • can be greatly simplified since isn't too large to need to be saved to a repo, purpose is intermediary model to pass on to ValidCodes

rbzargon added 3 commits May 5, 2019 06:19
Save codes to json in /data
data/code_combinations.json is too large -- ~250 MB, need to refactor to use generators
Approx number of code combinations by location type (whether valid or invalid):
State - 5.5k
Metro - 96,9k
County - 621k
City - 2.8 million
Neighborhood - 1.7 million
Zipcode - 10.6 million
~250mb code_combinations.json exceeds github 100mb limit
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant