I decided to try your app, so I downloaded from Play on my Note 8 tablet.
The first obstacle I found is the POI management. The navigator is important for me cause I have a CNG car, then I may need to find a methane station near my road.
I'm partecipating in a community (www.metanoauto.com) where the POIs are downloadable, so I retrieved the last version of all Europe gas station in csv format.
Using diggerqt I prepared the file to be used , then I copied it in the data directory in the tablet.
After that, I tried to used them, but the list seems empty Do you have a step to step tutorial, with pictures, on how to prepare a POI list and how to install/use it?
Can you search your own POIs? You do that from the POI screen, but you do not use the normal search, but the imports search. In that screen you simply select the imported POI file, type (part of) the name of the gas station.
And as Tomas mentioned: You need to switch on the POI category
The POI file is not correct indeed. It even makes my Navigator hang if I try to search. It doesn't show POIs on the map either. Which manual did you follow?
I have seen that you need to register at that website, which I don't want to do, but can you share a small part of your POI file which you used to make the mca?
Have you checked the csv-file : Examples : "CZ-TŘEBÍÄŒ HROTOVICKÁ 160 (AREÁL SPOLEÄŒNOSTI TEDOM) >+420568837234 CC 00-24 SOLO CON CNG CARD CENTRUM" "PL-POZNAŃ GÅOGOWSKA 429 >+48618390627 F 00-24 PF 6-14 FS Chiuso CC 00-24 CNG AUTO CARD" "PL-WAÅBRZYCH UL. LUDOWA 1D >+48746663340 F-PF-FS 00-24" should be ( according to metanoauto.com) : TŘEBÍČ HROTOVICKÁ 160 (AREÁL SPOLEČNOSTI TEDOM) POZNAŃ GŁOGOWSKA 429 WAŁBRZYCH UL. LUDOWA 1D
I had similar problems when trying to import a (different) csv-file. I don't know if it is the solution for you, but I could fix it the following way:
1. Special characters in the csv-file caused invalid mca files. I open the csv-file in Excel and saved it as .xls. Then, I used the Excel driver of digger to import the xls-file, which worked fine with special characters.
2. Table cells with descriptions containing more then 255 characters resulted in unusable mca-files. Looking at your csv-file that might be a problem for you. I used a script to restrict all cells to 255 characters.
I can easily create an mca with icons displaying the stations, but searching through the texts still doesn't work. There must be something incorrect in the strings.
Well, I suppose the problem maybe those strange letters you have in eastern languages.
I understand the historical roots, but also French and German decided to stop using ae and that beta sign that sounds like a double ss (even if a lot of people still use them..)
I'm starting from scratch, looking on those nations one by one. But I have to underline that Tyre accepted gracefully the same file..
It contains a converted to ASCII csv (linux -> iconv -f utf-8 -t ASCII -c CNG\ Europe.csv -o CNG-Europe.csv) A downloaded png from the internet, not a gas one but an "environmental friendly" one. Two printscreens in a pdf And the mca of course.
@hvdwolf : ... converting to ASCII is not a good idea, as this will garble the records ! Examples : "DE-MNCHEN (UNTERSENDLING) SCHFTLARNSTRAE 1 ..." "DE-NRNBERG MNCHENER STRAE 281 ..." "CZ-TEB HROTOVICK 160 (AREL SPOLENOSTI TEDOM) ..." "PL-POZNA GOGOWSKA 429 ..." .. should be : DE-MÜNCHEN (UNTERSENDLING) SCHÄFTLARNSTRAßE 1 DE-NÜRNBERG MÜNCHENER STRAßE 281 CZ-TŘEBÍČ HROTOVICKÁ 160 (AREÁL SPOLEČNOSTI TEDOM) PL-POZNAŃ GŁOGOWSKA 429
I know that converting to ASCII is a bad option, but if the only other option is to remove the records as DiggerQT can't handle them, then it is better to have a garbled, partially readable record then no record at all. What's more: Even with a garbled record you can at least see where the icon is on the map with the coordinates. This means that you can navigate to it. If you have to remove the record you have nothing at all. I have been thinking to do a sed search&replace for the characters like Č to C, but that's up to others and you still don't have the correct address.
Anyone else can modify the strings by hand just as long until the characters are excepted by the diggerQT engine.
(btw) I tested files downloaded from poiplaza, and *.GPX has one POI more than *.CSV, so if You have the possibility, download POI as GPX (Garmin gpx).
p.s. my colleague confirmed that the problem was with encoding of the original GPX file was (first line) <?xml version="1.0" encoding="ISO-8859-1"?> and only supported (by Digger) encoding is UTF8: <?xml version="1.0" encoding="utf-8"?> http://download.mapfactor.com/CNG_Europe_exp150201_6adca055e4.mca