On Sun, Oct 9, 2011 at 9:12 AM, kimaidou wrote:
> Hi list,
>
> I am trying to set up and osmosis database (apidb schema). Installation and
> data importation are done. I would like to know what exactly does the column
> "visible" represent in the nodes and ways tables ? I thought "visible =
> Fals
Hi,
On 10/09/2011 04:47 PM, Kai Krueger wrote:
Theoretically, you should be able to import the whole
planet on e.g. a 512Mb Ram machine in slim mode. It would just take a very
long time! (Unless you have a super fast disk). So it should fix the memory
problem "for ever".
I have a hunch that sl
Nick Whitelegg-2 wrote:
>
> Related to the ongoing discussion on talk, and given the large memory
> requirements of osm2pgsql imports, has anyone published a "tiled" import
> script, where the import area is broken into say degree tiles, and each
> tile imported as a separate osm2pgsql job? If no
Hi list,
I am trying to set up and osmosis database (apidb schema). Installation and
data importation are done. I would like to know what exactly does the column
"visible" represent in the nodes and ways tables ? I thought "visible =
False" meant "the node/way has been deleted, but I checked, and
Related to the ongoing discussion on talk, and given the large memory
requirements of osm2pgsql imports, has anyone published a "tiled" import
script, where the import area is broken into say degree tiles, and each tile
imported as a separate osm2pgsql job? If not, I'm inclined to do one mys
Hi,
I think I now have a first version of a patch to speed up Osm2pgsql by
parallelizing certain parts of it. Specifically it parallelizes the
stages of "Going over pending ways" / "Going over pending relations".
Previously osm2pgsql would fetch all ways / relations that are marked as
"pending" a
6 matches
Mail list logo
