geoips get plugin describes such plugin well, but we could definitely improve the information exposed to the user. For example, if we were to retrieve a sector plugin (let's say geoips get plugin sectors denver, it would be nice to have additional information about where this sector actually covers. This could be geolocated data such as lats and Lons, or in greater detail, its resolution in degrees, center point, area_extent etc. We should discuss what information we'd like to retrieve for every plugin of each interface, and implement this at a later time. This would make geoips get / describe plugin an extremely useful command.
Background and Motivation
This stems from a conversation held about #444.
Code to demonstrate issue
GeoipsGetPlugin found in geoips_get.py.
Checklist for Completion
[ ] Talk about what we would like exposed for every plugin of each interface
[ ] Implement this in GeoipsGetPlugin. This will likely be a large refactor / enhancement.
Requested Update
Description
geoips get plugindescribes such plugin well, but we could definitely improve the information exposed to the user. For example, if we were to retrieve a sector plugin (let's saygeoips get plugin sectors denver, it would be nice to have additional information about where this sector actually covers. This could be geolocated data such as lats and Lons, or in greater detail, its resolution in degrees, center point, area_extent etc. We should discuss what information we'd like to retrieve for every plugin of each interface, and implement this at a later time. This would makegeoips get / describe pluginan extremely useful command.Background and Motivation
This stems from a conversation held about #444.
Code to demonstrate issue
GeoipsGetPluginfound ingeoips_get.py.Checklist for Completion
GeoipsGetPlugin. This will likely be a large refactor / enhancement.