Hi,
[another try, this time to the list]
On Wed, Nov 06, 2013 at 10:10:03AM +0100, Frederik Ramm wrote:
> On 07/13/2013 01:03 PM, Jocelyn Jaubert wrote:
> > I'm currently using a workaround, which is to set maxInterval in
> > configuration.txt to 0.5 day to make sure that osmosis is not trying to
> > merge two diffs. Then I had to add a loop to run osmosis until there are
> > no recent diffs.
>
> I've just been bitten by the same problem when trying to keep an
> Europe-only Nominatim instance up to date with Geofabrik diffs.
>
> I wonder if simply dropping the --simplify-change from Nominatim's
> osmosis invocation will solve things - might lose a little performance
> for things modified on subsequent days but hey. (One could even do this:
> try with --simplify-change by default but if this fails, re-run
> without... Nominatim already re-runs osmosis if it fails so I'd just
> have to add the "drop simplify-change" code.)
That does not work either because osm2pgsql chokes on a osc diff
that was not simplified.
> > Maybe the best way to fix this is to add a note on a website explaining
> > that the diffs generated by Geofabrik are not meant for "direct"
> > consumption by osmosis with a big value on maxInterval ?
>
> I'll do that.
With Nominatim 2.1 and the settings as recommended at the Nominatim
installation website [1], the update process should be doing the
right thing and apply the daily diffs one after another.
Sarah
[1]
http://wiki.openstreetmap.org/wiki/Nominatim/Installation#Setting_up_the_update_process
___
osmosis-dev mailing list
osmosis-dev@openstreetmap.org
https://lists.openstreetmap.org/listinfo/osmosis-dev
