In the example provided by Adam, the image is cropped within the handler and served directly in response to the request. This will in effect crop the original image each time to serve the cropped version you are looking for. If you plan on serving the same cropped image repeatedly, then yes. I would indeed suggest that you store it and serve the cropped version directly. This will occupy more storage in total having both images in storage but have faster handler response time as it will not need to crop the image each time.
To make an informed decision on which is the best choice for you, I'd suggest trying both and comparing the additional storage space required to the additional request latency for live cropping. On Monday, June 13, 2016 at 12:22:57 PM UTC-4, Handerson Contreras wrote: > > Hello Everybody > > I have a problem trying to crop images in GAE. > > I'm using the Images API and adding parameters to the Url created by > > images.get_serving_url(key, size=None, crop=False, secure_url=None) > method, but i need to crop with a given bounding box. > > Do you know if this is possible by using get_serving_url method? > > or maybe you can give me another suggestion. > > Thanks > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/a6e0678e-f1bc-4423-bc3b-4d932a3f4004%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
