-
Notifications
You must be signed in to change notification settings - Fork 2
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
Data Freeze to 2023-10-07 #32
Comments
Thank you for notifying us. The data of the ohsome dashboard (both OSM History Stats and OSM Quality Analyses) should normally be only up to 2 weeks old. If you open up https://dashboard.ohsome.org/#backend=ohsomeApi you should see the End date set to What query do you run? If you run a period query, you will always get periods starting from the start date. So if you have yearly periods, starting at More information can be found in the documentation of the underlying ohsome API: https://docs.ohsome.org/ohsome-api/stable/time.html |
I run a query using your link and the requested data (count) was between 2007-10-07 (default) up to 2024-01-18 (today) however the result is depicted up to 2023-12-07. The results are shown in k (thousands) 21.7k and the csv file show data up to 2023-12-08 with the amount of 21677 (count). |
Basically yes. Essentially, the timestamps for the results are always calculated from the start date, where the period is added until the end date is reached. If you clear the start field, the last used value (or the default start date if no date was manually set previously) will be used. Here's what I would recommend to do if you want the most up to date data available:
|
I am a former OSM-Analytics user, and due that they are shooting down their service, all data indicate to use ohsome suite. However it looks like the working data available is up to 2023-10-07, basically just 2 o 3 months more updated that the last one published by OSM-Analytics.
Could you please Update the working data? more than 3 months old is useless the data...
Thanks
The text was updated successfully, but these errors were encountered: