-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Some images cropped/cut off #39
Comments
This is one that got cut off: I'll try to make a special warpable.json for just that |
|
So, i'll run this again and let's see how it goes - if it fails in the same places, or if this was a memory error and they'll get cut off differently: |
Uh oh, that's still stuck at 3 of 25. Not sure why. Will restart it.
Here's the restarted one: https://mapknitter-exports-warps.storage.googleapis.com/1558800253/status.json |
So, on the new version. Already at number 3! |
From notes here: #23 (comment) It looks like it happens on or just before this step, because images like this are copied in wrong, and then distorted, masked, and used in the final map: |
|
So, i'd guess it's at this step, before mask generation and mask application:
It's 20 mins until the next command, but i couldn't find any errors between them, besides a lot of garbage collection:
|
Maybe we can fetch this file next time: http://export.mapknitter.org/public/warps/1558824229/w132014.png |
Actually wait. Maybe we are seeing 2 types of cutoffs here. The one in the last image is diagonal bc the error was pre-distortion, i think? But the cutoff images in the big export outputs in this comment are all completely horizontal, as if they got cut off during the final compositing step. |
That final compositing step is:
|
This is the big image cut off in the final composite: https://s3.amazonaws.com/grassrootsmapping/warpables/47243/OVPKAP-20111028-85-170_medium.jpg So, we should restart and try to catch that image in |
We can try increasing memory at https://github.com/publiclab/mapknitter-exporter-sinatra/blob/main/nolimit.xml And/or set up a try/retry block? |
We could use this as a template: https://github.com/publiclab/mapknitter/blob/c391beb4e4b27a92bb0a2c11c68bba782145416a/nolimit.xml |
Oh, actually we've already applied that. |
I see a couple edges which are not fuzzy, and so that means they were cut off partway through their composite processes.
https://mapknitter.org/maps/otter-view-park-west
I'm wondering how it happened, but it could be either a crash partway through, OR it could be that their new bounding boxes are not properly calculated and they're just cropped wrong. I'll have to check the intermediate images to be sure.
The text was updated successfully, but these errors were encountered: