[mkgmap-dev] Converting S-57/ENC -> Garmin Format?

Fri Aug 16 20:45:33 BST 2013

Malcolm,

I feel a bit relieved that others have some knowledge in this area.
 Interestingly enough, I'm in the New York area as the post mentions.  Your
utility claims to convert S57->OSM.  Do you happen to know how much of the
original data is retained and/or milage this convertor has seen?

I followed the thread, compiling both "ISO8211-text convertor" and "S57-OSM
convertor". You mention that "these charts have many overlapping areas, so
removal of duplicates will be necessary in the merging process". Wow, that
could be very time consuming for all the NOAA Maps even with OpenCPN (maps
change almost yearly). Any fuzzy thoughts on automating this? I recall that
mkgmap has a bunch of layering code in it. I'm wondering if that code could
help here? Would integrating searender converter into mkgmap derivative
help? Alternatively, OpenCPN seems to correctly draws layers in order from
the NOAA S57 charts, so perhaps that code would help, however it's a bit
challenging to read as it's very flat in nature.

Any fuzzy thoughts are helpful. The goal is to get the S57 ENC NOAA charts
into both OSM and Garmin retaining as much information as possible.

Thanks again,
Nick

On Fri, Aug 16, 2013 at 2:57 PM, Malcolm Herring <
malcolm.herring at btinternet.com> wrote:

> Nick,
>
> You may interested in this thread:
> http://sourceforge.net/p/openseamap/mailman/message/31270792
> Also, RheinSkipper, a regular contributor to this newsgroup, has done a
> lot of work on making marine charts with mkgmap and will doubtless share
> his experiences.
>
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://lists.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20130816/f8ca2df5/attachment.html 