<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 70.85pt 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style>
</head>
<body lang="PL" link="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US">Robert, thank you for checking. I didn't realize how tricky it can be for special territories like Hong Kong. I'll play with 3<sup>rd</sup> party libraries and geolocation services.
Maybe finally I will implement more granular selection of probes per continent/state/city in my tools ;)<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal"><span lang="EN-US">Regards,<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="EN-US">Grzegorz</span><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US" style="mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm">
<p class="MsoNormal"><b><span style="font-size:12.0pt;color:black">From: </span></b><span style="font-size:12.0pt;color:black">Robert Kisteleki <robert@ripe.net><br>
<b>Organisation: </b>RIPE NCC<br>
<b>Date: </b>Thursday 2019-11-28 at 10:54<br>
<b>To: </b>"Ponikierski, Grzegorz" <gponikie@akamai.com>, "ripe-atlas@ripe.net" <ripe-atlas@ripe.net><br>
<b>Subject: </b>Re: [atlas] Unable to set probe location to Hong Kong<o:p></o:p></span></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">On 2019-11-27 14:47, Ponikierski, Grzegorz wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #B5C4DF 4.5pt;padding:0cm 0cm 0cm 4.0pt;margin-left:3.75pt;margin-right:0cm" id="MAC_OUTLOOK_ATTRIBUTION_BLOCKQUOTE">
<div>
<p class="MsoNormal">Hi all!<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">I was wondering why I see more probes in Hong Kong marked as Chinese<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">probes. For test, I tried to set location of my probe to Hong Kong and<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">even if I put location pin on map in the middle of Hong Kong it still<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">ends assigned to China. Are we still able to assign RIPE Atlas probes to<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Hong Kong? If not, then what about probes which are still assigned to<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Hong Kong? How to reliably get via API list of probes located in Hong<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Kong? Should we parse geo coordinates and use 3^rd party libraries to<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">figure out where probe is really located?<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Grzegorz<o:p></o:p></p>
</div>
</blockquote>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Hello,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The answer is purely technical. We're using a set of geocoding services<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">(coordinates -> country code) for this. The setup is such that if we<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">fail to get an answer from the primary provider, we try another one. In<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">this particular case the secondary provided a different answer than the<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">primary would have given.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">We'll see what we can do with probes that have been affected by this<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">issue. In the meantime, as you said, one can always use a 3rd party<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">library, and the probe API helps in various ways to filter probes.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Regards,<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal">Robert<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>