first yes, osm files may contain multiple versions. The latest version will completely override any earlier version. Data may not be combined in any way. Normally later versions are also later in the file. Not sure if this is really defined as a hard rule or just a convention because later versions come in later in time But it doesn't really make too much sense feeding a history osm file into splitter. the purpose of splitter isn't for general use and as far as I remember strips timestamps and version information. So this will clearly make it useless for any history data. On Nov 29, 2011, at 12:41 AM, GerdP wrote:

Hello list,

without intent, my patch_v7 for splitter added a restriction about the structure of OSM files (pbf or xml). I am not sure if this can cause problems: Is it possible that a valid OSM data file contains information for a given node-id or way-id "spread" over different places? Maybe with changesets? Splitter in trunk (r191) is able to handle this, but patched version r192 is probably not. For example: Can a file contain the definition of a way and its referred nodes, and later add some more nodes to this way? If yes: Would the SplitProcessor method "see" that this happened or would the parser combine the information first? I can test it myself, I just need a link to such data if it exists.

Ciao, Gerd

-- View this message in context: http://gis.638310.n2.nabble.com/Structure-of-OSM-data-tp7042085p7042085.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev