HomeALK


How to add Custom POIs to CoPilot Live Android
malaki86
I just thought of this today - try converting the bmp files to png files. I *think* that's what CoPilot uses.
DieselBoss
26 X 26 PNG files. If you dump them in the "NA/Save" folder along with a csv file, it will pick them up for importation upon the next reboot like it does with the POI files.
Ken in Regina
I used bmp and it worked. Can't recall the size.

...ken...
Drifter66
I haven't used 26x26 but copilot's instructions say 16bit as well. They comment that they think that with the Nexus 7 on Kitkat it may be a screen resolution problem. I get the icon on the list of available ones, so I can select it, but it won't attach to the POI set and so no icon appears on the POI set list or , of course, on screen.

Drifter66
PHEV
I'm struggling with the import on CoPilot v9.5. Copilot recognizes the new POIs at startup, and I make a new category and find the icon. However, I can't find any of the POIs after import. They don't show up on the map, and I can't find any of them if try to navigate to a POI. Also, the files found under the map/save are empty (three files of a few hundred bytes).

The two first lines of the csv file lookes like this:

Longitude, Latitude, Name
9.84448, 63.299277, Ladestasjon Raadhuset Orkdal
(Positive values for longitude for the Eastern Hemisphere?)

and I've tried with " enclosing the name and both with and without space after the commas. Textpad says the file uses ANSI character set.

Can anyone see something wrong? I'm using CoPilot v9.5 on a HTC android phone. I don't know if there's a difference between CoPilot Live and v9.5 and if there's something to be aware of similar to the regional settings in Windows (The phone uses Norwegian settings and some number formats are different in windows regional settings).
malaki86
Check for ANY extra commas in each line. Having one too many commas will crash the import.
PHEV
Quote:
Originally Posted by malaki86
Check for ANY extra commas in each line. Having one too many commas will crash the import.
I've seen the import crashing (just freezing CoPilot) but here the import reports to be fine, but I can't find any trace of the POI after import. The new category that I made just isn't listed. Even with a csv-file with only the two lines shown above leaves no trace of POIs in the new category.
GoneNomad
Quote:
Originally Posted by Ken in Regina
@Ken in Regina...
You can also use a TomTom .OV2 file without any modification. Just put it into the "save" folder and start CoPilot. The rest of the process is the same.
I guess the .OV2 file doesn't have the problems with commas in the text of a single field, like .CSV files do?


Quote:
Originally Posted by Ken in Regina
@Ken in Regina...
Copy the CSV file to the folder "...\com.alk.copilot.mapviewer\save" on your tablet or phone...
OK, so the .csv (and its .png icon file, if any) must be placed into the "...\save" folder, but...

Quote:
Originally Posted by Ken in Regina
@Ken in Regina...
here's the most important part that hasn't been included until now. If you want to remove a custom POI set that you didn't get quite right... they are stored in "...\com.alk.copilot.mapviewer\NA\save\user_places".

In that folder you will see a folder(s) with the name(s) of the custom POI set(s) you have added. Just delete the folder of the POI set you want to remove.
...after CoPilot starts up and recognizes those new .csv & .png files, it creates a new "user_places" folder?

FWIW, CoPilot now has a thread on their support forum explaining how to do this:

How do I import custom POIs on Android?
You will need to download Custom POIís from a POI Customer submitted database such as www.pocketgpsworld.com or www.poihandler.com in .OV2 format or .CSV format.

If adding custom POI icons, they need to be .PNG format, 22x22 pixels, 16 bit and they need to be the named the same as the corresponding .OV2 and .CSV file.

Please note if you are downloading Custom POIís in .CSV format, the following guidelines must be followed:
Every column must start with a heading from the following list.
- Lat or Latitude
- Long or Longitude
- Name

They also have instructions for iOS.
But no mention of being able to do it on Windows.

Also no mention of other headings being allowed now.
Ken in Regina
Quote:
Originally Posted by GoneNomad

...after CoPilot starts up and recognizes those new .csv & .png files, it creates a new "user_places" folder?
No, it creates a folder with the same name as your POI file was named INSIDE the "/user_places" folder.

...ken...
GoneNomad
Well, yes, that's what I meant, but here's the reason I ask:

If the first time you put a POI file in CoPilot, they need to be put here:
"...\com.alk.copilot.mapviewer\save"
Then CoPilot starts up, creates a new "user_places" folder inside that \save" folder, right?
And inside of that that \save" folder, it creates another folder with the same name as your POI file.

I was thinking that after that you'd put a POI file in the "user_places" folder. I guess not, because...

...according to their help file:
"...go to the relevant SAVE folder. Please select the folder starting with com.alk.copilot, and then select: ...NA/save"


My assumption is that it still works about the same as it did on the older version that existed when you tested it.
I got my old CoPilot (the $10 "full" version that allows this) license transferred to my new tablet now, so I will test it.
Ken in Regina
Yes, if the "user_places" doesn't exist it gets created. But you still/always put new POI files in the "save" folder.

...ken...
GoneNomad
Adding custom POIs & icons works fine in the latest Android CoPilot version as of today (9.6.4.144).

As mentioned in the OP, you need to find the "save" folder
But there are two "com.alk.copilot.mapviewer" directories.
Most android apps are in the "Android" directory, but not CoPilot.




On my Android 5 LG tablet, the "save" folder is here:

It may be different on other devices of OS, but I'd guess ALK is as consistent as possible.

Putting a properly formatted .csv and an .png file in this folder causes CoPilot to start a very straightforward POI import process the next time it launches.


BTW, CoPilot extracts the data from the .csv and .png and creates the files shown above, then deletes the .csv but not the .png icon file. It remains in the "save" directory, but is no longer needed; the data and icons are embedded (probably in that large "POI.gnx" file in the folder that CoPilot creates). Even if the .png is deleted after completing the POI import process, the icons still show up in CoPilot




I posted the full screen captures of this process here:

http://imgur.com/a/ayLY3

BTW, in another thread, I was highly critical of this process being a kludge.
While I still think that's true, it's also not that bad either.

The only drawbacks are that you can't chose the import file location(s) from within CoPilot, and you have to do one POI at a time, restarting CoPilot after adding new files.

One last issue I had: even though I sized the .png image @ 22x22, the icons displayed on the map have the logo cropped to about 1/4 original size. It's OK in the POI detail flag though:


It might be that it wasn't a 16-bit image, but I will have to check that later.

Looking at the selection of built-in icons, I'm guessing that imported icon images have to be 16-bit index color rather than rgb. Some sources say that .png doesn't support rgb, and if that's true, that might be what's causing the cropped icons on the map.


Attached Images
11-04-screenshot-1a.png   11-04-screenshot-2a.png   11-04-screenshot-3a.png   11-04-screenshot-4a.jpg   11-04-screenshot-5a.png  

Ken in Regina
The info I had at the time of the original post was the color depth had to be 8 bits per pixel (bpp) and it's in the original post. 22x22 bits @ 8bpp works for me. As I recall, Paint makes it fairly easy.

...ken...
GoneNomad
from ALK support thread:
"If adding custom POI icons, they need to be .PNG format, 22x22 pixels, 16 bit..."


I don't see any way to specify the bit depth of a .png file in the Win7 version of MS Paint.
I have Photoshop on another computer though.


Full-color (rgb) icons may not work correctly. All of CoPilot's built-in POI icons are colorized gray-scale, which usually is index color. It wouldn't surprise me if they left out that detail. Originally this custom POI scheme wasn't even officially supported.
Ken in Regina
I'm pretty sure you can set the color depth in Paint in a BMP file. I use an image program called IrfanView and it lets me save anything as anything else. So I just load the BMP and save it as PNG (or whatever).

...ken...
© laptopgpsworld.com About