OK, OK, maybe it's just short of 500 miles (448 to be exact), but it shouldn't stop you from listening to the Proclaimers while solving this week's challenge!
This week we have an awesome submission from @kelly_gilbert! In the words of Kelly:
Leading up to Alteryx Inspire 2019, a few of my colleagues and I are doing a walking challenge. We are (virtually) walking 448 miles along the Natchez Trace Parkway (https://www.nps.gov/natr/index.htm) from Natchez, MS, to Nashville, TN. The goal is to walk, run, bike, etc. ~3 miles per day (starting in January) to make it to Nashville in time for Inspire! I wanted to show our progress by displaying our current positions along the route.
Goal: create a map that contains
1) A line showing the route
2) Points identifying the start and end of the route
3) Points showing the current location of each participant. The participant's location is the node that is closest to (but not farther than) the number of miles they have completed.
* natchez_trace_coordinates.yxdb contains the lat/lon of points along the route
* Participant List contains information about the participants
* Activity Log contains the daily miles for each participant
Node coordinate data © OpenStreetMap contributors (https://www.openstreetmap.org/), and route generated using OSRM (http://project-osrm.org/). Both data sources are made available under the Open Database License: http://opendatacommons.org/licenses/odbl/1.0/. Any rights in individual contents of the database are licensed under the Database Contents License: http://opendatacommons.org/licenses/dbcl/1.0/
I have a bit further to walk to get to Nashville from the Seattle area... about 2,400 miles on foot, which Google maps (quite unrealistically) estimates will take me approximately 780 hours to traverse... so that means I should have started walking about 20 days ago. Or at my preferred walking speed, more like 20 weeks ago. Oops.
Guess I'll fly there after all. :)
My solution is below. I can see that my participants' positions are a little bit off based on the expected output, and I'm fairly certain it has something to do with the way I calculated distance along the path. I'm just getting my start with spatial tools so this was a great challenge! I'm sure my workflow could use a lot of work, so I'm excited to see what everyone else builds!