You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some maps are stalling and hitting on the right resolution isn't easy. See these 2 stalled maps:
Note we don't see output resolution until they're complete, and they probably crashed or stalled.
We should be able to calculate at least roughly what the output dimensions in pixels would look like for a given cm/px export, using the new cloud exporter.
Let's try to use the image collection bounds and the cm/px to estimate the output dimensions. We can even say that 10cm/px would result in HxW dimensions and 100 in HxW - in the dialog box where you enter the resolution.
Here is the calculation for x,y pixel dimensions in Ruby, from the exporter code:
This code is a bit tangled up but we could pull out the relevant portions into a JS function that accepts scale and a set of lat/lon bounds, and outputs x,y dimensions. This would be a great first step!
The text was updated successfully, but these errors were encountered:
Some maps are stalling and hitting on the right resolution isn't easy. See these 2 stalled maps:
Note we don't see output resolution until they're complete, and they probably crashed or stalled.
We should be able to calculate at least roughly what the output dimensions in pixels would look like for a given cm/px export, using the new cloud exporter.
Let's try to use the image collection bounds and the cm/px to estimate the output dimensions. We can even say that 10cm/px would result in HxW dimensions and 100 in HxW - in the dialog box where you enter the resolution.
Here is the calculation for x,y pixel dimensions in Ruby, from the exporter code:
https://github.com/publiclab/mapknitter-exporter/blob/db65afbbeccdecedc3c50fa43bbeea3103f3d546/lib/mapknitterExporter.rb#L66-L70
The full exact calculation can be found in this file, using the Proj4.js library to calculate
latitude,longitude => x,y
projection:https://github.com/publiclab/image-sequencer-app/blob/fad302f2d15745414bb362f28806a8568b4001c3/src/api/v2/util/converter-multiSequencer.js#L53-L61
This code is a bit tangled up but we could pull out the relevant portions into a JS function that accepts scale and a set of lat/lon bounds, and outputs x,y dimensions. This would be a great first step!
The text was updated successfully, but these errors were encountered: