Hi,

I was wondering if anyone managed to come up with a method of getting a probe selection via the API that is based on city. The web interface allows this, by searching for "place", which is subsequently handled by the Google Maps API (I think), and which then comes back with a number of probes on the map, in that given place. However I need this in the API, which only allows to select probes based on "area, country, prefix, asn".

I suspect we'll never be able to fulfill *all* the various wishes about how probe selection should work when scheduling a measurements ("I want to use blue probes, but not the square ones, and only three per ASN, selected by largest distance from the most sparse population of cats" kind). So we have a decent set of features directly supported by the measurement API, and ...

So if anyone has any ideas on how to achieve this in a dynamic way (so as not to have to manually build and maintain a list of probes), I'd be very interested in hearing about that.

... the next best thing is to use the probe API to make a probe ID selection, and supply that ID list to the measurement API. The probe API is pretty flexible, can do country selection as well as geocenter+radius or geographic bounding box. So I guess it can be of use here. See https://atlas.ripe.net/docs/rest/#probe, also the example section. Hope this helps, Robert

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/08/15 16:17, Paul Vlaar wrote:

Hi all,

I was wondering if anyone managed to come up with a method of getting a probe selection via the API that is based on city. The web interface allows this, by searching for "place", which is subsequently handled by the Google Maps API (I think), and which then comes back with a number of probes on the map, in that given place. However I need this in the API, which only allows to select probes based on "area, country, prefix, asn".

What I'm currently trying to come up with is a way to map, more or less, onto the list of ICANN specified probing locations for their DNS tests. This list is published here:

https://tld-monitor.icann.org/nodes.csv

I've been trying to go by the ASNs that the listed locations have their IP space in, but that frequently gives me a negative result (no probes present). The same for the prefixes themselves, of course. And just going by the enclosing country code is fine for a small place like Luxembourg, but not for a big country like Canada.

So if anyone has any ideas on how to achieve this in a dynamic way (so as not to have to manually build and maintain a list of probes), I'd be very interested in hearing about that.

I do have code to do the selection part of the process, that can automate the selection of probes, if it helps I can put it on Github? e1000$./select_probes.py -h usage: select_probes.py [-h] [-v] [-l LOCSTRING] [-p POINT] [-r RADIUS] [-n NUMBER] [-f FIELDS] [-a MAXPERAS] [-d] optional arguments: -h, --help show this help message and exit -v, --verbosity -l LOCSTRING, --locstring LOCSTRING location string, ie 'Amsterdam,NL' -p POINT, --point POINT location as <lat>,<lon>-string, ie '48.45,9.16' -r RADIUS, --radius RADIUS radius (km) within which to select probes -n NUMBER, --number NUMBER number of probes requested -f FIELDS, --fields FIELDS comma separated list of fields to return (output is tsv) -a MAXPERAS, --maxperas MAXPERAS maximum no. of probes per IPv4 source AS -d, --includedownprobes include probes that are down (default: don't include these) e1000$./select_probes.py -l "Maastricht,NL" -r 20 -f id,asn_v4 14648 9143 11917 9143 16979 61956 438 9143 20036 12392 18396 12392 13308 9143 13656 12392 16243 9143 cheers, Emile

Thank you,

Paul Vlaar

-----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQIcBAEBAgAGBQJVxMS2AAoJEKxthF6wloMOSCQQAMOcb+t+kq0MMrO1HsvtAfRa g6C+Z/O3VA/gOKNhlvsQvmYmHxfa4tFxu2kqP2r43SCe48JGQwKDeOHCF7pCaeL8 lxmw7gXZauX3G9bGPwPCTOJNhAdnDT2u/XhCZLf9KLuhfllHNLFgR0FRmDe6z/Gu yp/4JBfcPNJux/QGmy8ps0JFxCYovY6OeiNtPq04qWitE+cMDqHhK8PiBD53MUl9 cntoK9aNTfiozvtvhtFLpm7vcv1kpWcB/t7L2L03P+vfeceFTbXY0TR7/4lnXVH5 3Rdz6iZqBMCiuoE43+vI38nku8jtS3kiPsAsqYqkJiZQBjh9j7oYfQCu0+EbDVAW G7GeBqvAm2T+1Lko/2rZpqorfmuu72WYT2/s4TwsMYMlsID7tB7EEeSo/Txzhsd8 l6HqEO+S6c+cVW8CaOL7zheUdgezaLK69FFHFrCiIAVZ1CSI8SirhAyQei8HAAh+ yyS4cpx/yPEqIeG0hZL1Z+KhPSmQoxLSnx8TIcUyBCCufWNclYjLGo/rcxxYU7z7 r2vGjT7Arx62o5+53nzLt8wThwZVR0oyysZoC0GzRJxFu/lAGWCyWs3GC3TGjukF BuoibQzH1RFm6mxyz+ypqQTzx+7eTmklcPgLPkesQA26TqXTN33G/n1hQecb74mX FyzWMfw78vEHcGvSXs2Z =EFxL -----END PGP SIGNATURE-----