2017-04-17 13:05:40 +10:00
|
|
|
/************************************************************************
|
|
|
|
* This file has been generated automatically from *
|
|
|
|
* *
|
|
|
|
* src/core/qgsdistancearea.h *
|
|
|
|
* *
|
|
|
|
* Do not edit manually ! Edit header and run scripts/sipify.pl again *
|
|
|
|
************************************************************************/
|
|
|
|
|
|
|
|
|
|
|
|
|
2007-03-02 09:56:44 +00:00
|
|
|
|
|
|
|
class QgsDistanceArea
|
|
|
|
{
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
A general purpose distance and area calculator, capable of performing ellipsoid based calculations.
|
2017-04-18 08:11:51 +10:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
Measurements can either be performed on existing QgsGeometry objects, or using
|
|
|
|
lists of points.
|
2017-04-18 08:11:51 +10:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
If a valid ellipsoid() has been set for the QgsDistanceArea, all calculations will be
|
|
|
|
performed using ellipsoidal algorithms (e.g. using Vincenty's formulas). If no
|
|
|
|
ellipsoid has been set, all calculations will be performed using Cartesian
|
|
|
|
formulas only. The behavior can be determined by calling willUseEllipsoid().
|
2017-04-18 08:11:51 +10:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
In order to perform accurate calculations, the source coordinate reference system
|
|
|
|
of all measured geometries must first be specified using setSourceCrs().
|
2017-04-18 08:11:51 +10:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
Usually, the measurements returned by QgsDistanceArea are in meters. If no valid
|
|
|
|
ellipsoid is set, then the units may not be meters. The units can be retrieved
|
|
|
|
by calling lengthUnits() and areaUnits().
|
2007-03-02 09:56:44 +00:00
|
|
|
%End
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
%TypeHeaderCode
|
|
|
|
#include "qgsdistancearea.h"
|
|
|
|
%End
|
2007-03-02 09:56:44 +00:00
|
|
|
public:
|
2017-03-03 18:14:01 +01:00
|
|
|
|
2007-03-02 09:56:44 +00:00
|
|
|
QgsDistanceArea();
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
|
|
|
Constructor
|
|
|
|
%End
|
2012-09-03 23:49:46 +02:00
|
|
|
|
2016-02-03 16:59:49 +11:00
|
|
|
bool willUseEllipsoid() const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Returns whether calculations will use the ellipsoid. Calculations will only use the
|
|
|
|
ellipsoid if a valid ellipsoid() has been set.
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 2.14
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoid()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
2016-02-03 16:59:49 +11:00
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
void setSourceCrs( const QgsCoordinateReferenceSystem &srcCRS );
|
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Sets source spatial reference system.
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 2.2
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`sourceCrs()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
2014-01-09 17:58:57 +01:00
|
|
|
|
2016-09-15 18:26:43 +10:00
|
|
|
QgsCoordinateReferenceSystem sourceCrs() const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Returns the source spatial reference system.
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`setSourceCrs()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
2016-02-05 20:12:16 +11:00
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
bool setEllipsoid( const QString &ellipsoid );
|
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Sets the ``ellipsoid`` by its acronym. Known ellipsoid acronyms can be
|
|
|
|
retrieved using QgsEllipsoidUtils.acronyms().
|
|
|
|
Calculations will only use the ellipsoid if a valid ellipsoid has been set.
|
|
|
|
|
|
|
|
:return: true if ellipsoid was successfully set
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoid()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`willUseEllipsoid()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
2007-03-02 09:56:44 +00:00
|
|
|
|
2012-09-03 15:47:48 +02:00
|
|
|
bool setEllipsoid( double semiMajor, double semiMinor );
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Sets ellipsoid by supplied radii. Calculations will only use the ellipsoid if
|
|
|
|
a valid ellipsoid been set.
|
|
|
|
|
|
|
|
:return: true if ellipsoid was successfully set
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoid()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`willUseEllipsoid()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
2012-09-03 15:47:48 +02:00
|
|
|
|
2015-10-27 14:03:00 +11:00
|
|
|
QString ellipsoid() const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Returns ellipsoid's acronym. Calculations will only use the
|
|
|
|
ellipsoid if a valid ellipsoid has been set.
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`setEllipsoid()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`willUseEllipsoid()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
2012-09-03 23:49:46 +02:00
|
|
|
|
2014-01-27 09:22:24 +01:00
|
|
|
double ellipsoidSemiMajor() const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Returns the ellipsoid's semi major axis.
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoid()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoidSemiMinor()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoidInverseFlattening()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
|
|
|
|
2014-01-27 09:22:24 +01:00
|
|
|
double ellipsoidSemiMinor() const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Returns ellipsoid's semi minor axis.
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoid()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoidSemiMajor()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoidInverseFlattening()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
|
|
|
|
2014-01-27 09:22:24 +01:00
|
|
|
double ellipsoidInverseFlattening() const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Returns ellipsoid's inverse flattening.
|
|
|
|
The inverse flattening is calculated with invf = a/(a-b).
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoid()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoidSemiMajor()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`ellipsoidSemiMinor()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
|
|
|
|
|
|
|
double measureArea( const QgsGeometry &geometry ) const;
|
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Measures the area of a geometry.
|
2017-12-15 21:36:08 -04:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
:param geometry: geometry to measure
|
|
|
|
|
|
|
|
:return: area of geometry. For geometry collections, non surface geometries will be ignored. The units for the
|
|
|
|
returned area can be retrieved by calling areaUnits().
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 2.12
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`measureLength()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`measurePerimeter()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`areaUnits()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
|
|
|
|
|
|
|
double measureLength( const QgsGeometry &geometry ) const;
|
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Measures the length of a geometry.
|
2017-12-15 21:36:08 -04:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
:param geometry: geometry to measure
|
|
|
|
|
|
|
|
:return: length of geometry. For geometry collections, non curve geometries will be ignored. The units for the
|
|
|
|
returned distance can be retrieved by calling lengthUnits().
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 2.12
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`lengthUnits()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`measureArea()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`measurePerimeter()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
|
|
|
|
|
|
|
double measurePerimeter( const QgsGeometry &geometry ) const;
|
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Measures the perimeter of a polygon geometry.
|
2017-12-15 21:36:08 -04:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
:param geometry: geometry to measure
|
|
|
|
|
|
|
|
:return: perimeter of geometry. For geometry collections, any non-polygon geometries will be ignored. The units for the
|
|
|
|
returned perimeter can be retrieved by calling lengthUnits().
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 2.12
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`lengthUnits()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`measureArea()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`measurePerimeter()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
|
|
|
|
2017-11-14 16:07:39 +10:00
|
|
|
double measureLine( const QVector<QgsPointXY> &points ) const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Measures the length of a line with multiple segments.
|
2017-12-15 21:36:08 -04:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
:param points: list of points in line
|
|
|
|
|
|
|
|
:return: length of line. The units for the returned length can be retrieved by calling lengthUnits().
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`lengthUnits()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
|
|
|
|
2017-06-01 12:18:43 +02:00
|
|
|
double measureLine( const QgsPointXY &p1, const QgsPointXY &p2 ) const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Measures the distance between two points.
|
2017-12-15 21:36:08 -04:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
:param p1: start of line
|
|
|
|
:param p2: end of line
|
|
|
|
|
|
|
|
:return: distance between points. The units for the returned distance can be retrieved by calling lengthUnits().
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`lengthUnits()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
|
|
|
|
2017-08-26 03:34:12 +10:00
|
|
|
double measureLineProjected( const QgsPointXY &p1, double distance = 1, double azimuth = M_PI_2, QgsPointXY *projectedPoint /Out/ = 0 ) const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Calculates the distance from one point with distance in meters and azimuth (direction)
|
|
|
|
When the sourceCrs() is geographic, computeSpheroidProject() will be called
|
|
|
|
otherwise QgsPoint.project() will be called after QgsUnitTypes.fromUnitToUnitFactor() has been applied to the distance
|
|
|
|
\note:
|
|
|
|
The input Point must be in the coordinate reference system being used
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 3.0
|
2017-12-15 21:36:08 -04:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
:param p1: start point [can be Cartesian or Geographic]
|
|
|
|
:param distance: must be in meters
|
|
|
|
:param azimuth: - azimuth in radians, clockwise from North
|
|
|
|
:param projectedPoint: calculated projected point
|
|
|
|
|
|
|
|
:return: distance in mapUnits
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`sourceCrs()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`computeSpheroidProject()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
2012-09-03 23:49:46 +02:00
|
|
|
|
2016-07-17 14:56:05 +10:00
|
|
|
QgsUnitTypes::DistanceUnit lengthUnits() const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Returns the units of distance for length calculations made by this object.
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 2.14
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`areaUnits()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
2016-02-05 20:12:16 +11:00
|
|
|
|
Fix project unit confusion (pt 3): add area unit settings with a
ton of available area units (eg m2, km2, mi2, ft2, yd2, ha, ac,
etc)
Adds a new option in both the QGIS setting and project properties to
set the units used for area measurements. Just like the distance
setting, this defaults to the units set in QGIS options, but can
then be overridden for specific projects.
The setting is respected for area calculations in:
- Attribute table field update bar
- Field calculator calculations
- Identify tool derived length and perimeter values
Also adds unit tests to ensure that area calculated by attribute table
update bar, field calculator and identify tool are consistent wrt
ellipsoidal calculations and area units.
TODO: make measure tool respect area setting
(refs #13209, #4252 and fixes #12939, #2402, #4857)
2016-02-15 07:25:32 +11:00
|
|
|
QgsUnitTypes::AreaUnit areaUnits() const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Returns the units of area for areal calculations made by this object.
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 2.14
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`lengthUnits()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
|
|
|
|
2017-11-14 16:07:39 +10:00
|
|
|
double measurePolygon( const QVector<QgsPointXY> &points ) const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Measures the area of the polygon described by a set of points.
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
|
|
|
|
2017-06-01 12:18:43 +02:00
|
|
|
double bearing( const QgsPointXY &p1, const QgsPointXY &p2 ) const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Computes the bearing (in radians) between two points.
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
Fix project unit confusion (pt 3): add area unit settings with a
ton of available area units (eg m2, km2, mi2, ft2, yd2, ha, ac,
etc)
Adds a new option in both the QGIS setting and project properties to
set the units used for area measurements. Just like the distance
setting, this defaults to the units set in QGIS options, but can
then be overridden for specific projects.
The setting is respected for area calculations in:
- Attribute table field update bar
- Field calculator calculations
- Identify tool derived length and perimeter values
Also adds unit tests to ensure that area calculated by attribute table
update bar, field calculator and identify tool are consistent wrt
ellipsoidal calculations and area units.
TODO: make measure tool respect area setting
(refs #13209, #4252 and fixes #12939, #2402, #4857)
2016-02-15 07:25:32 +11:00
|
|
|
|
2016-07-17 14:56:05 +10:00
|
|
|
static QString formatDistance( double distance, int decimals, QgsUnitTypes::DistanceUnit unit, bool keepBaseUnit = false );
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Returns an distance formatted as a friendly string.
|
2017-12-15 21:36:08 -04:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
:param distance: distance to format
|
|
|
|
:param decimals: number of decimal places to show
|
|
|
|
:param unit: unit of distance
|
|
|
|
:param keepBaseUnit: set to false to allow conversion of large distances to more suitable units, e.g., meters to
|
|
|
|
kilometers
|
|
|
|
|
|
|
|
:return: formatted distance string
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 2.16
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`formatArea()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
2007-03-02 09:56:44 +00:00
|
|
|
|
Fix project unit confusion (pt 3): add area unit settings with a
ton of available area units (eg m2, km2, mi2, ft2, yd2, ha, ac,
etc)
Adds a new option in both the QGIS setting and project properties to
set the units used for area measurements. Just like the distance
setting, this defaults to the units set in QGIS options, but can
then be overridden for specific projects.
The setting is respected for area calculations in:
- Attribute table field update bar
- Field calculator calculations
- Identify tool derived length and perimeter values
Also adds unit tests to ensure that area calculated by attribute table
update bar, field calculator and identify tool are consistent wrt
ellipsoidal calculations and area units.
TODO: make measure tool respect area setting
(refs #13209, #4252 and fixes #12939, #2402, #4857)
2016-02-15 07:25:32 +11:00
|
|
|
static QString formatArea( double area, int decimals, QgsUnitTypes::AreaUnit unit, bool keepBaseUnit = false );
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Returns an area formatted as a friendly string.
|
2017-12-15 21:36:08 -04:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
:param area: area to format
|
|
|
|
:param decimals: number of decimal places to show
|
|
|
|
:param unit: unit of area
|
|
|
|
:param keepBaseUnit: set to false to allow conversion of large areas to more suitable units, e.g., square meters to
|
|
|
|
square kilometers
|
|
|
|
|
|
|
|
:return: formatted area string
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 2.14
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`formatDistance()`
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
Fix project unit confusion (pt 3): add area unit settings with a
ton of available area units (eg m2, km2, mi2, ft2, yd2, ha, ac,
etc)
Adds a new option in both the QGIS setting and project properties to
set the units used for area measurements. Just like the distance
setting, this defaults to the units set in QGIS options, but can
then be overridden for specific projects.
The setting is respected for area calculations in:
- Attribute table field update bar
- Field calculator calculations
- Identify tool derived length and perimeter values
Also adds unit tests to ensure that area calculated by attribute table
update bar, field calculator and identify tool are consistent wrt
ellipsoidal calculations and area units.
TODO: make measure tool respect area setting
(refs #13209, #4252 and fixes #12939, #2402, #4857)
2016-02-15 07:25:32 +11:00
|
|
|
|
2016-07-17 14:56:05 +10:00
|
|
|
double convertLengthMeasurement( double length, QgsUnitTypes::DistanceUnit toUnits ) const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Takes a length measurement calculated by this QgsDistanceArea object and converts it to a
|
|
|
|
different distance unit.
|
2017-12-15 21:36:08 -04:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
:param length: length value calculated by this class to convert. It is assumed that the length
|
|
|
|
was calculated by this class, ie that its unit of length is equal to lengthUnits().
|
|
|
|
:param toUnits: distance unit to convert measurement to
|
|
|
|
|
|
|
|
:return: converted distance
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`convertAreaMeasurement()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 2.14
|
|
|
|
%End
|
2016-02-05 20:12:16 +11:00
|
|
|
|
Fix project unit confusion (pt 3): add area unit settings with a
ton of available area units (eg m2, km2, mi2, ft2, yd2, ha, ac,
etc)
Adds a new option in both the QGIS setting and project properties to
set the units used for area measurements. Just like the distance
setting, this defaults to the units set in QGIS options, but can
then be overridden for specific projects.
The setting is respected for area calculations in:
- Attribute table field update bar
- Field calculator calculations
- Identify tool derived length and perimeter values
Also adds unit tests to ensure that area calculated by attribute table
update bar, field calculator and identify tool are consistent wrt
ellipsoidal calculations and area units.
TODO: make measure tool respect area setting
(refs #13209, #4252 and fixes #12939, #2402, #4857)
2016-02-15 07:25:32 +11:00
|
|
|
double convertAreaMeasurement( double area, QgsUnitTypes::AreaUnit toUnits ) const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Takes an area measurement calculated by this QgsDistanceArea object and converts it to a
|
|
|
|
different areal unit.
|
2017-12-15 21:36:08 -04:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
:param area: area value calculated by this class to convert. It is assumed that the area
|
|
|
|
was calculated by this class, ie that its unit of area is equal to areaUnits().
|
|
|
|
:param toUnits: area unit to convert measurement to
|
|
|
|
|
|
|
|
:return: converted area
|
|
|
|
|
2017-12-05 20:04:14 -04:00
|
|
|
.. seealso:: :py:func:`convertLengthMeasurement()`
|
2017-12-15 10:36:55 -04:00
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 2.14
|
|
|
|
%End
|
Fix project unit confusion (pt 3): add area unit settings with a
ton of available area units (eg m2, km2, mi2, ft2, yd2, ha, ac,
etc)
Adds a new option in both the QGIS setting and project properties to
set the units used for area measurements. Just like the distance
setting, this defaults to the units set in QGIS options, but can
then be overridden for specific projects.
The setting is respected for area calculations in:
- Attribute table field update bar
- Field calculator calculations
- Identify tool derived length and perimeter values
Also adds unit tests to ensure that area calculated by attribute table
update bar, field calculator and identify tool are consistent wrt
ellipsoidal calculations and area units.
TODO: make measure tool respect area setting
(refs #13209, #4252 and fixes #12939, #2402, #4857)
2016-02-15 07:25:32 +11:00
|
|
|
|
2017-08-26 03:34:12 +10:00
|
|
|
QgsPointXY computeSpheroidProject( const QgsPointXY &p1, double distance = 1, double azimuth = M_PI_2 ) const;
|
2017-04-17 13:05:40 +10:00
|
|
|
%Docstring
|
2017-12-15 10:36:55 -04:00
|
|
|
Given a location, an azimuth and a distance, computes the
|
|
|
|
location of the projected point. Based on Vincenty's formula
|
|
|
|
for the geodetic direct problem as described in "Geocentric
|
|
|
|
Datum of Australia Technical Manual", Chapter 4.
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. note::
|
|
|
|
|
|
|
|
code (and documentation) taken from rttopo project
|
2017-12-15 10:36:55 -04:00
|
|
|
https://git.osgeo.org/gogs/rttopo/librttopo
|
|
|
|
- spheroid_project.spheroid_project(...)
|
|
|
|
- Valid bounds checking for degrees (latitude=+- 85.05115) is based values used for
|
|
|
|
-> 'WGS84 Web Mercator (Auxiliary Sphere)' calculations
|
|
|
|
--> latitudes outside these bounds cause the calculations to become unstable and can return invalid results
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
.. versionadded:: 3.0
|
2017-12-15 21:36:08 -04:00
|
|
|
|
2017-12-15 10:36:55 -04:00
|
|
|
:param p1: - location of first geographic (latitude/longitude) point as degrees.
|
|
|
|
:param distance: - distance in meters.
|
|
|
|
:param azimuth: - azimuth in radians, clockwise from North
|
|
|
|
|
|
|
|
:return: p2 - location of projected point as longitude/latitude.
|
2017-04-17 13:05:40 +10:00
|
|
|
%End
|
2017-04-17 11:06:30 +02:00
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
};
|
2014-05-27 23:22:50 +02:00
|
|
|
|
|
|
|
|
2017-04-17 13:05:40 +10:00
|
|
|
/************************************************************************
|
|
|
|
* This file has been generated automatically from *
|
|
|
|
* *
|
|
|
|
* src/core/qgsdistancearea.h *
|
|
|
|
* *
|
|
|
|
* Do not edit manually ! Edit header and run scripts/sipify.pl again *
|
|
|
|
************************************************************************/
|