If you just drop that KML file to Qlik Sense, the county is identified by its name:
this is a problem because there duplicated by county name. It is not a Qlik Sense issue - census people really should have been used FIPS code instead but the question I have for you guys if it is possible somehow to use other attributes from KML file. They do have FIPS code in there, but it is rather recorded under GEOID note not NAME:
I think i almost got it work by replacing the Name attribute with CountyState code - I wrote regex to do that but then I gave up - it was something I did for proof-of-concept and it did not go that well.
Another option i was entertaining is to use spatial tools and rebuild KML file itself.
interesting project but unfortunately google maps API would be off limit for most commercial applications unless you get a full license (starts at $10,000 annually). at some point i did an extensive research and contacted google team to clarify license agreement. in a nutshell, if you work for someone and use google map API and that application is not accessible to public (not only employees of your company but the entire world), then you will be violating license agreement. Same thing with Microsoft. The only truly free solution i found back then was MapQuest open API which worked great for us. so keep this in mind