Coordinates on iPhone

[bergliebe]

I want to introduce newbie's to Geocaching. I want them to try how fun Geocaching is without them have to download an app before or register.

So I give them coordinates to look for on their smartphone.

For example 47 23.333 9 23.333.

Android users can type loc:47 23.333 9 23.333 and get to the correct tree but not iPhone users. Neither with apple maps nor with google maps.

What can I do that it works both for Android and iPhone users?

[+Chief301]

Android and iPhone are two completely different operating systems and therefore there isn't one app that works for both.

 

I have no experience with Android devices but Motion X Lite is a good, free, general purpose GPS app for the iOS platform.

[+coggins]

Google Earth works on both IOS and Android and 47 23.333 9 23.333 works out just dandy on an iPhone with Google Earth.

 

Google Earth for Android: https://play.google.com/store/apps/details?id=com.google.earth&hl=en

Google Earth for IOS: https://itunes.apple.com/us/app/google-earth/id293622097?mt=8

[bergliebe]

Thanks for your answers.

It works on Android, have to find an iPhone to test on that.

[+Lieblweb]

Since Geocaching is all done in Latitude and Longitude.... You should probably teach them about 'converting' those Decimal minutes to Longitude and Latitude.

Here's a nice website to convert them:

http://boulter.com/gps/

 

Your number: 47 23.333 9 23.333

Converts to this: N 47 23.333 E 9 23.333

 

In Google Maps - type in the coordinates like this: N47 23.333, E09 23.333

Spaces & commas to separate them. Works fine for Google maps and most all over mapping Apps I have on my Iphone.

Longitude & Latitude is what handheld GPS use AND the Geocaching.com

Edited September 11, 2013 by Lieblweb

[bergliebe]

Thanks. But that doesn't seem to solve the problem. It still shows the next address (Bächlistrasse 9) and not the tree.

[+coggins]

Thanks for your answers.

It works on Android, have to find an iPhone to test on that.

Oh, I'm typing this on an iPhone, yes it works on both unlike some other suggestions.

[bergliebe]

Great. It works on iPhone in Google Earth. Eventually a program where it works on iOS.

Both on Android (Google Maps/Earth) and iOS (only Google Earth) it works as following

loc:47 23.333 9 23.333 and shows the exact position and not the next address.

Thanks for all your help.

[+coggins]

Great. It works on iPhone in Google Earth. Eventually a program where it works on iOS.

Both on Android (Google Maps/Earth) and iOS (only Google Earth) it works as following

loc:47 23.333 9 23.333 and shows the exact position and not the next address.

Thanks for all your help.

You don't need to use "loc:" before the numbers, 47 23.333 9 23.333 works without the "loc:"

[+Walts Hunting]

Since Geocaching is all done in Latitude and Longitude.... You should probably teach them about 'converting' those Decimal minutes to Longitude and Latitude.

Here's a nice website to convert them:

http://boulter.com/gps/

 

Your number: 47 23.333 9 23.333

Converts to this: N 47 23.333 E 9 23.333

 

In Google Maps - type in the coordinates like this: N47 23.333, E09 23.333

Spaces & commas to separate them. Works fine for Google maps and most all over mapping Apps I have on my Iphone.

Longitude & Latitude is what handheld GPS use AND the Geocaching.com

Both numbers are long lat just in different datum forms. You are not "converting" to lat lon.

[+coggins]

Since Geocaching is all done in Latitude and Longitude.... You should probably teach them about 'converting' those Decimal minutes to Longitude and Latitude.

Here's a nice website to convert them:

http://boulter.com/gps/

 

Your number: 47 23.333 9 23.333

Converts to this: N 47 23.333 E 9 23.333

 

In Google Maps - type in the coordinates like this: N47 23.333, E09 23.333

Spaces & commas to separate them. Works fine for Google maps and most all over mapping Apps I have on my Iphone.

Longitude & Latitude is what handheld GPS use AND the Geocaching.com

Both numbers are long lat just in different datum forms position formats. You are not "converting" to lat lon.

Fixed that for you.