ISO 3166-2 Codes and the GeoLite2 databases about ems-file-service HOT 4 CLOSED

Pull request for adding this functionality to the Ingest Geoip plugin in Elasticsearch.

from ems-file-service.

this is interesting.

some quick thoughts:

• I wouldn't dismiss the join-on-two field approach. It is out of scope for the current visualizations (no new features basically), but we could consider this for the GIS-app if we want to provide a full end-2-end solution. It would be a nice round-trip use-case for many of our users use-cases (server metrics basically)
• The way we currently publish data is by country. Users would really only be able to see details of a single country. The multi-layered nature of the GIS-app would provide a means to work-around this though.

A little bit more exotic, but what would the file-size be of a fully joined (ie. ALL the countires and ALL their subdivisions). The current leaflet-implementation does not do well with large datasets, but a GL-based viewer would (e.g. in the order of 10k shapes should be doable). Could we produce a data layer like this to support the GIS-app (basically, a layer with full ISO 3166-2 support)?

from ems-file-service.

So it appears the GeoIP Ingest plugin actually omits the subdivision ISO code as an option. One can get the region (subdivision) name only. This appears to be the relevant code showing the options.

I don't think it would be too difficult to add the subdivision ISO code since it's available in the GeoIP2-Java API as subdivision.getIsoCode(). But I wonder if there was a deliberate reason for omitting it in the Ingest plugin?

from ems-file-service.

Closed with elastic/elasticsearch#31669

from ems-file-service.