Bug report #16433
adding kmz doesn't import placemarks, only tracks
|Affected QGIS version:||2.18.5||Regression?:||No|
|Operating System:||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||end of life|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||24342|
I've got a KMZ that was generated from GPS Kit<1> for iPhone and it seems that QGIS 2.18.6 doesn't see the placemarks and only imports the tracks.
I opened the KMZ in Google Earth, and was able to create a new sub folder inside the root folder and drag/drop all the placemarks into it - they were originally in the root folder of the project whereas tracks were in separate sub folders.
Then I did a Save As on this KMZ and created a new one which QGIS was able to import the placemarks once they were in a sub folder.
Unfortunately I don't have a iPhone to test out the GPS Kit app to see where the issue is, but may be able to provide some test data to someone directly if they are interested in testing it out.
I did some additional testing and noticed that it's limited to KMZs created from GPS Kit.
I created some data in Google Earth to test it out with placemarks in a subfolder, or in the root folder of the project and they both seem to import the placemarks fine.
Not sure what GPS Kit is doing to generate the kml/kmz that makes it problematic for QGIS to import the placemarks.
FYI, I've been told that ArcGIS can import the placemarks fine from the KMZ generated by GPS Kit.
I also submitted an inquiry to the app developer to see if they have any insight and can update this bug report when I hear back.
#4 Updated by Giovanni Manghi over 3 years ago
- Resolution set to end of life
- Status changed from Feedback to Closed
End of life notice: QGIS 2.18 LTR
QGIS 3.4 has recently become our new Long Term Release (LTR) version. This is a major step in our history – a long term release version based on the massive updates, library upgrades and improvements that we carried out in the course of the 2.x to 3x upgrade cycle.
We strongly encourage all users who are currently using QGIS 2.18 LTR as their preferred QGIS release to migrate to QGIS 3.4. This new LTR version will receive regular bugfixes for at least one year. It also includes hundreds of new functions, usability improvements, bugfixes, and other goodies. See the relevant changelogs for a good sampling of all the new features that have gone into version 3.4
Most plugins have been either migrated or incorporated into the core QGIS code base.
We strongly discourage the continued use of QGIS 2.18 LTR as it is now officially unsupported, which means we’ll not provide any bug fix releases for it.
You should also note that we intend to close all bug tickets referring to the now obsolete LTR version. Original reporters will receive a notification of the ticket closure and are encouraged to check whether the issue persists in the new LTR, in which case they should reopen the ticket.
If you would like to better understand the QGIS release roadmap, check out our roadmap page! It outlines the schedule for upcoming releases and will help you plan your deployment of QGIS into an operational environment.
The development of QGIS 3.4 LTR has been made possible by the work of hundreds of volunteers, by the investments of companies, professionals, and administrations, and by continuous donations and financial support from many of you. We sincerely thank you all and encourage you to collaborate and support the project even more, for the long term improvement and sustainability of the QGIS project.