Thanks Malcom! It seems the root cause of all my problems is taking the shortcut and using the NOAA shape files instead of original S-57 charts. I was lured to it by apparent simplicity and shp-to-osm.jar being just the right tool to do this translation.
I'll scarp this effort, and would proceed to direct conversion from S-57 to OSM. Once that is done would contemplate the import related issues. Can you e-mail me the pointers to your S-57 to OSM utility please? Thanks a lot, Sailor Jerry On Thu, Jan 10, 2013 at 4:25 AM, Malcolm Herring <[email protected]> wrote: > On 10/01/2013 00:47, Sailor Jerry wrote: >> Would greatly appreciate your feedback. >> > Jerry, > > Thanks for your prompt action. I have had a look through your OSM file > and have noted the following problems: > > 1. The master-slave relationships between objects have been lost. This > means that multiple nodes with the same coordinates are generated, one > each for buoy, light, topmark, fog signal, etc. I have looked at the > NOAA S-57 ENC file for part of SF Bay (US5CA13M.000 - Candlestick Point > to Angel Island) and these relationships are encoded, so either the > shape file generation or your OSM conversion must have ignored these. > > 2. Attributes not present in the ENC file encodings are present in your > OSM file: e.g. height and multiple attributes for lights. Your OSM file > has these present, but with values of zero. These are illogical values! > > 3. Attributes present in the ENC file encodings are not present in your > OSM file: e.g. buoy shapes and categories. > > 4. Overly long names. The value of "seamark:name" gets rendered on the > map, so it is important to use this tag sparingly and keep values as > short as possible to avoid map clutter. In particular buoy names should > be limited to the identification actually painted on the buoy, which is > usually just a number. The names on most other objects should be absent > altogether, particularly minor lights & beacons. > > I have uploaded the OSM file generated from the ENC file plus your file > cropped to the same area. Please compare these two. See: > https://sourceforge.net/projects/openseamap/files/Archive.zip > > I have written a small utility to make OSM files from ENC files. It > requires as input the output of a gdal.org utility "8211view". The new > version of our JOSM plugin will have this built in, but there are still > many months work before that will be available. If you want to try my > existing tool, PM me & I will explain the messy details. > > Regards, > Malcolm > > > > ------------------------------------------------------------------------------ > Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, > MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current > with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft > MVPs and experts. ON SALE this month only -- learn more at: > http://p.sf.net/sfu/learnmore_122712 > _______________________________________________ > OpenSeaMap-develop mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/openseamap-develop _______________________________________________ Imports mailing list [email protected] http://lists.openstreetmap.org/listinfo/imports
