EPE

 

I tried to use EPE today to update the Jo-Ann Fabric and Craft Stores POI file that I maintain.

Immediately upon loading the file I get a "script" error.

It happens as EPE is trying to display the Google Map in the lower left pane or when doing geocoding on a new POI. I am wondering if Google has changed something that Turbo was relying on in the API

Is anyone else having this problem?

<<Page 2>>

False Positive

jale wrote:

Not sure if I'm the first on reporting it, but the http://turboccc.wikispaces.com/Extra_POI_Editor site is rejected by McAfe Site Advisor with the note : "When we visited this site, we found it exhibited one or more risky behaviors."
Downloading EPE from the download page works fine though.

From time to time I will get warnings like that on various websites from Norton. All a/v products are subject to these false positives. I know Turbo's site is safe, so I would have no concerns.

--
Tampa, FL - Garmin nüvi 660 (Software Ver 4.90), 2021.20 CN NA NT maps | Magellan Meridian Gold

Just ran Norton on your above link

Norton said no risk found.
Lots have used it here and no one has ever mentioned a problem.

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

it's a mcAfee issue

jale wrote:

Not sure if I'm the first on reporting it, but the http://turboccc.wikispaces.com/Extra_POI_Editor site is rejected by McAfe Site Advisor with the note : "When we visited this site, we found it exhibited one or more risky behaviors."
Downloading EPE from the download page works fine though.

It's known and is a McAfee issue. Norton and others don't flag the site.

--
Illiterate? Write for free help.

Kaspersky gives the same warning

jale wrote:

Not sure if I'm the first on reporting it, but the http://turboccc.wikispaces.com/Extra_POI_Editor site is rejected by McAfe Site Advisor with the note : "When we visited this site, we found it exhibited one or more risky behaviors."

I got the same message from Kaspersky anti-virus, and like you, I trusted TURBOCC more than the message and downloaded EPE.

Phil

--
"No misfortune is so bad that whining about it won't make it worse."

An Ongoing Issue

jale wrote:

Not sure if I'm the first on reporting it, but the http://turboccc.wikispaces.com/Extra_POI_Editor site is rejected by McAfe Site Advisor with the note : "When we visited this site, we found it exhibited one or more risky behaviors."
Downloading EPE from the download page works fine though.

There have been reported issues with EPE and various anti-virus programs for some time now.

http://www.poi-factory.com/node/32163
and
http://www.poi-factory.com/node/41332

EPE triggers an alert with my Norton Internet Security software every time I download the program. I took a chance initially and ignored it. I’m not advising you do this but in my case, I have had no problems since that first download almost 4 years ago.

EPE

Thanks Turbo for all your time and effort, very much appreciated.

--
All the worlds indeed a stage and we are merely players. Rush

About EPE and anti-virus

Remember that EPE is reading & writing the configuration in the Registry. That alerts most of the anti-virus programs.

EPE v5.93 just released!

EPE v5.93 ready to download on my wiki

Changes from v5.92 to beta v5.93
•Added back the circle list. Cool! In the POI Edit page, you can add alert circles directly on the map. Use "Grab Circles" button afterward if you added or moved any circles.

What More Can I Say

turboccc wrote:

EPE v5.93 ready to download on my wiki

Changes from v5.92 to beta v5.93
•Added back the circle list. Cool! In the POI Edit page, you can add alert circles directly on the map. Use "Grab Circles" button afterward if you added or moved any circles.

I just downloaded it. A zillion thanks again!

Circles

Boy - I love this feature.

There are two rest areas on my way to visit a grandson - both are on the SB side of the Interstate but - perhaps because they are both just turnouts and very close to the Interstate - alert me when I am northbound.

So, I just found them in the Restarea file and put 30 meters in the "Proximity" field of each of them to get a 30 meter circle. Then I moved the POI pointer until the circle did not touch the NB lane when zoomed in to maximum. Will suggest new coordinates to MrKenFl to make his wonderful file that much more valuable.

Circles

Glad you love it John. I like it too! Never used it though! smile

I wonder if Lee Iacoca ever

I wonder if Lee Iacoca ever drove a Mustang?

--
Frank DriveSmart55 37.322760, -79.511267

Good one!

phranc wrote:

I wonder if Lee Iacoca ever drove a Mustang?

Good one! haha!

Not EPE, the site itself

turboccc wrote:

Remember that EPE is reading & writing the configuration in the Registry. That alerts most of the anti-virus programs.

It's not EPE but the site itself that triggers MacAfe reaction.

Google must have fixed this, Yea!

Strephon_Alkhalikoi wrote:

I suspect EPE uses Internet Explorer calls along with the Google Maps API to display its information, since IE is included in all Windows machines. If I am right, then this is not a problem with EPE, but with the Google API.

https://code.google.com/p/gmaps-api-issues/issues/detail?id=...

In short, the problem is that the API and IE's "Quirks Mode" aren't cooperating. Because of this you get the error. The workaround for IE is to disable Quirks Mode. However, I don't know if doing that would help EPE at the moment. According to Google at the link above, they've confirmed this as a bug and is looking into releasing a patch to the API next week.

I just noticed the script error is gone and the map and pointer is working once again. I came here to report all is playing well with EPE and noticed Turbo checked in and posted another update to this excellent program. Double Yea!

--
"There's no substitute for local knowledge" nüvi 750, nüvi 3597

great

turboccc wrote:

EPE v5.93 ready to download on my wiki

Changes from v5.92 to beta v5.93
•Added back the circle list. Cool! In the POI Edit page, you can add alert circles directly on the map. Use "Grab Circles" button afterward if you added or moved any circles.

This is great. The circle feature is very handy, when settin prox alerts.

--
DriveSmart 65, NUVI2555LMT, (NUVI350 is Now Retired)

Google issue

[quote=TXRVer
I just noticed the script error is gone and the map and pointer is working once again. I came here to report all is playing well with EPE and noticed Turbo checked in and posted another update to this excellent program. Double Yea!

Haaaa! Don't tell me I did all this for nothing... LOL! smile Just kidding.

Still I'm very happy about fixing the circle list and the View All POI on MAP is coming. My wife was on the computer last night but I am very close to a breakthrough. I will feel much better when this will work again.

Chocolates

turboccc wrote:

[quote=TXRVer
I just noticed the script error is gone and the map and pointer is working once again. I came here to report all is playing well with EPE and noticed Turbo checked in and posted another update to this excellent program. Double Yea!

Haaaa! Don't tell me I did all this for nothing... LOL! smile Just kidding.

Still I'm very happy about fixing the circle list and the View All POI on MAP is coming. My wife was on the computer last night but I am very close to a breakthrough. I will feel much better when this will work again.

Turbo don't put the chocolates by the computer. grin grin

--
All the worlds indeed a stage and we are merely players. Rush

Now you're telling me...

d-moo70 wrote:

Turbo don't put the chocolates by the computer. grin grin

The funny part is that this is exactly what happened. I came back from work (a bit late) and went to buy different kinds of chocolate for her. The wife had sent me a message at the office saying she was craving for chocolate. She went to the computer WITH the chocolate and spent the evening shopping on the web. On the positive side, I had the TV for me alone. smile

VIEW POI on MAP

JavaScript won tonight. 3 hours for nothing. I don't get it. I download a perfectly working example and it works on Firefox but not Internet Explorer. I'm confused. Will start over tomorrow.

Update: There is hope after all. It kind of works. There is a file path issue but I found a way to debug javascript inside Internet Explorer. Coococol!

VIEW POI on MAP

It works! It works! I have seen it!

I had to change the concept. Seems like javascript can't read from external files for security reasons. I was getting an "access denied" message. Spent 2 days trying to workaround it, then decided to do it differently.

Clicking on the marker or the POI name brings the POI detailed information. It used to be displayed as html rather than simple text. I am trying to bring back the html and with this will come some script errors with special characters. Be warned! I still need to test it a bit to eliminate obvious errors but I hope to release a new version this weekend.

Disclaimer: Stupid javascript! I hate you! smile

13000 POI on MAP

I just displayed 13000 POI on the map. Not a great idea. LOL!

Program froze for a few seconds (10 sec) but it worked. You just need to be patient.

As promised: EPE v5.94

Changes from v5.93 to beta v5.94

•Added back the StreetView in View menu. Select one poi and check it on StreetView. Note that StreetView is also available in the POI Edit window by dragging the "man" over the selected location.

•Added back the View POIs on MAP in view menu. View all loaded POIs on the map.

•Still missing: view routes on map (feature lost since v5.91). Working on it.

Thanks TurboCCC

I just downloaded it. You're the man!

Good Idea!

jgermann wrote:

Boy - I love this feature.

There are two rest areas on my way to visit a grandson - both are on the SB side of the Interstate but - perhaps because they are both just turnouts and very close to the Interstate - alert me when I am northbound.

So, I just found them in the Restarea file and put 30 meters in the "Proximity" field of each of them to get a 30 meter circle. Then I moved the POI pointer until the circle did not touch the NB lane when zoomed in to maximum. Will suggest new coordinates to MrKenFl to make his wonderful file that much more valuable.

I agree, the circles function in EPE is a great add! Thanks Turbo!

Good idea jgermann about the reduced 30 meter circle to avoid false alerts for rest areas on the wrong side of the highway.

I think the POI should also be moved to a point at least a half mile before the rest area entrance ramp. Otherwise, the alert will occur as you are passing it.

I generally plan my stops well in advance and navigate directly to the rest area POI but the proximity circle is still a good idea since it would serve as a reminder should I forget.

Several techniques will work

bdhsfz6 wrote:

...
Good idea jgermann about the reduced 30 meter circle to avoid false alerts for rest areas on the wrong side of the highway.

I think the POI should also be moved to a point at least a half mile before the rest area entrance ramp. Otherwise, the alert will occur as you are passing it.

I generally plan my stops well in advance and navigate directly to the rest area POI but the proximity circle is still a good idea since it would serve as a reminder should I forget.

The Combined Rest Areas file is downloaded as a .csv file. If you want to be alerted to upcoming rest areas, then you can load this particular file using "Manual" mode of POI Loader. When POI Loader comes to this file, it will ask whether it will ask you to choose from two settings
* Ignore this file?
or
* This file contains proximity alert points

Choose the "proximity alerts points" setting.

Then choose the radio button that says: Alert whenever you get close to a point" and enter your desired distance.

I usually put in 5000 so we will receive an alert about a mile from the entrance - enough time to decide is a pit stop is in order. However, you can use any number up to 200000 feet (37.88 miles).

Remember that the coordinates of the POI MUST be within 30 meters (about 98 feet) of the middle of the roadway on which you are traveling. That is why I was so happy to see the circle feature back working in EPE. We can all help out MrKenFL by making note of any "false positive" we find (for example, an alert for a SB rest area when we are traveling NB). Then, MrKenFL will be able to make this most valuable file even better.

Another technique would be to open the rest area .csv file in EPE and then put 5000 in the "proximity" field of every record. You would do this by clicking the menu item Edit > Replace Field which gives you a small dialog box in which you will pick the field you want to replace in all of the POIs (in our case, Proximity) and enter the value (in my case 5000) and then hit the "Replace All" button. Now, save the file as a .gpx file and you can load it using the "Express" mode of POI Loader.

Proximity circles

BTW, I set the default circle radius to 50m, but if you think that 30m is better for most application, I can reduce the default value to 30m.

From Garmin

turboccc wrote:

BTW, I set the default circle radius to 50m, but if you think that 30m is better for most application, I can reduce the default value to 30m.

David Martin 101 got this reply

Quote:

Fri, 01/17/2014 - 1:17pm
...
FROM GARMIN
Thank you for contacting Garmin International.

I'd be happy to assist you with this.
While navigating, the proximity point will need to be within 30 meters of the route, regardless of the distance set in the POI Loader, to trigger an alert. This helps to reduce false alerts that can occur if you are traveling on a road close to a proximity point even if it is not affected by the alert.

This is from a Garmin FAQ

Quote:

How close do I have to be to a proximity point before my nuvi will alert me?
Answer:
While navigating, the proximity point will need to be within 30 meters of the route, regardless of the distance set in the POI Loader, to trigger an alert. This helps to reduce false alerts that can occur if you are traveling on a road close to a proximity point even if it is not affected by the alert.
Last modified on: 03/10/2011

@jgermann

Thanks for the tutorial on proximity points. I’m far from being an expert with EPE and file manipulation.

It seems to me it is possible to put too fine a point on the circle radius / diameter though. I don’t know what sources MrKenFl uses in his Rest Areas Combined file but if Google Earth is one of them, you have to consider that the average position accuracy in most of North America is slightly less than 18 meters. When you couple that with the 10 meter accuracy of most automotive GPSr’s, the value of a 30 meter circle vs a 50 meter one is questionable and may actually defeat the intended purpose.

While automotive GPSr’s use position averaging to more closely follow a road or track, there is still an error in the positioning of the road on the map to consider. Selecting proper POI coordinates can be a tricky process when trying to work with small distances.

A series of field tests would be an interesting experiment to run to see how well different circle dimensions actually work. I suspect it would vary greatly across the country.

Minor Inconvenience

bdhsfz6 wrote:

It seems to me it is possible to put too fine a point on the circle radius / diameter though. I don’t know what sources MrKenFl uses in his Rest Areas Combined file but if Google Earth is one of them, you have to consider that the average position accuracy in most of North America is slightly less than 18 meters. When you couple that with the 10 meter accuracy of most automotive GPSr’s, the value of a 30 meter circle vs a 50 meter one is questionable and may actually defeat the intended purpose.

I believe that the position is usually the start of the Ramp to the Rest Area and that is where I set the position for the Ontario Rest Area File that I created.

As a result, I end up with the Rest Area Icon right at the start of the ramp.

I set my prox alert for Rest Areas at about 1 1/2 to 2 miles. It does trigger some false alerts for Rest Areas on the other side of the highway, but I like to have enough warning to be alerted in time to check with my wife to see if a break is warranted and also to ensure I have enough time to get ahead or drop behind the 18 wheeler, in my right lane.

Considering that Rest Areas are usually about 2-3 hours apart, a few false alerts proves to be a minor inconvenience.

--
DriveSmart 65, NUVI2555LMT, (NUVI350 is Now Retired)

I just did a test

bdhsfz6 wrote:

...

A series of field tests would be an interesting experiment to run to see how well different circle dimensions actually work. I suspect it would vary greatly across the country.

I have been experiencing two "false positive" alerts for rest areas on the way to my grandson's house. Just as soon ad Turbo got the proximity circle working again, I took the latest rest area file and found the two rest areas of concern.

I put a 30 meter circle around the pointer; then I zoomed in as far as possible on the map; then, I moved the pointed to a point on the ramp where the circle covered all of the Interstate lanes going in the proper direction BUT did not touch any of the leftmost lane going in the other direction.

I pressed the "Grab" to get the new coordinates for each of the two POIs. I then saved the file and loaded it to my 765.

Tested it an hour ago when I took something to my grandson. It worked fine. I did not get a NB alert but did get the proper SB alert.

I understand that we are talking very fine points here, but the "map" deals with coordinates which I would guess are pretty accurate. On the other hand, my devices are likely accurate to only 15 to 20 meters. BUT REMEMBER, the alert is based on the underlying map and the coordinates of the POI, not on my "exact" location.

oranges and watermelons

bdhsfz6 wrote:

Thanks for the tutorial on proximity points. I’m far from being an expert with EPE and file manipulation.

It seems to me it is possible to put too fine a point on the circle radius / diameter though. I don’t know what sources MrKenFl uses in his Rest Areas Combined file but if Google Earth is one of them, you have to consider that the average position accuracy in most of North America is slightly less than 18 meters. When you couple that with the 10 meter accuracy of most automotive GPSr’s, the value of a 30 meter circle vs a 50 meter one is questionable and may actually defeat the intended purpose.

The Google map isn't dealing with 'reported' accuracies from a GPS but with highly accurate survey points. It's public domain information as to the locations of roads and buildings. It has to do with property lines and points accountable to the permanent landmarks from the US Geological Service. Google would then align the satellite view with the known coordinates. That puts the off ramp in the correct location and a circle drawn around that location is then an accurate representation of the desired radius. The only variable in this is then your GPS which would have a variation because of the built-in inaccuracy.

--
Illiterate? Write for free help.

@Box Car

Great explanation.

Thanks

All of you are keeping my mind sharp

I love reading all the "stuff" all of you write explaining "stuff" I don't quiet understand. I read it, and sometimes re read it. It makes me think and keeps my mind from getting gray "I hope", even if I don't fully understand it most of the time.
Thanks for all the help with keeping my old brain sharp....

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

And thinks TURBOCCC

I downloaded your latest and it is the first time I have been able to keep the internet on and look at the map while using your EPE.
Thanks.

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

How About the right click options

How about putting back the right click options?

Why?

bobinot wrote:

How about putting back the right click options?

Hi bob,

Which feature are you looking for in the right click menu? Center? Find marker?

Just wondering if there was anything mandatory that would require the work.

Me too!

mgarledge wrote:

I love reading all the "stuff" all of you write explaining "stuff" I don't quiet understand. I read it, and sometimes re read it. It makes me think and keeps my mind from getting gray "I hope", even if I don't fully understand it most of the time.
Thanks for all the help with keeping my old brain sharp....

Hi mgarledge,

I'm glad to see I am not the only one. I'm sure it is only a terminology issue.

Proximity circle: for me this is the circle that goes with the POI. This circle is bigger than the alert circle below.

Alert circles: Those are the little circles used to make the alert. These circles need to be inside the proximity circle above.

My understanding is that the alert circle should be about 30m and big enough to take into account the imprecision of our GPS.

So, if I could get the same explanation from Garmin with the terms above, I think it would improve my understanding.

It has been 2+ years since I heard about circles, but am I correct in saying that when alert circles are used the alert will not come when you enter the proximity circle anymore but when entering an alert circle?

Also, I think we need to make sure that the alert circle is passed before passing the marker. If passed after, it will not trigger an alert.

Anything else?

IIRC

turboccc wrote:

Proximity circle: for me this is the circle that goes with the POI. This circle is bigger than the alert circle below.

Alert circles: Those are the little circles used to make the alert. These circles need to be inside the proximity circle above.

My understanding is that the alert circle should be about 30m and big enough to take into account the imprecision of our GPS.

So, if I could get the same explanation from Garmin with the terms above, I think it would improve my understanding.

It has been 2+ years since I heard about circles, but am I correct in saying that when alert circles are used the alert will not come when you enter the proximity circle anymore but when entering an alert circle?

Also, I think we need to make sure that the alert circle is passed before passing the marker. If passed after, it will not trigger an alert.

Anything else?

The alert circles provide direction so a POI would only alert if you were approaching in the direction of the POI where alert circles were placed. This means you could set an alert for a camera that would only trigger if you were going in the direction the camera would take a photo.

--
Illiterate? Write for free help.

Reading it fast

turboccc wrote:
mgarledge wrote:

I love reading all the "stuff" all of you write explaining "stuff" I don't quiet understand. I read it, and sometimes re read it. It makes me think and keeps my mind from getting gray "I hope", even if I don't fully understand it most of the time.
Thanks for all the help with keeping my old brain sharp....

Hi mgarledge,

I'm glad to see I am not the only one. I'm sure it is only a terminology issue.

Proximity circle: for me this is the circle that goes with the POI. This circle is bigger than the alert circle below.

Alert circles: Those are the little circles used to make the alert. These circles need to be inside the proximity circle above.

My understanding is that the alert circle should be about 30m and big enough to take into account the imprecision of our GPS.

So, if I could get the same explanation from Garmin with the terms above, I think it would improve my understanding.

It has been 2+ years since I heard about circles, but am I correct in saying that when alert circles are used the alert will not come when you enter the proximity circle anymore but when entering an alert circle?

Also, I think we need to make sure that the alert circle is passed before passing the marker. If passed after, it will not trigger an alert.

Anything else?

Thanks, When reading this fast it makes my mind go in circles. I slowed down and it helps with the understanding.
Thanks for all you help and work, Mary

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

Not Entirely Correct

Box Car wrote:

[
The Google map isn't dealing with 'reported' accuracies from a GPS but with highly accurate survey points. It's public domain information as to the locations of roads and buildings. It has to do with property lines and points accountable to the permanent landmarks from the US Geological Service. Google would then align the satellite view with the known coordinates. That puts the off ramp in the correct location and a circle drawn around that location is then an accurate representation of the desired radius. The only variable in this is then your GPS which would have a variation because of the built-in inaccuracy.

I’m not sure what you mean by oranges and watermelons but you may have missed my point. I did not say that Google Earth used “reported accuracies” from GPSr’s. That is only the case with Street Level View which uses uploads from Google’s own GPS equipment. In fact the G E coordinate system is an offset of the WGS84 datum which relies primarily on USGS benchmarks.

You are correct when you say G E uses, although indirectly, these highly accurate benchmark survey points. Property lines, buildings and roads are of no use unless their locations are surveyed and documented. “Bluebooked” USCGS benchmarks, which have been surveyed to an accuracy of less than a quarter inch, are the backbone of the WGS84 datum.

The problem with G E accuracy has to do with the distance and topography between these survey points when the aerial imagery overlay is created. Although a great deal of care is used in aligning G E imaging with the WGS84 datum, it is impossible to maintain consistent accuracy across an entire image. The effect caused by the angle of the camera lens relative to the earth’s surface, the irregular shape of the earth and atmospheric image distortion are the main culprits. The error is further compounded when these images are seamed together. The edges of the images are sometimes stretched or compressed to appear to line up physically. This causes skewing of the data.

It’s like trying to scale from a series of taped together road maps when viewing them at an angle instead of straight on.

Detailed information on this subject can be found by simply doing an internet search on “Google Earth Position Accuracy”.

G E error varies greatly with location and even the time of year but is generally accepted to be between 10 and 20 meters throughout most of North America. If you have high resolution G E imagery available where you live, you can see this visually by doing a little experiment. Boot G E and zoom in on a well-defined object in an open area near you. A light pole in a Walmart parking lot would be a good choice. Zoom in as close as possible with G E and place a push pin on the light pole or other object you picked. Leave G E booted, drive over to Walmart with your GPSr and park as close to that light pole or other object as possible. Allow your GPS to position average for a few minutes and create a waypoint. Drive home and enter the coordinates of that waypoint in G E. Use G E’s measuring tool to find the distance between the push pin and the waypoint you entered. This is the COMBINED error of both your GPSr AND Google Earth. It will vary with time of day, time of year, overhead obstruction etc.

This experiment can also be done entirely in the field if you have the G E mobile app running on your smartphone, Ipad or tablet.

I’ve used this process many times to improve the accuracy of critical waypoints in some of my files. Running the process several times and averaging the results will further improve the overall accuracy but never eliminate the error completely. I find it surprising to see some errors are quite small while others are appalling!

A visual representation of the G E error alone is more difficult to create. It requires a location that has a series of high resolution G E images available that were taken over a period of time. You can see part of this error by again zooming in as close as possible on a well-defined object. Place a push pin on the object and use the time slider to go back to previous images. In many cases, the object will appear to move while the push pin and coordinates do not.

For example, boot Google Earth and go to 38° 53.371'N by 77° 2.107'W. Zoom in on the Washington Monument and carefully place a push pin at the Northeast corner of the monument base. Use the time slider to go back in time and note the movement of the monument relative to the push pin. This is only one component of the overall G E error and is caused mainly by image seaming. Another component is the lens angle of the image relative to the ground as indicated by the apparent monument and shadow angles which change from image to image. This angle is important because the WGS84 datum is based on the theoretical or smoothed out shape of the earth called the Geoid. GE obviously uses images of the earths surface and can vary with changes in topography.

Keep in mind this location was picked for its graphic representation rather than the magnitude of the error which here averages only 5 or 6 meters. In many locations, the error is far greater. In other locations there is almost no error at all. When creating a POI file which encompasses a large geographic area, it must be assumed there will be some error.

My original point, although a very minor one, it this: When you couple G E error with that of most GPSr’s, the performance difference between 30 and 50 meter circles is relatively small in a POI file covering a large geographic area.

As POI file creators, we like to think the coordinates we obtain from Google Earth are 100% accurate but unfortunately, it just isn’t so. For the most part, the data is accurate enough for what we create. I do feel however that all POI file contributors here at the factory should be aware of this issue. In my case, I don't want to send a mountain biker over a cliff because I misplaced the waypoint for a trail warning marker.

Please understand my original post was not an attempt to be critical of jgermann’s choice of a 30 meter circle over Turbo’s default 50 meter. If any offense was taken, I apologize. It is such a minor point that it hardly justifies this lengthy technical treatise. Hopefully, it will serve to further sharpen Mary's brain (LOL)

Circles and more circles

Box Car wrote:

The alert circles provide direction so a POI would only alert if you were approaching in the direction of the POI where alert circles were placed. This means you could set an alert for a camera that would only trigger if you were going in the direction the camera would take a photo.

Thanks for more circles Box Car. grin

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

Right click

What I looking for is when you can move the pointer to that location where you right click. Sometimes that pointer is off the screen. When I click on the location to open the edit screen it doesn't come up. then the program locks up when I right click the icon on the task bar to close program I get runtime error number 5.

No effect on right click for me

bobinot wrote:

What I looking for is when you can move the pointer to that location where you right click. Sometimes that pointer is off the screen. When I click on the location to open the edit screen it doesn't come up. then the program locks up when I right click the icon on the task bar to close program I get runtime error number 5.

Ok. I think I understand what you want: the ability to simply right click to move the marker at that location rather than dragging it manually. I think I can do that.

About current version: Right click for me does nothing at all. It does not lock the program or crash EPE. I would need additional repro steps to fix this.

Window off screen?

turboccc wrote:
bobinot wrote:

What I looking for is when you can move the pointer to that location where you right click. Sometimes that pointer is off the screen. When I click on the location to open the edit screen it doesn't come up. then the program locks up when I right click the icon on the task bar to close program I get runtime error number 5.

Ok. I think I understand what you want: the ability to simply right click to move the marker at that location rather than dragging it manually. I think I can do that.

About current version: Right click for me does nothing at all. It does not lock the program or crash EPE. I would need additional repro steps to fix this.

ah! Maybe your problem has nothing to do with right click. maybe your POI Edit window is off screen, ie outside the visible area. EPE will remember the last position of all its windows. Maybe there is a glitch and now it remembers a position outside the screen. In that case, the only way to fix this is to type the following command in a DOS command line window:

Extra_POI_Editor -reset

it should fix the issue you are having. The only drawback is that it will reset the entire EPE configuration. You will have to reconfigure EPE again. Doing a few screen shots of the EPE config may help you to restore it afterward.

Fix

I got it fix by reinstalling everything it also cleans out my drive.

Circle vs rectangle

Way back when, I did some testing to determine how far off the centerline of a road a POI could sit and still create an alert. I determined it to be about 98 feet. Then, realizing Garmin device's native mode in metric, I wound up with 30 meters.

Later I found confirmation of this from Garmin.
Go to
http://iqc.garmin.com/eCustomer/KODSelfService/request.do?create=kb:garmin&report()=p%7B0d7773a0-b9cd-11de-73d6-000000000000%7D
Then click on the question
How close do I have to be to a proximity point before my nüvi will alert me?

Quote:

While navigating, the proximity point will need to be within 30 meters of the route, regardless of the distance set in the POI Loader, to trigger an alert. This helps to reduce false alerts that can occur if you are traveling on a road close to a proximity point even if it is not affected by the alert.

f you select the Proximity alert, then whenever your device enters the bottom of an imaginary rectangle which is centered on the road on which the device is traveling and which rectangle's height is the proximity distance you entered and which rectangle's width is 60 meters (approximately 196 feet) AND the coordinates of the individual POI fall within the rectangle, THEN a Proximity alert will occur.

This last point is important. If the author of the Custom POI file has set the coordinates of individual POIs to be 30 meters or less from the roadway on which the device will be traveling, then Proximity alerts will be triggered. If the coordinates are more than 30 meters from the roadway on which the device is traveling, no alert will be sounded.

To make this relevant, if MrKenFL put the coordinates of a rest area in the median of an Interstate (rather than on the ramp as he usually does) then a user would get an alert going either direction (even though one would only be able to access the rest area from one direction).

Think of the "radius" of the circle perpendicular to the route as the critical vector. The circle gives this vector to you.

Now what to do

You have me going in circles and now you have me going in imaginary rectangle.. Hope Jill can keep up...
grin confused crying shock laugh out loud surprised

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

Jill will do fine

mgarledge wrote:

You have me going in circles and now you have me going in imaginary rectangle.. Hope Jill can keep up...
grin confused crying shock laugh out loud surprised

Funny!

mgarledge wrote:

You have me going in circles and now you have me going in imaginary rectangle.. Hope Jill can keep up...
grin confused crying shock laugh out loud surprised

Mary, you are funny!

<<Page 2>>