Downloading ad-hoc Atlas measurements as JSON
Hi All, One of my current frustrations is that when downloading ad-hoc Atlas measurements, the file name is always the same: "RIPE-Atlas-measurement.json". This is unfortunate. It would be great if the web server would by default call this measurement by its ID. Anyone else experiencing this problem? Regards, Jon
Hi, sounds like a good idea, we'll add it to the roadmap! Thanks, Vesna On 17-sep.-15 12:11, Jonathan Brewer wrote:
Hi All,
One of my current frustrations is that when downloading ad-hoc Atlas measurements, the file name is always the same: "RIPE-Atlas-measurement.json". This is unfortunate. It would be great if the web server would by default call this measurement by its ID.
Anyone else experiencing this problem?
Regards,
Jon
On 2015-09-17 12:14, Vesna Manojlovic wrote:
Hi,
sounds like a good idea, we'll add it to the roadmap!
Thanks, Vesna
FYI: this has just been deployed. Cheers, Robert
On 17-sep.-15 12:11, Jonathan Brewer wrote:
Hi All,
One of my current frustrations is that when downloading ad-hoc Atlas measurements, the file name is always the same: "RIPE-Atlas-measurement.json". This is unfortunate. It would be great if the web server would by default call this measurement by its ID.
Anyone else experiencing this problem?
Regards,
Jon
On Wed, Sep 23, 2015 at 2:58 PM, Robert Kisteleki <robert@ripe.net> wrote:
FYI: this has just been deployed.
RIPE-Atlas-measurement-{{ id }}.json. Works for me! :-) -- "If you want to go fast, go alone. If you want to go far, go together."
On 23 Sep 2015, at 14:04, Iñigo Ortiz de Urbina <inigo@infornografia.net> wrote:
On Wed, Sep 23, 2015 at 2:58 PM, Robert Kisteleki <robert@ripe.net> wrote:
FYI: this has just been deployed.
RIPE-Atlas-measurement-{{ id }}.json. Works for me! :-)
a dated option like 20150923 would be nice as well Colin
date & measurement ID make more sense... will you make that change? b On 23-sep.-15 15:05, Colin Johnston wrote:
On 23 Sep 2015, at 14:04, Iñigo Ortiz de Urbina <inigo@infornografia.net> wrote:
On Wed, Sep 23, 2015 at 2:58 PM, Robert Kisteleki <robert@ripe.net> wrote:
FYI: this has just been deployed.
RIPE-Atlas-measurement-{{ id }}.json. Works for me! :-)
a dated option like 20150923 would be nice as well
Colin
On 2015-09-23 15:05, Colin Johnston wrote:
On 23 Sep 2015, at 14:04, Iñigo Ortiz de Urbina <inigo@infornografia.net> wrote:
On Wed, Sep 23, 2015 at 2:58 PM, Robert Kisteleki <robert@ripe.net> wrote:
FYI: this has just been deployed.
RIPE-Atlas-measurement-{{ id }}.json. Works for me! :-)
a dated option like 20150923 would be nice as well
Colin
Colin, can you explain what is your use case here? Such naming only really affects downloads via the web page / browser; when using the API one can easily choose a suitable download filename. We could add the end time as well, not just the start time, and we can choose unix timestamps vs. ISO times. All this is pretty simple, but I'd really like to avoid religious wars about how exactly to do this :) Regards, Robert
participants (5)
-
Colin Johnston -
Iñigo Ortiz de Urbina -
Jonathan Brewer -
Robert Kisteleki -
Vesna Manojlovic