#16649 closed defect (needinfo)
Photomapping: "Error on file" even though JOSM can load
Reported by: | anonymous | Owned by: | anonymous |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core image mapping | Version: | tested |
Keywords: | template_report | Cc: |
Description
What steps will reproduce the problem?
This does not happen on all computers.
- Take geotagged photos using osmand (osmand redirects to oneplus 5 camera)
- Move to computer
- Load into JOSM
What is the expected result?
Everytime you click on a image it loads
What happens instead?
Sometimes the image loads, other times the geotagged images box says "error on file xyz"
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: 2018-07-29 00:41:59 +0200 (Sun, 29 Jul 2018) Build-Date:2018-07-29 01:32:17 Revision:14066 Relative:URL: ^/trunk Identification: JOSM/1.5 (14066 en) Windows 7 32-Bit OS Build number: Windows 7 Professional (7601) Memory Usage: 247 MB / 247 MB (122 MB allocated, but free) Java version: 1.8.0_181-b13, Oracle Corporation, Java HotSpot(TM) Client VM Screen: \Display0 1366x768 Maximum Screen Size: 1366x768 Dataset consistency test: No problems found Last errors/warnings: - W: No configuration settings found. Using hardcoded default values for all pools.
Attachments (0)
Change History (5)
comment:1 by , 7 years ago
Owner: | changed from | to
---|---|
Status: | new → needinfo |
comment:2 by , 7 years ago
Component: | Plugin photo_geotagging → Core image mapping |
---|
comment:3 by , 7 years ago
Resolution: | → needinfo |
---|---|
Status: | needinfo → closed |
comment:4 by , 7 years ago
Hello, I have now access to my GNU/linux computer and it was suffering from the problem a a week or so ago, but now as I try to report the bug it dissapears. (Typical isn't it?)
I think it might have been due to the update, but I am not sure if it is fixed completely yet, so don't close it
comment:5 by , 7 years ago
The bug was closed because more info was needed. Until you're able to provide this information there's no reason to reopen it.
This ticket lacks a lot of needed information:
Thanks.