Hi. This is my first post here. Fairly new to POI stuff.
Using a Kenwood system (510) in vehicle.
I brought up the direct satellite display info on screen and then read the coordinates directly from there for a location (speed camera).
It showed on screen: N47 17 294 W122 10 856 when the car was right at the location.
I converted to decimal: 47.2881 / -122.18067
Unfortunately google earth shows that out in the middle of puget sound, lol.
It seems odd that the unit itself would be incorrect on the coordinates since that's what it uses to display the map.
Is there something simple that I am missing?
When I Google Map those coordinates (47.2881,-122.18067), I get a location on highway 164 (Auburn Way S). Your first set of coordinates seems to be missing some punctuation or has extra numbers. Is it supposed to be DMS or Deg, Min?
-122.18067 / 47.2881 is what google earth shows for the proper location.
-122.40444 / 47.365 is what the conversion gave me when I took the numbers right off the unit's screen and converted.
This is what the "satellite info" screen showed on the unit for location:
Note: This is a 20mph speed camera in a school zone. Auburn seems to be going nuts with their camera program this year.
Again, I think you are missing punctuation or are plugging the coordinates in to the wrong converter.
When I plug 47.2881, -122.18067 into my Zumo and change the coordinates to dd mm.mmm, I get N47 17.286 W122 10.840 which plots out on Google Maps to that same location (or nearly the same) on Auburn Way S.
If I plug your original coordinates like this (N47 17.294 W122 10.856) into my Zumo, I get N47.28823 W122.18093.
OK so N47,17,294 on screen shound be read N47 17.294.
Thanks for correcting my syntax on those for converting
I'm not sure why the unit is showing commas since I'm not aware of any coordinate formats that contain commas.
Just for reference, here are some coordinate comparisons.
Coordinates can be expressed in several different formats. They are most commonly Degrees Minutes Seconds (DDD MM SS), Decimal Degrees (DDD.DDDD), or Degrees, Decimal Minutes (DDD MM.MMM). The last format is the most common in current GPS models. The second one is the one we use in Custom POI files.
Degrees, Minutes and Seconds
DDD° MM' SS.S"
N 32° 18' 23.1" W 122° 36' 52.5"
N 32.30642° W 122.61458°
Degrees and Decimal Minutes
N 32° 18.385' W 122° 36.875'
And be sure to remember that the integer part of the minutes and seconds can't be greater than 59 just like minutes and seconds on a clock.
Motorcycle Mama, I am using a SPc340. I am puting coordinates in my POIs as follows.
-83.5410228 33.502054 (From Google Earth)
When I use POI Editor I get two results:
Lat 33.8281 Long -83.9035
. N S 33.49.11° ' " E W 83.54.12 (periods may be degree symbo;?)
The differance in the numbers doesn't concern me here. I am trying to understand the different formats and which format I use for the 349. Thanks for your help. I will also reread the above post and see if I can understand the different types.
Ok, I'm confused.
If you have these coordinates (-83.5410228 33.502054 [From Google Earth]), you should not need any conversion, so I'm not sure where this (Lat 33.8281 Long -83.9035) comes from.
On my Zumo when I input -83.5410228 33.502054, I get
N 33° 30' 07.4" W 083° 32' 27.7" (DMS) and
N 33° 30.123' W 083° 32.462' (Degrees Decimal Minutes).
Common mistakes include putting a decimal point where there should be a space and the mixing up the different format types.
When I create a POI I use Excel and save as a CSV file. I enter it as a decimal number(?) without letters but wit a minus sign (-) where appropriate. When I download my favorites file the Coord. appear to be in the Degrees Decimal Minutes format, Can I convert this format to the one I use in the Excel file> If so how.
I use the geocode converter at the above URL. For your purpose, you can cut the name, desc, latitude, longitude from the Excel file and paste it into the utility. You can do the whole column at once too.
Yeah, I can confirm the coordinates as MM stated. I got the same as her. Perhaps it was an input error.
terms | privacy | contactCopyright © 2006-2022