2005-12-30 04:56:31 +00:00
|
|
|
|
|
|
|
struct QgsRasterViewPort
|
|
|
|
{
|
2007-01-09 02:39:15 +00:00
|
|
|
%TypeHeaderCode
|
|
|
|
#include <qgsrasterviewport.h>
|
|
|
|
%End
|
|
|
|
|
2005-12-30 04:56:31 +00:00
|
|
|
/** \brief The offset from the left hand edge of the raster for the rectangle that will be drawn to screen.
|
|
|
|
* TODO Check this explanation is correc!*/
|
|
|
|
int rectXOffsetInt;
|
|
|
|
float rectXOffsetFloat;
|
|
|
|
/** \brief The offset from the bottom edge of the raster for the rectangle that will be drawn to screen.
|
|
|
|
* TODO Check this explanation is correc!*/
|
|
|
|
int rectYOffsetInt;
|
|
|
|
float rectYOffsetFloat;
|
|
|
|
/** \brief Lower left X dimension of clipped raster image in raster pixel space.
|
|
|
|
* RasterIO will do the scaling for us, so for example, if the user is zoomed in a long way, there may only
|
|
|
|
* be e.g. 5x5 pixels retrieved from the raw raster data, but rasterio will seamlessly scale the up to
|
|
|
|
* whatever the screen coordinates are (e.g. a 600x800 display window) */
|
|
|
|
double clippedXMinDouble;
|
|
|
|
/** \brief Top Right X dimension of clipped raster image in raster pixel space.
|
|
|
|
* RasterIO will do the scaling for us, so for example, if the user is zoomed in a long way, there may only
|
|
|
|
* be e.g. 5x5 pixels retrieved from the raw raster data, but rasterio will seamlessly scale the up to
|
|
|
|
* whatever the screen coordinates are (e.g. a 600x800 display window) */
|
|
|
|
double clippedXMaxDouble;
|
|
|
|
/** \brief Lower left Y dimension of clipped raster image in raster pixel space.
|
|
|
|
* RasterIO will do the scaling for us, so for example, if the user is zoomed in a long way, there may only
|
|
|
|
* be e.g. 5x5 pixels retrieved from the raw raster data, but rasterio will seamlessly scale the up to
|
|
|
|
* whatever the screen coordinates are (e.g. a 600x800 display window) */
|
|
|
|
double clippedYMinDouble;
|
|
|
|
/** \brief Top Right X dimension of clipped raster image in raster pixel space.
|
|
|
|
* RasterIO will do the scaling for us, so for example, if the user is zoomed in a long way, there may only
|
|
|
|
* be e.g. 5x5 pixels retrieved from the raw raster data, but rasterio will seamlessly scale the up to
|
|
|
|
* whatever the screen coordinates are (e.g. a 600x800 display window) */
|
|
|
|
double clippedYMaxDouble;
|
|
|
|
/** \brief Distance in pixels from clippedXMinDouble to clippedXMaxDouble. */
|
|
|
|
int clippedWidthInt;
|
|
|
|
/** \brief Distance in pixels from clippedYMinDouble to clippedYMaxDouble */
|
|
|
|
int clippedHeightInt;
|
|
|
|
/** \brief Coordinate (in geographic coordinate system) of top left corner of the part of the raster that
|
|
|
|
* is to be rendered.*/
|
|
|
|
QgsPoint topLeftPoint;
|
|
|
|
/** \brief Coordinate (in geographic coordinate system) of bottom right corner of the part of the raster that
|
|
|
|
* is to be rendered.*/
|
|
|
|
QgsPoint bottomRightPoint;
|
|
|
|
/** \brief Distance in map units from left edge to right edge for the part of the raster that
|
|
|
|
* is to be rendered.*/
|
|
|
|
int drawableAreaXDimInt;
|
|
|
|
/** \brief Distance in map units from bottom edge to top edge for the part of the raster that
|
|
|
|
* is to be rendered.*/
|
|
|
|
int drawableAreaYDimInt;
|
|
|
|
};
|
|
|
|
|