Suggest an Idea

[CHansford]

Folks,

I use the Geo-operations function a lot on SaaS and wondered why I wasn't getting as many returned polygons from my Postal Code fields when using them in a native Map on Qlik SaaS.

Having looked at the returned Name field after using 

Postalcode:
Load Name,LocationPolygon Extension GeoOperations.ScriptEval('
Select * from
Load() DATASOURCE uk LOCATIONSERVICE type="XPC", country="GB"
');

I see that the postcodes are being returned like this Ab10 1, Ab10 6, etc.

The issues is that in the UK we only use Capital Letters in our Postcodes, so where an Outward Code has 2 alpha characters it won't match.  Now yes I could amend my script to bring back the Name field as uppercase, however that doesn't solve the issue when I just use the native map.

Can you update the Geodatabase so that all the UK Postcodes are in Capital Letters?

Regards

Chris

[CHansford]

It would be good to get some feedback on some of these ideas, or at least a response from a moderator.  This is one such issue that could be dealt with quickly.

Stay safe

[Patric_Nordstrom]

Thank you all for your feedback on ways to improve our product. While this is something we understand would be useful, it's not on the short-term roadmap. Please continue to show your support for this idea by commenting and liking.

Thanks, 
Patric

[CHansford]

Patric,

Thanks for letting me know that a very simple upper case change to the UK Postcode Geodata is not on the short-term roadmap, despite it being a Data Quality issue and something that other BI software companies manage to get right.  I will therefore continue to use a workaround to solve this vexing issue in the hope that one day it might actually get to the Roadmap.

Regards, stay safe

[Patric_Nordstrom]

Even if the postal codes are stored in small caps you should still get hits in the map chart.

Ab10 6, ab 10 6 and AB 10 6 returns a matching area in the map chart.

[CHansford]

Hi Patric,

Thanks for the clarification, at Postal District level (AB12 3)  the Map area polygons work, but when matching to the input postcode in a straight table it doesn't. Which is a shame.

[Patric_Nordstrom]

Not sure if I agree

I get the following hits:

When doing "Load" using namedAreaField

NamedAreaLookup:
load * Inline [
lookup_zip_nr;lookup_zip
1;"AB10 6,GB"
2;"Ab10 6,GB"
3;"ab10 6,GB"
] (delimiter is ';');


Load * Extension
GeoOperations.ScriptEval('
Load()
DATASOURCE zip INTABLE keyField="lookup_zip_nr", namedAreaField="lookup_zip"', NamedAreaLookup);

[CHansford]

Patric,

you are the expert and this does work, could it be the use of  ,GB as I've used 'UK' previously.

Cheers

[Patric_Nordstrom]

No worries, glad it worked out

[Meghann_MacDonald]

From now on, please track this idea from the Ideation portal. 

Link to new idea

Meghann

NOTE: Upon clicking this link 2 tabs may open - please feel free to close the one with a login page. If you only see 1 tab with the login page, please try clicking this link first: Authenticate me! then try the link above again. Ensure pop-up blocker is off.