Resolve location endpoint

[jsdelivr]

Resolve location endpoint

[jimaek]

To clarify all of the above is supposed to get eaten by a single input "location". Its not different parameters, they are all examples the user should be able to pass to a single input and get back a resolved json of correctly formatted location parameters that the /measurement endpoint can process.

So its a conversion of 1 magic input to many typed inputs

[zarianec]

Summary of internal discussion:

1. Build additional probe client metadata object index that will contain all the possible values user can do "magic" queries over.
2. Maintain manual aliases for some locations like United States of America -> USA
3. Simulate partial match using String.contains() filter

New probe client metadata object:

{
    "location": {
        "continent": "EU",
        "region": "western-europe"
        "country": "UK",
        "state": "TX"
        "city": "frankfurt at main"
        "isp": "Amazon.com ISP Provider"
    },
    "index": [ "europe", "united kingdom", "western europe", "texas", "frankfurt at main", "amazon.com isp provider" ],
}

[jimaek]

Manual aliases we should add:

• USA = us
• England = uk
• AWS = amazon.com inc.
• united states = us
• vultr = choopa llc
• other?

[patrykcieszkowski]

• other?

I don' think we discussed that - do we want to include both ISO and full state/country/continent formats?

[patrykcieszkowski]

• GB = united kingdom
• northern ireland = GB

[jimaek]

do we want to include both ISO and full state/country/continent formats

Yes, the user should be able to write "Germany" and it should automatically convert to "DE". I have it as an example input in the task. So all those inputs should work correctly