Map location problems after switching to the Pro version
Hello,
We had been running the community version of Observium for a few weeks. I set the syslocation for each device, and when using the Google API each device appeared on the map exactly where it should. I used google instead of mapquest because when using mapquest a number of locations were wrong even though I used the exact address mapquest.com showed when I looked it up.
We recently went Pro, and it's well worth the money. However, the map is no longer useful. We currently have 62 devices we're monitoring, all within a small geographic area in central Indiana around Lafayette. 61 of the 62 devices show up within a single block around our default latitude & longitude.
For example, in the event log I find an entry for mulberry-sw1:
2015-01-14 09:25:00 mulberry-sw1 System Geolocation (GOOGLE) -> [40.420760, -86.890249] United States (Country), Indiana (State), Tippecanoe County (County), Lafayette (City)
This is just wrong. The actual location string for this device (which has been untouched since it worked correctly for the community version) shows that it's in Mulberry, Indiana. That's even in a different county.
Am I doing something wrong? Any help would be greatly appreciated.
Thanks! -- Richard Kuhns rjk@wintek.com Main Number: 765-742-8428 Wintek Corporation Direct: 765-269-8541 427 N 6th Street Internet Support: 765-269-8503 Lafayette, IN 47901-2211 Consulting: 765-269-8504
If you override the sysLocation in Observium and set it to Mulberry, Indiana does that correct it?
On Wed, Jan 14, 2015 at 8:44 AM, Richard Kuhns rjk@wintek.com wrote:
Hello,
We had been running the community version of Observium for a few weeks. I set the syslocation for each device, and when using the Google API each device appeared on the map exactly where it should. I used google instead of mapquest because when using mapquest a number of locations were wrong even though I used the exact address mapquest.com showed when I looked it up.
We recently went Pro, and it's well worth the money. However, the map is no longer useful. We currently have 62 devices we're monitoring, all within a small geographic area in central Indiana around Lafayette. 61 of the 62 devices show up within a single block around our default latitude & longitude.
For example, in the event log I find an entry for mulberry-sw1:
2015-01-14 09:25:00 mulberry-sw1 System Geolocation (GOOGLE) -> [40.420760, -86.890249] United States (Country), Indiana (State), Tippecanoe County (County), Lafayette (City)
This is just wrong. The actual location string for this device (which has been untouched since it worked correctly for the community version) shows that it's in Mulberry, Indiana. That's even in a different county.
Am I doing something wrong? Any help would be greatly appreciated.
Thanks!
Richard Kuhns rjk@wintek.com Main Number: 765-742-8428 Wintek Corporation Direct: 765-269-8541 427 N 6th Street Internet Support: 765-269-8503 Lafayette, IN 47901-2211 Consulting: 765-269-8504 _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Derek wrote:
If you override the sysLocation in Observium and set it to Mulberry, Indiana does that correct it?
No, I've tried that. It doesn't help any :-(
On Wed, Jan 14, 2015 at 8:44 AM, Richard Kuhns <rjk@wintek.com mailto:rjk@wintek.com> wrote:
Hello, We had been running the community version of Observium for a few weeks. I set the syslocation for each device, and when using the Google API each device appeared on the map exactly where it should. I used google instead of mapquest because when using mapquest a number of locations were wrong even though I used the exact address mapquest.com <http://mapquest.com> showed when I looked it up. We recently went Pro, and it's well worth the money. However, the map is no longer useful. We currently have 62 devices we're monitoring, all within a small geographic area in central Indiana around Lafayette. 61 of the 62 devices show up within a single block around our default latitude & longitude. For example, in the event log I find an entry for mulberry-sw1: 2015-01-14 09:25:00 mulberry-sw1 System Geolocation (GOOGLE) -> [40.420760, -86.890249] United States (Country), Indiana (State), Tippecanoe County (County), Lafayette (City) This is just wrong. The actual location string for this device (which has been untouched since it worked correctly for the community version) shows that it's in Mulberry, Indiana. That's even in a different county. Am I doing something wrong? Any help would be greatly appreciated. Thanks! -- Richard Kuhns <rjk@wintek.com <mailto:rjk@wintek.com>> Main Number: 765-742-8428 <tel:765-742-8428> Wintek Corporation Direct: 765-269-8541 <tel:765-269-8541> 427 N 6th Street Internet Support: 765-269-8503 <tel:765-269-8503> Lafayette, IN 47901-2211 Consulting: 765-269-8504 <tel:765-269-8504> _________________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/__cgi-bin/mailman/listinfo/__observium <http://postman.memetic.org/cgi-bin/mailman/listinfo/observium>
On 14.01.2015 17:44, Richard Kuhns wrote:
Hello,
We had been running the community version of Observium for a few weeks. I set the syslocation for each device, and when using the Google API each device appeared on the map exactly where it should. I used google instead of mapquest because when using mapquest a number of locations were wrong even though I used the exact address mapquest.com showed when I looked it up.
We recently went Pro, and it's well worth the money. However, the map is no longer useful. We currently have 62 devices we're monitoring, all within a small geographic area in central Indiana around Lafayette. 61 of the 62 devices show up within a single block around our default latitude & longitude.
For example, in the event log I find an entry for mulberry-sw1:
2015-01-14 09:25:00 mulberry-sw1 System Geolocation (GOOGLE) -> [40.420760, -86.890249] United States (Country), Indiana (State), Tippecanoe County (County), Lafayette (City)
This is just wrong. The actual location string for this device (which has been untouched since it worked correctly for the community version) shows that it's in Mulberry, Indiana. That's even in a different county.
Am I doing something wrong? Any help would be greatly appreciated.
See in device edit tab -> Geolocation -> Last update status
Show screenshot for this page (expand form with last update status)
Thanks!
Richard Kuhns rjk@wintek.com Main Number: 765-742-8428 Wintek Corporation Direct: 765-269-8541 427 N 6th Street Internet Support: 765-269-8503 Lafayette, IN 47901-2211 Consulting: 765-269-8504 _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Mike Stupalov wrote:
On 14.01.2015 17:44, Richard Kuhns wrote:
Hello,
We had been running the community version of Observium for a few weeks. I set the syslocation for each device, and when using the Google API each device appeared on the map exactly where it should. I used google instead of mapquest because when using mapquest a number of locations were wrong even though I used the exact address mapquest.com showed when I looked it up.
We recently went Pro, and it's well worth the money. However, the map is no longer useful. We currently have 62 devices we're monitoring, all within a small geographic area in central Indiana around Lafayette. 61 of the 62 devices show up within a single block around our default latitude & longitude.
For example, in the event log I find an entry for mulberry-sw1:
2015-01-14 09:25:00 mulberry-sw1 System Geolocation (GOOGLE) -> [40.420760, -86.890249] United States (Country), Indiana (State), Tippecanoe County (County), Lafayette (City)
This is just wrong. The actual location string for this device (which has been untouched since it worked correctly for the community version) shows that it's in Mulberry, Indiana. That's even in a different county.
Am I doing something wrong? Any help would be greatly appreciated.
See in device edit tab -> Geolocation -> Last update status
Show screenshot for this page (expand form with last update status)
Attached!
-- Richard Kuhns rjk@wintek.com Main Number: 765-742-8428 Wintek Corporation Direct: 765-269-8541 427 N 6th Street Internet Support: 765-269-8503 Lafayette, IN 47901-2211 Consulting: 765-269-8504
This is a known bug, there were several emails about this a month or so ago. It has its own jira ticket (http://jira.observium.org/browse/OBSERVIUM-1133 ) . Location abbreviations that are manually set are for whatever reason not looked up against the full addresses defined in config.php. We have this issue running the last three stable versions and the current.
rob
-----Original Message----- From: observium [mailto:observium-bounces@observium.org] On Behalf Of Richard Kuhns Sent: 14 January 2015 17:57 To: Observium Network Observation System Subject: Re: [Observium] Map location problems after switching to the Pro version
Mike Stupalov wrote:
On 14.01.2015 17:44, Richard Kuhns wrote:
Hello,
We had been running the community version of Observium for a few weeks. I set the syslocation for each device, and when using the Google API each device appeared on the map exactly where it should. I used google instead of mapquest because when using mapquest a number of locations were wrong even though I used the exact address mapquest.com showed when I looked it up.
We recently went Pro, and it's well worth the money. However, the map is no longer useful. We currently have 62 devices we're monitoring, all within a small geographic area in central Indiana around Lafayette. 61 of the 62 devices show up within a single block around our default latitude & longitude.
For example, in the event log I find an entry for mulberry-sw1:
2015-01-14 09:25:00 mulberry-sw1 System Geolocation (GOOGLE) -> [40.420760, -86.890249] United States (Country), Indiana (State), Tippecanoe County (County), Lafayette (City)
This is just wrong. The actual location string for this device (which has been untouched since it worked correctly for the community version) shows that it's in Mulberry, Indiana. That's even in a different county.
Am I doing something wrong? Any help would be greatly appreciated.
See in device edit tab -> Geolocation -> Last update status
Show screenshot for this page (expand form with last update status)
Attached!
-- Richard Kuhns rjk@wintek.com Main Number: 765-742-8428 Wintek Corporation Direct: 765-269-8541 427 N 6th Street Internet Support: 765-269-8503 Lafayette, IN 47901-2211 Consulting: 765-269-8504
participants (4)
-
Derek -
Mike Stupalov -
Richard Kuhns -
Robert Hatch