Discrepancy between Explore GSV dimensions and static API dimensions

[misaugstad]

Brief description of problem/feature

The GSV canvas on the Explore page is 720 x 480, but it seems like the max size you can get from the static GSV API is 640 x 480. Any time we use static GSV, we have been assuming that we can use the canvas_x and canvas_y parameters that we saved from where the user placed the label on their canvas. But if the label was placed on the rightmost area on the Explore page, it's location won't be shown on the smaller static image. What does this impact:

1. The URL that we provide through our /attributesWithLabels endpoint to download imagery tries to download larger images than are possible. We know that this is being used by the tool that Chu made for Devon and I to resolve disagreements.
2. The thumbnail images in Gallery can have labels spilling of the edge, already captured in issue #2608

It's not entirely clear whether the image is just getting cut off on the left, or if we are cutting off 30 pixels from each side. Need to investigate a bit!

Also I think that Validate is using 720 x 440 instead of 480..? So maybe we want to resize Validate so that it can show labels that were placed around the bottom of the screen on Explore. Though I don't think that this is as important, nor as difficult to fix.

Potential solution(s)

I think that we may also store the pitch and heading for where the user would be looking if they were looking at the label head on. We could center the label on the images instead of trying to make it look like it did for the original labeler.

Or we might just try to simulate a slight pan to the side for labels that are right on the edge of the image, so that we can make sure that the image that gets downloaded from static SV actually shows the label.

[misaugstad]

Now that the UI automatically resizes to fill the browser, I wonder if it would be worthwhile to resize the Explore and Validate windows to match the dimensions that we can query from the GSV static API?