PROJ/src/PJ_axisswap.c, branch emscripten-build Forked from https://github.com/OSGeo/PROJ Fix warnings found by clang with new warning flags to be added in later commit 2018-05-30T09:48:28+00:00 Even Rouault even.rouault@spatialys.com 2018-05-29T20:45:18+00:00 f773897a3025438326c1131e1586d9ddae080c4f Fixes consist in: - no use of comma operator for multi statement purpose - avoid confusing comma in for loops first and third clauses - avoid implicit long to int casts by storing to long, or explicit bound checking before cast 
Fixes consist in:
- no use of comma operator for multi statement purpose
- avoid confusing comma in for loops first and third clauses
- avoid implicit long to int casts by storing to long, or explicit bound checking before cast
Partial changes for IWYU 2018-05-14T07:16:05+00:00 Kurt Schwehr schwehr@google.com 2018-05-14T07:16:05+00:00 74d082a5360b4939fcbc54fb18382b723771cafe 






Change units of axisswap to 'whatever'
2018-03-27T09:37:13+00:00

Kristian Evers
kristianevers@gmail.com

2018-03-26T22:07:24+00:00

bcd647fe82e45efd51c3a64e348b99b38c839e2b

Since units are validated during pipeline setup we need to make sure
that axisswap can be used for more than just projected outputs.





Since units are validated during pipeline setup we need to make sure
that axisswap can be used for more than just projected outputs.







Renamed PJ_IO_UNITS_RADIANS to PJ_IO_UNITS_ANGULAR
2018-01-31T15:26:57+00:00

Thomas Knudsen
thokn@sdfe.dk

2018-01-29T19:47:44+00:00

52c20a2e095c63fab6e4158c92b8995d882cbe62












axisswap initialization: avoid switch case fallthrough
2018-01-11T12:46:52+00:00

Even Rouault
even.rouault@spatialys.com

2018-01-11T11:22:24+00:00

754f62987a8035497236e2fae24cc4e9d8d91937

case without break are really confusing, and should be avoided as much
as possible IMHO.
Also error out if a unrecognized character is provided as the axis value.





case without break are really confusing, and should be avoided as much
as possible IMHO.
Also error out if a unrecognized character is provided as the axis value.







Fix breakage of previous commit (bis)
2018-01-11T12:46:38+00:00

Even Rouault
even.rouault@spatialys.com

2018-01-11T12:46:38+00:00

29916584ae00a16ef0974d419a89d6f12edecc12












Fix breakage of previous commit
2018-01-11T12:22:20+00:00

Even Rouault
even.rouault@spatialys.com

2018-01-11T12:22:20+00:00

a00d13a1fdd869596bf2f13a39f12a0ab7961fb3












PJ_axisswap.c: validate axis value. Fixes https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5073. Credit to OSS Fuzz. master only
2018-01-11T11:13:47+00:00

Even Rouault
even.rouault@spatialys.com

2018-01-11T11:13:47+00:00

d109f6e826e7a2542d7e1bd50cc62e5fa9ac373e












Allow usage of classic +axis parameter in axisswap.
2018-01-08T18:58:06+00:00

Kristian Evers
kristianevers@gmail.com

2018-01-08T10:54:54+00:00

47953f0a93cd90d0d52b74f2b2705516f018b2f1

Instead of +order the classic PROJ.4 parameter +axis can used instead.
This is mostly an inititive to simplify backwars compatibility in the
4D API. P->axis is initialized in pj_init() it can be assumed that it
is set up correctly.

+order and +axis are mutually exclusive.





Instead of +order the classic PROJ.4 parameter +axis can used instead.
This is mostly an inititive to simplify backwars compatibility in the
4D API. P->axis is initialized in pj_init() it can be assumed that it
is set up correctly.

+order and +axis are mutually exclusive.







Discern between 2D projected and 3D cartesian linear units (#732)
2018-01-08T02:41:45+00:00

Thomas Knudsen
busstoptaktik@users.noreply.github.com

2018-01-08T02:41:45+00:00

07bb446ec474cf62094070a8ea848b37c911a075