> On Jun 20, 2017, at 10:54 AM, Craig Gallen (opennms) <cgal...@opennms.org> > wrote: > > I looked at generating a geohash but it isn't just the asset table, its > is also collected latitude and longitude values which need converted and > this would need to be done in the measurements api.
If it can be collected, I would use the SNMP Asset Provisioning Adapter to store the coordinates, there. If you need geoLocation for each resource being measured, we need a richer resource model but until that is done I'm sure we could store in the strings.properties until then we could offer that also from the server side. Just a thought. I really don't have a dog in this fight. It would be interesting that if once the client side has the geoHash, that it could push it back to the server so that it could be used everywhere and not have to be recomputed every hit. :David David Hustace The OpenNMS Group, Inc.
signature.asc
Description: Message signed with OpenPGP
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Please read the OpenNMS Mailing List FAQ: http://www.opennms.org/index.php/Mailing_List_FAQ opennms-devel mailing list To *unsubscribe* or change your subscription options, see the bottom of this page: https://lists.sourceforge.net/lists/listinfo/opennms-devel
