[Benchmarking] Meeting summary - May 11 + OSM import plan

[Dane Springmeyer]

Hi Oliver,

Jeff and I chatted last wednesday about this. The two of us, at least, are fine with the process of importing on Linux, then dumping to move to other databases (that people choose) as well as windows.

Others okay with that plan?

Oliver, thanks again for offering this support with your tool.

Dane


On May 12, 2011, at 2:02 AM, Oliver Tonnhofer wrote:

> 
> On 11.05.2011, at 17:36, Dane Springmeyer wrote:
>> # Key Decisions
>> As a group we decided to use the imposm tool (http://imposm.org/) to import OSM data into PostGIS. This will provide a common source of data for the "vector" test.
>> 
>> Pros of imposm where discussed:
>> [...]
>> Cons were:
>> * None discussed. Hopefully we can use this mailing list to understand any drawbacks - Only potential I can see is that it has a more flexible output schema than osm2pgsql so those of us familiar with osm2pgsql will need to adjust a bit.
> 
> Jeff asked me if imposm supports Windows. I'm not sure if everyone was aware of it, but it only runs on unix systems, because one library is not available on Windows. Imposm can import from the Linux host to a PostGIS on the Windows host, though.
> Don't know if that does change anyone's mind.
> 
> For the DB schema:
> Here is a list of all tables that imposm creates by default:
> http://imposm.org/docs/imposm/latest/database_schema.html
> 
> Here is the configuration of the default mapping:
> https://bitbucket.org/olt/imposm/src/tip/imposm/defaultmapping.py
> You can see which OSM tags are included in which table.
> I'll post a complete PostgreSQL schema in the wiki.
> 
> Regards,
> Oliver
> 
> -- 
> Oliver Tonnhofer    | Omniscale GmbH & Co KG    | http://omniscale.de
> http://mapproxy.org | https://bitbucket.org/olt | @oltonn
> 
> 
> _______________________________________________
> Benchmarking mailing list
> Benchmarking at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/benchmarking