Uploaded image for project: 'Metron (Retired)'
  1. Metron (Retired)
  2. METRON-679

Investigate including additional GeoIP fields

Add voteWatch issue
    XMLWordPrintableJSON

Details

    • Improvement
    • Status: To Do
    • Minor
    • Resolution: Unresolved
    • None
    • None
    • None

    Description

      The newer downloadable database we're using provides a wider array of fields than our old solution. We may also want to update some naming (we've been using metro code and calling it dma code, even in the old solution, for example). Data pulled from plaintext download at: http://dev.maxmind.com/geoip/geoip2/geolite2/

      Currently used fields:

      • geoname_id (renaming it LocId).
      • city_name
      • country_iso_code
      • metro_code (but renaming it dma code)
      • postal_code
      • latitude
      • longitude
      • network (indirectly, it's the field used for pulling back data for IP and is included here for completeness)

      Unused fields in block file:

      • geoname_id,
      • registered_country_geoname_id
      • represented_country_geoname_id
      • is_anonymous_proxy
      • is_satellite_provider
      • accuracy_radius

      Unused from location file:

      • geoname_id
      • locale_code
      • continent_code
      • continent_name
      • country_name
      • subdivision_1_iso_code
      • subdivision_1_name
      • subdivision_2_iso_code
      • subdivision_2_name
      • time_zone

      I believe the only field present we didn't use in the old data is area_code, which isn't present in the new data anyway.

      Attachments

        Activity

          People

            Unassigned Unassigned
            justinleet Justin Leet

            Dates

              Created:
              Updated:

              Slack

                Issue deployment