View Full Version : Coolest Pool

07-14-2005, 11:31 AM
Have a look at this swimming pool

30 4'21.25"N

07-14-2005, 12:27 PM

It has a well known water brand name written on its ground with black tiles.

07-14-2005, 12:52 PM
Ixo - how did you convert

5127'10.95N, 006'22.48"
51.45304246553663,-0.1062441012009909 ?

Copy/pasting your string of numbers took me right to the Evian pool. I put the kmz file here (http://www.googleearthhacks.com/forums/downloads.php?do=file&id=378)

07-14-2005, 02:02 PM
Hmm, I think I put a placemark (CTRL-N) and then copied it to the clipboard and to a text-editor. There you find the decimal coordinates in the <coordinates> tag. Beware that they are internally noted as lon/lat whereas the Google Earth search field expects lat/lon. So you have to swap the numbers.

I personally like the lon/lat notation because it resembles x/y. I think that's why the Keyhole programmers choosed it like this. "Correctly" spoken, people use lat/lon as a standard. That's why the Google Earth interface expects lat/lon.

If you are intending to convert degrees, hours, minutes to decimal degrees by hand (or with a small program) you have to convert the base from hours (60) and seconds (60) to 100. Have a look at Alltrans (http://www.allsat.de/en/software_alltrans.htm) to play around with coordinate transformations. I could also give you some C++ code if that helped?

07-14-2005, 03:40 PM
It works! Thanks Ixo. (I first tried to open the kmz file in notepad - that didn't work. Right click and choose copy, then open Notepad and paste.)

It is so nice to have people far wiser than myself here on the GEH forums who are willing to share.

07-14-2005, 04:04 PM
So are we assuming that the pool is also *filled* with Evian?

07-14-2005, 04:29 PM
how did you convert
5127'10.95N, 006'22.48"
51.45304246553663,-0.1062441012009909 ?

I discovered the secret! The answer is in this thread (http://www.googleearthhacks.com/forums/showthread.php?t=102).

07-18-2005, 08:35 PM
where do I search latatude and longitude?

07-19-2005, 01:52 AM
nevermind I see how now.