POI Factory's Speed/Red Light Cameras

 

Am i the only one that thinks this way? If im going to pay for the Speed/Red Light Cameras Poi's and I did... i think it should come without every poi stating poi-factory after all we are paying for it. What do you think?

Ok as it is

knightflt wrote:

Am i the only one that thinks this way? If im going to pay for the Speed/Red Light Cameras Poi's and I did... i think it should come without every poi stating poi-factory after all we are paying for it. What do you think?

I do not see a difference between earning or paying for the Camera files.

The fact that the two files are "branded" could be taken into account at the time that the decision is made to purchase, if the fact that there is "branding" is objectionable.

File Branding

I'm okay with the file branding, at least it causes some effort to post on another site.

No im not sure you guys are

No im not sure you guys are getting what i am saying. every time i come to a speed/red light camera poi point or intersection a poi pops up on my gps eg: red light camera 4st and 8ave poi-factory can do without there name popping up in the poi on the gps

I have never noticed it

knightflt wrote:

No im not sure you guys are getting what i am saying. every time i come to a speed/red light camera poi point or intersection a poi pops up on my gps eg: red light camera 4st and 8ave poi-factory can do without there name popping up in the poi on the gps

I wonder if that is the difference between paid and free.
You get them free here if you are active.

Is JM maintaining 2 different files?

--
Nuvi 2460LMT.

don't notice anymore

ever since we got the 2350LMT I don't believe there is any red bar across the top. Only a dinging sound. But somehow, the garmin also has its own red light files that match the POI file, so two dinging sounds. VERY ANNOYING, if anyone else is in the vehicle except my wife it's embarrassing, but I figure better to have an annoying sound than to not be alerted. Passengers often wonder why it's necessary to be alerted at red light intersections. I guess they tend to think logically when they're not the driver, if you don't run the light, why would you worry? Then, you have annoying sounds upon approach of them. To each his own I suppose...

Remove them

If you don't like "POI Factory" showing up on the poi's you download from the POI Factory then remove the phrase. Load the file into a spreadsheet and do a search and replace. Search for *[space]POI Factory* and replace with [space].

But why do you think that is a bad thing. Did you replace the author's splash screen on all of your computer programs?

4th field

In both my files the "poi factory and date" info is in the 4th field of the csv files. I don't see them on the alert banner. I see the 3rd field.

--
Harley BOOM GTS, Zumo 665, (2) Nuvi 765Ts, 1450LMT, 1350LM & others | 2019 Harley Ultra Limited Shrine - Peace Officer Dark Blue

2 Files? / 4th Column

@pwohlrab - Two different files?

Nope, There's only one version of the files. They're the same for everyone.

@bear007

Correct. The fourth column contains poi factory and date. I sometimes use this info for troublshooting with end users (to make sure the correct file is loaded, etc.)

The fourth column description hasn't been showing up in the alerts, but it might be that Garmin has recently made some changes.

Is anyone else seeing 4th column info showing on their alerts?

Jonathan

not here

JM wrote:

@pwohlrab - Two different files?

Is anyone else seeing 4th column info showing on their alerts?

Jonathan

Not in the 260 or the 2460LMT

--
Garmin 38 - Magellan Gold - Garmin Yellow eTrex - Nuvi 260 - Nuvi 2460LMT - Google Nexus 7 - Toyota Entune NAV

.

Nothing on my 3790 is showing, just "RLC Alert: X and Y"

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

All I see is the 3rd column

That was why I questioned a 2nd file for free vs paid. But then it would really make no sense to have duplicate files. It was only a thought based on the ops question.

--
Nuvi 2460LMT.

Not seeing the 4th column

Not seeing the 4th column on my 760.

dobs108

not on my 1490

Either

--
1490LMT 1450LMT 295w

3490 - 4th column

I see RLC & the named intersection

What's the OP device?

Maybe it would help if the OP would let us know what GPSr he's using that shows that fourth column.

I have a nuvi 255 I must

I have a nuvi 255 I must have had something going on with my office or something or maybe a glitch in loading with the garmin poi loader, completely took all the poi's off the garmin and did a reinstall of the poi's and now all is working good without changing the exel files to not show poi-factory in the pop up on the garmin when approaching the poi
the only thing that is wrong is that the speeds in Canadian city's are in mph even though i have the poi loader set to read in metric and km/h so i did have to go into the exel the file and adjust the speeds to km/h

.

Punctuation is your friend. Trust me on this one.

A wall of text is not fun to read.

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

alert speeds

knightflt wrote:

...the only thing that is wrong is that the speeds in Canadian city's are in mph even though i have the poi loader set to read in metric and km/h so i did have to go into the exel the file and adjust the speeds to km/h

Quick Solution:

Select miles/hour for the units in POI Loader when loading the files, and that should correct the alert speeds.

More details (if you're interested):

The descriptions in the file show local units (km/h for locations in Canada). However, the speed tags (which are not shown but used to set the alert speed) are all in mph. This is necessary because the tag values must have the same units throughout the file, and the file contains both USA and Canada locations. This does not affect the way the speed is displayed on the GPS, it only means you'll need to tell POI Loader that the speed tags are in MPH.

Jonathan (aka JM)

.

JM, it sounds like he did that already. I'm thinking his unit is in 'MPH' mode, i.e. System Units.

The nuvi will auto-translate the speed from one to the other. But, the main Unit speed is what it will show on the screen.

What I mean is, even though I'm in Canada, I can set the nuvi to show feet, and MPH instead of meters, and KPH.

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

Setting in POI Loader vs. setting in nuvi

Juggernaut wrote:

JM, it sounds like he did that already. I'm thinking his unit is in 'MPH' mode, i.e. System Units.

The nuvi will auto-translate the speed from one to the other. But, the main Unit speed is what it will show on the screen.

What I mean is, even though I'm in Canada, I can set the nuvi to show feet, and MPH instead of meters, and KPH.

Could be, but I still suspect the problem is the setting in POI Loader.

The OP said "i have the poi loader set to read in metric and km/h".

For the camera files, the setting in POI Loader must be miles/h because all of the speed tags in the source file (e.g., @45, @30, @31.1, @37.3, etc.) are in miles per hour.

The mph / kph choice in *POI Loader* is used to calculate the alert speed that is saved in the .gpi file and sent to the GPS. This setting *must* match the file. If the wrong setting is chosen, then the .gpi file that is generated will contain incorrect speed values.

The mph / kph choice in the *nuvi* is used to specify what the user wants to be shown on the nuvi's display. This setting determines how the values from the .gpi file are translated to show on the display. This setting can be whatever the user prefers.

Jonathan

Maybe, maybe not

JM wrote:

The OP said "i have the poi loader set to read in metric and km/h".

For the camera files, the setting in POI Loader must be miles/h because all of the speed tags in the source file (e.g., @45, @30, @31.1, @37.3, etc.) are in miles per hour.

The mph / kph choice in *POI Loader* is used to calculate the alert speed that is saved in the .gpi file and sent to the GPS. This setting *must* match the file. If the wrong setting is chosen, then the .gpi file that is generated will contain incorrect speed values.

The mph / kph choice in the *nuvi* is used to specify what the user wants to be shown on the nuvi's display. This setting determines how the values from the .gpi file are translated to show on the display. This setting can be whatever the user prefers.

Jonathan

I'm not seeing that issue on my unit. When I load the cameras files its set to Metric. 110 Meters. I get one warning. I did not get out and measure if its 110 meters away from the intersection, but the distance feels right. What i can say is, that on my old 765T it would warn me 3 times before and once after i passed the intersection. Not sure why it did that.

--
3580LMT - 2598LMT - DriveSmart 65 --- We do not live in Igloo's and do not all ride to work on snow mobiles.

@speed2

It sounds like you're using distance alerts (110 meters) and these are working just as you'd expect.

If you're using manual mode to set an alert distance, then the distance setting should work just fine in which ever units you've selected.

The situation I was describing was for the speed-based alerts, where the alert speed is being read from @ speed tags inside the file. In this situation, POI Loader needs to know what units are being used for the @ speed tag values. (And this only applies to the speed cameras file.)

My 295W doesn't display that

knightflt wrote:

No im not sure you guys are getting what i am saying. every time i come to a speed/red light camera poi point or intersection a poi pops up on my gps eg: red light camera 4st and 8ave poi-factory can do without there name popping up in the poi on the gps

My 295W doesn't display that, just shows a small banner that shows the speed limit from the file.

--
GM Built-in Navigation system - Samsung S6 Edge+ Smartphone with Garmin Viago, Google Maps & HERE Apps

I do

JM wrote:

It sounds like you're using distance alerts (110 meters) and these are working just as you'd expect.

If you're using manual mode to set an alert distance, then the distance setting should work just fine in which ever units you've selected.

The situation I was describing was for the speed-based alerts, where the alert speed is being read from @ speed tags inside the file. In this situation, POI Loader needs to know what units are being used for the @ speed tag values. (And this only applies to the speed cameras file.)

I do those at 600 meters. Works fine. We don't have those here in b.c. but portland does, where we go once a year. I might still be on the wrong track here? If so, it's no biggy to do mph in manual.

--
3580LMT - 2598LMT - DriveSmart 65 --- We do not live in Igloo's and do not all ride to work on snow mobiles.