This object is in archive!
Save and restore config for calibration of pictures
Completed
Hello locus help,
I have already ask at the german forum, but it seems nobody has an answers. That's why I ask it again in english.
Is it possible to save the calibration points of an image and load them again if necessary? If necessary also with the TotalCommander and text editor - if you know where Locus stores it. Because Locus only remembers the calibration points of the last import.
Background: I have some pictures (from a proprietary GIS application at work, where you can only export image files) that I want to get into Locus. I have several different maps, each with exactly the same dimensions.
I am grateful for every tip - thank you!
VG Peter
I like this idea 
Good day Peter,
this is currently not possible. On-board calibrator store it's internal configuration in non-readable binary format so no save & restore or manual edit is possible.
This is quite unusual use-case to be true. Are we talking here about one-time calibration of multiple images or about repetitive work you do again and again? I may rewrite system from binary format to text format so it should be possible to edit it manually, but I needs to know that the work worth it. Usually it's best if more people find some improvement useful, which most probably won't be this case :).
Menion
Good day Peter,
this is currently not possible. On-board calibrator store it's internal configuration in non-readable binary format so no save & restore or manual edit is possible.
This is quite unusual use-case to be true. Are we talking here about one-time calibration of multiple images or about repetitive work you do again and again? I may rewrite system from binary format to text format so it should be possible to edit it manually, but I needs to know that the work worth it. Usually it's best if more people find some improvement useful, which most probably won't be this case :).
Menion
Morning Menion,
wow - you are very fast.
Yes, it would be a repetitive work.
Around every month few "maps" (tiles of a bigger area).
Best regards Peter
Morning Menion,
wow - you are very fast.
Yes, it would be a repetitive work.
Around every month few "maps" (tiles of a bigger area).
Best regards Peter
Good day Peter,
hmm oki, in next version will be in top menu option to save & restore calibration configuration over text file. Try it and let me know how it works. It will need some work on your side anyway.
Prepare one calibration, then save it as template. In text editor, you will have to modify generated XML file (saved in Locus/export) to support also other images with same configuration.
For now, I believe that usable solution with potential to improve, if there will be more interest.
Good day Peter,
hmm oki, in next version will be in top menu option to save & restore calibration configuration over text file. Try it and let me know how it works. It will need some work on your side anyway.
Prepare one calibration, then save it as template. In text editor, you will have to modify generated XML file (saved in Locus/export) to support also other images with same configuration.
For now, I believe that usable solution with potential to improve, if there will be more interest.
Hi Menion,
that sounds perfect!
Some xml work is no problem for me.
I will try and report.
Many thanks.
Peter
Hi Menion,
that sounds perfect!
Some xml work is no problem for me.
I will try and report.
Many thanks.
Peter
One question: will it be available in the official version or only in the beta?
BR Peter
One question: will it be available in the official version or only in the beta?
BR Peter
Hello,
if you are using Beta versions = even better. In next Beta version this will definitely be ready for testing!
Menion
Hello,
if you are using Beta versions = even better. In next Beta version this will definitely be ready for testing!
Menion
Installed version 3.32.2.4 BETA, but the menu "... \ Load configuration/Save configuration" is missing.
Installed version 3.32.2.4 BETA, but the menu "... \ Load configuration/Save configuration" is missing.
Maybe your version is too old.In the current version 3.32.2.7 beta there are options (look at the three dotsin the right top corner of the calibrator window).I haven't testet the loading already, but saving is working and the xml filelooks fine.
Remark: I can't answer on my phone chrome browser (leave a comment --> locked), but on chrome on desktop it's working!?
Maybe your version is too old.In the current version 3.32.2.7 beta there are options (look at the three dotsin the right top corner of the calibrator window).I haven't testet the loading already, but saving is working and the xml filelooks fine.
Remark: I can't answer on my phone chrome browser (leave a comment --> locked), but on chrome on desktop it's working!?
Thanks for the help. Now everything works.
I suggest saving the configuration file in the \Locus\mapItems\calibrated_mapset folder.
I propose the name of the configuration file to do the same as the name of the calibrated card.
By the way, why after creating a calibrated map the folder \Locus\data\import is not cleared? It takes up a lot of space and it seems to me never again is used.
Thanks for the help. Now everything works.
I suggest saving the configuration file in the \Locus\mapItems\calibrated_mapset folder.
I propose the name of the configuration file to do the same as the name of the calibrated card.
By the way, why after creating a calibrated map the folder \Locus\data\import is not cleared? It takes up a lot of space and it seems to me never again is used.
Hello Menion,
I still owe you a final answer: great work!
The function works exactly the way I wished it to. For my part I would not have needed the export of the map, but now I see an advantage e.g. for all those who want to transfer the calibration 1:1 to a second device.
For me it works perfectly: after loading the calibration file, the user can select another/new card. Even if the user only load the calibration file - without having the exported map in the same folder - the feature loads the map's base points without complaint (and with a discreet warning that there is a problem with the image file). The user can then load a new map: perfect!
Regarding Vyacheslav's suggestions: using the name of the map would only work if the user have already loaded the file as a map once. But since the user can export the calibration file already before (which I think is a good thing), one could at most use the name of the image file. Since this file name is not alltime really meaningful (e.g. from a photo taken with the mobile phone camera from a display board), I would leave the configuration file name as you have implemented it. I renamed the exported files e.g. with the file explorer afterwards. I think this is sufficient for most users completely.
Please don't delete the source files after the import unasked , for my feeling this wouldn't correspond to any expected behaviour. I could imagine that the user can set a checkmark when importing if he wants to have the source files deleted.
So again: thank you very much!
Many greetings
Peter
Hello Menion,
I still owe you a final answer: great work!
The function works exactly the way I wished it to. For my part I would not have needed the export of the map, but now I see an advantage e.g. for all those who want to transfer the calibration 1:1 to a second device.
For me it works perfectly: after loading the calibration file, the user can select another/new card. Even if the user only load the calibration file - without having the exported map in the same folder - the feature loads the map's base points without complaint (and with a discreet warning that there is a problem with the image file). The user can then load a new map: perfect!
Regarding Vyacheslav's suggestions: using the name of the map would only work if the user have already loaded the file as a map once. But since the user can export the calibration file already before (which I think is a good thing), one could at most use the name of the image file. Since this file name is not alltime really meaningful (e.g. from a photo taken with the mobile phone camera from a display board), I would leave the configuration file name as you have implemented it. I renamed the exported files e.g. with the file explorer afterwards. I think this is sufficient for most users completely.
Please don't delete the source files after the import unasked , for my feeling this wouldn't correspond to any expected behaviour. I could imagine that the user can set a checkmark when importing if he wants to have the source files deleted.
So again: thank you very much!
Many greetings
Peter
Hello guys,
Peter, thanks for a positive reaction, appreciate your feedback.
I also thought that export together with photo will be useful. It is not always obvious where the photo is stored so in this case, it's all at one place.
About content of "import" folder: content here is automatically generated when data are loaded from the mapItems directory. This is an old problem in the app, that this directory is increasing, but the content is not automatically deleting. You may try to delete it manually, but the result may not be perfect, so if this is not a problem, don't do it :).
So task completed, perfect.
Hello guys,
Peter, thanks for a positive reaction, appreciate your feedback.
I also thought that export together with photo will be useful. It is not always obvious where the photo is stored so in this case, it's all at one place.
About content of "import" folder: content here is automatically generated when data are loaded from the mapItems directory. This is an old problem in the app, that this directory is increasing, but the content is not automatically deleting. You may try to delete it manually, but the result may not be perfect, so if this is not a problem, don't do it :).
So task completed, perfect.
Replies have been locked on this page!