Peuchele bio photo


Pedí pollo que yo pago la diferencia!


POIMan for Sygic is an Android application that lets you keep your Sygic’s Point of Interests (POIs) up to date and manage them (add / remove) in an easy way.

This application will download the POI’s list from a definable URL (by default and let the user select and download the available POIs from that list. Since the POIs are in TomTom format (*.ov2), POIMan will convert them to the Sygic format (*.upi). Also the BMPs are downloaded and resized to a suitable size that Sygic displays properly.

Download Source Code

POIMan for Sygic on GitHub


Screenshot #1 Screenshot #2
Screenshot #3 Screenshot #4

About the UPI format (Sygic POIs)

It was pretty difficult to find information on the Internet about Sygic’s Mobile Maps (SMM) POIs file format (*.upi). Different from the TomTom OV2 format which is well documented and easy to find (see and

One of the goals of POIMan for Sygic was converting the OV2 to UPI, in order to get the most popular POIs to work in SMM. So, the only way to do it without documentation was comparing an OV2 binary to its already converted UPI (converted using another existing tool — most people uses PoiEdit and try to discover what the differences are.

Differences between OV2 and UPI

  • All the strings in the UPI files seems to be stored as inverted wide chars. By inverted I mean that each character occupies 16 bits, but the byte order is swapped (I guess is like a little-endian wide char string). And all the strings are null-terminated (two null bytes).
  • There is a header in the UPI file. Contrarily to OV2 that starts directly with records, the UPI has a header and the format is the following:
    • First byte is the length of the POI file name (without extension) that will follow this byte including the null character (remember: everything multiplied by 2 since it is wide char)
    • A string with the name of the POI file without extension
    • Something that seems to be a filler record, composed by one byte 0x02 followed by 9 null bytes (0x00)
    • A byte with the length of the BMP file name that will follow this byte (including null character)
    • A string with the BMP file name including the extension
  • The simple POI record in OV2 is the type 0x02 while in the UPI format is type 0x03
  • The skipper record (type 0x01 in both formats) seem pretty much the same in both files, they are ‘rectangles’ composed by four coordinates (lat1, lon1) (lat2, lon2). However in the OV2 you can find skipper records following other skipper records, like if you subdivide the rectangles into smaller groups where the POIs that will follow belongs, but this does not works well when you convert them to UPI. So, in other words the POIs should be contained in only one rectangle, so the simples solutions was to use the outer rectangle and skip the rest.

List of tested XML’s

In the preferences page, you can configure the URL that will be used to download the POIs list. The URL usually points to an XML file, which schema is pretty much standard. This XML contains the links to the OV2 files (TomTom POIs), BMPs, map and group to which each POI belongs, etc. However, I’ve found differences regarding the contents of the tags, for example: sometimes the URL to the BMPs are relative to the URL list, sometimes it is the full path; also I’ve found that some pages may require a user name and password to download the OV2 so in the URL you’ll find the %Username% and %Password% variables that POIMan will replace with whatever the user inputs in its preferences page.

In theory, you should be able to use any XML of this page however, due to these differences I’ve found, it might not work correctly, let me know if you find any problem.

Tested XML’s

This is the list of XML’s already tested. If you have more to add please let me know.