I have tried everything I know to load the Flying J POI file. I copy the file using the "save as". The POIloader tells me there are no data files in that directory even thought the "search" function has no problem finding the file.
What am I doing wrong???????
Just curious if you downloaded a zipped file and didn't unzip it so you have a *.csv file?
I don't have access right now to a copy of POI loader to test it, but the format of the file looks okay.
Make sure you've copied the CSV file (from inside the ZIP file) to a new directory.
Make sure POI Loader is set to look in the directory where you put the CSV file.
Here's a page with step-by-step instructions:
Installing POIs with POI Loader
Thanks for the replies guys but nothing I do seems to work!
I can open the file. It is ending in .csv I simply cannot get the POI loader to give me any response except "no data in this file".
All loaded successfully now. Apparently, I am (was) simply trying to make this thing too hard.
Thanks to all who tried to help.
I'm sorry I didn't read the discussion sooner. I'm glad it worked out for you.
I used the POI this week, but it wouldn't alert on any of the Flying J's I passed. They're accurately shown in the POI but no alert. It seems they must be directly in front or ON the route that I'm traveling to alert. I didn't expect this and am a little disappointed.
I managed to load the FlyingJ POIs to my C340 with a five mile proximity set at the time of upload. First I downloaded the csv file, then opened it in my OpenOffice spreadsheet where I swapped the lat and long fields. Then I uploaded into ExpertGPS. I applied the proximity distance and saved as a GPX file. I would be happy to share that GPX file if anyone wants it.
I've had the same problem. I pass a Flying J going to and from work every day. Despite having the proximity alert set, it does not alert me to the Flying J, even when I pull into the place to get fuel!
POI Loader will not automatically set alerts for the Flying J file. You need to set them using the "manual mode" as you're loading the file with POI Loader.
Once the basics are confirmed, then you might try troubleshooting with a smaller test file.
See this post for additional troubleshooting ideas:
Straight from the Help file of POI Loader...
Creating Custom POI Files
Advanced users can create their own .csv and .gpx data files that include Custom POI lists or TourGuide files
POI Loader loads all .csv and .gpx data files saved in a particular folder. When creating or downloading Custom POI data files, it is recommended that you save all the data files you want to upload to your device in one single folder.
POI Loader determines whether or not a file contains speed and proximity alert points based on specific criteria. Use the following information to help you create Custom POI files:
· If a file name contains a valid speed number or if all records in a file have speed encoded in the name, then all records in the file will include speed and proximity alerts. For example, a data file with the file name "Speed_30" generates speed alerts of 30 mph (or kph, depending on the type of units selected in POI Loader) for each POI in the file.
· If the file name contains "redlight", POI Loader assumes all records in the file have proximity alerts with a distance of 400m/0.25 miles
· If a file contains "GATSO," "mobile," "SPECS," "safety," "speed," or "camera," but does not have a speed, POI Loader uses a default alert speed of 0, which means you will always be alerted. You can override this default value by entering the speed in Manual mode.
· You can also enter speeds for each POI individually by adding the @ symbol and a number after the name of the POI. For example, a Custom POI named "Ridgeview@25" would create a POI named "Ridgeview" with a 25 mph speed alert.
· POI Loader calculates proximity alert distance based on speed. You can enter proximity alert distance for individual Custom POIs in a .gpx file. You can also enter proximity alert distance for all Custom POIs in a data file using Manual mode.
Understanding Speed and Proximity Alert Information
POI Loader automatically scans .csv and .gpx data files for speed and proximity alert information.
You can also use Manual mode to specify default speed and proximity alert information as needed.
Speed information can be included in the file name or in the names of individual POIs within the file.
POI Loader determines speed information based on the following information, listed from highest to lowest priority:
1. Speed information included in the name of the individual Custom POI. For example, a POI named "SpeedZone@30" will have an alert speed of 30 regardless of the speed information specified in Manual mode or in the file name.
2. Speed information entered in Manual mode.
3. Speed information included in the file name. POI Loader interprets any numbers in the file name as speed information.
Proximity Alert Information
Proximity alert information can be calculated automatically based on speed information. It can also be included in .gpx data files or added in Manual mode.
POI Loader determines proximity alert information based on the following criteira, listed from highest to lowest priority:
1. Proximity alert information listed for individual POIs in a .gpx file. This information overrides all other proximity alert information.
2. Proximity alert information entered in Manual mode.
3. Proximity alert distance calculated by POI Loader based on speed information in the file name or in individual POI names. This calculation uses the following formula:
Prompt Distance = 36 seconds * Speed.
4. A default proximity alert distance of 400 meters/0.25 miles if the file name contains the word "redlight."
5. If there is a TourGuide audio file attached and no other proximity alert information is available, POI Loader assigns a proximity alert distance of 0.25 miles.
All of this Meaning the proximity alert needs to be set up in the flying j csv file. If you open the csv using POI LOader's "Manual Mode" you should be able to have POI Loader Automatically set the proximity for you based on the settings you chose.
would love to get a copy of yor file
just bought my nuvi 660 2 days ago
Thanks a million for creating this file! I'm not sure where to send corrections?
I tried to convert this file to .ov2 for TomTom. However, I get the following error:
GPSBabel error: Invalid latitude 87105.000000 in waypoint .
I would realy like to get that flying j thing. I drive semi, and have been having trouble with the pilot/TA/fling j / petro/loves/walmart. The only one that works great is teh rest areas. I get the loves to kick off ever now and then but thats about it . Can you please help me with this. The tomtom was so much easier with the poi
I don't see a previous post....
I would realy like to get that flying j thing. I drive semi, and have been having trouble with the pilot/TA/fling j / petro/loves/walmart.
I get the loves to kick off ever now and then but thats about it .
The problem is that the Truck Service Centers (TA, Loves, Flying J etc.) are located anywhere from 100 to 2000 feet off the highway you are driving on. In order for the proximity alerts to work consistently the location would have to be closer (probably 50 ft) from the highway. That is why the rest area proximity alerts are quite consistent. The coordinates set are at the actually exit ramp entrance.
You would have to see the "Truck Stop" in the Custom POIs section of your GPSr and press "GO" to take you there.
There have been tutorials written here on POI Factory on some other methods but I have not studied up on them as my units can't use them.
H. Hannah has written considerably re: the other methods of getting alerts to function within a radius and not a straight line.
I tried changing the prox to 5500 ft and 7000 ft
no luck on it sounding off. I will check into hanna and see what there is to see.Just getting fruastrated is all. I like the garmin for accuracy,but the totom was easier for the poi
HANNA ,How Can I get ahold of you ? I could really use your help on my garmin 200. Having trouble with the POI's. Can you please help me ?
flying j now has an updated files on their website for a free download. can be downloaded in 2 different formats
seems that the flying j poi doesn't want to work on my new nuvi850. do you mind sending me a copy via email?
I guess this is the place for correction??
Wayland MO - Flying J
that's what makes this site awesome.
OK, I've read all the postings in this thread but still can't figure out why I can't add the Flying J locations. I download the GPS coordinates (decimal) from the FJ site. It is in CSV format. I tell POI Loader to install the file on my Nuvi and I get an error message "file is in invalid format". ??? Any suggestions on what I am doing wrong?
format. I just downloaded the file and it has the coordinates at the end of each line. The coordinates must be in columns A and B. You will have to reformat that file. Why don't you try downloading the file from poifactory?
I just downloaded the POI-Factory versionit to my 255w in preparation for a trip next week and had no problem. The files here are very accurate and quite a few people put a lot of effort into it.
I wanted to make a quick and dirty POI file for Factory tours. There is a site that has some organized by state. Their file also had the coordinates at the end. It is simple to download the CSV file and open it with Excel (or any other worksheet program that will handle CSV). You can then move the columns to get them in the right order.
I can't load the Flying J file either ........
Are you having trouble with the file from The POI Factory or the file from the Flying J website?
The file on the FJ site has errors as to the coordinates. I have gone through each location and corrected the coordinates in the GPX version.
I thought it was time to update my two year old 'Flying-J' POI. I always 'Verify' the POIs before installing and found that both the "Fuel - Flying J.csv" and the "FlyingJ_wlinebreaks.csv" at http://www.poi-factory.com/node/491 have errors.
Fuel - Flying J.csv: Line 52 is missing the minus sign in the longitude coordinate; and line 117 has the latitude as both the longitude and latitude.
FlyingJ_wlinebreaks.csv: Line 7 and 79 are missing the minus sign in the longitude coordinate; and line 147 has the latitude as both the longitude and latitude.
I also checked Flyingjs.csv (w/RV dump stations) at http://www.poi-factory.com/node/22377 and it, too, has errors.
Line 3 is missing the minus sign in the longitude coordinate; and line 248 has 0.0000 as the longitude coordinate.
RT, thanks for pointing those out, I have them all fixed now.
I would like to take advantage of your generous offer for the subject file.
I'm not sure how to get you my email address without the entire planet having access as well. Pleaswe advise best practice.
Thanks very much.
terms | privacy | contactCopyright © 2006-2019