You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Having the city, country, region of the origin IP is very useful, but for direct mapping it would be even more useful to have latitude and longitude (lat / lon) added into the data set for immediate mapping instead of having to do a post-transmission lookup again to turn the city/province/nation data back into a lat/lon for mapping use.
This could be located in a mmdb-city-file format, and could even use the same file as the City lookup (but for flexibility, a separate file should be able to be specified - re-using the mmdb-city-file is not a good idea.) It seems wise to make this an optional data set, as it is not always needed and could be added in the same way that the other GeoIP fields are added as optional data to insert in the geoip data block.
Is your feature request related to a problem? Please describe.
Having the city, country, region of the origin IP is very useful, but for direct mapping it would be even more useful to have latitude and longitude (lat / lon) added into the data set for immediate mapping instead of having to do a post-transmission lookup again to turn the city/province/nation data back into a lat/lon for mapping use.
This could be located in a mmdb-city-file format, and could even use the same file as the City lookup (but for flexibility, a separate file should be able to be specified - re-using the mmdb-city-file is not a good idea.) It seems wise to make this an optional data set, as it is not always needed and could be added in the same way that the other GeoIP fields are added as optional data to insert in the geoip data block.
Describe the solution you'd like
Configuration:
Result:
The text was updated successfully, but these errors were encountered: