Advent of Code is back! Unwrap daily challenges to sharpen your Alteryx skills and earn badges along the way! Learn more now.

Weekly Challenges

Solve the challenge, share your solution and summit the ranks of our Community!

Also available in | Français | Português | Español | 日本語
IDEAS WANTED

Want to get involved? We're always looking for ideas and content for Weekly Challenges.

SUBMIT YOUR IDEA

Challenge #32: Alteryx '16 Grand Prix (Race 2, L2)

patrick_digan
17 - Castor
17 - Castor

Solution attached

Spoiler
Capture.PNG
Natasha
9 - Comet

I took a different approach without the distance tool. I don't have the drive time package but my result matched.  

Spoiler
Instead of using a distance tool, I used a spatial Info tool to display the length of a line that followed the route.
Screen Shot 2017-10-28 at 13.05.44.png
JoshKushner
12 - Quasar

11 minutes. You win this round @jdunkerley79

samN
10 - Fireball

Just under 10 min. Its fun to see more variety in solutions when spatial widgets are used

ggruccio
ACE Emeritus
ACE Emeritus

Took more like 15 minutes, because I used the "driving distance" based on TomTom data, then was troubleshooting why it didn't match the output...which I found was based on "distance".  Provided solutions for both.

PhilipMannering
16 - Nebula
16 - Nebula

Solution attached.

 

Spoiler
challenge_32 - Snip.PNG
LandonG
8 - Asteroid

Solution attached.

jasperlch
12 - Quasar

Another good exercise on Spatial tools.

dsmdavid
11 - Bolide

Forgot to time myself...

Spoiler
32.png
msicak
8 - Asteroid

8.40 mins. lost 30 sec reformatting to match the desired output. 

 

Spoiler
challenge32.png