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 #161: Triangles, Triangles, Triangles

TungThanhHo
8 - Asteroid

my solution with some help from posted solutions

martinding
13 - Pulsar
Spoiler
161.png

grazitti_sapna
17 - Castor

Solution to this with great efforts:

 

Sapna Gupta
CammyPhillips
8 - Asteroid
Spoiler
Spoiler
CammyPhillips_0-1670847422706.png

 

FinnCharlton
13 - Pulsar
Spoiler
FinnCharlton_0-1671529364729.png

 

FrederikE
13 - Pulsar
Spoiler
FrederikE_0-1672135993776.png

 

BS_THE_ANALYST
13 - Pulsar

Was a fun challenge! My interpretation of the problem was that each vertex of the triangle cannot share a longitude or latitude with any other vertex of that same triangle. I think that's the literal definition of non-collinear.

 

For my solution, it actually appeared that the furthest northeastern point and the furthest southeastern point lie on the same longitude. However, after checking the points themselves, this wasn't the case, so that is a valid triangle (non-collinear).

 

Lastly, I was concerned about comparing the different values for the longitudes/latitudes as the precision of a double might not be precise enough to equate two lats/longs. After checking the documentation, the datatype double is accurate up to 15 digits precision. Every data point is within this precision. 

BS_THE_ANALYST_0-1673545993252.png

 

Solution below:

Spoiler
BS_THE_ANALYST_1-1673546104674.png

 

 

 

kristiadiuisan
8 - Asteroid
Spoiler
Alteryx_challenge_161_KU.png
RobbieA
8 - Asteroid

My solution to 161, tricky challenge:

olga_strubbe
10 - Fireball
Spoiler
olga_strubbe_0-1680285071056.png

 

Loved this fun spatial challenge, thank you, @JoeM !