Can I modify a RLC file?

 

New to this..... Can I add a new rlc to the file I downloaded from POI, using the 'intersection' (or does it only accept lat/lon)?

--
signat

You Can Add

You can add a Redlight Canera location but you MUST use coordinates not intersection.

--
Nuvi 2460LMT 2 Units

report missing location

The best thing is to report the missing location so it gets added to the master file here at POI-Factory otherwise every time you download the RLC weekly update you will have to manually add the location you mentioned.

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

Link to Report Enforcement Camera Locations

Just go to the following link to report it and it will be verified and added to the main data file:

http://www.poi-factory.com/node/455

--
Garmin Drive Smart 55 - Samsung Note 10 Smartphone with Google Maps & HERE Apps

Most GPS units will let you

Most GPS units will let you save your current location. When you look at the details it saves the lat and long information as your location. You can use that information for your own POI, including red light camera.

I suspect there is a way to get lat and long with something like google maps.

Is it a RLC?

poirfs wrote:

New to this..... Can I add a new rlc to the file I downloaded from POI, using the 'intersection' (or does it only accept lat/lon)?

When someone asks about adding a new RLC, I always wonder about whether or not they are speaking of a camera that monitors turn lanes and the like.

When I first became a member of the site and got enough posting to be able to download the camera files, I went to each of the camera locations in my municipality to check them out.

I would park as close as I could to the intersection and then do a Tools > Where Am I? to record the coordinates. I found several coordinates that were off enough to feel that the coordinates should be tweaked.

Then I would look to see if I thought the "camera" was really an Automated Traffic Enforcement device. As I recall, I found two that were not really ATE devices. I then got a list of the camera locations according to the Traffic Engineer to verify they were not ATE. I reported those to JM and he removed them from the file.

I think one of the reasons that the poi-factory file is so accurate is that our members keep them so by double checking each other.

Often a new member will want to be helpful and will report actual "cameras" that are not ATE devices. The way these situations are corrected is by having someone else verify them.

So - I would encourage all members who live in a municipality that has ATE to do a search on the file for their municipality and check them out on a day when time can be taken for a drive. The drive could be used to verify alerts for special POIs of interest to the member or to check out how TourGuides work, for instance.

If you have never done so, I encourage you to look at
http://www.speedtrap.org/

Work your way down through your state to your municipality and see how many of the "speedtraps" reported are actually correct. In my municipality, I find that most of the reports are spurious.

At poi-factory we keep our camera files at a high degree of accuracy.

speedtrap.org

jgermann wrote:

If you have never done so, I encourage you to look at
http://www.speedtrap.org/

Work your way down through your state to your municipality and see how many of the "speedtraps" reported are actually correct. In my municipality, I find that most of the reports are spurious.

At poi-factory we keep our camera files at a high degree of accuracy.

I just went through the site for locations in my area. One complained of a speed trap where the posted limit is 55 and he was cited for doing 74. That's not just speeding, that's reckless driving.

--
Illiterate? Write for free help.

Knoxville, TN RLC

Recently on a trip to Knoxville, TN, I was alerted to a RLC that looked like it had been removed. There was no time to get a good look.

Anyone who is in Knoxville please look at the entrance to Turkey Creek and verify?

I don't remember the cross streets. Sorry

--
NUVI40 Kingsport TN

POI files only use lat/lon

poirfs wrote:

New to this..... Can I add a new rlc to the file I downloaded from POI, using the 'intersection' (or does it only accept lat/lon)?

Look inside the POI Factory RLC file by opening it in Notepad. You will see that each line of the file is a location that uses a text string beginning with the coordinates (lat/lon).

Rather than modifying the POI Factory file by adding another line for your additional location, consider creating another RLC file with this one location. The filename should be different but do not add any numbers to the filename. Keep both RLC files in the same folder on your PC and POI Loader will find them both.

I use Google Earth to get the coordinates. You can view the intersection from above and place a marker right in the middle. Read Google Earth Help to get the coordinates in degrees and decimal degrees to about five places.

It is not necessary to provide coordinates in reporting a Red Light Camera location to POI Factory but it sure helps!

dobs108 smile

People need to look at the pictures

Problem is that people think any camers up there on the yard arm is a RLC. There is a guide on here that shows you pictures of what a RLC looks like that can help you out. Although I think I was fooled yesterday. In order for a RLC to cite you, there needs to be a camera down the road just a little bit from the intersection in order to take a picture or film you after you run the light. A camera just looking at you when you are let's say stopped at the light, will not be able to take a picture after you run it. Normally the one's on the yard arm up high at the intersections are not RLC, but I seen one yesterday, well my GPS reported one so I looked for it, and it looked just like the normal cameras up high but it was positioned down the road a little way in order to catch you after going through. Will try to find the website that lists them here, I believe I found it once before.