The locations I parsed in the first pass through OpenBeta's climbing data (https://github.com/OpenBeta/climbing-data/tree/main) provided the basic functionality, but the hierarchy makes more sense for some areas than others. I need to go back in and clean up some of them (examples: IL is too granular, and parts of UT are too broad).
Also might refactor data processing into a script and just use the notebook for EDA. This would make it easier to rerun with slight tweaks (or new custom locations).
The locations I parsed in the first pass through OpenBeta's climbing data (https://github.com/OpenBeta/climbing-data/tree/main) provided the basic functionality, but the hierarchy makes more sense for some areas than others. I need to go back in and clean up some of them (examples: IL is too granular, and parts of UT are too broad).