boost_mirror/geometry
1
0
Fork 0
mirror of https://github.com/boostorg/geometry.git synced 2025-05-11 05:24:02 +00:00
Code Issues Packages Projects Releases Wiki Activity

[doc] Document Axis Order convention

Browse Source 
Clarifies question #427
This commit is contained in:
Mateusz Loskot 2017-10-11 20:21:20 +01:00
parent 477b502bb4
commit 658a7d99cd
1 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
doc/design_rationale.qbk
View File

@ -637,6 +637,20 @@ and modify our distance function:
Of course also the apply functions in the dispatch specializations will return a result like this. Of course also the apply functions in the dispatch specializations will return a result like this.
They have a strategy as a template parameter everywhere, making the less verbose version possible. They have a strategy as a template parameter everywhere, making the less verbose version possible.
[heading Axis Order]
This is an important note for users who develop GIS applications, require compliance with OGC
standards or use variety of coordinate reference systems (CRS).
Boost.Geometry convention is that coordinate values of 2D tuple is always given according to
mathematical axis order: X,Y. Considering GIS applications, that always means easting,northing or,
in terms of geographic coordinate system: longitude,latitude.
Boost.Geometry does not allow or respect coordinate values listed in the axis order as
specified by coordinate reference system (CRS).
In practice, users may easily adapt point types with alternate axis ordering and
specify coordinate access in order as expected by Boost.Geometry.
[heading Summary] [heading Summary]
In this design rationale, __boost_geometry__ is step by step designed using tag dispatching, In this design rationale, __boost_geometry__ is step by step designed using tag dispatching,