Extra_POI_Editor up to v5.97 (.gpi file creation discussion - like POI Loader and more)

**Bielgeets** · 23rd March 2011, 05:48 PM

Ok This is better now.The .gpi file is now the same as my original poi-file (instead of "POI Made with EPE"
Very good work! Thanks a lot

Bielgeets

turboccc · 28th March 2011, 02:41 AM

I read some information about directional POI.

It seems possible to specify a direction or even multiple directions to trigger an alert. Each direction can be unidirectional or bi-directional. You just specify the bearing angle with a tolerance. For example, bearing 57 degrees with a tolerance of +/- 25 degrees. This way you are sure to hit the mark without making the alert bi-directional. If you specify the alert is bi-directional, it will also trigger the alert at 237 degrees (57+180) with the same +/- 25 degrees tolerance.

Pretty cool. The normal POI Loader cannot chew those bearing information, but GPI Creator can. Maybe EPE will do it too..

**tom1807** · 29th March 2011, 03:17 AM

I checked the different delievered XSD files, only the GPI_XML.xsd carries the Bearing information, and the gpx file must have the "v3 GPX_EXT.xsd" Tag

Code:

Please Login or Register to see the links

I would love to see the bearing type, especially for speed cameras

turboccc · 29th March 2011, 03:30 AM

Originally Posted by tom1807

I checked the different delievered XSD files, only the GPI_XML.xsd carries the Bearing information, and the gpx file must have the "v3 GPX_EXT.xsd" Tag
I would love to see the bearing type, especially for speed cameras

Well, you won't have to wait long. I already modified EPE to read/write bearing information from/to gpx files. I guess the most complex part will be to get bearing information for all POIs. Although you can a very wide bearing width (to ensure uni-directionality), you still have to give a bearing angle and this depends from where you are coming from. You have to use StreetView or GoogleEarth and figure it out. It seems like a very long thing to do.

**tom1807** · 29th March 2011, 03:36 AM

Well, I only have the Speedcameras of Garmin Taiwan, which carry some of this already, by direction W, E, S, N or SW, SE and so on.
I could give u the screenshots, but the names inside are partly in chinese.
The file is encrypted but not locked, thats why GPI Viewer can display them

**tom1807** · 29th March 2011, 04:00 AM

Name: 測速照相速限50 means Speedcamera Speedlimit 50
ikcHGA

Comment: 測速照相速限50公里 means Speedcamera Speedlimit 50km
ijYI3C

More interesting are the POI's for the Tollstation where more information about the circles are saved:
imt4Jg

turboccc · 29th March 2011, 04:05 AM

I could be wrong, but the Circles are different from the Bearing type, right? I was not able to find the bearing angle and width information in GPI_Viewer.

What it the purpose of the Circles compared with the Proximity? Is it to get additiional proximity alerts at different position?

**tom1807** · 29th March 2011, 04:40 AM

The Help writes the following:

Alert specified an optional alert for the POI.
AlertCircleList an optional list of alert cirlces.
Radius is the radius of the alert circle.
Center is the center of the alert circle

Below the example of the Johnson County Entertainment.xml

Code:

Please Login or Register to see the links

Bearing Point looks like this:

Code:

Please Login or Register to see the links

BearingList is an optional list of bearings for the alert. The alert will be triggered only while traveling along the specified bearings.
Angle is the angle of the bearing. North corresponds to 0 degrees, east corresponds to 90 degrees, and so on.
Width specifies a +/- range for the bearing. For example, if the angle is 55 degrees and the width is 15 degrees, the alert can be triggered while travelling at any bearing between 40-70 degrees. This element is optional; a width of 25 is used by default.
BiDir specifies whether the bearing applies in the opposite direction (180 degrees). This element is optional; this is false by default.

turboccc · 29th March 2011, 12:28 PM

Yes, I had read the help. Maybe I just do not understand, but I was more looking for an application-type explanation. Why having different circles when you can have proximity? Maybe small circle can be outside the proximity range and you could trigger the alert from different routes coming to a POI. Or maybe put them only on one side of the road...

Note: POI Loader does not like any of the gpx files with the new extensions. That is a bummer. I would have hoped it would simply ignore the new statements. Now it means we have to create gpx files for POI Loader and gpx files for GPI Creator.

**tom1807** · 29th March 2011, 02:10 PM

I am no expert on this like u, but I noticed that Garmin speedcams are really giving only alarm when the speedcam is really on that side.
Maybe its related to that

Thread: Extra_POI_Editor up to v5.97 (.gpi file creation discussion - like POI Loader and more)

Thread Tools

Display

Hybrid View

Advertissements

Tags for this Thread

Bookmarks

Bookmarks

Posting Permissions