This object is in archive!
Direct *.osm.pbf vector map support
Declined
Direct *.osm.pbf vector map support, like OsmAnd (http://wiki.openstreetmap.org/wiki/DE....
Direct *.osm.pbf vector map support, like OsmAnd (http://wiki.openstreetmap.org/wiki/DE....
I like this idea 
Are you sure that OsmAnd directly uses osm.pfb? Because IMO you have to use OsmAndMapCreator on PC to load .osm.pfb file and generate the .obf file (+PIS for navigation), which is similar to the way how the map files are generated for the mapsforge library used in Locus.
If so, you can use osmosis + mapsforge writer plugin to create the map file from osm.pfb for Locus and second format should not be necessary. The instructions how to do it could be found at:
http://code.google.com/p/mapsforge/wi...
Simpliest way (may fail if the map is large, then you would need to use the hd mode mentioned in the wiki article)
osmosis --rb file="input.osm.pfb" --mw file="output.map"
Are you sure that OsmAnd directly uses osm.pfb? Because IMO you have to use OsmAndMapCreator on PC to load .osm.pfb file and generate the .obf file (+PIS for navigation), which is similar to the way how the map files are generated for the mapsforge library used in Locus.
If so, you can use osmosis + mapsforge writer plugin to create the map file from osm.pfb for Locus and second format should not be necessary. The instructions how to do it could be found at:
http://code.google.com/p/mapsforge/wi...
Simpliest way (may fail if the map is large, then you would need to use the hd mode mentioned in the wiki article)
osmosis --rb file="input.osm.pfb" --mw file="output.map"
Thanks, I know the way to convert the file to the map-format. But I also found the problem with the pbf format and locus.
http://forum.asamm.cz/viewtopic.php?f...
Thanks, I know the way to convert the file to the map-format. But I also found the problem with the pbf format and locus.
http://forum.asamm.cz/viewtopic.php?f...
Yes, although I think menion meant GPL (not LGPL) license in his post in that thread, this is true, libOSM which would be a good candidate has the GPL license.
Moreover, even if this was not the problem, the osm.pbf file requires more processing when used in tile-based map generators. That is one of the reasons OsmAnd and Mapsforge use a different way to represent data and to exchange the speed of tile generation for the file size and also drop some data.
Yes, although I think menion meant GPL (not LGPL) license in his post in that thread, this is true, libOSM which would be a good candidate has the GPL license.
Moreover, even if this was not the problem, the osm.pbf file requires more processing when used in tile-based map generators. That is one of the reasons OsmAnd and Mapsforge use a different way to represent data and to exchange the speed of tile generation for the file size and also drop some data.
any changes in this topic?
any changes in this topic?
lost in "ideas" ... no changes. This topic is not possible. It had to be implemented on MapsForge side. Anyway as wrote moravecp, pbf files are not optimized on on-device rendering so it will take quite more CPU then not to render map ...
lost in "ideas" ... no changes. This topic is not possible. It had to be implemented on MapsForge side. Anyway as wrote moravecp, pbf files are not optimized on on-device rendering so it will take quite more CPU then not to render map ...
Replies have been locked on this page!