KML / KMZ import.
Geplant
VertiGIS web going to allow you to upload a KML/KMZ files like Essentials?
Looks like supported file types are CSV, Excel, and shapefiles, in zip files or folders.
Are there future plans for KML / KMZ?
-
good question - add me to this idea also
1 -
we hope to get this in there at some point
2 -
Any update on this?
0 -
I noticed that the new VertiGIS Studio Web 5.35 was released yesterday. I was wondering if there are any updates on the KML/KMZ upload feature that was mentioned inside the matrix?
I also saw that the “planned” tag has been added to this thread. Can you share any additional information or estimated timelines for when this might be available?
Thanks in advance for any updates you can provide!
0 -
any updates??
0 -
any updates? I need kml upload feature in studio web
0 -
The team has begun working on KML import. You should see that in the next couple of versions (i.e. either in August 2025 or October 2025 version of VSW depending on how long it takes).
No plans for KMZ at this time.
6 -
Thanks Cam… That is great news!!
0 -
Yes, I agree. That's great news!
0 -
Hi,
From the VertiGIS Studio Web 5.37 Release Notes:
- Users can now import KML files directly into an active app session.
I did a test in the VSW SaaS and configured Layer Actions with a ‘Quick Add Layer from File’ command, assuming that this would be the supported method. I selected a *.kml file that I validated online at https://aleos-uk.com/datatester and which also opens nicely in ArcGIS Pro (3.5.2). Yet, it doesn't load into the VSW app.
Can someone clarify what I'm missing? Do I have to approach this differently? Or any side notes concerning the *.kml file itself?
BR
Sander
0 -
Johanne van Linge
0 -
Sander Van Raemdonck - you can't use the import from CSV command, you need to add an import from KML command to studio web
0 -
Helen Dornan, many thanks for pointing that out! I was confused because of the screenshot posted with the original request. That shows the interface from a Layer Action menu item. The command works indeed when applied to a button or toolbar menu item. Brilliant!
0 -
Most of our customers are only using the “Quick Add Layer from File” command… Why is it not (yet) integrated in there? Is this on the roadmap?
1 -
Hi, I tried the recently released Import from KML command. However, I found that this affects map performance significantly. It made everything really slow, which I suspect it's because it loads individual feature as its own ‘layer’ in the map, see screen shot below for illustration. The imported features are the points in pink colour.
For additional context, I downloaded the KML file from an open data catalogue built upon an ArcGIS Hub.
Is this something that is expected for the tool and for this format? I'm currently exploring if there is any other KML import option that will not compromise performance. Any input is much appreciated, thanks!
1 -
Amanda Putri What is the object count in the KML you imported?
0 -
Sander Broekaert I don't think it will be integrated. In Web 5.40 there will be an Import from DXF function, this is also a separate command.
0 -
It seems like there is a bug with saving the imported KML file in a project: only the group layer seems to be saved in the json, not the layers with the data that are inside.
This results in the fact that, when you load the project (json), the KML group layer is present in the layer list, but not the foldout of the layers below. Consequently, the layers on the map are not visible and cannot be made visible.
0 -
Tanja Goethals We are working on a bug not related to KML import and saved projects … you've given a good hint here as to what might be going on. Issue # is 342161
1 -
Update - now have the Import KMZ workflow doing a map.zoom-to-layer-extent using the root layer id of the added kmz file and the retrieved map extension id gotten from the map activity. I needed the flexibility as our viewer has 4 different layouts that are using different maps. I think this is as good as it is going to get - it still fails a very few times on some files, but that gets trapped since the Run Operation that add the layers from kml is running in a Try-Catch activity. The extracted KMLs for these problem files also do not load, so thing it is something about these particular files. KMZ is a messy, messy format.
I have created a Import KMZ workflow that works for 95% of the time that operates on the strategy of using the Create File workflow activity to creat a file from them uploaded KMZ file called the same thing but with a .zip extension. I then used the Unzip activity to extract the doc.xml or whatever the software decided to name the root kml file (because sometimes is it not called doc.kml). It then uses the layers.from-xml to import what is in that kml file. The 5% of the time it fails is because there is some group layer causing issues, but I am working just now to try to handle that issue and also the issue of zooming to the extent of the data which is a different process than zoom to polyline or polygon issues. I plan to finish that up today. I am super-pleased with how well it works thus far and am very confident I can get rid of these last group-layer and zoom to layer extent related issues shortly. The difficult part of this was figuring out the syntax for the Vertigis commands and also the file blobs from the unzipped KMZ, as usual, but I finally got it. Of course, the core issue is the messiness of the KMZ format, which makes the shapefile format look amazingly neat by comparison.0
Bitte melden Sie sich an, um einen Kommentar zu hinterlassen.
Kommentare
20 Kommentare