[atlas] Regularly Publish Metadata, Was: feature requests

Hey,

good to see the recent flurry of feature requests. I take it as an indication of active usage. Having become somewhat of a power user myself recently I have a request too. Let me suggest a little more structured way to make these requests. This would help everyone, including the developers, to understand them better. Also a snazzy title will make it easier to identify requests in the road map.

Here is my first one:

Title: Regularly Publish Metadata

Description: 

Regularly publish a snapshot of all metadata, such as
https://atlas.ripe.net/contrib/active_probes.json
and
https://atlas.ripe.net/atlas/publicprobesgrid.json?start=XX&limit=XX&sort=XX&dir=XX

A period of once every 24 hours would be sufficient.


Use:

When analysing past measurements it is often required to refer to the state of RIPE Atlas at the time of the measurement. Referring to the current state will be less and less useful as the data analysed is more and more in the past. Changes in the meta data will make the results confusing at best and misleading at worst.


Assumed complexity:

Low, just dump it once a day and make it available in a structured way thru the API.

Assumed cost:

A little storage, not significant in the great scheme of things.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: </ripe/mail/archives/ripe-atlas/attachments/20131112/0ea6bbc2/attachment.sig>