Community Spring Cleaning week is here! Join your fellow Maveryx in digging through your old posts and marking comments on them as solved. Learn more here!

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 #70: Trade Area Drivetime Radii

SeanAdams
17 - Castor
17 - Castor

:-) I knew you wouldn't leave us hang @MattD - you're a legend!

Now I have to go back and redo this challenge using your über macro - but that's OK 'cause it's like a second version of challenge 70!

 

(For those Flula AutoTunes fans, that's that "über" with an uuuu like "uuuu - this spaghetti's on my feet" - http://tinyurl.com/ooqtfqq  :-))

Simona
7 - Meteor

A bit in late but I managed to find some time to look at last week challenge :)

A bit sad that I do not have the drive time installed but... I did it using kilometres instead! 

Spoiler
I used only a few tools, first turning the lat long into centroids, then building trade areas polygons around the points, then just the summarize tool to get the intersection and lastly the spatial info to know the area in km of that polygon. Pretty nice!!
Capture.PNG
MattD
Alteryx Alumni (Retired)

Here's a solution!

 

Spoiler
Solution.PNG
Former Alteryx, Inc. Support Engineer, Community Data Architect, Data Scientist then Data Engineer
Garrett
11 - Bolide

Looks like everyone used pretty much the exact same approach. Assuming you had drivetime data handy of course...

LordNeilLord
15 - Aurora

Not having the drivetime tools I went for 11.5 miles trade area which gave me roughly the same AreaSqMi as the solution:

 

Spoiler
Weekly Challenge 70.png
nick_ceneviva
11 - Bolide

My solution is attached.  Because I didn't have the drive time data sets available, I just used a trade are of 15 miles.  Looking at some of the other solutions it looks like I did a round about way to get the intersection but could have easily done it just using the summarize tool.  

jamielaird
14 - Magnetar

Here's my solution.  

 

Since I don't have the drivetime data I used a radius of 11.25 miles, based on 30 mins at 45 MPH.

 

I added a validation step by splitting the polygon into boundary points and using the awesome macro provided by @MattD to calculate the drivetime between each office and boundary point.  Results seem to show that the 30 min estimate is reasonable.

 

Spoiler
challenge-70.png

 

 

patrick_digan
17 - Castor
17 - Castor
Spoiler
Having never really worked with spatial objects, I didn't realize you could use the summarize tool to get the intersection!
marcreid
7 - Meteor

Used 11.5 miles for the trade area so got a slightly smaller overlap area

Spoiler
image.png
ggruccio
ACE Emeritus
ACE Emeritus

Depends on drivetime engine - I used TomTom Q2 Off Peak