Photo points in KMZ don't show in Google Earth in full resolution

Evan shared this question 2 months ago
Answered

Hello All,

I've begun testing photo points for work using Locus Map Pro and GPS Averaging for accuracy. When exporting the photo points as a KMZ, they only show as a tiny thumbnail in Google Earth even though the filesize seems correct (3 photos = 10mb KMZ, 6 photos = 20mb).

I found one link mentioning that Google Earth sometimes displays 400 pixels wide but the thumbnail is not close to that, nor is it clickable. How do you believe I can troubleshoot this? I need accurate points and a usable photo resolution to identify a plant's location and type.

Thank you.

Comments (9)

photo
1

Hi

default width for exported photos in kmz is 60 pix.

You can modify this value inside config.cfg with an editor.

Navigate with file manager to:

Locus folder, there you´l find confi.cfg

search for "IMPORT & EXPORT"

export_photo_width= xxx

and change this value to e.g. 250 and save your changes

After restart of locus youl´ll get 0ed579d01df3fe97f2f43a7536cf9eea


I need accurate points and a usable photo resolution to identify a plant's location and type

Note:

if you create a point and "take a photo" as attachement to this point the photo is geocoded with the coords received at that moment !

If you next use "GPS Averaging for accuracy" the coords will be more accurate for the point but not for the photo, so if you only share the geocoded photo the possition could be "far away" from real possition

Wolfgang

photo
1

Hi Wolfgang,

Thank you for your reply. I may not have been clear, the thumbnail isn't an issue but your information has been helpful and I will probably adjust it to a larger size because your attachment looks very good.

The KMZ seems to contain full or near full resolution photos (judging by filesize) but I can't access them through Google Earth. I share the KMZ with the prinicipal contractor to track the movement of plants through the environment and he needs to see the photo in at least 1024x to full res where it is mapped in the KMZ. The KMZ I share, the photo points seem accurate to the environment, the timestamp is there etc, the coords are good, but I, and he, can't see the full resolution photo.

I logged a ticket with Locus to see if a script could reduce the photos to, say, 1600x1200 before zipping up in the KMZ and sharing because reception in the field is poor and large uploads don't work too well. That's a different issue. The issue is how to view the full res included in the KMZ. Are there other software to test to make sure it's just a Google Earth problem that you know of?

Or the CSS change you are suggesting is the only method to say set it at 4000x3000 or combinations thereof? Wouldn't that be a better menu setting rather than a file change?

Thank you.

photo
1

Hi Evan,

The original image is really packed in KMZ file. There is a workaround how to get the image but's quite tricky:

  • to rename the file extension from *.kmz to *.zip
  • unpack the package (kmz file is only zip package)
  • original image is located in "files" folder

There is also topic that focus on possibility to open image in Google Earth. http://help.locusmap.eu/topic/export-all-visible-elements-to-kmz-file-doesnt-show-big-pictures Unfortunately this problem has no solution. It seems that Google Earth (in the latest versions) is too strict and doesn't allow to open local file.

However there is another workaround in case that you want to play with KMZ definition. Google Earth doesn't open local file but can open "image with full http url". I mean : to upload image in some server/cloud, to get share URL and in final step edit KML/KMZ file. I can provide more info if you want to play with it.

Thank you

Petr

photo
1

Thanks Petr. That's helpful.

While I could play around with options, I don't think I can convince my employer to muck around with it, or upload in the field due to time constraints. I basically pull phone out, take a Photo Point (which Wolfgang indicates won't use GPS Averaging) so I will change to logging a Point, taking a photo and attaching it to the point, and moving on. Then I share the KMZ when I hit reception.


What do you think would be the best option to use Locus and GPS Averaging to log points with a decent enough resolution photo to share with someone, even if we have to leave Google Earth behind? Any ideas?

photo
photo
1

For anyone reading, it seems there is no easy or clear fix.

I have downloaded an application called Geosetter which takes your photos and inserts them right into Google Earth at whatever resolution you choose.

Yes, it doesn't work in the field but I'm resigned to Locus not working either so will be requesting a refund under Australian Consumer Law.

photo
1

I'm not sure if I can understand. Are you able to create click-able image in KMZ? I mean the point with thumbnail of image and GE display full image when you click on it?

photo
1

No, Petr. The tiny thumbnail in Google Earth is not clickable.

Geosetter allows me to resize the photos beforehand before I pass them to it, label them how I see fit, change the size of the thumbnail etc.

So now I just take photos with 'Open Camera' with location settings on and running the track feature in 'GPS Averaging'. I then give the several GPXs to GPSVisualiser, get rid of the waypoints into a KMZ, pass the photos to Geosetter and export a KMZ. Combine the two and that's good enough.

The only thing I'm missing losing Locus is the GPS Averaging waypoints for accuracy. The track feature of Locus is not as accurate as 'GPS Averaging'. If only someone could flesh out GPS Averaging as an app, it would work for me.

photo
1

I see ... I only mention that you can influence the size of the attachment using export_photo_width parameter in Locus config file.

photo
1

Yes, Petr. Thank you.

Unfortunately, the fact that it didn't work out of the box and I couldn't use Locus to reduce photo size when exporting to KMZ was the death knell for my Locus usage. I think it was very close to what I wanted but I only need a few things to work well and my use case wasn't covered. At the moment, I use photos to mark points on the 'GPS Averaging' track GPX. On some sites, a photo is possibly too extraneous so my workflow doesn't suit point leaving at this juncture. I've attached a run for an example.

If other readers are reading this, don't let me dissuade you from buying Locus Map Pro. From what I could see for hiking, geocaching and similar, it's a very nice app.

photo