Distance limits ability to see Custom POIs

 

mgarledge recently had a problem with being able to see a Budapest POI on her unit. This was discussed in the thread "BaseCamp Help And Information" (see http://www.poi-factory.com/node/35029) Note that mgarledge was the OP of that thread)

Anyway, she learned Basecamp well enough to have it send files to her unit. She was doing well until she discovered that a location in Budapest would not show up on her unit but a similar location in Prague would. She was tearing her hair out, as it were. I inputted her Budapest location and I could see it.

So it appeared that the file from Basecamp was valid - it was working on my units.

We then decided that it must be "distance" dependent where the "distance" was from each of our units. She could change her "search near" location and find Budapest.

I set about determining if distance from the unit could be a factor on the unit recognizing a POI. I seemed to remember a similar issue several years ago but could not find the thread.

What I have determined is that my units (765 and 2595) will not recognize a location that is over 6,263 miles from the unit itself. Since the programming of our Garmins internally uses the metric system, I had thought that the distance would be a round kilometer number but it is not. It is 10,079.

Let's all try to remember this when someone asserts that their POI can not be found.

.

The distance limitation is in the Garmin knowledge Base:

Why are my Custom POIs not showing up when I go to Extras on my device?

"If they are several hundred miles away, they will not show up even when searching by name. To find these points you will need to set your location near the Custom POIs and then search for them."

 
Also, I get a smaller maximum distance on my 2595 (with V8.20 firmware).

At 7100 km or 4400 miles, mgarledge's Budapest POI was visible from my location, so I added another for Moscow, which did not show up.

It's approximately 8700 km or 5400 miles to Moscow according to my 2595. So the maximum POI distance for my 2595 is somewhere between 7100-8700 km or 4400-5400 miles.

--
Nüvi 2595LMT

Interesting

WAASup wrote:

...
Also, I get a smaller maximum distance on my 2595 (with V8.20 firmware).

...

My "About" says
Model: nuvi 2595
Hardware Version: nuvi 2595 C2p2 A V7 8GB 128MD s TE
Software Version: 8.20
...

so we should be getting similar maximum distances. Plus my 765 gets, as far as I can determine, exactly the same results on distances from a file I created using EPE for points in Africa and Egypt - that is, we both see the same locations and fail to see other locations farther than 6,263 miles from my house.

I had found Garmin's answer myself but it said "hundred's of miles when I knew that it had to be "thousands" of miles (at least for nuvis)

I do not know why it would make a difference but I followed your Moscow trials. I used a file with the EPE coordinates of 37.620691 & 55.753947 for Red Square. When I used your location, I did not get Moscow. The best I could do was Barry's Bay which showed a distance of 4512 miles.

I wonder what being farther north has to do with it?

So, the mystery remains.

If not for John

I said I was done with trying to work out my problem and going to sew. John emails me for my files and thanks to his interest I started back working with him.

Thanks to jgermann (John) and everyone else who helped keep me on track.

This is a great network of friends here.
And I didn't have to pull my hair out. smile

--
Mary, Nuvi 2450, Garmin Viago, Honda Navigation, Nuvi 750 (gave to son)

.

I'd think the easiest solution would be to simulate your position, and check POI's from that location on the GPS.

The KISS (Keep It Simple, Silly) principle.

--
nüvi 3790T | Those who make peaceful revolution impossible, will make violent revolution inevitable ~ JFK

How to...

Juggernaut wrote:

I'd think the easiest solution would be to simulate your position, and check POI's from that location on the GPS.

The KISS (Keep It Simple, Silly) principle.

When KISS relates to me, I usually phrase it as "Keep it simple, stupid!" I learned a long time ago to try to eliminate as many variables and/or conditions as possible when debugging. That it why, when dealing with someone's POI problems, I suggest deleting all existing .gpi files (or alternatively renaming .gpi files to .gpiold) so that the unit will be working with only the problem POI(s). That "simplifies" to problem.

Applying "simulation" to distance problems is interesting. On my newer 2595, the "Searching Near" feature on the screen which follows "Where To?" gives us an easier way to "simulate" being in another place.

On my 765, if I wanted to check distances from a location other than my current location, I would have to do
Tools > Settings (wrench) > system > GPS Simulator > On > OK > Back (hold down).

Then I could do
Where to > [down arrow] > Cities > Spell > [name of city] > map > Set Loc. > back > Extras > custom POIs > [find category].

So, even though I could get my 2595 thinking it is actually at another city by following steps similar to the 765, the newer model "Searching Near" is the way to go.

Search nearby

This was another lesson for me. I have only used the search nearbt from where I am now.

Would have never known about checking poi problem with search nearby if not for John keeping me on track.

--
Mary, Nuvi 2450, Garmin Viago, Honda Navigation, Nuvi 750 (gave to son)

I have to look out the

I have to look out the window.

:)

triliby wrote:

I have to look out the window.

grin grin

--
Mary, Nuvi 2450, Garmin Viago, Honda Navigation, Nuvi 750 (gave to son)