Could someone please tell me the average time it takes to convert their files (type and # of waypoints) to GPI files? I have been starting to create GPX files to load into POI LOADER 2.5.2 and my times seem long in comparison to some comments on other posts.
I have run a trial on two machines using a file from this site (http://www.poi-factory.com/node/14577). Times for this file were approximate 8 minutes. Reading how many POIs people store and the single POI method, it could take hours to regen a complete library of data
Thanks for your help in understanding this process.
I am not sure what you mean, but I load 600,000+ POI's in my Zumo using the POI loader in about 2 minutes or less. How many are you trying to load?
I open up POI Loader and select the custom option to write the gpi to my PC. I select a folder where the test file is stored and click next to process. The test file has just shy of 13k POI entries and it takes 8-9 minutes to covert the gpx file to the poi.gpi file.
I am on a fast pc with plenty of ram and at my rate of creation, your 600,000 records would take 6 hrs to create the poi.gpi to place on my nuvi.
Can you explain in a little more detail what you mean by, "create the poi.gpi to place on my nuvi."
When I use POI Loader to load POI files directly onto my nuvi, it takes only a few minutes. The way you describe it, it sounds like you are following different steps.
I've never run POI Loader the way you described - that is, to select Custom Folder (on the PC) as the Save Option to create the gpi file, so I tried it with the same 2.38MB gpx file you used. Surprisingly, I got the same result - about 8 minutes and that gpx file was the only file in the folder.
I watched WinXP Task Manager and the POI Loader program showed 50% CPU utilization the whole 8 minutes. When it finished, POI Loader displayed 12,853 entries were created. I'm going to load the same file again, but this time loading directly to my nuvi 660 to see if there is any difference.
1) Find a GPX or CSV file to load
2) Place it into a directory on my PC
3) Open up POI LOADER
4) I am prompted with three options (create file on my nuvi, create mappoint (advanced), or custom)
5) I am selecting custom to simulate the creation of file that would be placed directly on the nuvi under the POI directory and to see the size of the output file
6) I select the folder to save the file
7) I select the directory that has the GPX file and run manual mode but do not make any changes to the speed or proximity settings
8) i click next and POI starts its process
9) 8-9 min later it writes POI.GPI to my PC for 13K POI records in the GPX.
I understand that the process is usally to write the file directy to the nuvi, but the custom option would the process to write the file to the SD card.
I hope this process is clear enough and explains what i am running up against. It does not seem right to take so long to create the GPI. I also hope that you dont feel i am being anal. I thought i was being clear in my description, but i guess its not translating well over the forum
OK, I ran the second test, creating the gpi file directly on my 660 and got virtually the same result - 8 minutes, 12,853 POI entries.
Time to try a different gpx file. I'm going to search around the site and find another one to try and compare the times. I'll post back with the results.
I just ran 2 tests with my C330. All .csv format !
I loaded 13,912 POIs in 23 files in Express Mode with POI Loader in about 12 seconds.
In manual mode I loaded 12,787 POIs in 21 files with POI loader in about 4 minutes. that's with setting the proximity alert distances for all !
Am I not understanding the problem ???????????????
I found this 1.61MB gpx file and tested it.
This one took nearly 4 minutes and created 18,088 POI entries.
It appears that your results may not be out of line for the size of the given gpx file you are loading. If you scan the other files available here at the Factory, both csv and gpx formats, not too many are over 1MB in size. But obviously, the 2.38MB NRHP file in your example, is one of the larger files and does take that long to load. At least it did on your and my PCs. So, size matters.
My first question is "Why is this file in GPX format when it's only 3 fields and appears there's nothing in it that requires the GPX format (like phone dialing)? Converting it to CSV reduces the file size by about a fouth and reduces the load time to the computer to less than 5 seconds.
With that said, this is what I do when I send out a POI that can't be posted here because of personal information. See # 8 at http://www.poi-factory.com/node/16639) They simply save the *.pgi file to their GPS. This method has all of the advantages of the 'renaming' method of loading POIs.
The down side of this procedure is it isn't compatible with everyones GPS unit ... the GPS has to be seen as a drive on their computer.
RT - Great question for anyone who has authored or is thinking of authoring a POI file when considering what format to use. No point in creating a bloated file that serves no real purpose.
The slow file creation IS caused by the gpx file. I tried to create a gpi using the gpx file and my computer also took over five minutes. I then converted the same gpx file to csv format using GeePeeEx Editor. Then it only took four or five seconds to create the gpi file!!
Ok, I just want to say, "Duh!?". : )
Stop to think about it for a second. The GPX files contain TONS more fields and thus more for POI Loader to go through when the files are being loaded.
First, it's important that trmcmanus gets his question answered. Miss POI, I think if a gpi file is not 'Garmin Controlled', I agree with trmcmanus that we should have a place to upload *.gpi files. In addition to the speed and convenience of 'copying' them to the GPS, there is the huge advantage of the file already containing alerts and mp3. Think of the work and questions this would save. And it won't overwrite the other POIs. Downside ... the GPS has to be seen as a drive on their computer.
Secondly, in this case, the file does not "contain TONS more fields". It has only 3 fields (longitude, latitude, and name) that don't appear to contain anything requiring gpx format (like dialable phone numbers). With this file, why in the world would anyone want to use a gpx file that takes 8 minutes to load when the same information can be had with a csv file that takes less than 5 seconds to load. Miss POI, can we include the converted csv file with the original gpx file? If so, I'll send it to you.
At least for all the NRHP regions, there are both GPX and CSV files already available on the respective pages.
That's a good idea RT, but I can see a potential problem. I'll use the rest area combined file as an example. It lists 3 possible icons and 3 possible audio files. That's 9 possible combinations and 9 gpi files.
I can hear it now - if we were to pick just one possible combination, someone else would want a different combination of csv/bmp/mp3 files.
Then there is me who has a 660 with the mp3 player skipping problem who wants his audio alert files as wav files.
I'm not sure its a workable solution, but I am certainly open to other ideas and thoughts.
Couldn't just have the gpi option as some GPS units aren't seen as a drive. They would have to be 'in addition to'. One could download and save on the GPS the gpi file if they wanted that particular one. The gpx and csv options would still be there for the 'discriminating' user.
I am going to speak to Jon about this and we will see if this is a benefit to the site.
Thanks for everyones help on this topic. I will look for CSV files first or convert to CSV prior to loading is there is no reason to use the GPX format.
I think it has also been confimered that the Garmin POI Loader utility is basic as best and does not parse out data efficiently for conversion into the poi.gpi data file. It seems to work best on simple structured input formats like a CSV
Please send the file this way and I will add it as an attachment on the page.
The file in question (http://www.poi-factory.com/node/14577) ... contains 12,379 <wpt> entries - but it also contains the same data collected into a ROUTE.
An undocumented feature of POILoader, is that it also converts <rtpte>'s into POIs. Whether it is the duplication, or some other cause, removing these <rtpte>'s alleviates the problem.
(With the original file I got bored of waiting after 20 mins, and aborted POILoader. With the <rtpte>'s removed, it took 4 mins.)
terms | privacy | contactCopyright © 2006-2020