<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Data in GeoAnalytics in GeoAnalytics</title>
    <link>https://community.qlik.com/t5/GeoAnalytics/Data-in-GeoAnalytics/m-p/87994#M502</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Yes, the process of handling bad location input data is topic for several blog posts. &lt;SPAN style="font-size: 10pt;"&gt;However, here's some advice:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Add country code to the locations string (or use the drop down): 'New York, US'&lt;/LI&gt;&lt;LI&gt;Add location type to locations string (or use the drop down): 'New York,US:P*' to get hits on the city not the state&lt;/LI&gt;&lt;LI&gt;Use codes when possible (country, region etc) names are often spelled wrong&lt;/LI&gt;&lt;LI&gt;Remove any trash in the location string&lt;/LI&gt;&lt;LI&gt;Use NamedPointLookup and NamedAreaLookup to flush out mismatches when the data is loaded&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Check the &lt;/SPAN&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/docs/DOC-18635" style="font-size: 13.3333px;"&gt;QGA coverage&lt;/A&gt;&lt;SPAN style="font-size: 13.3333px;"&gt; to expect per country&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;Buy &lt;A href="https://bi.idevio.com/products/qlik-geocoding"&gt;Qlik Geocoding&lt;/A&gt; to get matching to street address number level&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Read more how the Location Service works:&lt;/P&gt;&lt;P&gt;&lt;A href="https://bi.idevio.com/products/idevio-maps-for-qlik-sense/documentation" title="https://bi.idevio.com/products/idevio-maps-for-qlik-sense/documentation"&gt;https://bi.idevio.com/products/idevio-maps-for-qlik-sense/documentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try the NamedPointLookup Example at&lt;/P&gt;&lt;P&gt;&lt;A href="https://bi.idevio.com/geoanalytics/geoanalytics-connector-examples" title="https://bi.idevio.com/geoanalytics/geoanalytics-connector-examples"&gt;https://bi.idevio.com/geoanalytics/geoanalytics-connector-examples&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Patric&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 15 Oct 2018 13:33:00 GMT</pubDate>
    <dc:creator>Patric_Nordstrom</dc:creator>
    <dc:date>2018-10-15T13:33:00Z</dc:date>
    <item>
      <title>Data in GeoAnalytics</title>
      <link>https://community.qlik.com/t5/GeoAnalytics/Data-in-GeoAnalytics/m-p/87993#M501</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can anyone guide me how to make data consistent for GeoAnalytics? I have multiple entries for City, State and Country for pickup and delivery , but the data have lots of missing fields and null values. Also some of the fields have wrongly associated values with different types of inputs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So what can be the best practice for getting proper data for Geo-Analytics implementation?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 09 Oct 2018 12:36:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/GeoAnalytics/Data-in-GeoAnalytics/m-p/87993#M501</guid>
      <dc:creator>d_ankusha</dc:creator>
      <dc:date>2018-10-09T12:36:13Z</dc:date>
    </item>
    <item>
      <title>Re: Data in GeoAnalytics</title>
      <link>https://community.qlik.com/t5/GeoAnalytics/Data-in-GeoAnalytics/m-p/87994#M502</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Yes, the process of handling bad location input data is topic for several blog posts. &lt;SPAN style="font-size: 10pt;"&gt;However, here's some advice:&lt;/SPAN&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Add country code to the locations string (or use the drop down): 'New York, US'&lt;/LI&gt;&lt;LI&gt;Add location type to locations string (or use the drop down): 'New York,US:P*' to get hits on the city not the state&lt;/LI&gt;&lt;LI&gt;Use codes when possible (country, region etc) names are often spelled wrong&lt;/LI&gt;&lt;LI&gt;Remove any trash in the location string&lt;/LI&gt;&lt;LI&gt;Use NamedPointLookup and NamedAreaLookup to flush out mismatches when the data is loaded&lt;/LI&gt;&lt;LI&gt;&lt;SPAN style="font-size: 13.3333px;"&gt;Check the &lt;/SPAN&gt;&lt;A _jive_internal="true" href="https://community.qlik.com/docs/DOC-18635" style="font-size: 13.3333px;"&gt;QGA coverage&lt;/A&gt;&lt;SPAN style="font-size: 13.3333px;"&gt; to expect per country&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;Buy &lt;A href="https://bi.idevio.com/products/qlik-geocoding"&gt;Qlik Geocoding&lt;/A&gt; to get matching to street address number level&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Read more how the Location Service works:&lt;/P&gt;&lt;P&gt;&lt;A href="https://bi.idevio.com/products/idevio-maps-for-qlik-sense/documentation" title="https://bi.idevio.com/products/idevio-maps-for-qlik-sense/documentation"&gt;https://bi.idevio.com/products/idevio-maps-for-qlik-sense/documentation&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try the NamedPointLookup Example at&lt;/P&gt;&lt;P&gt;&lt;A href="https://bi.idevio.com/geoanalytics/geoanalytics-connector-examples" title="https://bi.idevio.com/geoanalytics/geoanalytics-connector-examples"&gt;https://bi.idevio.com/geoanalytics/geoanalytics-connector-examples&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Patric&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 15 Oct 2018 13:33:00 GMT</pubDate>
      <guid>https://community.qlik.com/t5/GeoAnalytics/Data-in-GeoAnalytics/m-p/87994#M502</guid>
      <dc:creator>Patric_Nordstrom</dc:creator>
      <dc:date>2018-10-15T13:33:00Z</dc:date>
    </item>
  </channel>
</rss>

