Sure, I know this. But if I create an indes with, for example, a st_within
condition, than osmosis falls already while replicating diffs...
That's why I want to solve the problem in osmosis itself, not in the db.
Yesterday on Russian irc channel we found a solution to add to NodeDao.java
And in works!
and (select count(1) from (select n.geom as geom, count(1) as node_count
from way_nodes wn join nodes n on n.id = wn.node_id where wn.way_id =
w.idgroup by 1) n_group) 1
added to the request below works fine!
I will look at it for a couple of days to make sure it works in all
You can have several nodes on the same position which could also lead to a
broken geometry but will not be caught be looking just at the nodes.
Jochen
On Sat, Apr 09, 2011 at 02:22:58PM +0400, Kirill Bestoujev wrote:
Date: Sat, 9 Apr 2011 14:22:58 +0400
From: Kirill Bestoujev
Anyway, I'm now replicating 18 hours of diffs to the planet (with a
st_within index on it - so any invalid geoms will be cought), for the moment
2 hours replicated fine. I will look at the process (all the logs are saved)
- if everything goes will till Monday we can be sure that the problem is
I do look at them - (select n.geom as geom, count(1).
2011/4/9 Jochen Topf joc...@remote.org
Sorry, that was a bit unclear. You can't just look at the node ids, you
have
to look at the geometries of those nodes, too.
Jochen
On Sat, Apr 09, 2011 at 02:36:36PM +0400, Kirill Bestoujev wrote:
Hey everyone,
I started a full planet import on the 29th, 11 days ago. I'm trying to get an
idea how long this will take. I just want to know if this will take about 20
days or more like 40 days.
Here's my setup:
2 dual core Opterons, cpu is not the bottleneck
8 GM ram, htop reports this
