On 05.06.2011, at 14:01, Stefan Keller wrote: >> Thanks for the comparison. >> I'm the author of Imposm, so I have some clarifications :) >> >> It is written in Python and _uses_ C/C++ libraries. > > I've added that.
Great. > So this seems to be similar with our osm2gis. > osm2gis supports also diff update but we had problems importing whole > planet. So we concentrated on managing regions which in turn makes > diff update complicated (because diffs are always against whole > planet). > => Did you manage to import whole planet? I use it mostly for country extracts, but it also works with planet imports. The last import of a planet file took 20 hours on a host with 8GB RAM and a SATA RAID 1, it should be much faster on a host with more RAM. >> In short, it does everything to make the fastest rendering possible and this >> is one of the reasons that Imposm is used >> for the annual WMS benchmarking at the FOSS4G in Denver. > > Oh, I thought that will be our osm2gis :-> Sorry if I grabbed that spot :) Dane suggested imposm on one of the last IRC meetings and it was accepted. It is already deployed and there is a first import of Colorado. >> I think it would be a great idea to move your comparison to the OSM wiki, so >> that everyone can extend the list of features. What do you think? > > Good idea - but where? There's already > http://wiki.openstreetmap.org/wiki/Software/Desktop but now it seems > to be a need for "Tools to import OSM data into PostgreSQL for > rendering, servicing and editing use cases". Software/GeoSpatialDatabaseImport? Regards, Oliver -- Oliver Tonnhofer | Omniscale GmbH & Co KG | http://omniscale.de http://mapproxy.org | https://bitbucket.org/olt | @oltonn _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
