It looks like MP is inconsistent with how they define regions and subregions for the location of a climbing route. For example, the longest location is:
Motherlode Rock - North Face > Motherlode Rock > Central Pinnacles > Holcomb Valley Pinnacles > Big Bear City Area > Big Bear North > Big Bear Lake Area > San Bernardino Mountains > California
A shorter location is:
Bob's Rock > Buena Vista > Colorado
Why this is a problem:
Cleaning the location string is not really possible, meaning that it's not query-able
Solutions:
HARD: MP gives latitude, longitude for each route. We could do a 'classifier' (ML sidequest?) that categorizes the lat longs based off of a geo bounding box, and sorts them into our manually defined climbing defined regions
EASY: extract the state from the location string, use that as the location
EASY: Pull climbing area csv data manually (Ex: Yosemite, Red River Gorge, etc), and encode the area with each data push
Our route dataset comes from Mountainproject.com (MP)
It looks like MP is inconsistent with how they define regions and subregions for the location of a climbing route. For example, the longest location is:
Motherlode Rock - North Face > Motherlode Rock > Central Pinnacles > Holcomb Valley Pinnacles > Big Bear City Area > Big Bear North > Big Bear Lake Area > San Bernardino Mountains > CaliforniaA shorter location is:
Bob's Rock > Buena Vista > ColoradoWhy this is a problem: Cleaning the location string is not really possible, meaning that it's not query-able
Solutions: