Truck Stop Guide

 

Just wanted to put out a Channel to get some idea on what is the best format and or layout that would work for over 50% of people. I know I wouldn't be able to make one file that would fit the needs of all. But I'll do my Best.

Please post comments, corrections, idea's or just a thought. I'm open to all. Since this is my first project. Though I jumped in to such a large project.

Page 1>>

Feedback

Greetings,

Just wanted to let you know that I think you are putting together a very useful file of all of the independent truck stops. They have a lot to offer and are can be found where there are no national names in the area. I like how you included additonal data on what the facility has to offer.

I am not a professional driver, but this should be very helpful for RV owners such as me and for anyone travelling the interstate and highways.

I prefer the CVS format. Seeing as it can be viewed and edited by a text edit program or a spreadsheet program, it is much easier for the end user to work with. It also creates a smaller file that downloads faster when you have a sloooooow connection (ie: a marginal wi-fi or land line). The only reason I can think of to use a GPX format is if the GPX file will do something that can not be done in a CVS file. Not being that familar with the differences, I cannot think of any reason to go GPX.

One additional data item that would be very helpful is stating if a truck stop has a dump facility. I would think that would be helpful to some professional drivers and most RV'ers. Example:
PD - Pay Dump Facility
FD - Free Dump Facility
ND - No Dump Facility

I will let you know if I come across any updates in my area.

Thanks,
BH

--
Garmin Nuvi 760, 2699, Oregon 450, Montana 680t

Only one thing NEEDED...

cool

FIRST, yes the project you are on is a big one but you are doing a GREAT job!

You can save yourself a lot of time and headaches by including a phone number when you can,,, that way whatever the question may be, it can be answered by making a call to the stop by the user...

No matter what you do!!! someone will want you to add something new just because.

However, it's your project and it's your call.

Happy and safe trucking.

--
"Destination Eternity" Garmin 765T, & Samsung Galaxy Note Edge

Don't forget us in the great white north

starlillie01 wrote:

Just wanted to put out a Channel to get some idea on what is the best format and or layout that would work for over 50% of people. I know I wouldn't be able to make one file that would fit the needs of all. But I'll do my Best.

Please post comments, corrections, idea's or just a thought. I'm open to all. Since this is my first project. Though I jumped in to such a large project.

--
I drive, therefore I am happy. Rodeo, wildlife and nature photography rodeophoto.ca

A couple of small things

1 - Include a header line for the .csv file.

2 - Not sure where you're getting your data from, but something that would be REALLY useful would be as to whether or not the truckstop has food, and if so, what type (deli, fast food, sit-down restaurant, 24hr or not). I have a large truckstop guide that shows that info in it (it doesn't say WHAT restaurants are there - just as to the fast food/deli/restaurant/24hr thing.

For me to use the data in CoPilot v8 Truck Laptop, I had to use Excel to remove the comma's in the data fields (not the ones seperating the data, just the ones IN the field. Streets & Trips imports it fine, though.

Keep up the great work. Love this collection

Can't have a header line in csv.

malaki86 wrote:

1 - Include a header line for the .csv file.

2 - Not sure where you're getting your data from, but something that would be REALLY useful would be as to whether or not the truckstop has food, and if so, what type (deli, fast food, sit-down restaurant, 24hr or not). I have a large truckstop guide that shows that info in it (it doesn't say WHAT restaurants are there - just as to the fast food/deli/restaurant/24hr thing.

For me to use the data in CoPilot v8 Truck Laptop, I had to use Excel to remove the comma's in the data fields (not the ones seperating the data, just the ones IN the field. Streets & Trips imports it fine, though.

Keep up the great work. Love this collection

If you are referring to the first line in the csv as a header (which I believe it is called), the file will be kicked out and won't load. It would be incorrect data.

--
Nuvi 2460LMT.

The Small Things

1 - The other file I have posted does have the header in in. I goofed and have to update it when I get the chance to.

2 - I get my information from a wide variety of places, such as seeing them as I go past them. Which is an on going task. If I mark a place and then try to verify it on Google maps and if it shows nothing I have to wait till I pass that area again to verify. Other locations doesn't seem to have that much info.

on that note, if or when I ever get close to finishing the task at hand right now with Location, address, phone numbers and parking spaces I will task the feat of putting in what is available to eat at the stop.

Which is no small task with 1 person tasking this job. I knew what I was getting in to.

It's also hard right now with so many places closing and being bought by large chain company's. UGGHH!!!

Thanks,

Truck Stops

There are already at least 3 files on this forum dealing with truck stops.

poi-factory.com/node/30339
poi-factory.com/node/491
poi-factory.com/node/26860

Don

.

donaldb530 wrote:

There are already at least 3 files on this forum dealing with truck stops.

poi-factory.com/node/30339
poi-factory.com/node/491
poi-factory.com/node/26860

Yes, but starlillie01 is maintaining lists of independent truck stops, and 30339 is one of those lists. The other two you cited include chains.

CSV format file issue

The new CSV format file is not displaying all of the data on Garmin devices. I believe this is because the Garmin POI Loader picks up data only from columns A, B, C and D. The data in the additional columns is dropped.

Example from prior GPX file:

Liberty Fuel Truck Stop - I-10
Exit 138 - Phoenix, AZ - ($,L)
1201 N 59th Ave
Phoenix AZ 85035
Phone: (602) 233-1196

Example from current CSV file:

Liberty Fuel Truck Stop - I-10
Exit 138 - Phoenix, AZ - ($,L)
1201 N 59th Ave

The last two lines with the City/State/Zip and the phone number (contained in columns past D) are not displayed.

I hope the above makes sense. Please let me know if you need more details.

Thanks for keeping this POI file of independent truck stops up-to-date!

--
Garmin Nuvi 760, 2699, Oregon 450, Montana 680t

The csv file is not set up correctly

BH in AZ wrote:

The new CSV format file is not displaying all of the data on Garmin devices. I believe this is because the Garmin POI Loader picks up data only from columns A, B, C and D. The data in the additional columns is dropped.

Example from prior GPX file:

Liberty Fuel Truck Stop - I-10
Exit 138 - Phoenix, AZ - ($,L)
1201 N 59th Ave
Phoenix AZ 85035
Phone: (602) 233-1196

Example from current CSV file:

Liberty Fuel Truck Stop - I-10
Exit 138 - Phoenix, AZ - ($,L)
1201 N 59th Ave

The last two lines with the City/State/Zip and the phone number (contained in columns past D) are not displayed.

I hope the above makes sense. Please let me know if you need more details.

Thanks for keeping this POI file of independent truck stops up-to-date!

The file located at http://www.poi-factory.com/node/30339 has 8 individual columns that have all the info in. All info is what you are looking for. The columns need to be combined so you have 4 columns where the 4th column contains address (city, state, zip) and phone #.

--
Nuvi 2460LMT.

POI Loader restrictions

From the help file

"

POI Loader assumes a .csv file utilizes the following format for each POI (brackets [ ] denote optional text):

,,["][@]["],["] [comment]["]

Longitude and latitude must appear in WGS84 decimal degrees format (ddd.ddddd; negative numbers indicate West and South).

If you include quotes around the name or comment, you can include line breaks in the text.

The following are examples of Custom POIs in the proper format:

-94.81549,38.80390,Bonita

-94.79731,38.81099,Ridgeview@25

-94.74240,38.81952,Heritage Park,Perfect site for a picnic

-94.76416,38.81227,Garmin,"1200 E. 151st Street

Olathe,KS 66062
913/397.8300"

"

CSV format file issue (suppose to be a GPX)

BH in AZ:

I might have been tired since one file is suppose to be the gpx file for garmins and the other is suppose to be a .csv file that is extended to allow others to use EPE to make their own file. I guess I didn't catch that which is my bad. Sorry about any complications may have caused. I hope the newer one fixes any issues. If not let me know.

Here is the .csv file:
http://www.poi-factory.com/node/32870

New files

Ok, test time I put new files up. lets hope i dind't make anything worse.

What's up with this starlillie01?

--
nüvi®3580LMT,nüvi®2598LMT| We do not live in Igloo's, and do not all ride to work on snow mobiles.

Same here?

cool

Speed2 wrote:

http://s19.postimage.org/9idq9ktwj/Truck_Stop.jpg

I got the same message,,,
Converted the file to CSV and all went well.
There is a problem in the GPX file but did not have time to correct it... change to csv and move on.

--
"Destination Eternity" Garmin 765T, & Samsung Galaxy Note Edge

.

Microchip wrote:

cool

Speed2 wrote:

http://s19.postimage.org/9idq9ktwj/Truck_Stop.jpg

I got the same message,,,
Converted the file to CSV and all went well.
There is a problem in the GPX file but did not have time to correct it... change to csv and move on.

smile

--
nüvi®3580LMT,nüvi®2598LMT| We do not live in Igloo's, and do not all ride to work on snow mobiles.

OOPS

Microchip wrote:

cool

Speed2 wrote:

http://s19.postimage.org/9idq9ktwj/Truck_Stop.jpg

I got the same message,,,
Converted the file to CSV and all went well.
There is a problem in the GPX file but did not have time to correct it... change to csv and move on.

Same thing. works fine on my 3790LMT though

--
nüvi®3580LMT,nüvi®2598LMT| We do not live in Igloo's, and do not all ride to work on snow mobiles.

It's still in GPX format

starlillie01 wrote:

BH in AZ:

I might have been tired since one file is suppose to be the gpx file for garmins and the other is suppose to be a .csv file that is extended to allow others to use EPE to make their own file. I guess I didn't catch that which is my bad. Sorry about any complications may have caused. I hope the newer one fixes any issues. If not let me know.

Here is the .csv file:
http://www.poi-factory.com/node/32870

Both of your files seem to be in GPX format, I'm looking for the CSV file.

Shlomie

the error in this file

The error is that the symbol field doesn't have a symbol name but has the display instructions.

[sym]SymbolAndName[/sym] This should be:
[sym]Truck Stop[/sym]

(replace the [ and ] with < and >)

--
Illiterate? Write for free help.

.

Box Car wrote:

The error is that the symbol field doesn't have a symbol name but has the display instructions.

[sym]SymbolAndName[/sym] This should be:
[sym]Truck Stop[/sym]

(replace the [ and ] with < and >)

Still can't get it to work. I don't get an error now but there's nothing in the file. sad

--
nüvi®3580LMT,nüvi®2598LMT| We do not live in Igloo's, and do not all ride to work on snow mobiles.

Truck stops

It's going to take a lot more work than I want to devote to this to figure out all the potential problems in the file. If I used the file, it would be different but the list DonaldB maintains is good enough for me. If starlille doesn't post an update, I may take some time and try to figure out the fields used from the HTML tags and then create a master source file. Even that's a day or more of work.

--
Illiterate? Write for free help.

.

Box Car wrote:

It's going to take a lot more work than I want to devote to this to figure out all the potential problems in the file. If I used the file, it would be different but the list DonaldB maintains is good enough for me. If starlille doesn't post an update, I may take some time and try to figure out the fields used from the HTML tags and then create a master source file. Even that's a day or more of work.

Thanks

--
nüvi®3580LMT,nüvi®2598LMT| We do not live in Igloo's, and do not all ride to work on snow mobiles.

Bad GPX file

From what I can see, all you need to do is open the file in EPE and use Edit > Replace Field... to change the following values:

Symbol: Truck Stop

Display: SymbolAndName

and then save the file. The resulting GPX file passes XML validation against the GPX/GPXX schema and should work (but I don't own a Garmin so I can't test it).

So OK... I'll Bite..

"StarLillie01" said in part..

starlillie01 wrote:

Just wanted to put out a "Channel"...

What? Putting out a "CHANNEL"? confused Would that be in High Definition.. as I have NO idea what you're talking about. neutral

Nuvi1300WTGPS

--
I'm not really lost.... just temporarily misplaced!

.

Nuvi1300WTGPS wrote:

"StarLillie01" said in part..

starlillie01 wrote:

Just wanted to put out a "Channel"...

What? Putting out a "CHANNEL"? confused Would that be in High Definition.. as I have NO idea what you're talking about.

Have you never heard the term "open a channel", as in "establish a connection with other people"...?

confused

LOL

VersatileGuy wrote:
Nuvi1300WTGPS wrote:

"StarLillie01" said in part..

starlillie01 wrote:

Just wanted to put out a "Channel"...

What? Putting out a "CHANNEL"? confused Would that be in High Definition.. as I have NO idea what you're talking about.

Have you never heard the term "open a channel", as in "establish a connection with other people"...?

confused

--
nüvi®3580LMT,nüvi®2598LMT| We do not live in Igloo's, and do not all ride to work on snow mobiles.

.

This file from VersatileGuy works
Truck Stop Guide VG tweak.gpx

--
nüvi®3580LMT,nüvi®2598LMT| We do not live in Igloo's, and do not all ride to work on snow mobiles.

File Corrections

This is bad on my part, but if you check now at:

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

I put the CSV file back, and its just saved from excel not a EPE file.

Hope This is what you were looking for.

For the other errors, I found what may have been the mistakes and worked on them. they uploaded to my Garmin 3790 with no errors.

FYI - I had deleted my main file and had to revert to a backup copy and my have been the cause of some of the columns out of the correct order. I hope I'm back on the right track now.

Sorry all for taking so long, Days have been long out here.

I made a file that is a little cleaner for Garmin gps, let me know if this is any better or worse.

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

.

starlillie01 wrote:

This is bad on my part, but if you check now at:

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

I put the CSV file back, and its just saved from excel not a EPE file.

Hope This is what you were looking for.

For the other errors, I found what may have been the mistakes and worked on them. they uploaded to my Garmin 3790 with no errors.

FYI - I had deleted my main file and had to revert to a backup copy and my have been the cause of some of the columns out of the correct order. I hope I'm back on the right track now.

Sorry all for taking so long, Days have been long out here.

I made a file that is a little cleaner for Garmin gps, let me know if this is any better or worse.

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

Truck Stop Guide Master 12-30-12.csv does not work.
Neither does your last link. Access denied? lol that's funny, never had that in here.

--
nüvi®3580LMT,nüvi®2598LMT| We do not live in Igloo's, and do not all ride to work on snow mobiles.

re: access denied

Speed2 wrote:

Access denied? lol that's funny, never had that in here.

That file was uploaded as a brand new POI file so it needs to be approved by the administrators before the rest of us can access it.

.

VersatileGuy wrote:
Speed2 wrote:

Access denied? lol that's funny, never had that in here.

That file was uploaded as a brand new POI file so it needs to be approved by the administrators before the rest of us can access it.

Ok maybe i didn't explain myself correctly.
The actual file "Truck Stop Guide Master 12-30-12.csv"
when you load it does not work. I have access to that file. The link "http://www.poi-factory.com/node/38663"
I do not have access to.

--
nüvi®3580LMT,nüvi®2598LMT| We do not live in Igloo's, and do not all ride to work on snow mobiles.

just because it says CSV

Just because it says CSV are you trying to load it using POI Loader or did you read starlillie's note that said it had extra columns and was his source file?

--
Illiterate? Write for free help.

.

Box Car wrote:

Just because it says CSV are you trying to load it using POI Loader or did you read starlillie's note that said it had extra columns and was his source file?

Under post "File Corrections" Sun, 12/30/2012 - 11:00pm. I don't see what you are trying to point out.

--
nüvi®3580LMT,nüvi®2598LMT| We do not live in Igloo's, and do not all ride to work on snow mobiles.

This file is bad.

Speed2 wrote:
starlillie01 wrote:

This is bad on my part, but if you check now at:

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

I put the CSV file back, and its just saved from excel not a EPE file.

Hope This is what you were looking for.

For the other errors, I found what may have been the mistakes and worked on them. they uploaded to my Garmin 3790 with no errors.

FYI - I had deleted my main file and had to revert to a backup copy and my have been the cause of some of the columns out of the correct order. I hope I'm back on the right track now.

Sorry all for taking so long, Days have been long out here.

I made a file that is a little cleaner for Garmin gps, let me know if this is any better or worse.

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

Truck Stop Guide Master 12-30-12.csv does not work.
Neither does your last link. Access denied? lol that's funny, never had that in here.

The file that is referenced at: http://www.poi-factory.com/node/32870 won't work. The 1st line can not have name fields. Delete line 1 and try again. As for the rest of the file, the csv will only load the 1st 4 columns so the rest are useless in the csv. People will have to convert to a gpx to make use of all the fields. That would be a good thing.

--
Nuvi 2460LMT.

Looking forward to helping out

This POI is invaluable to me as an over the road professional driver. I especially enjoy it because I tend to like the smaller truck stops over the larger big chain ones.

Over the last 12 months I've found about 150 truck stops that don't appear in this file. I'll be sending updates/additions when I can over the next few months.

Thanks for the great job on this file!

--
Amazing GPS: I once was lost but now am found.

Additons

I Will Welcome any stops I don't have. I only drive a region anymore so anything out of my normal 5 states I don't get to find. I will be looking forward for the additional work. smile

Here ya go, actual locations (not just nearby)

-82.576220 , 31.102919,"Valdosta Hwy US 84/HWY38 GA”

-77.796744 , 36.128020,"I 95 Sb BP”

-81.956317 , 34.746555,"I 26 Eb SC”

-79.535061 , 34.344622,"Highway 38 W HWY 38 Hess SC”

-77.180441 , 41.052203,"I 80 Wb on hill”

--
Amazing GPS: I once was lost but now am found.

truck stop file

many thanks for you efforts..we traveled for 6 months across the usa in a 5th wheel..this file is worth its weight in gold..using a rm 7710 with "truck stop guide master 12-30-12..csv file..
question..i see a lot of comments of files with only 4 columns of data..is there a newer file with all the data from the above file ??
again thanks

crisco65

--
jim crisco

Awesome

I'm going to install this and try it out. I have a dezl560 and am disappointed that garmin did not include the independent/mom&pop truckstops. Many of these have ample parking (20+ trucks) and even the a fuel only stop is useful for truckers. We can't exactly whip into the nearest gas station for a bathroom break.
I'll send you locations as I find them.
Thanks again for starting and continuing this.
Rusty

--
Garmin dezl560 LMT

Be careful! Not very reliable

I've found that the locations for many of these stops to be WAY off. By a mile in some cases. I'm hoping that the locations in this file would be verified at some point.

If you choose to go to one of these locations that you're not familiar with, and it's late at night and your running low on time, you can find yourself in big trouble because you won't be able to easily find the truck stop.

--
Amazing GPS: I once was lost but now am found.

Just Remember

Vito wrote:

I've found that the locations for many of these stops to be WAY off. By a mile in some cases. I'm hoping that the locations in this file would be verified at some point.

If you choose to go to one of these locations that you're not familiar with, and it's late at night and your running low on time, you can find yourself in big trouble because you won't be able to easily find the truck stop.

Just remember that most of the locations are listed by address. As shown many, many times, POI locations are at the mercy of the GIS information concerning street addresses and the location of address number locations as reported by local governments.

--
Frank Nuvi 3597LMT 37.322760, -79.511267

Sure

That's fine. But a professional driver has to account to a clock and goes into violation if he goes over his 11-14. Therefore it's important to to know about the accuracy of this file; so that ample time is given searching for these stops, some of which are in fact erroneous, location-wise.

So while the reason you state for this discrepancy is valid, and perfectly legitimate, it really doesn't address the issue at hand and a warning is still needed.

--
Amazing GPS: I once was lost but now am found.

Some more data, please

Vito wrote:

I've found that the locations for many of these stops to be WAY off. By a mile in some cases. I'm hoping that the locations in this file would be verified at some point.

If you choose to go to one of these locations that you're not familiar with, and it's late at night and your running low on time, you can find yourself in big trouble because you won't be able to easily find the truck stop.

@Vito,

I understand your comments. What I was wondering was whether you were talking about the "Truck Stops" that initiated this thread (http://www.poi-factory.com/node/30339) or the several different truck stop POI files on our site.

Perhaps we could come up with a way for truckers to assist in getting the locations of the file more accurate, but that raises the question of what we mean by accuracy.

I am not a trucker, but my sense is that many truck stops are a fair distance off the roadway - so would not fall within the 30 meters of the center of the route one is on for purposes of sounding an "alert". That would be one definition of accuracy.

Alternatively, you may be saying that the coordinates of some of the places you are questioning are not even in the vicinity.

Which is it?

Note: I see that starlillie01 has recently given you thanks for locations is the file

This might be too much work, but if you knew a route you would be following, you could have EPE load the route and then "merge open" a POI file. You would ask EPE to "Find POI on Route" and then walk through what was found one by one, looking at the "satellite" view to make sure there were truck stops at the coordinates given.

If enough truckers took some time in doing this, these files would be more useful.

garmin dezl

For some reason I can't route to these stops on my Garmin dezl. If anyone knows why I'd love to hear it.

More info, plz

kizbit wrote:

For some reason I can't route to these stops on my Garmin dezl. If anyone knows why I'd love to hear it.

When you try to create a route to one of these, what happens? Error messages, etc...

To be clear...

jgermann wrote:
Vito wrote:

I've found that the locations for many of these stops to be WAY off. By a mile in some cases. I'm hoping that the locations in this file would be verified at some point.

If you choose to go to one of these locations that you're not familiar with, and it's late at night and your running low on time, you can find yourself in big trouble because you won't be able to easily find the truck stop.

@Vito,

I understand your comments. What I was wondering was whether you were talking about the "Truck Stops" that initiated this thread (http://www.poi-factory.com/node/30339) or the several different truck stop POI files on our site.

Perhaps we could come up with a way for truckers to assist in getting the locations of the file more accurate, but that raises the question of what we mean by accuracy.

Using Google Earth the exact location of a truck stop can be verified and included in the POI. I do this with the POI files I've uploaded here. As far as accuracy, it needs to be VERY accurate when it comes to trucking. A driver can't make U-turns etc etc like a car can. Going down the wrong street can be literally hazardous. Not to mention spending additional time, wasted, which could have been avoided if the location were more precise to begin with. In trucking, TIME IS MONEY, literally, hence my comment about the locations.

--
Amazing GPS: I once was lost but now am found.

Makes Sense

Vito wrote:

...
Using Google Earth the exact location of a truck stop can be verified and included in the POI. I do this with the POI files I've uploaded here. As far as accuracy, it needs to be VERY accurate when it comes to trucking. A driver can't make U-turns etc etc like a car can. Going down the wrong street can be literally hazardous. Not to mention spending additional time, wasted, which could have been avoided if the location were more precise to begin with. In trucking, TIME IS MONEY, literally, hence my comment about the locations.

This is just to satisfy my curiosity - from a trucker's point of view, what would be the best coordinates to apply to a truck stop?

Would it be the front door of the building? The entrance to the parking area? The main entrance on the principal approach road?

For me, The Truck entrance

For me, The Truck entrance on the principal approach road. Reasoning being, the GPS will bring you off on the correct approach road but finding the Truck Entrance is tricky sometimes.

--
Frank Nuvi 3597LMT 37.322760, -79.511267

Thanks for the...

jgermann wrote:
Vito wrote:

...
Using Google Earth the exact location of a truck stop can be verified and included in the POI. I do this with the POI files I've uploaded here. As far as accuracy, it needs to be VERY accurate when it comes to trucking. A driver can't make U-turns etc etc like a car can. Going down the wrong street can be literally hazardous. Not to mention spending additional time, wasted, which could have been avoided if the location were more precise to begin with. In trucking, TIME IS MONEY, literally, hence my comment about the locations.

This is just to satisfy my curiosity - from a trucker's point of view, what would be the best coordinates to apply to a truck stop?

Would it be the front door of the building? The entrance to the parking area? The main entrance on the principal approach road?

...great question! For a truck driver entering into a truck stop, the best coordinates would always be at the entrance of the fuel isle. The fuel isle is easily seen in Google Earth. The fuel island entrance is almost always the best way to approach the truck parking.

If the "truck stop" is something like McDonalds (which has parking for big rigs in some cases), then the best coordinates would be the entrance to the parking lot for the trucks. Sometimes there may be adjoining streets near the McDonalds, or Hardees, or a restaurant truck stop, and it's best to identify the street with the clear shot to the parking.

--
Amazing GPS: I once was lost but now am found.

Agreed

phranc wrote:

For me, The Truck entrance on the principal approach road. Reasoning being, the GPS will bring you off on the correct approach road but finding the Truck Entrance is tricky sometimes.

Yes, this is good as well. If it's too confusing to figure out which is the entrance and which is the exit from the truck stop, for trucks (many truck stops these days are "travel centers" and have car entrances/exits as well), the principle road approach will always be a good alternative.

--
Amazing GPS: I once was lost but now am found.
Page 1>>