missing info about update frequency and last update of the OSM database used but the service

[severinmenard]

eg http://garmin.openstreetmap.nl/ mentions the date of the OS database used for the exports

For the HOT export, frequency is key to know for people/organizations that would like to use OSM for the baseline data included within a workflow that includes GIS use of the data.
The date of the OSM database should be mentioned when creating or clicking on Start a new run + an info file should be added into the .zip archive to inform anyone reusing the data.

[mataharimhairi]

@severinmenard depending on how we decide to pull the data from OSM, this may be a fixed update time interval which should address the issue as we will be able to add a note on the website letting the user know of the frequency.

[severinmenard]

We have people interested to jump into OSM for whom the frequency will be
key to attract new people in OSM. Two examples :

• (research) groups creating geodata platform and interested to put use OSM
  for all the structures. But they have been very clear regarding the update
  frequency. Once a day is not enough, otherwise they stick with their close
  platform
• geography students. I currently teach a lot of them in Senegal on my free
  time. They follow the classic way to create data into their own shapefiles.
  A big loss of data for OSM. By definition, students need to rush when
  finishing their duty work. No way they can wait for one day to see their
  last edits available.

When it started the HOT Exports had a few minutes gap from the current
state of the OSM database, because it was taking the last diff files. We
really to get back to this.
From a 2012 email with Geofabrik: The updates are run in a continuous loop.
This means that the database is usually 3-4 minutes behind OSM.

On Wed, Jun 17, 2015 at 4:22 AM, mataharimhairi notifications@github.com
wrote:

@severinmenard https://github.com/severinmenard depending on how we
decide to pull the data from OSM, this may be a fixed update time interval
which should address the issue as we will be able to add a note on the
website letting the user know of the frequency.

—
Reply to this email directly or view it on GitHub
#98 (comment).