Commit r3872: simplify sources which implement osm format readers, mo effect on output expected.
Version mkgmap-r3872 was committed by gerd on Tue, 28 Mar 2017 simplify sources which implement osm format readers, mo effect on output expected. - remove interface LoadableOsmDataSource - remove input format specific (pbf,o5m,xml) implementations of OsmMapDataSource - OsmMapDataSource now implements LoadableMapDataSource and decides which parser is to use These changes allow to remove various sources. A few classes were renamed to remove the format specific parts in the name. Osm5XmlHandler was renamed to OsmXmlHandler (no idea what the 5 meant, I always confuse it with 05m) A side effect of these changes is that the --coastlinefile option now accepts o5m format as input, but maybe the option should be removed as well. I've also allowed to use gzip-ed o5m files (o5m.gz) as it needs no extra code. http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=3872
On 28/03/17 09:13, svn commit wrote:
Osm5XmlHandler was renamed to OsmXmlHandler (no idea what the 5 meant, I always confuse it with 05m)
It represents the version number of the API. When mkgmap was first written, OSM had a different XML format where ways were made up of lists of "segments" which consisted of two points. That was version 0.4, and the classes were named OSMXmlHandler (later OsmXmlHandler) and so on. Version 0.5 of the api was not backward compatible and so for a while mkgmap supported both and the classes implementing the new version where named starting Osm5 The next and current version of the api 0.6 did not have changes that affected us. ..Steve
participants (2)
-
Steve Ratcliffe -
svn commit