Port Geocode tool back into new Capture interface, next steps

[Georjane]

@jywarren and @Tlazypanda
I think I will be picking up this issue next from publiclab/spectral-workbench.js#265

thank you

[Georjane]

Hi @Tlazypanda @TildaDares @jywarren 👋🏽

I was able to upload my first spectrum today locally.
I was trying to test the functionality of the geocoding tool on the old capture interface to compare it with the new capture/v2 version.
But I realized from this comment here that geocoding of the spectrum doesn't work anymore.
Please I would like to understand exactly what the geocode button is expected to do. Thank you

[Georjane]

I was also facing the error below when I added the geocode button from the old capture interface to the new capture v2. I tried debugging but to no avail. 😞

[Tlazypanda]

Hey @Georjane the Geocode part not working is what we are discussing on the call - the part where I mentioned that the params are not getting saved correctly on to the backend which is why it stopped working. Hence it's not included in the second version so we need to add it and get it working ✨

This error suggests that data variables passed as an argument here is actually nil, can you log the data variable here reference - https://stackoverflow.com/questions/57197682/in-decode64-undefined-method-unpack1-for-nilnilclass-nomethoderror

[jywarren]

I believe the geocode button requests a location from the browser API for location, then it tries to attach it to the form using hidden inputs with ID #lat and #lon:

spectral-workbench/app/assets/javascripts/capture.js

Line 340 in 8f89e0f

geolocate: function() {

Hope that helps! It uses a callback so the code is a little tangled, but it's not too long!

[Georjane]

Hey @Georjane the Geocode part not working is what we are discussing on the call - the part where I mentioned that the params are not getting saved correctly on to the backend which is why it stopped working. Hence it's not included in the second version so we need to add it and get it working ✨

This error suggests that data variables passed as an argument here is actually nil, can you log the data variable here reference - https://stackoverflow.com/questions/57197682/in-decode64-undefined-method-unpack1-for-nilnilclass-nomethoderror

Hi @Tlazypanda
please i have difficulties understanding this line of code $('#geotag').val('true'!=$('#geotag').val())
Thank you!

[jywarren]

I believe it's ensuring that the value is either true or false, and if it's not true it automatically defaults to false! A bit convoluted, though!

…

On Wed, Jan 19, 2022, 6:40 AM Witah Georjane ***@***.***> wrote: Hey @Georjane <https://github.com/Georjane> the Geocode part not working is what we are discussing on the call - the part where I mentioned that the params are not getting saved correctly on to the backend which is why it stopped working. Hence it's not included in the second version so we need to add it and get it working ✨ This error suggests that data variables passed as an argument here is actually nil, can you log the data variable here reference - https://stackoverflow.com/questions/57197682/in-decode64-undefined-method-unpack1-for-nilnilclass-nomethoderror Hi @Tlazypanda <https://github.com/Tlazypanda> please i have difficulties understanding this line of code $('#geotag').val('true'!=$('#geotag').val()) Thank you! — Reply to this email directly, view it on GitHub <#848 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAF6J72GYEFGPDL2T5FVQ3UW2PKLANCNFSM5L7WVJ3A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>