search

wiktorn / Overpass-API

Overpass API docker image
MIT License
134 stars 48 forks source link

Installation went well but no data #32

Closed matthieugouel closed 4 years ago

matthieugouel commented 4 years ago

Hi, I created an instance using this command : 

docker run \
  -e OVERPASS_META=yes \
  -e OVERPASS_MODE=clone \
  -e OVERPASS_DIFF_URL=https://planet.openstreetmap.org/replication/minute/ \
  -v /big/docker/overpass_clone_db/:/db \
  -p 12346:80 \
  -i -t \
  --name overpass_world \
  wiktorn/overpass-api

Everything went well and I was asked to launch the container with docker start. 

 database ready.
Overpass ready, you can start your container with docker start

I did it and tried to do a request using a Python, that is normally working on the regular overpass API. 

response = overpy.Overpass(url="http://localhost:8082/api/interpreter").query(
    """
[out:json][timeout:900];
area["name"="Boston"]->.boundaryarea;
(
 node(area.boundaryarea)["amenity"="university"];
 way(area.boundaryarea)["amenity"="university"];>;
 relation(area.boundaryarea)["amenity"="university"];>>;
);
out meta;
"""
)

Unfortunately, I get no response. I don't have any error but it's like the database is empty although there is 169G inside the directory containing the database.

When I check the logs of the container, I see my requests, along with the minutely updates and other stuff. Here is an extract : 

Reading XML file ... finished reading ways. After 0h19m46s: in "recurse", part 0, on line 26. Stack: 0 of 0 101297 of 0 0 of 0
After 0h20m1s: in "recurse", part 0, on line 26. Stack: 0 of 0 103524 of 0 0 of 0
After 0h20m16s: in "recurse", part 0, on line 26. Stack: 0 of 0 105693 of 0 0 of 0
After 0h20m31s: in "recurse", part 0, on line 26. Stack: 0 of 0 107515 of 0 0 of 0
After 0h20m46s: in "make-area", part 0, on line 29. Stack: 0 of 0 109766 of 0
Flushing to database ...After 0h21m1s: in "recurse", part 0, on line 26. Stack: 0 of 0 110915 of 0 0 of 0
After 0h21m16s: in "make-area", part 0, on line 29. Stack: 0 of 0 112117 of 0
After 0h21m31s: in "recurse", part 0, on line 26. Stack: 0 of 0 112888 of 0 0 of 0
.132.227.123.9 - - [29/Jan/2020:17:16:08 +0000] "POST /api/interpreter HTTP/1.1" 200 298 "-" "Python-urllib/3.6"
After 0h21m46s: in "make-area", part 0, on line 29. Stack: 0 of 0 114677 of 0
After 0h22m1s: in "recurse", part 0, on line 27. Stack: 0 of 0 116832 of 0 0 of 0
After 0h22m16s: in "recurse", part 0, on line 27. Stack: 0 of 0 118522 of 0 0 of 0
After 0h22m31s: in "recurse", part 0, on line 27. Stack: 0 of 0 120368 of 0 0 of 0
After 0h22m46s: in "recurse", part 0, on line 26. Stack: 0 of 0 122218 of 0 0 of 0
After 0h23m1s: in "recurse", part 0, on line 26. Stack: 0 of 0 124587 of 0 0 of 0
After 0h23m16s: in "recurse", part 0, on line 26. Stack: 0 of 0 126290 of 0 0 of 0
After 0h23m31s: in "recurse", part 0, on line 26. Stack: 0 of 0 128083 of 0 0 of 0

I'm I missing something ?

Best, Matthieu.

wiktorn commented 4 years ago

I see that your query uses areas:

area["name"="Boston"]->.boundaryarea;

These are not part of OSM dumps, but are created/updated by Overpass itself. The database when is started is not yet filled with areas, this is done in background when instance is up. You can see signs of it in your logs:

After 0h21m16s: in "make-area", part 0, on line 29. Stack: 0 of 0 112117 of 0

Check your database without using areas, or give it some time (depending on how much data you have loaded) to generate areas definitions.

matthieugouel commented 4 years ago

Oh, I see. Thanks a lot !