On Tuesday, October 10, 2017 at 3:53:39 AM UTC+2, A Thompson wrote: > > Please someone correct me, but from a naive experiment I just did I don't > think the summit:cross=yes tag in the .osm ends up being incorporated in > OsmAnd's .obf database. > ... >
Thanks a lot for your swift reply, this does make sense! I made some additional research meanwhile. Vector maps (as the ones handled by Osmand) would need a database (with spatial extension) to process queries and the OBF files adopted by Osmand should just be a sort of sqlite3 structure storing all features. The tool to import them from OSM is OsmAndMapCreator (or similar), basing on a file named *rendering_types.xml*, as explained here <http://osmand.net/help/docs/Custom_Rendering_How-To.htm> ("Add new Features to the Map" paragraph). Unfortunately the basic frontend Osmand feature that shows the properties of a geographic feature misled me and I thought that the appropriate column was already available. I did not consider to examine the DB itself. Thanks also to notifying me the tools you mentioned. At the end I might assume that, as *summit:cross* is not a column mentioned in the default *rendering_types.xml* file, then it is missing in the DB. This would mean that not only the *rendering_types.xml* file must be edited and a new custom .obf database has to be generated, but also that no map file downloaded from Osmand will be able to show the new feature until, I guess, a merge update is performed here <https://github.com/osmandapp/OsmAnd-resources/blob/master/obf_creation/rendering_types.xml> and all hosted DB files are subsequently refreshed. So I should no more rely on the downloaded maps to show the new feature (at least until the new feature is also managed by the map generator hosted by Osmand). -- You received this message because you are subscribed to the Google Groups "Osmand" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
