Ford Dealer Locations????

There was some talk here of starting a file. It was decided to wait until after the first of the year because so many were closing.

See
http://www.poi-factory.com/node/17569

Daniel

I've started with the Mid-Atlantic, and I've seen some other regional ones as well. I should be submitting something in the next couple of days that will cover NJ, PA, DE, MD, VA, WV and NC.

Maryland, Delaware and New Jersey are complete. I should have Pennsylvania, West Virginia, Virginia and North Carolina complete soon.

West Virginia and Pennsylvania are now complete.

added new .gpx and .csv files for dealers in GA, SC, NC, VA, MD, DE, NJ, PA and WV.

Good to see Hwyman is working on this. I traded in my Mustang for a Sebring a few weeks ago so I won't be doing anything more on the Az Ford poi that I started working on months ago.

just added Florida and Alabama and also posted a combined file that will be updated as I add states.

Added Arizona and Arkansas.

I'm working alphabetically now so I can make sure I don't overlook anyone.

If you find any errors, please let me know!

Added California to the US file

The states of CO, CT and ID have been added to the master file.

Added IL

Great... thanks for the work.

I drive a Ford and when traveling, it would be nice to always know the nearest dealership if I needed service or warrenty work.

Thanks,

Jeff

Sorry for the delays in updating this project, but witht he holidays and things going on at work, I'm finally able to provide some updates. Today the following states have been added to the US files:

Indiana, Iowa, Kansas, Kentucky and Louisiana

Added Massachusetts

I just downloaded this file (Newest version) and when I try to install it with the newest Garmin POILoader, I keep getting an error in line 165, and it says it will load everything up to there then lose the rest of the info. I tried looking at the info in Notepad and Excel, but I can't see what's wrong, if anything. Anyone else getting this?

Thanks, BTW for the work on this file. Sorry I have to come in with a complaint...

I uploaded a corrected file, see if that one helps.

I still get the error with the April 7 upload, but I still was concerned that the amount of data in the 4th column was too much for my 'old' GPS. So I opened the csv in Excel and just deleted that whole 4th column, and it loaded fine.

So I'm thinking the original csv is fine for any GPS that can handle that much data in the 4th 'info' column, but I'm an amature at this.

The date on the file on the Factory still shows 04-05-2010.

Try the gpx file.I have no problem with it.You may also get a better display on the gps screen without the more button.

I'll give the gpxa try. Didn't think of that. But looking at all the 4th field data(Ph#, address, & operating hours), it looks like way more than will display on my Nuvi260. I'll try it in a few minutes and report back with the results.

Oops, there isn't a gpx. Just the csv and ov2 for Tomtom.

See http://www.poi-factory.com/node/25350

Thx! Giving it a try...

Well, not only did the gpx load without a problem, all that info displays very neat and organized, and there is a 'MORE' button that displays the extra info that doesn't show on the first page, and it's all very neat and orderly.

Don't know how you guys do it (Organize it all so well) with all that information, but thanks a bunch!

Glad it worked out.I prefer to use the gpx files.The main reason not only for the display but you can easily build your alerts in using Extra Poi Editor.This allows you the option of using express mode for poiloader. See http://www.poi-factory.com/node/28521

The gpx file does not claim to have Texas and for the most part doesn't. No file to my knowledge contains a Ford dealer in Rolla Missouri that I, unfortunately, had to use last summer.

I find the dealer poi's in my Nuvi with 2010.1 to be more reliable.

I've been away on business travel and just now am back home. Currently, I am working on the Ford POI files alphabetically by State, currently working on Michigan. I plan to add more states as soon as possible.

All of the dealer locations I'm using in the POI file are verified through Ford's Dealer Connections website, but I'm finding that is not always accurate.

Hwyman,
I figured you were busy. Golfnm8 has sent me over some New Mexico Ford dealerships to add when you are ready.

Miss POI

Just got it, and should have the updates posted either today or tomorrow!

Thanks, golfnm8 for the New Mexico dealers!

I get an error at line 164 when I enter it in a 765T.

POI Loader chokes on line 164. I looked at it, didn't see anything that stands out, ran it through Verifier 1.0 and it didn't complain.

I then opened it in Extra_POI_Editor and then saved it back as a Garmin CSV and that seems to have cured whatever was causing the problem. Note: Since POI Loader stopped at line 163, I couldn't tell if other lines after 164 might have also been problematic.

I converted the csv file to a gpx using Extra Poi Editor and loaded to gps with no problems.

I found the error in the csv file and it has been corrected. I test loaded it on my Nuvi 1250 and it loaded without issue.

Any reason the gpx version doesn't have same locations as the csv?I noticed some states missing like TX,TN and UT missing on the gpx cover sheet.

I have just been converting the csv to gpx as a work around.

Befuddling. There's a similar problem with some other csv files.

What would be the difference between a "Garmin" csv file and one created in Notepad or Excel?

Of note... On one such file, I noted that the line in error had in column-4, a blank "first" line followed by a line break and more info. On a hunch, I replaced the blank lines, there were more in following entries, with some verbage.

Now, here's what totally confuses me... It eliminated the load error message but still stopped loading thereafter... as if there is some kind of hidden "file termination" character.

Perhaps this additional info will help someone figure out what is going on.

Right now, I'm working on the states in alphabetical order. There may be instances where if I'm working on one state (let's say California) and there is a state on the border, like Nevada, I'll include it since it's close. the csv and the gpx should be a mirror file, since I create the csv from the gpx file.

I think that was my issue. The csv file was created with the Extra POI editor. I would save it as a 4-column csv file. saving as a garmin csv seems to have corrected the error.

Okay... I need to Update that comment.

In this instance, the fix worked. It was indeed the blank lines (I just didn't realize it had worked as I had the old poi.gpi file on the garmin and the new one on the SD card.) I've corrected that issue and yes, the entire file (and another) loaded.

So perhaps every csv file that has a load failure should be checked for blank and/or null lines in column 3 and/or 4.

EPE must be fixing the blank line issue that POI Loader chokes on.

But not everyone has it nor should we be required to run EPE for every csv on the site, especially as they are often in flux.

Perhaps we can get file maintainers to value-check their csv files for blank lines going forward.

I will double check mine prior to loading additions in the future.

MI added today.

Golfnm8 provided corrected coordinates for Team Ford in Silver City, NM. I have uploaded corrected files. Thanks, Golfnm8, for the update!