| 1 | | Dutch inland ENCs are encoded in a slightly different way than most (maritime) ENCs. They are, however, compliant with the IHO S57 3.1 specification. The difference is that in a vector record (section 7.7 of the S57 spec), a line can be encoded in two ways: |
| 2 | | one SG2D record with repeating rows or a repeating series of SG2D with one row (or even a combination thereof).[[BR]] |
| 3 | | The current (1.7.3) driver only supports the former encoding. This patch adds support for the both encodings.[[BR]] |
| | 1 | Dutch inland ENCs are encoded in a slightly different way than most (maritime) ENCs. They are, however, compliant with the IHO S57 3.1 specification. The difference is that in a vector record (section 7.7 of the S57 spec), a line or polygon feature can be encoded in more than one way: |
| | 2 | one SG2D record with repeating rows of coordinates or a repeating series of SG2D records with one row of coordinates (or even a combination thereof). |
| | 3 | The current (1.7.3) driver only supports the former encoding. This patch adds support for both encodings. |
