7 Replies Latest reply: Oct 29, 2017 12:31 AM by Nikhil Garg RSS

    Making State boundary differ from existing state boundary

    Nikhil Garg

      Hello Everyone,

       

      I am new to qliksense and need some help regarding maps

      We all know about political Geographic boundaries. But in my project, we have defined Market territories and based on that we are creating state boundaries.

      For ex: If we have:

      Following Market territory On India Map under Tamil Nadu as:

      MKT1, MKT2, MKT3

       

      Following Market territory On India Map under Andhra Pradesh as:

      MKT4, MKT5, MKT6

       

      Now, in my project, i have:

      Following Market territory under Tamil Nadu as:

      MKT1, MKT2

       

      Following Market territory under Andhra Pradesh as:

      MKT4, MKT6

       

      Following Market territory under Tamil Nadu-Karnataka as:

      MKT3, MKT5

       

      I have to create a state mapping(Tamil Nadu, Karnataka, Tamil Nadu-Karnataka) and show them accordingly on maps in qliksense.

      How can i acheive this? Does anyone came across such situation?

      vikasmahajan gwassenaar hic, mtarallo  Can you help me in this?

       

      Thanks,

      Nikhil Garg

        • Re: Making State boundary differ from existing state boundary
          Michael Tarallo

          Hi Nikhil - thanks for reaching out - I did not see this until you replied as a comment in the other post - my Qlik handle is not mtarallo - that is my test account - so I won't see notifications. If you ever need to reach me - you can tag me with @michael_tarallo and then select mto form the list. However - I may not always reply.

           

          I may not be understanding this correctly - but let me give it a shot.

           

          In regards to this - this takes some thought. If the state boundaries to be displayed are the same coordinates, but are only identified my different keys (MKT1, MKT2, MKT3) - I would imagine that you would have to edit the KML of the map - to use those identifiers for the States you want to display.

           

          I attached some quick sample data a a sample app - here when I select Mike (Rep) - it shows me FL and GA as mine and if I select Jeff it shows me NY and NJ.

           

          Basically in the KML file (US MAP) - there is a <PLACEMARK> tag that holds the key that you associate on  - and what I did was replace the traditional State ISO2 Code with the key value that is linked to my sales reps - so FL and GA became MKT1 and NY and NJ became MKT2.

           

          The I associated my sales table (mike_map_data)  - on the "market" field to the mike_US.Name field in the map data (KML file)

           

          Is this what you mean?

           

          <Placemark>
          <name>MKT2</name>
          <Snippet></Snippet>
          <description>
          <![CDATA[<table border=0 cellpadding=0 cellspacing=0  width=250 style="FONT-SIZE: 11px; FONT-FAMILY: Verdana, Arial, Helvetica, sans-serif;">
          <tr>
          <td bgcolor="#E3E1CA" align="right">
          <font COLOR="#000000">
          <b>CODE</b>
          </font>
          </td>
          <td bgcolor="#E4E6CA"> <font COLOR="#008000">NJ</font>
          </td>
          </tr>
          </table>]]>
          </description>
          <styleUrl>#shp2kml</styleUrl>
          <Polygon><outerBoundaryIs><LinearRing><coordinates>-75.489281,39.714858,0.0 -75.475974,39.720084,0.0 -75.474768,39.741832,0.0 -75.460394,39.763362,0.0 -75.427647,39.778243,0.0 -75.411755,39.789771,0.0 -75.420468,39.798983,0.0 -75.345932,39.848517,0.0 -75.25374,39.845538,0.0 -75.246996,39.850405,0.0 -75.185605,39.877406,0.0 -75.142901,39.881602,0.0 -75.135805,39.896887,0.0 -75.147159,39.93474,0.0 -75.139865,39.955919,0.0 -75.110963,39.97669,0.0 -75.084587,39.975733,0.0 -75.068046,39.985392,0.0 -75.045675,40.007635,0.0 -74.983485,40.034074,0.0 -74.956202,40.058014,0.0 -74.871924,40.078057,0.0 -74.829022,40.116161,0.0 -74.746294,40.124359,0.0 -74.72548,40.149307,0.0 -74.738825,40.177726,0.0 -74.842763,40.248453,0.0 -74.88066,40.299592,0.0 -74.92115,40.314034,0.0 -74.932503,40.333774,0.0 -74.950188,40.345474,0.0 -74.972841,40.404448,0.0 -75.000476,40.408621,0.0 -75.021266,40.401324,0.0 -75.057453,40.420171,0.0 -75.070119,40.456254,0.0 -75.06368,40.521003,0.0 -75.079786,40.545356,0.0 -75.124526,40.564799,0.0 -75.182282,40.556799,0.0 -75.197572,40.570684,0.0 -75.193513,40.583769,0.0 -75.200388,40.614743,0.0 -75.197939,40.634206,0.0 -75.208918,40.650738,0.0 -75.184061,40.669792,0.0 -75.205355,40.686062,0.0 -75.187754,40.723857,0.0 -75.193644,40.748004,0.0 -75.170313,40.774809,0.0 -75.130319,40.772708,0.0 -75.100541,40.791659,0.0 -75.089211,40.821391,0.0 -75.099542,40.839285,0.0 -75.054619,40.855673,0.0 -75.056488,40.872046,0.0 -75.073686,40.884626,0.0 -75.079736,40.903349,0.0 -75.135525,40.962937,0.0 -75.139302,40.977528,0.0 -75.116619,41.000248,0.0 -75.069979,41.010716,0.0 -75.035256,41.028203,0.0 -75.001152,41.062486,0.0 -74.966292,41.082677,0.0 -74.988883,41.081761,0.0 -74.984595,41.099381,0.0 -74.949994,41.111855,0.0 -74.914768,41.141106,0.0 -74.862887,41.206771,0.0 -74.866411,41.226817,0.0 -74.825196,41.282706,0.0 -74.794143,41.295215,0.0 -74.791663,41.311965,0.0 -74.700062,41.350573,0.0 -74.371981,41.19585,0.0 -74.24236,41.137627,0.0 -74.213039,41.123612,0.0 -73.896698,40.99853,0.0 -73.896148,40.960872,0.0 -73.908966,40.927314,0.0 -73.922394,40.88604,0.0 -73.977061,40.797487,0.0 -74.00626,40.737731,0.0 -74.006183,40.704002,0.0 -74.129058,40.647072,0.0 -74.115531,40.705627,0.0 -74.146858,40.67548,0.0 -74.208253,40.591188,0.0 -74.27891,40.514304,0.0 -74.268915,40.463749,0.0 -74.224503,40.443585,0.0 -74.121885,40.451459,0.0 -73.978441,40.323616,0.0 -74.039231,40.101842,0.0 -74.091426,40.116086,0.0 -74.083773,40.088182,0.0 -74.034295,40.091367,0.0 -74.04979,40.056856,0.0 -74.122181,40.051561,0.0 -74.077333,40.042273,0.0 -74.159229,39.878605,0.0 -74.171427,39.718275,0.0 -74.237676,39.624047,0.0 -74.323342,39.572086,0.0 -74.328851,39.523628,0.0 -74.412389,39.542621,0.0 -74.40112,39.502628,0.0 -74.460418,39.426757,0.0 -74.447501,39.381075,0.0 -74.658234,39.287251,0.0 -74.622527,39.281632,0.0 -74.624587,39.250829,0.0 -74.802292,39.026374,0.0 -74.879254,38.989844,0.0 -74.876301,38.956682,0.0 -74.968125,38.971739,0.0 -74.890202,39.11386,0.0 -74.916654,39.170639,0.0 -75.014407,39.198364,0.0 -75.119958,39.184692,0.0 -75.415672,39.374972,0.0 -75.552763,39.490514,0.0 -75.516689,39.566568,0.0 -75.570234,39.617735,0.0 -75.489281,39.714858,0.0</coordinates></LinearRing></outerBoundaryIs></Polygon>
          </Placemark>
          

           

           

           

           

           

          When applicable please mark the appropriate replies as CORRECT. This will help community members and Qlik Employees know which discussions have already been addressed and have a possible known solution. Please mark threads as HELPFUL if the provided solution is helpful to the problem, but does not necessarily solve the indicated problem. You can mark multiple threads as HELPFUL if you feel additional info is useful to others.

           

          Regards,

           

          Michael Tarallo (@mtarallo) | Twitter

          Qlik

          • Re: Making State boundary differ from existing state boundary
            Michael Tarallo

            BTW - this is using our default mapping - not Qlik GeoAnalytics - just so you know.

            • Re: Making State boundary differ from existing state boundary
              Nikhil Garg

              Hey ,

              Thanks Pooja. My mistake was i was using KPI oblject and checking value of variable in that. However when i take Text Object it works fine.

              Thanks anyways