time measurement about overpass-turbo HOT 7 OPEN

In addition it would be interesting to see how many minutes the Overpass API lags behind. While in the long run overpass-api.de should be back to 1-2 minutes, we currently experience up to 10-30 minutes in delay during peak hours. An unsuspecting user might not be aware of this situation.

Relevant Info: see Overpass API response in attribute osm_base: <meta osm_base="2014-01-02T20:21:02Z"/>

from overpass-turbo.

What about the distance of all returned ways?

from overpass-turbo.

Yeah, additional stats would be nice. I'm thinking about implementing this as a hover state of the current object counter in the bottom right.

from overpass-turbo.

As a first step, I've now added a lag to OSM db info as a tooltip of the current stats display in the bottom right corner (try it on the beta @ http://overpass-turbo.eu/master/). I'll add more stuff if this turns out to be a good solution. btw: @JotPe I fear that in browser-javascript one doesn't get the information about when the actual receiving of data begins, so a query execution time measurement will be out of scope, unfortunately… (except if the Overpass API would provide that information as a HTTP header or something) //cc @drolbr

from overpass-turbo.

@tyrasd thanks for tooltip. Wouldn't be a seperate tab a better solution? I guess in future more meta infos will be printed (way distance!?) Regards Johannes

from overpass-turbo.

I watched the time lag behind osm data increases with time. In the new meta tab it's necessary to display timestamp of query, timestamp of finish, static osm data lag and your actual behind osm data lag.

from overpass-turbo.

Yes, the tooltip is probably only a intermediate solution. (I didn't want to "waste" a tab for only one or two additional stats as in the current state. Once we have more to show, a tab is probably the best solution.)

from overpass-turbo.