Difference between revisions of "Geohashing talk:Coordinate calculators"
From Geohashing
imported>Angel |
imported>GeorgDerReisende (explanation and calculation) |
||
| Line 7: | Line 7: | ||
**Yesterday I got the coords from geohashdroid, but failed due to other stuff. When I mentioned to someone that I'd failed, they were curious, so I went to give them a carabiner link. Carabiner and geohashdroid disagree about where yesterday's hash was, and today's. Bearing in mind the message up there ^^ I went and checked anthill; which gives me yet another different location for today's, but I can't figure out if I can use that to double-check yesterday's. Is there a page somewhere explaining what the issue is, and which software may be working? | **Yesterday I got the coords from geohashdroid, but failed due to other stuff. When I mentioned to someone that I'd failed, they were curious, so I went to give them a carabiner link. Carabiner and geohashdroid disagree about where yesterday's hash was, and today's. Bearing in mind the message up there ^^ I went and checked anthill; which gives me yet another different location for today's, but I can't figure out if I can use that to double-check yesterday's. Is there a page somewhere explaining what the issue is, and which software may be working? | ||
| + | |||
| + | **I don't know when your yesterday was, but if you are in doubt of the correct hash, you can calculate it on your own: (be aware, we are east of W30 here) you take the date in the form 2015-03-23 (next monday) and the last known DJIA open rate from the day before or, if that day has none, the last day more before 17,961.13 (last friday) from [http://www.google.com/finance/historical?q=indexdjx:.dji here] and concatenate them in the following: 2015-03-23-17961.13 . Then use http://elmar-eigner.de/md5_maker.html for the calculating of the md5. The first sixteen digits are the decimal places for the latitude and the last sixteen digits are the decimal places for the longitude. Then use http://www.easysurf.cc/cnver17.htm#bf16tobf10 for the calculating of the decimal fractions. This results in: | ||
| + | |||
| + | {| class="wikitable" | ||
| + | |- | ||
| + | | 2015-03-20 || 18072.58 || 2015-03-20-18072.58 || f5c988ff692d329d397cafe01d7114c2 || f5c988ff692d329d || 397cafe01d7114c2 || lat.9601064323007236 || lon.22455882283742695 | ||
| + | |- | ||
| + | | 2015-03-21 || 17961.13 || 2015-03-21-17961.13 || 8c0f44b40817bb5cdd30af937ebbde39 || 8c0f44b40817bb5c || dd30af937ebbde39 || lat.5471079768686583 || lon.8640241370292041 | ||
| + | |- | ||
| + | | 2015-03-22 || 17961.13 || 2015-03-22-17961.13 || 126668d2c12d34071b14da6f1b440bcc || 126668d2c12d3407 || 1b14da6f1b440bcc || lat.07187514443755988 || lon.10578694546281059 | ||
| + | |- | ||
| + | | 2015-03-23 || 17961.13 || 2015-03-23-17961.13 || 9b39321ec7e2856536662533ced5ed90 || 9b39321ec7e28565 || 36662533ced5ed90 || lat.6063414883755148 || lon.21249611391871043 | ||
| + | |} | ||
| + | |||
| + | [http://geohashing.info/ eupeodes'], [http://geo.crox.net/poster/2015-03-20_51_10 crox'] and [http://tjum.anthill.de/geohash.html Ekorren's] calculations are ok, because they calculate the hashes on their own, but everybody making calculation of peeron's base are wrong. --[[User:GeorgDerReisende|GeorgDerReisende]] ([[User talk:GeorgDerReisende|talk]]) 07:09, 22 March 2015 (EDT) | ||
Revision as of 11:09, 22 March 2015
Who is the tool and why does he have a page?
why is the Peeron Map listed under "not working"? it seems up at the original address and okay to me. Tom (talk) 02:50, 20 June 2014 (EST)
- As of right now, it's not listed under "not working" anymore, but I'm still having trouble with it. The buttons on the upper right corner of the map for switching between street view and earth view, and toggling 45° view, are all hidden behind the white "Geohashing Coordinate Calculator" banner, and so I can't click them. --Dvdllr 10:20, 15 January 2015 (EST)
- Yesterday I got the coords from geohashdroid, but failed due to other stuff. When I mentioned to someone that I'd failed, they were curious, so I went to give them a carabiner link. Carabiner and geohashdroid disagree about where yesterday's hash was, and today's. Bearing in mind the message up there ^^ I went and checked anthill; which gives me yet another different location for today's, but I can't figure out if I can use that to double-check yesterday's. Is there a page somewhere explaining what the issue is, and which software may be working?
- I don't know when your yesterday was, but if you are in doubt of the correct hash, you can calculate it on your own: (be aware, we are east of W30 here) you take the date in the form 2015-03-23 (next monday) and the last known DJIA open rate from the day before or, if that day has none, the last day more before 17,961.13 (last friday) from here and concatenate them in the following: 2015-03-23-17961.13 . Then use http://elmar-eigner.de/md5_maker.html for the calculating of the md5. The first sixteen digits are the decimal places for the latitude and the last sixteen digits are the decimal places for the longitude. Then use http://www.easysurf.cc/cnver17.htm#bf16tobf10 for the calculating of the decimal fractions. This results in:
| 2015-03-20 | 18072.58 | 2015-03-20-18072.58 | f5c988ff692d329d397cafe01d7114c2 | f5c988ff692d329d | 397cafe01d7114c2 | lat.9601064323007236 | lon.22455882283742695 |
| 2015-03-21 | 17961.13 | 2015-03-21-17961.13 | 8c0f44b40817bb5cdd30af937ebbde39 | 8c0f44b40817bb5c | dd30af937ebbde39 | lat.5471079768686583 | lon.8640241370292041 |
| 2015-03-22 | 17961.13 | 2015-03-22-17961.13 | 126668d2c12d34071b14da6f1b440bcc | 126668d2c12d3407 | 1b14da6f1b440bcc | lat.07187514443755988 | lon.10578694546281059 |
| 2015-03-23 | 17961.13 | 2015-03-23-17961.13 | 9b39321ec7e2856536662533ced5ed90 | 9b39321ec7e28565 | 36662533ced5ed90 | lat.6063414883755148 | lon.21249611391871043 |
eupeodes', crox' and Ekorren's calculations are ok, because they calculate the hashes on their own, but everybody making calculation of peeron's base are wrong. --GeorgDerReisende (talk) 07:09, 22 March 2015 (EDT)
