Hi,
On 10/18/2011 07:06 PM, Igor Podolskiy wrote:
this seems to run OK, but invariably, after leting this run for a few
hours with a 5 minute interval (to catch up, my initial extract is a
couple of months old) the database table only holds a small number (less
than 20) nodes. What is going wron
Hi all,
The server running jxapi.osm.org was running low on disk space and had run
into some other problems. I'm going to clean it up and reimport tomorrow
after the planet is released. I will keep the jxapi software disabled until
that time. I imagine it will not be available until some time this
Hi Martijn,
Thanks for you elaborate explanation. I see the problem with the ways
potentially lacking geometries.
Would the problem be much simpler if I constrain the data set to nodes only?
not in the general case unless you do some kind of processing on the
changes. If someone sets a gnis:id=
Igor,
Thanks for you elaborate explanation. I see the problem with the ways
potentially lacking geometries.
Would the problem be much simpler if I constrain the data set to nodes only?
Why are you using osm2pgsql for the database update step? Is that because
you require that schema or are there ot
Hi Martijn,
this seems to run OK, but invariably, after leting this run for a few
hours with a 5 minute interval (to catch up, my initial extract is a
couple of months old) the database table only holds a small number (less
than 20) nodes. What is going wrong here?
well, sorry to say that, but
Hi all,
I'm trying to keep an thematic planet extract PostGIS database up to date
using osmosis. The cron job I run is:
#!/bin/bash
exec &> /home/mvexel/osm/replicate-gnis/log.txt
if ps -ef | grep -v grep | grep osmosis ; then
exit 0
else
if [ -s /home/mvexel/osm/replicate-gnis/us-gnis-ne
6 matches
Mail list logo