Thanks for you all,
I'll be trying to provide a fix for these issues this week.
Best regards,
Tamas
2013/4/2 rburhum
> Hello Tamas and Dennis,
>
> Indeed the C# bindings to not handle UTF8 characters correctly. I submitted
> a bug report about it a couple of months ago with a reproducible
Hello Tamas and Dennis,
Indeed the C# bindings to not handle UTF8 characters correctly. I submitted
a bug report about it a couple of months ago with a reproducible case.
http://trac.osgeo.org/gdal/ticket/4971
For the case that I submitted, the values for the fields in C-API GDAL are
coming out
Thanks for the quick reply.
Let's back up a bit. Just take the following two methods of the Feature class
in the OGR wrapper:
public string GetFieldAsString(int id);
public void SetField(int id, string value);
For these two the wrapper also uses no special encoding, which means that ANSI
is use
Nikhil,
You can find S52 rendering in OpenEV CVS in openev/contrib/S52.
This work is base on very old S52 specs.
Note that S57/S52 specs are in the process of been replace by S-100/S-101.
For further info e-mail me directly as S52 as little to do with GDAL.
rgds,
Sylvain.
>__
2013/4/2 Dennis Gocke
> Hi,
>
> I have a few questions regarding the C# wrapper and UTF8 encoded strings.
>
>
> This is mostly an issue when working with OGR. If I understand correctly
> strings are supposed to be encoded in UTF8 internally. Some drivers might
> not follow that rule, but most do,
Hi,
I have a few questions regarding the C# wrapper and UTF8 encoded strings.
This is mostly an issue when working with OGR. If I understand correctly
strings are supposed to be encoded in UTF8 internally. Some drivers might not
follow that rule, but most do, is that correct?
The problem tha
Hi All,
I could parse the S57 data set to my application written in writing it in
Windows C# using VS2010 but I am stuck without a module to display the nautical
charts.
Nautical charts are formatted to the NOAA S57 or S60 formats of the original
.BSB format.
Does anyone know of a DLL or plug i
