Qlik is able to read KML file without issues. I've noticed some malformed KML files causing issues with my in the past. I wonder if this is an area KML, but it's not correctly defined.
Please inspect the file to determine if the first coordinate and the last one are the same. This means the area is "closed". Does this make sense?
Live and Breathe Qlik & AWS. Follow me on my LinkedIn | Know IPC Global at ipc-global.com
Hello my name is Sanjeev Mansotra, a core educator and social advocate from India.
Qlik Sense may not be able to read the file from QGIS due to a format compatibility issue. Here's a step-by-step approach to solving it:
1. Check the File Format: QGIS commonly exports files in formats like GeoJSON, Shapefile (SHP), or CSV. Qlik Sense supports CSV, Excel (XLSX), JSON, and KML for geospatial data. Make sure the file is exported in one of these supported formats.
2. Convert the File: If the file format is not supported by Qlik Sense, you can convert it using QGIS or other tools:
In QGIS:
Open the QGIS project and load the layer you want to export. Right-click on the layer in the Layers Panel and select Export > Save Features As. Choose CSV or GeoJSON from the Format dropdown list. Set the coordinate system to WGS 84 (EPSG:4326), as this is commonly used in Qlik Sense. Save the file. Using Online Conversion Tools:
If you want a simpler method, you can use an online tool like MyGeodata Converter to convert the file to a format compatible with Qlik Sense.
3. Load the File into Qlik Sense: Once the file is in a format that Qlik Sense can handle, open Qlik Sense and navigate to the Data Load Editor. Use the Data Manager to upload the CSV, JSON, or KML file. Configure the data to be correctly interpreted, especially for geospatial data.
4. Verify Geospatial Data (for maps) in Qlik Sense: If you're using the data for map visualizations, ensure that Qlik Sense recognizes the fields as latitude and longitude (if using coordinates) or area/polygon (if using polygons from files like GeoJSON or KML).
