As one IP can only execute one query at a time, and it takes a while before Overpass decides to start a query (they are queued), it's not possible to have one query per street (it would take very long to load the page). That's why all streets of a village are combined into one request.
If someone is willing to experiment, it might be fixable by enlarging the timeout too (see http://wiki.openstreetmap.org/wiki/Overpass_API/Overpass_QL#timeout ), though it will probably ask a bit of trial-and-error to get a decent timeout. Regards, Sander 2015-11-03 12:55 GMT+01:00 Glenn Plas <gl...@byte-consult.be>: > I forgot to add the reason: > > http://overpass-api.de/command_line.html > > "504 Gateway Timeout is sent if the server has already so much load that > the request cannot be executed. In most cases, it is best to try again > later. Please note that the server decides this based on the timeout and > maxsize parameters of the request, so smaller values for them may also > make the request acceptable." > > If you try it with 1 street (small request) instead of all the streets > of a post code, it actually works for me now. But any street wildcard > request are to big it seems as they are executed in a single request. > > Glenn > > > On 03-11-15 11:50, Glenn Plas wrote: > > Hi Louis, > > > > I assume you are talking about the problem with street analysis, > > Overpass API has been timing out since a few days when using Sander's > > toolset: > > > > Remote Address:46.4.41.83:80 > > Request > > URL: > http://overpass-api.de/api/interpreter?data=%5Bout%3Ajson%5D%3Barea%5B%22boundary%22%3D%22postal_code%22%5D%5B%22postal_code%22%3D%222800%22%5D-%3E.area%3B(node%5B~%22%5Eaddr%3A(official_)%3Fhousenumber%24%22~%22.*%22%5D%5B%22addr%3Astreet%22~%22%5EM.*%24%22%5D%5B%22addr%3Apostcode%22!~%22.%22%5D(area.area)%3Bway%5B~%22%5Eaddr%3A(official_)%3Fhousenumber%24%22~%22.*%22%5D%5B%22addr%3Astreet%22~%22%5EM.*%24%22%5D%5B%22addr%3Apostcode%22!~%22.%22%5D(area.area)%3Brelation%5B~%22%5Eaddr%3A(official_)%3Fhousenumber%24%22~%22.*%22%5D%5B%22addr%3Astreet%22~%22%5EM.*%24%22%5D%5B%22addr%3Apostcode%22!~%22.%22%5D(area.area)%3Bnode%5B~%22%5Eaddr%3A(official_)%3Fhousenumber%24%22~%22.*%22%5D%5B%22addr%3Astreet%22~%22%5EM.*%24%22%5D%5B%22addr%3Apostcode%22%3D%222800%22%5D(area.area)%3Bway%5B~%22%5Eaddr%3A(official_)%3Fhousenumber%24%22~%22.*%22%5D%5B%22addr%3Astreet%22~%22%5EM.*%24%22%5D%5B%22addr%3Apostcode%22%3D%222800%22%5D(area.area)%3Brelation%5B~%22%5Eaddr%3A(official_)%3Fhousenumber% > 2 > 4% > > > 22~%22.*%22%5D%5B%22addr%3Astreet%22~%22%5EM.*%24%22%5D%5B%22addr%3Apostcode%22%3D%222800%22%5D(area.area)%3B)%3Bout%20center%3B > > Request Method:GET > > Status Code:504 Gateway Timeout > > > > It started on sunday evening, still not working. > > > > Glenn > > > > > > > > On 03-11-15 08:24, Louis van Boeckel wrote: > >> wat is er mis met de adressen inport , update niet meer? > >> > >> --- > >> Dit e-mailbericht is gecontroleerd op virussen met Avast > antivirussoftware. > >> https://www.avast.com/antivirus > >> > >> > >> _______________________________________________ > >> Talk-be mailing list > >> Talk-be@openstreetmap.org > >> https://lists.openstreetmap.org/listinfo/talk-be > > > > > _______________________________________________ > Talk-be mailing list > Talk-be@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk-be >
_______________________________________________ Talk-be mailing list Talk-be@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk-be
