id summary reporter owner description type status priority milestone component version severity resolution keywords cc 3175 BSB driver to interpret PLY border polygon records at a header vadp warmerdam "Current BSB driver does not interpret border polygon records (PLY) at a KAP file header. Hence a resulting image contains non-chart raster data, mostly -- white chart borders. All PLY records at BSB header define an external border of a usable chart data area at BSB raster (navigabve boundaries). Each PLY record describes a node of this polygon. A format to PLY record is: {{{ PLY/,, }}} where is a sequential number of a polygon node; , are the coordinates of a node; Here is a sample of PLY record set: {{{ PLY/1,42.848493354,17.669935397 PLY/2,42.848476901,17.833244816 PLY/3,42.848498863,18.310012913 PLY/4,42.750101633,18.310063433 PLY/5,42.583347680,18.309925613 PLY/6,42.519703886,18.309939725 PLY/7,42.519743095,18.000004138 PLY/8,42.519736633,17.669913981 PLY/9,42.583380432,17.670003492 PLY/10,42.666775490,17.670020630 PLY/11,42.750096134,17.670037729 }}} Latitude, longtitude values are given according to local chart's datum, so they must be altered according to DTM record content to bring them into WGS84 (see ticket [http://trac.osgeo.org/gdal/ticket/3172 #3172])" enhancement closed normal closed_because_of_github_migration GDAL_Raster unspecified normal wontfix bsb hamish manimaul schwehr