Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Replication with custom data not possible? #3543

Closed
weskamm opened this issue Sep 24, 2024 · 2 comments
Closed

Replication with custom data not possible? #3543

weskamm opened this issue Sep 24, 2024 · 2 comments

Comments

@weskamm
Copy link

weskamm commented Sep 24, 2024

Describe the bug
I want to setup my own replication server with custom data.
When trying to run nominatim replication --init the code tries to determine the state of the database by calling the openstreetmap API with the highest node id found in the database. This does not work when using custom data (which has node ids that are not contained in the OSM data itself). The code bails out at

node_url = f'https://www.openstreetmap.org/api/0.6/node/{osmid}/1'

with error "Failed to load URL: https://www.openstreetmap.org/api/0.6/node/1000000000017/1"

Are there any options to circumvent this behaviour / supplying a timestamp by ourselves?

To Reproduce
Insert in entry in the db with an osm-id that does not exist

Software Environment (please complete the following information):

  • Nominatim version: 4.2, but seems to be the same on current master
  • Postgresql version: 14
  • Postgis version:
  • OS:

Hardware Configuration (please complete the following information):

  • RAM:
  • number of CPUs:
  • type and size of disks:

Postgresql Configuration:

Nominatim Configuration:

Additional context

@lonvia
Copy link
Member

lonvia commented Sep 27, 2024

There is currently no way to supply an external timestamp. I can see how this could be useful.

If you have a recent version of Nominatim (4.4+) then Nominatim will try to take the date from the osm2pgsql_properties table first. You can set the date there manually to the date you need if no proper date was set when importing the original file. You need to set the current_timestamp property.

@weskamm
Copy link
Author

weskamm commented Oct 8, 2024

Ok thanks, this is a valuable option!

@weskamm weskamm closed this as completed Oct 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants