unforum

[KiLLyourTV]

[SPEC] New approach on Axon Puzzle.

[floorneyne]

I like the idea. Plus, if you find a distance that comes out to, like 999 km (27) then you can quit!

Xnbomb among others made a post about converting the coordinates to degree-minutes in that monster thread. I've read the whole thing as it developed, so just try searching through it (I'm sure it's a page higher than 20). Hope that helps... looking forward to seeing the results of your experiment!

[KiLLyourTV]

Ok, I found a site to convert to degrees and another to find the distance between them..

Thing is, I don't have the time to look them all up while I am at work, so if anyone wants to test my theory, by all means please do!!

KiLLyourTV

[sherpa]

Already posted in another thread, here's some of the maths already done.

Note, you don't need to convert to minutes using the site in Dana's blog.

[KiLLyourTV]

Can't view it at work, don't have Excel.

Has anyone tried adding the numbers in the distance (in km) together.
For example, if its 1326 km you get 12, which is the letter L etc.

The only reason I suspect this is because of the occurrence of 21 which is mentioned

KiLLyourTV

[firefox]

ive done some of it, with the values someone else has posted around here somewhere.
so far, there are outliers bugga like 28.
i take it that the values and distances (spreadsheet link around one of these forums) are correct.

also there are not many vowels.

will do more tonight tho, methinks to avoid errors we need to partition groups of numbers to different people, any volunteers?

ill also look more into the addition / subtraction of the numbers. something should be there. (if not well, i have time to burn)

[sherpa]

Just ran a few formulae in Excel.

All the numbers add up to less than 26. the distribution is fairly good, with averages in the 13-14 range for miles, nautical miles and kilometres.

I have a feeling this is more a property of the numbers themselves, than a property forced upon them. It's hard to get over 26 - for example 999 would be the ONLY three digit number to do so, and most of the distances are three digits (or a little above 1000, introducing nice low numbers into the bargain).

Add to this the facts that
* The numbers don't translate into meaningful straight-alpha readings, there are a lot of ks and few vowels
* How would you design this??

and I'm not sure this is really going anywhere, but others can feel free to try it

[KiLLyourTV]

Yeah, if it doesn't work, oh well. It was worth a shot to bring it to the open. I would have tested it at work, but that is damn near impossible for me to do.

Time to get back to thinking of what it could point to.

[msekolpsu]

Has anyone tried using nautical miles with this method? A ship probably would, but also the interesting thing is that 5913 miles = 5139 nautical miles. Both equal 21 = 7 x 3.

If that doesn't work, I was wondering if the numbers equal less than 26 or less than 21. If it's less than 21, perhaps the vowels are skipped.

[sherpa]

[msekolpsu]

Doesn't the number in Row 51 = 1999 = 28?

[sherpa]

Row 51-

32.7670N -117.0569E 41.9334N -87.6455E 2770 1720 1500 60 degrees (east-northeast)

From the website in Dana's blog; no 1999s there.

[keybsnbits]

has anybody actually strung all the letters together? with that many letters, I seriously doubt that we would have to rearrange them.

[msekolpsu]

Next line down sherpa, I'm going off the Excel spreadsheet posted here.

30.2072     -92.0384          47.681      -122.1254       1999

[sherpa]

Posted where? [Edit: ah, hang on, you mean the rough distances in 'deg min sec' sheet, not the ones in 'distances table', same spreadsheet.]

The one I have - again, this is using the site in Dana's blog, not direct calculation - has for line 52 (and maybe it would have helped if you'd clarified which line that is, first?) as :

30.2072N -92.0384E 47.6810N -122.1254E 3210 2000 1730 316 degrees (northwest)

I see the 1999/2000 could be differences in calculation methods, but this method has it as still adding up under 26..