
On Fri, Aug 16, 2013 at 6:38 PM, Nick Hughes <nixon8890@gmail.com> wrote:
On Fri, Aug 16, 2013 at 4:25 PM, Malcolm Herring < malcolm.herring@btinternet.com> wrote:
On 16/08/2013 20:45, Nick Hughes wrote:
Do you happen to know how much of the original data is retained and/or milage this convertor has seen?
It converts all the S57 objects & attributes within the ENC file, with the option to selectively filter. The converter is an unfinished project, in that the line/area object processing is incomplete. Since I am in the the process of porting searender to Java, I have stopped work on the original, with the long-term aim of doing direct 8211-OSM conversion. However, the renderer must come first!
The only mileage s57toosm has seen is my testing it with random NOAA, Dutch RWS & German WSV charts.
Ok, how far along is the Java port?
I converted one NOAA chart and opened the OSM.xml with JOSM. Apologies if I'm a bit new to this, I'm usually developing kernel code. It was just a bunch of dots representing nodes. There were no icons for each node, which I suspect is correct behavior. There was no information on depth soundings or buoy pathways. So I'm suspecting that the converter needs enhancements in this area?
FYI I saw the "all" option. I tested "ways" and JOSM has issues reading the OSM file.
I will start by reading up on S-57 and ISO 8211.
Thanks again, Nick