1. POI/Attachement – Azimut
I do not understand the azimut value 50°/15°, both photos are shot from same position looking west (270°).
(http://s30.postimg.org/luh2ohqvx/Azimut.jpg) (http://postimg.org/image/luh2ohqvx/)
2. Export question and wish
Exporting a POI with attached photo as .kmz and selected checkbox "Insert a formatted description" the POI and photo is displayed in GE well. :)
Exporting the same POI without selecting this checkbox, the size (1,4MB) of the .kmz is the same, but the photo is not displayed in GE. For what is the photo exported? Please can you explain the function of this checkbox.
Wish/question, is it possible to implement a checkbox in export dialog "compress photosize for web"?
I think for web 100KB/photo is good enough, otherwise the folder size grows unnecessary if more POI´s exported at once.
3. Photo-POI
When I delete an opened POI, a checkbox is visible "Delete also files (photo) in memory". :)
If I want to delete more POI´s at once, this checkbox is not available and only the POI is deleted. :(
1. hard to say - these azimuth values should be took from recorded GPS position. If you stand still, you probably know that GPS returns a little bit "nonsensec", so this should be the case.
2. by "Formatted description" i mean text that contain all possible values and is formatted as HTML table. You may simply export same points, once with checked and once unchecked "Formatted description" and check content in exported file or display it in Google Earth for example.
About photos - they are placed as <img src=""> HTML tag in description. So if you do not enable "Insert formatted description", photo is attached, but not visible
3. hmm quite risky isn't it? Sometimes you may have connected also photos taken not directly in Locus and I'm really not sure, if this is good idea ...
Hello menion,
thanks for your answer
Quote1. hard to say - these azimuth values should be took from recorded GPS position. If you stand still, you probably know that GPS returns a little bit "nonsensec", so this should be the case.
Is it possible for you to connect this angle to the magnetic compass? as in settings for maprotation "speed value".
The accurat angle of an photoschot is very usefull information for orientation.
most photos are taken while standing still
QuoteWish/question, is it possible to implement a checkbox in export dialog "compress photosize for web"?
I think for web 100KB/photo is good enough, otherwise the folder size grows unnecessary if more POI´s exported at once.
Can you please give me your perspective on this wish? is it possible?
Quote3. hmm quite risky isn't it? Sometimes you may have connected also photos taken not directly in Locus and I'm really not sure, if this is good idea ..
Ok i understand your consideration, on the other hand if this action is restricted to the "photo-poi" folder i see no risk.
My problem is, i cannot see which photo of this folder is used and which is not used and so the storage is filled with needless images.
Hello,
seems you are really hard-core user of points+photos in Locus. Good, because I think that this part in Locus is not the best. I still think it should be better, but because I do not use this feature or any other program (where you should play with points & photos), I really appreciate some feedback on this topic ... it's on discussion not just between me and you. What is missing, what makes better, mainly how should look like exported files etc ...
about questions:
1. - there is one big problem - I do not know exact time, when you press "take photo button". So I do not know exact time, when I should take and use angle from sensors. Because when you start this feature, it's too early and when you return to Locus, it's too late.
2. checkbox on reducing size - I'll think about it, probably possible
3. removing unused photos - I have one think in my mind - some united "Clear cache" dialog, from where should be removed all unneeded files (like photos, geocache data, old cached files, etc.). I'll do something with this ..
Hello menion,
of corse i use photopoi quite often, it is helpfull tool as tourguide and secondly use is to document historical landmarks on boarderlines.
QuoteI really appreciate some feedback on this topic ... it's on discussion not just between me and you
I am also excited on comments of other users. ;)
For better understanding i played a little and noticed following:
driving with car, at the moment i press "Add new point" the values for coordinates, speed, azimut are correct and stored, but i move on, and so the values of the taken photo doesnt fit, see screenshot.
(http://s28.postimg.org/84rlctpih/Test.jpg) (http://postimg.org/image/84rlctpih/)
QuoteSo I do not know exact time, when I should take and use angle from sensors.
an idea:
if speed is less than 1m/sec
and change to screen "attachement" use magnetic compass. Store the values for azimut and coordinates at the moment "take" is pressed. Go back to normal prozess at the moment the poi is stored
if speed is more than 1m/sec, store the values for azimut and coordinates and speed at the moment "take" is pressed.
your answer for 2+3, i´ll wait patiently :)
There is one problem - "at the moment "take" is pressed." - I have no idea when take is pressed.
What you do
1. tap to add photo - I know time and also location (if GPS in Locus is on)
2. in camera, you press "Take" - and I have no idea when this happen
3. you confirm photo you took - also no idea when this happen
4. photo return to Locus and Locus attach it to point - at known time and location
So hard to help here.
About point 3 from previous discussion, today I created this screen. I'm sure it will be helpful. This dialog will be in misc > settings
(http://s27.postimg.org/k7t71v4a7/device_2014_01_04_112126.jpg) (http://postimg.org/image/k7t71v4a7/)
Quotetoday I created this screen. I'm sure it will be helpful. This dialog will be in misc > settings
Thank you, the screen looks very helpfull, i ll test it as soon as available :)
QuoteThere is one problem - "at the moment "take" is pressed." - I have no idea when take is pressed.
I think there is a little missunderstanding, i mean the "take" button in locus/POI screen/Attachement and not the take button in the camera app.
Sorry for my persistence,
current situation:
while moving (? ~5% of application use) the coords dont fit to the photo, i have the possibility to correct them with the pencil.
while standing still (? ~95% of application use) the azimuth is wrong, i dont have a possibility to correct the value
So please at least switch to magnetic compass once "Add new point" is opend.
It's still not so simple :) I'll have to think more about it ... also keep in mind, that azimuth is attached to point, not to photos, so if you took five photos on same spot, azimuth will make no sense
If you will have free evening - http://forum.locusmap.eu/index.php?topic=3613.msg25904#msg25904 ;) . I really suggest!!! to backup all your photos. Firstly you'll be able to check if Locus deleted only correct one and also just for case, if Locus delete all of them :)
Hi,
maybe exif Information could help. It holds the original time of the photo. Unfoftunately not the orientation (in my Xperia V). If Locus could remember the orientation every second (since calling the feature till submitting the photos), it could later assign the orientation to the exif timestamps. Not very clean solution, but maybe a way...
p.s. I use "photo editor" to see/change exif of photos. Developer is open to questions. https://play.google.com/store/apps/details?id=com.iudesk.android.photo.editor
QuoteFirstly you'll be able to check if Locus deleted only correct one and also just for case, if Locus delete all of them
thank you menion
after first tests, for me it works correct! :) not used photos are deleted.
@druki: agree, this should work. I already tried to check time when photo was saved, but it happen in moment, you confirm photo, not when you press "take", but your solution should work.
@balloni: thanks, good to hear
Hello menion
Quotethere is one big problem - I do not know exact time, when you press "take photo button"
after a long search, I found the open source app "Open Camera" since V1.6 it is possible to display the direction/azimuth angle on device and store this value in exifdata.
If I take a photo direct with "Open Camera" the direction is written well in exifdata,
If I take a photo with locus/POI/advanced/Take/Open Camera the direction is missing in exifdata and the altitude is wrong.
Can you please take a look on it, my which is to export geotagged photos (.kmz) with including exifdata
(http://s28.postimg.org/tvsegi8wp/image.jpg) (http://postimg.org/image/tvsegi8wp/)
Hello menion
QuoteIf I take a photo direct with "Open Camera" the direction is written well in exifdata,
If I take a photo with locus/POI/advanced/Take/Open Camera the direction is missing in exifdata and the altitude is wrong.
Can you please take a look on it, my which is to export geotagged photos (.kmz) with including exifdata
sorry for inquire, but it is important for me to know if it is possible
Ah don't be sorry. I often forget on any topics, there is quite lot of them, so remind me, even more then once in these cases ;)
I'll check this also tomorrow, anyway I'm sure there will be something I may do ...
hmm so generally is a problem wrong altitude right?
I'm just testing it and exact same place taken in time (+- minute) within Locus and directly with OpenCamera give me same altitude values, so I'm unable to reproduce your problem.
Anyway, what I think:
1) Locus set location and altitude after you take a photo over "Add photo" feauture. Anyway most of camera programs already set these values, so there is no reason, why should locus overtwrite them. So in next version, I firstly check if these values are set and if so, I'll not overwrite them (as now). This should also solve some possible problem with altitude you have
2) you also wanted to store current angle of view when you take a photo. But now I see, that it makes absolute sense, that such feature should do camera program itself, not Locus. We already discuss some possibilities, but non is perfect.
QuoteSo in next version, I firstly check if these values are set and if so, I'll not overwrite them
sounds good, i´ll test it :D
Quoteyou also wanted to store current angle of view when you take a photo. But now I see, that it makes absolute sense, that such feature should do camera program itself
so it is ;)after long search i found "open camera", this app store the current angle in exifdata, if the photo is taken direct with this app but if you take it with locus the current angle is missing.
Try it yourself, "Take" a photo and "Pick" a photo and you will see the difference in exifdata
I know I know, Locus do not store angle into EXIF. That's what we discuss here.
I just want to say, that it make sense that this value should write camera program, not Locus.
And as I see, exists "OpenCamera" program that do this, so there is no need for some workaround in Locus
Puh....i try it oncemore with other words, hope to make it understandable for you.
1. take a photo with "OC", it is stored with exif "Image Direction" in DCIM/OpenCamera. I can "Pick" it to a POI and this photo contains furthermore the "Image Direction" :) see screenshot in post #11 right below "green rectangle" and attached photo "OpenCamera"
2. start locus, add "new POI"/Attachement/Photo-Take, do it with "OC" and save it. This photo is stored without exif "Image Direction" in Locus/data/photo_poi. :( see screenshot in post #11 top right "red arrows" and attached photo "Locus+OpenCamera)
in my amateurish understanding this behavior depends on locus
ah understand, but this is a problem of OpenCamera, not Locus.
It works in a way
1. Locus send request to system: "take image and save it to xxx.jpg file"
2. You pick application, take photo and confirm
3. Locus check result and if file exists, attach it to point
4. In current version, Locus also overwrite location and altitude values. In next version this won't work and Locus write location and altitude only if it's not already set
So if in image took by Locus are missing any EXIF data, then sorry, but it's not problem of Locus, but OpenCamera program, so I suggest to contact it's developer, who should set also all EXIF data if request is from 3rd party app
Thank you very much for your description and time 8)
now i understand
I´ll contact the developer as you suggest
sure, you're welcome. Sorry it took so long till I answered exactly. Your question was clear, but I always answered on little bit different question :)