topic Re: GeoAnalytics City Bubble Map Manual Remap and Bad Location in GeoAnalytics

GeoAnalytics City Bubble Map Manual Remap and Bad Location

mshann01 — Mon, 09 Apr 2018 19:14:40 GMT

I'm working with a map of CT and using a bubble chart for cities. However, there's one town that will not get plotted correctly: Newtown, CT. This always plots in Hartford, CT. I tried using the Manual Remap to try and move it to another location but it doesn't ever change. It always shows up in Hartford, CT. I tried to manual remap to "New Haven,CT" and that doesn't even move it to New Haven. County and zipcode area layers all report correctly. It's just the town of Newtown that won't display correctly. There's nothing else funny about the data or the spelling.

Re: GeoAnalytics City Bubble Map Manual Remap and Bad Location

Patric_Nordstrom — Thu, 12 Apr 2018 09:52:07 GMT

Hi Mark,

I got a correct match when supplying county:

='Newtown,Fairfield County,CT'

Unclear why the "Newtown" district in Hartford have higher precedence,

Thanks,

Patric

Re: GeoAnalytics City Bubble Map Manual Remap and Bad Location

mshann01 — Fri, 13 Apr 2018 14:39:53 GMT

Thanks Patric. Any idea why the Manual Remap won't allow me to fix those on the fly? I tried a few different formatting options but haven't had any luck.

Re: GeoAnalytics City Bubble Map Manual Remap and Bad Location

Patric_Nordstrom — Fri, 13 Apr 2018 14:45:12 GMT

The following works for me in the "Manual remap" field in Qlik Sense, the "Country" dropdown is set to "United States".

Watch so you get exact string with spaces. The syntax is "from string":"to string"

"Newtown,CT":"Newtown,Fairfield County,CT"

Thanks,

Patric

Re: GeoAnalytics City Bubble Map Manual Remap and Bad Location

mshann01 — Fri, 13 Apr 2018 15:47:26 GMT

Yes I have those same options and format set but I'm using QlikView 12.20. I think that's the only difference.

Re: GeoAnalytics City Bubble Map Manual Remap and Bad Location

Patric_Nordstrom — Thu, 03 May 2018 11:20:26 GMT

Hi Mark, yes looks like a bug, we opened a case for it. Thanks, Patric