Create Status.json

[sashadev-sky]

References #326

Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!

• PR is descriptively titled 📑 and links the original issue above 🔗
• tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR -- or run tests locally with rake test
• code is in uniquely-named feature branch and has no merge conflicts 📁
• screenshots/GIFs are attached 📎 in case of UI updation
• ask @publiclab/reviewers for help, in a comment below

We're happy to help you get this ready -- don't be afraid to ask for help, and don't be discouraged if your tests fail at first!

If tests do fail, click on the red X to learn why by reading the logs.

Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software

Thanks!

[sashadev-sky]

@icarito @jywarren I created an endpoint here exports/:id/status and made just a button to show an example of it connecting to the UI... it just updates to the status message once:

You wanted this to be saved as a local JSON file now?

Here is an example string of the full JSON it returns:

{"bands_string":"","cm_per_pixel":5.0,"created_at":"2019-04-03T20:49:39Z","export_type":"normal","geotiff":false,"height":null,"id":1,"jpg":false,"map_id":1,"size":null,"status":"warping 2 of 2","tms":false,"updated_at":"2019-04-03T21:09:38Z","user_id":1,"width":null,"zip":false}

Note user_id is included above, so that covers the usernames @jywarren was asking about

[sashadev-sky]

(will remove the console.logs when it should be merged)

[jywarren]

So, we can probably fetch the json here, and parse it instead of a simple string response: https://github.com/publiclab/mapknitter/blob/907f5b37f81cb5fc03c1f2f98a1ae6f57fd6ec30/app/views/maps/_sidebar_exports.html.erb#L104-L113

…

On Fri, Apr 5, 2019 at 12:44 PM Sasha Boginsky ***@***.***> wrote: ***@***.**** commented on this pull request. ------------------------------ In app/views/maps/_sidebar_exports.html.erb <#483 (comment)>: > @@ -112,6 +115,26 @@ var exporting, exportResolutionSlider setInterval(exportProgress,5000) Ok will do! — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#483 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABfJwfb_4AsWeD90hkOAM9Gukesu5rEks5vd31kgaJpZM4cbhh3> .

[sashadev-sky]

@jywarren Ok this is updated! I'll clean up the code and resolve merge conflict if / when you think this is ready to merge

also in my last PR, for now updated the endpoint to mirror the old progress endpoint: export/status/:id

[sashadev-sky]

@jywarren what is my next tasks after this?

[jywarren]

oh wow, does this work now? Can you update the screenshot? Awesome, it looks good!

[jywarren]

I think next step will be to allow for it to have a remote status.json file. So, we:

1. add a remote_url column to Exports
2. check if it exists
3. if it does, we redirect requests to status to the remote URL (which'll be our external exporter)
4. we think of how the client may send a remote URL up to the MapKnitter Rails app for storage?

[jywarren]

And then, start to hook up the multiple image select to a remote exporter, if @tech4GT or @icarito are ready to receive a request soon? Even if it's not totally ready?

[sashadev-sky]

@jywarren ok you want this in this PR or a new one?

[sashadev-sky]

@jywarren I overrwrote the exportProgress method like you asked to make it call our new endpoint export/status/:id instead of export/progress/:id. You can see in gif below it makes calls to this endpoint now when you hit Run Export button.

[jywarren]

This is great. We can def. do the work on a remote status.json file in a follow-up. Is this ready to merge then? Awesome work, Sasha!!!

[sashadev-sky]

@jywarren this failed due to keyserver issue, but it's ready to merge as soon as travis is back up and running!

Just to confirm #413 or Leaflet.DistortableImage#203 is the next step?

[sashadev-sky]

@jywarren update it worked! Please answer my question above too though :) Thank you!!

[jywarren]

Awesome. Either would be a great next step!

[sashadev-sky]

@jywarren Ok to me seems like #413 is the next logical step so starting on that this week!