| 1 | = Support for measured geometries in drivers = |
| 2 | |
| 3 | The support for measured geometries in drivers has been implemented. |
| 4 | |
| 5 | However, it will take some time for the support to be implemented / work in production ready quality. |
| 6 | |
| 7 | On this page the work is described. |
| 8 | |
| 9 | == Memory == |
| 10 | |
| 11 | === Status === |
| 12 | |
| 13 | * Implemented, no known issues |
| 14 | |
| 15 | === Existing tests === |
| 16 | |
| 17 | * pass |
| 18 | |
| 19 | === New tests === |
| 20 | |
| 21 | * swig/perl/t/00-measures-02.t pass without skips |
| 22 | |
| 23 | |
| 24 | == ESRI Shapefile == |
| 25 | |
| 26 | === Status === |
| 27 | |
| 28 | * Implemented |
| 29 | * See discussion on the list: when XYM or, especially, XYZM shapefiles a opened, the result should actually be XY or XYZ if M is not used. |
| 30 | |
| 31 | === Existing tests === |
| 32 | |
| 33 | * test_ogrogr_py skips three tests |
| 34 | |
| 35 | === New tests === |
| 36 | |
| 37 | * swig/perl/t/00-measures-03.t pass without skips |
| 38 | |
| 39 | == PostgreSQL == |
| 40 | |
| 41 | === Status === |
| 42 | |
| 43 | * Implemented |
| 44 | * The driver often uses the numeric dimension (2,3,4) to determine the geometry flags (Z,M) and 3 is ambiguous since it can be XYM or XYZ, the situation probably causes bugs |
| 45 | |
| 46 | === Existing tests === |
| 47 | |
| 48 | * pass |
| 49 | |
| 50 | === New tests === |
| 51 | |
| 52 | * swig/perl/t/00-measures-04.t pass without skips |