It is much easier to implement a raster format than a vector format.There are three main reasons, why there are so much raster formats supported but only a few vector formats: And as it is, like you say, used by only a single application, the motivation reduces even more. Which is not a showstopper (the Garmin maps were reverse-engineered even without source codes available), but it drastically reduces the willingness to implement support for such a format. There is no OBF support (yet) because there is no documentation at all for the format. obf files seem to be largely based on data, so maybe the support for 's own format would be a good alternative, as it's not supported either and I can't open. obf format is only used by OsmAnd (and its forks like OffRoad), which is still like the biggest open source free map navigator app for Android, so some support for this format would be appreciated. Tiles based maps are like converting text into images, very ancient and unpractical format for offline maps use. obf file support and instead image based files/tiles are supported, which require lots of disk space and an internet connection with every zoom level and every missing tile, and are, like, the worst possible format. The vector maps can be freely downloaded: Having basic read-only support for offline vector maps would be nice.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |