How to Properly Use the Map Report
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2019 08:15 AM
Hi Everyone,
I'm having some trouble with a map report I created and am looking for assistance. I want to look at the total of open tickets per US State and thought a map report might be a better representation than a table. My company is currently on the London platform.
I am using the Incident table and have the condition "State not one of resolved, closed." I have created a new map source called "Incidents Open by State" and map to the affected user location fields, using the OOTB source "Incident open by location" as a blueprint. The report runs, but the output is not what I would have expected, even with the style options I have selected. Here is what I see by default when I run the report:
If I zoom in and pan the report to come into view I am left with this:
I can keep zooming in, but it will only show me one city. For example:
Finally, this is what I have set under style options:
I would have thought that all of the states would be shaded from white to blue, based on their total volume. I thought by default it would be an image of the US map that fits the screen/window size. In addition, when zooming in I would see more than one city, unless that is a function of a drilldown I would need to create?
If anyone could help me have a better understanding of how these map reports work I'd really appreciate it.
- Labels:
-
Dashboard
-
Performance Analytics
-
Reporting
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-26-2019 09:34 AM
It looks like the map isn't configured correctly for what you want to see. Do you have the map "Incident opened by location"? See if that gets you closer.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-29-2019 01:46 PM
Hi Adam,
I tried that, but it suffers from the same issues in terms of incorrect representation.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-31-2019 01:16 PM
That's an interesting issue.
Have you validated the latitude and longitude errors as mentioned in the warning on the top of your screenshot? This may be a data quality issue.
Also, how are you defining the affected users locations? There is an existing map source called "Incidents by caller location", which I'm guessing you already tried but doesn't suit your needs.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-08-2019 07:56 AM