.. _doxcsid-interface_p1_1_1_camera_sdk_1_1_i_stored_image_handle_1a739c0e51c4c0ce198c7260871c51ac5a:

IStoredImageHandle.RequestTileAsync Method
++++++++++++++++++++++++++++++++++++++++++

Definition
""""""""""

*Namespace:* ``P1.CameraSdk``

Request a *tile* : a (scaled) crop of the full image

.. ref-code-block:: csharp
	:class: doxyrest-overview-code-block

    public void RequestTileAsync(:ref:`TileRequest<doxcsid-class_p1_1_1_camera_sdk_1_1_tile_request>` tileArguments);

Tiles are a cropped and scaled jpeg encoded previews of the full image. The camera takes the requested crop of the image, scales it and, optionally, converts it to jpeg.

The crop is defined in full image coordinates, meaning the pixel range of the full (visible) image dimensions. Origo is upper left corner. Any scaling is applied *after* cropping, meaning that if the crop dimension is 100 px, scaling by 0.5 results in an output image that is ~50 px.

This method is asynchronous and will return immediately. The requested tile object is returned by a notification. To retrieve the object, you must listen for the :ref:`EventType.CameraTileReady <doxcsid-class_p1_1_1_camera_sdk_1_1_event_type_1a908c1d34ddeedfdb73052b23ff9c9916>` notification, *before* calling this method. Note that this notification :ref:`EventType <doxcsid-class_p1_1_1_camera_sdk_1_1_event_type>` is shared with incoming *previews*.

Note that the camera might not (and will likely not), give the exact crop you requested. The resulting might differ a few pixels in offset or size. This is due performance optimizations in the image conversion pipeline. Speed is favoured over precision.



.. rubric:: Parameters:

.. list-table::
	:widths: 20 80

	*
		- tileArguments

		- Specification of requested tile.



.. rubric:: See also:

:ref:`RequestPreviewAsync(ImageFormat) <doxcsid-interface_p1_1_1_camera_sdk_1_1_i_stored_image_handle_1a3e0b063cbfc935126303890b2cf93c40>`