Cannot display high resolution geotagged images

[EliasJonsson]

JOSM reports "Error on file" followed by the-file-name.jpg upon importing geotagged images with high resolution.
In my case the image was 3024*4032 pixels and that proved to be too much for JOSM to swallow.

Workaround:
Scale the image down, then import it, JOSM will import and display the image just fine.
In my case, scaling down to 552*736 pixels solved the problem.

[EliasJonsson]

original geotagged image

[EliasJonsson]

scaled down image

[simon04]

Thanks for your report, however your ticket is incomplete and therefore not helpful in its current form.

Please add all needed information according to this list:

• The required parts of the Status Report from your JOSM.
  • Please, use Report Bug from Help menu and copy & paste.
• Describe what behaviour you expected.
• Describe what did happen instead.
• Describe if and how the issue is reproducible.
• Add any relevant information like error messages or screenshots.

To ensure that all technical relevant information is contained, create new tickets by clicking in JOSMs Main Menu on Help → Report Bug.

Remember: This is a generic notice so we don't need to write the same stuff again and again. It may only apply in parts to the specific case!

---

Opening attachment:202004111050.jpg​​ in r16239 works just fine

[Klumbumbus]

attachment:202004111050.jpg​

That definitely looks like couch mapping. The next evolution of armchair mapping? ;)

[EliasJonsson]

Replying to Klumbumbus:

attachment:202004111050.jpg​

That definitely looks like couch mapping. The next evolution of armchair mapping? ;)

Actually, was thinking about installing wheels and an electric motor on that couch just so that I never have to take another step again!

[skyper]

Please, we need your status report, see comment:1.

Replying to EliasJonsson:

Replying to Klumbumbus:

attachment:202004111050.jpg​

That definitely looks like couch mapping. The next evolution of armchair mapping? ;)

Actually, was thinking about installing wheels and an electric motor on that couch just so that I never have to take another step again!

Make sure to have enough power for all the equipment not just the engine. Maybe a solar panel and some small wind generator on the roof can help.

[EliasJonsson]

What steps will reproduce the problem?

1. Click and drag 202004111050.jpg and drop it in JOSM window

What is the expected result?

successfully imported and displayed geotagged file. By that means an image in JOSM located at the coordinates it was taken/captured and that it will display in a proper manner when clicked upon.

To be more specific, by a proper manner means a resized image that does not extend further that the edge if the screens edges.

What happens instead?

A window appears, saying "Error on file 202004111050.jpg".

Please provide any additional information below. Attach a screenshot if possible.

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-04-06 09:47:17 +0200 (Mon, 06 Apr 2020)
Build-Date:2020-04-07 01:30:48
Revision:16243
Relative:URL: ^/trunk

Identification: JOSM/1.5 (16243 en) Windows 10 64-Bit
OS Build number: Windows 10 Home 1909 (18363)
Memory Usage: 247 MB / 247 MB (65 MB allocated, but free)
Java version: 1.8.0_241-b07, Oracle Corporation, Java HotSpot(TM) Client VM
Screen: \Display0 1440x900
Maximum Screen Size: 1440x900
Dataset consistency test: No problems found

Plugins:
+ BuildingGeneralization (23)
+ auto_tools (73)
+ buildings_tools (35405)
+ editgpx (35248)
+ reltoolbox (35405)
+ utilsplugin2 (35405)

Last errors/warnings:
- W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out
- W: java.net.SocketTimeoutException: Read timed out. Cause: java.net.SocketTimeoutException: Read timed out

[EliasJonsson]

Drag 'n drop failure upon importing.

[EliasJonsson]

Replying to skyper:

Make sure to have enough power for all the equipment not just the engine. Maybe a solar panel and some small wind generator on the roof can help.

Good call! Solar wind powered powered electric couch it is then!

[simon04]

In 16284/josm:

see #19067 - ImageDisplay: tune logging

[simon04]

I cannot reproduce. It might be an issue with the amount of free memory. I've added some logging statements in r16284. Would you retry using this (or any newer version) and provide the status report again? Thanks!

[EliasJonsson]

Replying to simon04:

I cannot reproduce. It might be an issue with the amount of free memory. I've added some logging statements in r16284. Would you retry using this (or any newer version) and provide the status report again? Thanks!

At first, also I was unable to reproduce the error; importing the large image was successfull. Then I opened a large data set also with lots of gpx data. When all was downloaded I tried importing the image which then failed.
Here is the log data:

URL:https://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2020-04-12 23:55:52 +0200 (Sun, 12 Apr 2020)
Build-Date:2020-04-13 01:30:46
Revision:16284
Relative:URL: ^/trunk

Identification: JOSM/1.5 (16284 en) Windows 10 64-Bit
OS Build number: Windows 10 Home 1909 (18363)
Memory Usage: 247 MB / 247 MB (5 MB allocated, but free)
Java version: 1.8.0_241-b07, Oracle Corporation, Java HotSpot(TM) Client VM
Screen: \Display0 1440x900
Maximum Screen Size: 1440x900
Dataset consistency test: No problems found

Plugins:
+ BuildingGeneralization (23)
+ auto_tools (73)
+ buildings_tools (35405)
+ editgpx (35248)
+ reltoolbox (35405)
+ utilsplugin2 (35405)

Last errors/warnings:
- W: Update plugins - You updated your JOSM software. To prevent problems the plugins should be updated as well.  Update plugins now?
- W: Cannot lock cache directory. Will not use disk cache
- W: Abort loading of %UserProfile%\Desktop\202004111050.jpg since it might not fit into memory

[taylor.smock]

@EliasJonsson:
How are you launching JOSM?
Memory Usage: 247 MB / 247 MB (5 MB allocated, but free) seems to be a bit small. For reference, JOSM launched used the josm-latest.jnlp shows Memory Usage: 798 MB / 1820 MB (395 MB allocated, but free). If you are running from the command line, add -Xmx2048m to the java launch arguments (so java -Xmx2048m -jar ${PATH_TO_JOSM_JAR}).

Since the warning indicates that it cannot fit the 202004111050.jpg into memory, you probably need to increase the memory allotment to JOSM.

Worst case scenario for (standard) 4k images is ~25 mb per picture, so you can probably get away with using an -Xmx275m value instead of -Xmx2048m value, if memory is an issue for you, but if you can, try to use the larger memory value.

[EliasJonsson]

Replying to taylor.smock:

@EliasJonsson:
How are you launching JOSM?

Just double-clicking on the josm-lastest.jar icon on the desktop in Windwows 10.

Memory Usage: 247 MB / 247 MB (5 MB allocated, but free) seems to be a bit small. For reference, JOSM launched used the josm-latest.jnlp shows Memory Usage: 798 MB / 1820 MB (395 MB allocated, but free). If you are running from the command line, add -Xmx2048m to the java launch arguments (so java -Xmx2048m -jar ${PATH_TO_JOSM_JAR}).

The largest amount I could allocate was 1400m. Downloaded the 64-bit version of java and added -d64 -Xmx2048m. That worked better.

Since the warning indicates that it cannot fit the 202004111050.jpg into memory, you probably need to increase the memory allotment to JOSM.

Indeed. Increasing the amount of available memory worked out and now JOSM can import any sized images, inclusive the larger ones, without hassle.
Thank you for helping out finding the root of the problem.

[GerdP]

Duplicate of #14593? Can't we display a warning whenever the user runs JOSM on a 64-bit OS using a 32-bit JRE?