[sample data] update web log geo.src field to match country code of geo.coordinates

[nreese]

Fixes #40401

Web logs sample data has inconsistencies between geo.src, geo.dest and geo. coordinates where in most cases geo. coordinates is not contained in either country denoted by geo.src or geo.dest. This inconsistency makes understanding the web logs samples impossible and diminishes the usefulness of web logs dashboard and maps.

When web logs were originally generated, geo.coordinates were assigned based on a random pick in US airport locations. This assignment did not verify that the src or dest country were US.

This PR fixes the problem by assigning geo.src for each row to "US". That way, the source country and the geo.coordinates are always consistent. Below is the script used to update the data set.

'use strict'

const fs = require('fs');
const readline = require('readline');

async function load () {
  let failures = 0;
  const logs = [];
  const readStream = fs.createReadStream('./logs.json');

  const rl = readline.createInterface({
    input: readStream,
    crlfDelay: Infinity
  });

  for await (const line of rl) {
    try {
      const log = JSON.parse(line);
      // {"srcdest":"IN:US","src":"IN","dest":"US","coordinates":{"lat":39.41042861,"lon":-88.8454325}}
      log.geo.src = 'US';
      log.geo.srcdest = 'US:' + log.geo.dest;
      logs.push(log);
    } catch (err) {
      failures ++;
      console.log(`Unable to parse line, error: ${err.message}`);
    }
  }

  const writeStream = fs.createWriteStream('./updated_logs.json');
  logs.forEach(log => {
    writeStream.write(JSON.stringify(log, null, ''));
  });
  writeStream.end();
  
  console.log(`success: ${logs.length}, failures: ${failures}`);
}

load().catch(console.log);

Why not update geo.coordinates for original geo.src country? Well, Maps has a tutorial where geo.coordinates are reverse geo coded with United States Census Bureau Combined Statistical Area (CSA). Changing geo.coordinates would have broken this tutorial. Also, changing geo.coordinates to match original geo.src country would have been harder to code.

There were a few visualizations that used geo.src. Since geo.src is now always "US", these charts had to be updated to provide more meaningful visualizations. For example, the old sanky diagram kind of sucks when geo.src is always the same value

Updated charts:

[elasticmachine]

Pinging @elastic/kibana-gis (Team:Geo)

[timroes]

Tested sample data dashboard and it seems consistant and visualizations making all sense. thanks for taking care of it. LGTM

[nreese]

@elasticmachine merge upstream

[thomasneirynck]

❤️

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: e0a53ce
• Storybooks Preview
• Documentation Changes

Metrics [docs]

✅ unchanged

History

• 💚 Build #150426 succeeded fdf119b
• 💔 Build #150390 failed 98352ab

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream

[kibanamachine]

💚 Backport successful

Status	Branch	Result
✅	7.x

This backport PR will be merged automatically after passing CI.