You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PROJ C++ API defines an osgeo::proj::common::UnitOfMeasure::Type enumeration with the UNKNOWN, NONE, ANGULAR, LINEAR, SCALE, TIME and PARAMETRIC values. For example the METRE is declared of the LINEAR, which is fine. But the following are more problematic:
METRE_PER_YEAR declared of type LINEAR
ARC_SECOND_PER_YEAR declared of type ANGULAR
PPM_PER_YEAR declared of type SCALE
The consequence is that METRE_PER_YEAR is created by PROJ-JNI as an Unit of type Length while it should be a unit of type Speed. Same apply to other rate of changes unit.
There is no clean fix at this time since PROJ does not provides an API for determining that a unit of measurement is actually a rate of change instead than directly the specified type. A possible workaround could be to parse the unit name.
The text was updated successfully, but these errors were encountered:
PROJ C++ API defines an
osgeo::proj::common::UnitOfMeasure::Type
enumeration with theUNKNOWN
,NONE
,ANGULAR
,LINEAR
,SCALE
,TIME
andPARAMETRIC
values. For example theMETRE
is declared of theLINEAR
, which is fine. But the following are more problematic:METRE_PER_YEAR
declared of typeLINEAR
ARC_SECOND_PER_YEAR
declared of typeANGULAR
PPM_PER_YEAR
declared of typeSCALE
The consequence is that
METRE_PER_YEAR
is created by PROJ-JNI as anUnit
of typeLength
while it should be a unit of typeSpeed
. Same apply to other rate of changes unit.There is no clean fix at this time since PROJ does not provides an API for determining that a unit of measurement is actually a rate of change instead than directly the specified type. A possible workaround could be to parse the unit name.
The text was updated successfully, but these errors were encountered: