2018

Qlik Product Innovation

August 2018 Previous month Next month

For most geo-related use cases, the highest level of needed detail is the town or postal code district. There are, however, certain use cases where one needs to also include street addresses.  And for that, Qlik now offers Qlik Geocoding.  Initially released this past April, Qlik Geocoding is an optional, add-on subscription service to Qlik GeoAnalytics Base and Qlik GeoAnalytics Enterprise Server that determines the coordinates of a street address or the other way around.

 

The service is provided through the Qlik GeoAnalytics Connector (for both QlikView and Qlik Sense) using the operations “AddressPointLookup” and “PointToAddressLookup”. “AddressPointLookup” is used for forward geocoding (given this address, what are the coordinates).  “PointToAddressLookup” is used for reverse geocoding or converting coordinates to an address.  This could be useful, for example, to convert GPS coordinates to a street location. 

 

An example of forward geocoding can be seen in this screenshot.  The original addresses are in the table on the left.  The related coordinates that were returned by Qlik Geocoding are in the table on the right.

 

Qlik’s source of geocoding information is the Esri World Geocoding Service and, like any mapping source, the completeness and level of detail will vary by country.  Countries with rich datasets should accurately return the correct house number.  Countries with limited datasets may only be able to match to the street or region, not the address.

 

Qlik Geocoding is only offered as a hosted service and is subscription priced based on how many lookups are done each year.  Because of this, we recommend that you store all completed look-up results locally for future reference.  Thus, you only need to use Qlik Geocoding in the future for new addresses.  This can significantly reduce the number of address lookups and thus minimize the cost of using Qlik Geocoding.

 

To learn more about our Qlik Geocoding service check out this video by our Mike Tarallo, which provides a brief presentation about the service and a more in depth how-to with some tips and tricks along the way. Mike has also provided some sample data and a Qlik Sense example as well for you to use within your Qlik Sense implementation.

 

 

 

Resources mentioned in this video:

 

https://help.qlik.com/en-US/geoanalytics/Content/Home.htm/

Qlik GeoAnalytics

Terms and Conditions

• Geocoding Template:  https://bi.idevio.com/products/qlik-geocoding

2017 was a very busy year for Qlik NPrinting from the standpoint of improving stability and performance. While this continues to be a focus, 2018 is on track to be the year of feature enhancements. With the June 2018 release and September 2018 Internal Preview, significant advancements in features have been introduced to make Qlik NPrinting more robust than ever.

 

Here is a summary of some of the biggest enhancements in Qlik NPrinting since January…

 

Support for more forms of authentication and authorizationThis not only allows Qlik NPrinting customers standardization between systems, but also improves user experience and increased security.

 

  • SAML authentication: Qlik NPrinting supports Single Sign-On (SSO) by using SAML. SAML (Security Assertion Markup Language) is an open standard for exchanging authentication and authorization data between parties - i.e. an identify provider (IdP) and service provider (SP). Based on XML the most important use case is with Web Browser Single Sign-On. Both Qlik NPrinting Web Console and NewsStand can be configured to manage SAML authentication.
  • JSON Web Token (JWT): Supports authentication on both Qlik Sense and QlikView with DMS. JWT is an open standard for secure transmission of information between two parties used for authentication and authorization. JWT enables SSO in Qlik NPrinting, minimizing the number of times a user must log on.
  • QlikView server DMS authorization: Qlik NPrinting connections to QlikView Server now support DMS authentication. Section access can be integrated easily with Qlik NPrinting without the need of other actions. Qlik NPrinting On-Demand plugin works for Access Point users authenticated with DMS credentials.
  • Kerberos authentication: Qlik NPrinting now supports the use of Kerberos and NTLM. Just be sure the browsers used to access Qlik NPrinting are also configured to support Kerberos!

 

Qlik Sense pivot table supportQlik NPrinting supports pivot tables as objects from Qlik Sense connections, the same as QlikView connections. This allows for more flexibility to enhance reports with insight from pivot tables, without manually manipulation.

 

Monthly and yearly schedules – Time-based triggers now allow the creation of monthly and yearly schedules, which provides users with more flexibility to get the right information at the right time. This feature removes a gap from Qlik NPrinting 16.

 

Enhanced error handling – Qlik NPrinting filtering system has been improved and it is now able to manage many errors that appeared with messages like “Wrong content node response” or “Apply empty response”. Static empty content or invalid selections are managed without errors. The enhanced error handling is crucial for administrators minimizing downtime.

 

Upgrades to PostgresSQL, RabbitMQ and Erlangimportant updates that make Qlik NPrinting more secure and reliable.

  • Qlik NPrinting Repository is now based on PostgreSQL 10.1
  • The PostgreSQL administration tool was upgraded from 3 to 4.
  • Qlik NPrinting Messaging service (RabbitMQ and Erlang) have been updated. RabbitMQ [server] from version 3.5.7 to v3.7.4. RabbitMQ [client] from version 3.6 to v5.0.1. Erlang OPT from version 18.1 to v20.3.

 

Import users and roles from LDAPAs a first step towards tighter integration with Qlik Sense user management, it is now possible to import users, with attributes, and roles from a generic LDAP source into Qlik NPrinting by configuring imports directly from the Qlik NPrinting Web Console.

 

Password protected reports – Qlik NPrinting can generate reports protected with reading and/or writing passwords. Passwords can be set at report, publish task, or user level, which provide our customers with increased confidence that reports are safe.

 


Along with numerous security enhancements, improved QlikView cache generation, these are just some of the key advancements so far this year. And we’re still delighted for what the remainder of 2018 has in store for Qlik NPrinting!

Qlik is committed to making our products available and providing an outstanding user experience to everyone... When technology imitates the diversity of its users, there are no limits to what people can achieve. Qlik Sense has features that enable people who access our products in different ways to more easily interact with data and visualizations.

These features will continue to be developed as we strive to bring analytics and technology to all users with all abilities. Here are some best practices for creating accessible apps.

Building Accessible Apps

Accessibility is more than product features. When building an application, a developer also needs to design with accessibility in mind. This includes principles such as:

  • Keeping a flat structure instead of a complicated grid.
  • Providing an overview first, then more detail in subsequent scrollable sheets.
  • Using standard colors and a limited palette, choosing for readability.
  • Using charts that include the accessible data view
  • Providing text descriptions and context as much as possible.
  • Limiting values in dimensions to 10 or less.


While it may be more work, your apps will be easier to grasp and use for everyone, not just people with disabilities.

Keep a flat structure

When creating a layout, use a flat and easy structure, with few columns and rows. Complex structures make accessing your app difficult for users with keyboard navigation. Try navigating your sheets with the keyboard and see how users will perceive your app. A flat design also improves sheet readability for all users.

Provide an overview first and the details later

A fundamental design paradigm is “Overview first, details later”. For example, start by providing summaries and KPIs, rather than a complex table. Scrollable sheets let you put more details further down on the page, reducing the number of sheets needed in your app. 

Limit colors and choose selectively

Choose colors wisely. Colors can carry important information, but be sure to keep the palette small and distinct. More information on using colors can be found on our Data Visualization Foundations: Color blog post. Sticking to the default colors in Sense is good idea, they provide good readability for users with low vision.

Use charts with a data view

When designing your app, use charts that have the built-in data view. This lets users change the chart to a table, to help inspect and select values. Most of the standard Qlik Sense visualizations include this feature.

Extensions are useful, but you should confirm that they comply with the level of accessibility that you require.


Provide text descriptions

Have you noticed that all visualizations come with fields for a title, a subtitle, and a footer? Providing accurate text descriptions makes life a lot easier for all your users. You might think that your 80-20 bar chart with accumulated sums of sales for current and previous year is self-explanatory. But without context, your users may waste time deciphering your data. Also, screen readers will pick up the descriptions and have them read back.

Limit categories

When working with nominal data, try to find hierarchies or make aggregations if the number of categories is greater than 10. For example, displaying the top 10 values, and rest as ‘Others’ will make your data easier to understand and read aloud. You can always have tables with all the details but be sure put them at the end of the sheet.

Roadmap

 

Qlik is focused on the development of accessibility features in our products. Additional support for other user roles is on the roadmap. Supporting universal use in our solutions is an evolving process that will continue to employ new technologies and techniques as they become available. Our aim is to expand beyond the existing features within Qlik Sense Enterprise and Qlik Cloud Business.


We've optimized a demo app for your reference that can be found here.