When I successfully export Google Tiles as an output, it seems to work fine in Google Earth as long as I launch the .kml from the default location for my Pix4D project on my machine. However, if I move this google tile bundle to a shared network folder, the .kml link to the associated image tile files and kmls are broken…it seems to have a hard path to the original export path. Is this the intent? You can’t share this to others?
To share the KML file, it is needed to share both the KML file and the tiles of the different zoom levels stored in folders. If only the KML file is shared, Google Earth will focus on the area, but the tiles will not be loaded. To share KML file and all zoom levels, it is convenient to create a KMZ file: a compressed version of the KML file. The KMZ file contains all the tiles and coordinate information needed to load the data. Could you try this and let me know whether it solved your problem?
Yes I saved all files from the 3_dsm_ortho\2_mosaic\google tiles folder. It will not load the tiles from the server location…only the C drive where they were outputted to. I am happy to try to make a .kmz file…is there a procedure I can follow to bundle them in .kmz format?
I agree with Michael. I have followed your attached procedure and once you move the the \google tiles folder, it no longer shows the imagery in google earth. I have compressed the folder (KML along with all subfolders) into a KMZ and it will open as long as the KMZ is located within my 3_dsm_ortho folder, but as soon as the KMZ is moved to a shared location, the imagery is no longer visible on google earth.
I do not know what I am missing but it is proving to be a nightmare to try and share pix4d Ortho with non pix4d users.
Thank you for letting us know that our article was not straightforward enough.
I updated our instruction. The missing step is covered here:
The recipient has to uncompress the folder on his computer. The file can then be opened by double-clicking the kml file or by dragging and dropping it into Google Earth.
If a recipient attempts to open the file from the shared file, s/he may run into issues.
These cookies are necessary for the website to function and cannot be switched off in our systems.
They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences,
logging in, or filling in forms. These cookies do not store any personally identifiable information.
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site.
They help us to know which pages are the most and least popular and see how visitors move around the site.
All information these cookies collect is aggregated and therefore anonymous.
If you do not allow these cookies we will not know when you have visited our site, and will not be able to monitor its performance.
These cookies may be set through our site by our advertising partner (Google).
They may be used by Google to build a profile of your interests and show you relevant adverts on other sites.
They do not directly store personal information but are based on uniquely identifying your browser and internet device.
If you do not allow these cookies, you will experience less targeted advertising.