EPE

^

I have done just that! It is not released yet, but if you right click it will move the marker at that position. If you click, it creates an alert circle.

I think I have done it now. I fixed all lost features since 5.92 (time of the first google API change. The last feature was to restore the ability to view routes when selecting "View POIs on MAP".

Why is this cool?

Let's say you load a GPX route in EPE. Then, you Merge Open some POIs like the Offbeat Tourist Attractions. Click View All POIs on MAP to see route and POIs. Close window. Now lets see only the POIs that are less than 10 miles away from the route. Edit menu: Find POIs on Route. Specify distance and run. Now go back to View All POIs on MAP. You can see your route and only the POIS that are within specified distance.

Details of the release:

Changes from v5.94 to beta v5.95

•Added back route display in View POIs on MAP. Each route has a different color.
•In the POI Edit page, a right-click on the map can be used to move POI marker to a new position. It is still possible to drag the POI marker.
•Fixed an issue where EPE would crash when grabbing alert circles in POI Edit window.
•Fixed an issue where the alert circles would not get redrawn after pressing the geocoding button in the POI Edit window.

I have been snowed in too long.
Enjoyed everyone's post today.

Thanks turboccc for taking the time to correct some of the problems we were having. We depend on this program to do so many things in the poi community.It has always been a great program, thanks to your efforts.

My pleasure, Charles. I know you have always been very supportive and provided a lot of feedback to me and supported the others.

Now, I'll start looking at my old TODO list to see if there's anything (easy ) I could implement next.

Turboccc, I must say thanks for all you do, There would have been no "Offbeat Tourist Attractions" file or updates for that matter if this program did not exist.

Your program is all I use and it works perfect. I just had to give you a thankyou shout for all you do for everyone!

Would you please take a look at the site. McAfee is still blocking http://turboccc.wikispaces.com/Extra_POI_Editor as a dangerous site.

Turbo can do about McAfee barfing when you try to access the site. YOU need to tell your copy of the AV software to ignore the issue and open the site.

Boxcar is right. I can't do much. If you tell your McAfee antivirus that the site is safe, it should stop bugging you.

If you have doubts, use a site such as VirusTotal to scan the files or site you want. I ran it on my site and got a "clean site" (See list below). Clearly, the site is good.

URL Scanner

Result

ADMINUSLabs Clean site
AegisLab WebGuard Clean site
AlienVault Clean site
Antiy-AVL Clean site
AutoShun Unrated site
Avira Clean site
Baidu-International Clean site
BitDefender Clean site
Blueliv Clean site
C-SIRT Clean site
CLEAN MX Clean site
CRDF Clean site
Comodo Site Inspector Clean site
CyberCrime Clean site
Dr.Web Clean site
ESET Clean site
Emsisoft Clean site
Fortinet Clean site
FraudSense Clean site
G-Data Clean site
Google Safebrowsing Clean site
K7AntiVirus Clean site
Kaspersky Clean site
Malc0de Database Clean site
Malekal Clean site
Malware Domain Blocklist Clean site
MalwareDomainList Clean site
MalwarePatrol Clean site
Malwarebytes hpHosts Clean site
Malwared Clean site
Netcraft Unrated site
OpenPhish Clean site
Opera Clean site
PalevoTracker Clean site
ParetoLogic Clean site
PhishLabs Unrated site
Phishtank Clean site
Quttera Clean site
Rising Clean site
SCUMWARE.org Clean site
SecureBrain Clean site
Sophos Unrated site
Spam404 Clean site
SpyEyeTracker Clean site
StopBadware Unrated site
Sucuri SiteCheck Clean site
Tencent Clean site
ThreatHive Clean site
Trustwave Clean site
URLQuery Unrated site
VX Vault Clean site
Web Security Guard Clean site
Websense ThreatSeeker Clean site
Webutation Clean site
Wepawet Clean site
Yandex Safebrowsing Clean site
ZCloudsec Clean site
ZDB Zeus Clean site
Zerofox Clean site
ZeusTracker Clean site
malwares.com URL checker Clean site
zvelo Clean site

Thanks Bob. I know you too have been a big fan. I like your Offbeat Tourist Attractions as well and I use it when I travel to the States.

It's when I see such achievements that I'm happy to contribute in some way in what you are all doing at POI-Factory. Continue the good work!

I know the site is OK. It is not the antivirus that makes the problem but the Site Advisor. I reported the url to them as they are the only one that can change that. We'll see...

Hi. Just looked in (havent been here for months) and see EPE has been udated, and circles are working again !!
Thank you very much Turbo ccc . I do use EPE for Speed traps every week so i have been working in MapSource to make circles and copy/past coordinates in to EPE.

Just to mention, bearing list do now working in the latest Garmin nuvis. BearingList is quite easier to make directional than circles . Im not sure if EPE is writing this to gpi.

Im so happy ,so happy...

Vestenfjell

Hi vestenfjell,

Glad to see you are still using EPE after all this time. To tell the truth, I didn't remember if EPE was writing bearing to gpi. I had to look in the code. hehe! Good news! It does, but I have no idea if it works or not. I probably emulated what GPI Creator is doing. Let me know.

I should see if there is a way to view the bearing directly on the map. That would be quite nice and helpful to set them. Not for the next week since I'm a bit busy but I'll try the weekend of March 14th.

Hi again vestenfjell,

You probably know this better than me. How bearing are working exactly? lol!

0 degree means North. Which one? Geographic? Magnetic? On a Google map, I would assume it is full North at the vertical, right?

"tolerance" should also be a +/- value.

I assume the detection starts at the proximity circle. So if I used a proximity circle of 200 meters, a beading of 0 degree and a tolerance of +/- 20 degrees, it means the alert will be triggered from an angle of +/- 20 degrees from top and will start once I crossed the proximity circle at 200 meters from the POI. Correct?

So I will draw 2 lines from the POI: one at -20 degrees and the other at +20 degrees. It should be easy to see the bearing that way.

At first, I will not allow to drag the bearing directly on the map. You'll have to enter the bearing in EPE and the map will reflect the change.

I had to go back and look for earlier tests to see if I had tested EPE with BearingList. And I had tested BearingList in EPE, and it worked.
I havent started using BearingLists in my files , just because that there are so many older nuvis in use. And its also a big job to replace the CircleList.

In mail Garmin stated early in 2014 that nuvi series 2xx5, 34xx, 35xx with software 6,91 and newer works with BearingLists. I gess there will be more compatible models in the future.
As for the bearing it looks as it be geografic, north vertical.
As you asume the detection starts at the proximity circle, with tolerance of +/- entered degrees.

Visual 2 lines starting in center (poi) is just greate if you can do that, its more than I had expected.

Vestenfjell.

1. Circle List: I have set Proximitiy Alerts on a variety of files and I can see that with changes made to EPE that I can click on the map and add a circle that has a default diameter of 30 meters. I then grab the circle and it shows in the Circle List.

I also see that I can edit that diameter, by changing the value in the bottom of list and update that. That's the part, that I understand.

I can also add more than one circle, but I don't understand why I would want more than one proximity alert on any POI. Can anyone explain when this might be useful?

2. Bearing List: vestenfjell's post makes this somewhat understandable, but still somewhat confusing. I presume that the bearing list creates a directionality to the Proximity Alert, and narrows the focus so that you won't get overlap of two Prox Alerts for something like rest areas on both sides of the highway.

It makes sense, to be able to do this, but it seems like a lot of work, especially on a huge file like Rest Areas Combined.

How do you get the bearing in the first place? There doesn't seem like there's an easy way to do so.

Do you need to use more than one set of bearings and tolerances? How do you decide how much tolerance?

Hi,

Both circlelist and bearinglist can make directional alert.
CircleList kan also make several alert circles inside the proximity, not necessarily directional. The description of CircleList from Garmin is used in TourGuide. How to make this circlelist directional is just a study of how things work.

I cant draw inside this forum, so if you want you can look at a cuple of pages at my homepage.

This two pages are the only in English:

BearingList
https://sites.google.com/site/odingpsm/circles/bearinglist

CircleList
https://sites.google.com/site/odingpsm/circles

Vestenfjell

That all make sense now. I haven't used Speed Camera Alerts and likely won't. However, I will likely experiment sometime.

Final Question (I hope): What's the easiest way to get bearings?

I use a transparent protractor called "On Screen Protractor" I just put the protractor on the map on EPE or MapSource ,and a moveable line tells me the bearing.
Slightly awkward but it works.

As you've found out, it's a great job with large files.
I have somtime thought of it like this: It's to much work just to make files for my own, so I have to share it ,hmmm, but then I have to maintain it . Never ending.

Thanks Vestenfjell, I learn from pictures. This helps so much.
Mary

I came across this old thread about Circle List, Bearing List, Directional POI and similar topics by TurboCCC, vestenfjell, JD4X4 and others. Now my head is spinning 360 degrees. Interesting!

http://www.poi-factory.com/node/31703?page=3

I have successfully drawn a bearing arc/pie over the proximity circle in an html file. Now I need to incorporate this to EPE.

Phase 1: Draw the bearings on the map
Phase 2: Adjust the bearings within the map;
Phase 3: Create bearings directly in the map.

It was nice to hear that bearing are in the pipeline . I really appreciate the work you do with EPE . Thank you, again.

Bearing List on MAP!!!

Changes from v5.95 to beta v5.96

•Added ability to view Bearing Alerts on MAP in POI Edit window.

Note: When saving to a .gpi file, EPE will use circle list if circles are present. Otherwise, bearing list will be used if present. .gpi files can't use both at the same time.

TurboCCC!!!

I'm not clear how we utilize this. Do we still have to determine the bearing using a protractor or another means and then EPE will display the bearing? OR do we right click or something and we then can draw the bearing on the map?

Turboccc,Than you for the update.
This was nice.
@
GPSgeek: At the momet you have to use protractor, or guess and edit . You have to write the bearing and tolerance in the field and push add.

Found 2 bugs:

*When click and make circles they appear as r=30m in fields and on map as r=50m, until you clic in the field.

*Bearing:if i write in field and push update, and no earlier bearings are marked I get:Run-time error 35600
Index out of bound, and program close.

Vestenfjell

I figured was the case. I don't expect to make much use of it, but for a smallbpoi, it might be handy. I'm not particularly bothered by overlapping alerts from the opposite direction, since I have few pois with prox alerts.

I will check posted issues.

I think you can use EPE to create bearing directly. You add a new one with approximate angle and tolerance and the. You fine tune. Takes 2 or 3 adjustments to make it work.

turboccc.For some reason when I double click on one of the pois.The next screen is not coming up.Getting run time error 5.Went back to previous version and got the same problem.Running windows 8.1 64 bit.

Double click poi work fine on my win 8.1. 64 bit.

Any chance to get bearing and tolerance implanted in
M-column csv fields ?
I got a hole bunch of pois with bearing in a csv file.

Fixed the 2 earlier issues mentioned by vestenfjell. Not release 5.97 yet. Was waiting for other feedback.

Charles: Could it be related to your specified POI file or to a specific POI? Double clicking should work. Clearly not Windows-version related. I need more information to fix since I can't reproduce.

Note: Runtime error 5 is caused by an "Invalid procedure call or argument". Looks like a procedure call with a bad argument. I wonder what is causing this in your case.

vestenfjell: Interesting idea to have angle and tolerance in the M-Column. I will look at it.

How should we call this?

"Bearing Angle" and "Bearing Tol"? For completeness, we should add "Bearing Bidir".

What about merging those 3 fields:

"Bearing" and the field could look like a concatenation of Bidir, Angle and Tolerance:
"True, 180, 20". You get me, right? This is a single field with 3 information delimited by commas.

Just to make this really complex, how should we handle multiple bearings per POI? Ahaaaa!

Why not add multiple lines within the field?
"True, 180, 20
False, 28, 5"

It is not much different than in the Description field which has more than one line.

I can see why a single entry per column would be more interesting for the user, but it would not really support multiple bearings per POI. Remember that EPE supports reading and writing CSV files. To write them correctly, I should be able to save multiple bearings.

Feedback? Comments?

To quote Artie Johnson from Rowan and Martin's Laugh-in, "Interesting. Very interesting."

Using your examples, you have an issue in the limitations of the CSV format. According to Garmin, their CSV format is four fields so you are left with the raw file having to be an M-Column. That doesn't mean the defined column couldn't contain multiple comma delimited elements.

True and false could be shortened to + and - and they could be prefixes for the bearing. You could also assume all entries were TRUE unless otherwise indicated.

Difficult choices, I don't envy you in this, but whatever decision you make we will work with.

Well, I am somewhat flexible. I'm not the one using it. Yes, I'd prefer a format that will support all the functionality in EPE. For me, a complex field with 3 bearing info is not a problem.

Remember that EPE supports complex CSV fields such as "Address, City, State". Why not "Bidir, Angle, Tolerance"? And why not multiple lines? Since CSV supports it, so can EPE.

I am just putting myself in vestenfjell's shoes. He already has the information in 2 columns. Now he needs to merge the 2 columns. Not that difficult, but more work. Adding the Bidir "true/false" could effectively be optional. As for multiple lines, I know CSV supports it, but looking at it is rather bad in Excel unless you do a line by line scroll.

Soooo, I am listening to my users first and we'll see how it goes. If vestenfjell is happy with a multiple-line-triple-info-per-field then that's the way I'll go. If not, I can compromise some more.

Charles: Could it be related to your specified POI file or to a specific POI? Double clicking should work. Clearly not Windows-version related. I need more information to fix since I can't reproduce.

I removed the EPE completely from the computer and done a new install.I can now double click on the poi and the next page will come up as normal.Manage to clear the script error after some research on the internet.

In the example of an address the elements parsed are in a specific position within the description field. If the position is not present, would you require the presence of delimiters to mark the empty fields much like Rand McNally does in their CSV layout?

In a normal POI entry for a store you would have the number and street then city, state, then post code and telephone number with each of the elements separated by the comma delimiter. The length of the telephone number element could be used to toggle if a post code was present or not as the normal 10 digit telephone takes either 12 or 14 characters to represent it in human readable format. The longest US post code is 9 characters.

If you assume the directional entry would describe an intersection, then you only have street names which would then be followed by the bearing data. Different data as the objects being defined are different. The fact all elements of a street address may not be present is indicated by the end-of-record sequence so EPE stops parsing for the missing elements. You have made assumptions in EPE on how the fourth field in a CSV is structured. You have assumed the first element will always be the street address followed by the other elements in their logical order. What happens when your parsing routine reads the fourth field of a CSV and the order is different than assumed? Yes, you can adjust the elements in the setup, but those are more global changes rather than a per file or per record change.

When all is said and done, there really isn't any difference between an M-Column layout and a standard CSV. You look for the elements in a particular order which is predefined. The primary difference is using the M-Column layout I can arrange the elements to match my input file rather than following the predefined layout shown under options - 4-Column CSV Fields.

I think where this is heading is that you can only do bearings with an M-Column layout and not by adding elements to a 4-column CSV file layout.

Merging columns.

Its easier of course not merging columns, but I can live with merging.

In The Igo files i have are 1 for one direction, and 2 for BirDir.

@Box Car: In all cases, this is for M-Column and not for 4-Column CSV. 4 columns is just not enough

@vestenfjell: What go you mean by "1 for one direction, and 2 for BirDir"? Are you saying that my proposed BiDir field values should be "1" and "2" instead of "False" and "True"? If so, I like it.

For all of you out there whose heads are spinning as fast as the propellers on our beanies, just a couple of notes to clear some of the technobabble.

Turbo is correct when he states EPE reads and writes CSV files, and if once we get all this figured out, EPE will read a CSV file that has bearing information included.

Now, for a translation.

If you dig into the options on EPE you will see a choice on the drop down menu under options for M-Column layout. That's what you will have to play with if you are going to attempt to add bearing data to a POI. M-Column data is normally saved as an Excel spreadsheet, but you can also save it as a CSV. When you save the file, I suggest you enable output of column headers so the columns are labeled.

Now, CSV files are text files, Excel files ending in XLS of XLSX are not. In a CSV output of a file built using the M-Column layout, each element is in a separate column in the same order as you defined under M-Column.

When we figure all this out and EPE will handle circle lists and bearings, I'll update my FAQ "Using Extra POI Editor to Create and Edit CSV files" http://www.poi-factory.com/node/41653 with instructions.

What I ment was the GPS Brand "Igo" have 1 for one direction and 2 for biDir in their .txt poi files.
I thought it maybe was not necessary to invent something new.
"Igo" .txt poi files are like this: Lon,lat,Type of poi,speed,DirType(0,1,2),Bearing.
(0 are for for all around alert, so it dont fit Garmin.)

I already have files with bearings for Igo gps .txt poi files. I only have to rotate the bearings 180 degrees.

Vestenfjell.

How do you specify the tolerance/width of the bearing? A bearing is an angle with a tolerance. So you would get a 7th column with Igo, right?

I have never seen an Igo txt file with tolerance, so I gess there must be some predifined tolerance in the Igo.
There are not any tolerance in my Igo files.
But Im not saying there cant not be an 7th column in Igo, course Idont know.
I thought I just copy in 20 degree in excel for toleranece asan element for the Garmin use.

I had 2 crazy last weeks at the office. Oh man! Days, evenings, week-ends, plus a one day trip to the Big Apple, caught a virus and back to work for another week. Arggg! That was tough.

I should be back on the bearings soon.

Yes, you need another tree in your forest.

Happy Easter to the best people in the world!

(Those who read this thread!)

Changes from v5.96 to beta v5.97

•Fixed default circle to 30m when drawing the first time.

•Fixed EPE crash when updating a bearing that does not exist.

•Fixed Geocoding issue which was not returning coordinates in some conditions.

Thanks again for the update!