Discuss Photo mapping page here:
Memory Problems with Photo Mapping
I hit some fairly chronic memory problems when trying to do Photo Mapping in JOSM.
First time I tried, it crashed (well repeatedly warned of low memory and refused to do anything else), meaning I lost my work. But since then I've been more cautious, resizing all my photos to a miniscule 300x200, and only opening about 15 at once. Still it runs out of memory after using it for a while, requiring JOSM to be restarted.
Hmmm... I guess this would be the bug (and fix!?) : http://josm.openstreetmap.de/ticket/526
minor? Isn't anybody doing photo mapping?? Maybe I've just got less memory than everyone else :-(
-- Harry Wood 16:39, 3 January 2008 (UTC)
- OK looks like Frederick fixed it very recently (10th Dec 2007 bug #84). So anyone seeing this still, just download the latest JOSM. Seems to be working for me-- Harry Wood 21:42, 3 January 2008 (UTC)
Distinguishing the different time stamps
Photos can have several timestamps.
- EXIF timestamp - specific to certain formats like JPG, embedded inside a photo
- Filesystem level timestamp - A generic file timestamp most file systems have.
The article should distinguish the two.
- Which one does JOSM use? Is it configurable? Is it both?
- Explain that filesystem timestamps can easily be lost in certain transfer methods. (Which? mass storage? MTP? HTTP?)
It appears audio mapping only relies on filesystem level timestamps and audio files rarely have embedded timestamps, but I need to dig deeper to be sure.
General landscape photos should be noted in OSM?
Let's say User A leaves all trails and walks directly through the woods from point B to C taking pictures every 300 paces at coordinates D1/D2 etc. (i.e., NOT points of interest) and puts them on the Internet at URLs E, F, G in the Public Domain.