Hello zenfunk,

I can't help you with the data input (although if you are not unhappy with typing, I would recommend that you use JOSM to input your tags) but I just wanted to say that there is now support for seamark tags in the mkgmap program so some marine objects (lights and buoys) can be shown on Garmin GPS units (not sure about the plotters, they are particularly weird, but other units, eTrex, Nuvi, etc. are OK). I put together a demo map of the Baltic for the OpenSeaMap dudes and it looks good where there is actually marine stuff defined. Please contact me if you want more info on using mkgmap to create marine maps for the Garmin.

Mark

Hi,

How are you making your garmin maps, if you're using mkgmap, please post details of your problems to the mkgmap dev mailing list and we can help sort out the routing problems. Alternatively, send me a message with your email address and we can communicate directly.

Cheers,

Mark

How do you get a decent log out of a Nuvi 255? I have one and the logged points appear to be (a) locked to the existing roads (b) wide apart

Support for marine POIs is just becoming available in mkgmap so in the future
you should be able to generate Garmin marine maps directly from OSM data.

If you buy this book (not expensive) and read it (preferably twice), you will have no problems tensioning your wheel:

http://www.wheelpro.co.uk/wheelbuilding/book.php

Yes, you could say that this is a bug in mkgmap and it has been discussed a few times on the mkgmap dev mailing list. Unfortunately, there are no plans in hand for fixing this due to lack of knowledge of the Garmin data format. If we knew how to fix it, it would have been done by now.

It's not, as Richard suggests, the case that we are filtering out information. It's more that we are not putting in some missing stuff that makes the GPS recognise the presence of the junction.

I agree with the other comments that you should not adjust the OSM data to make the Garmin map work right.

Hi Rhubarb (great name!)

To get all the latest funky features in mkgmap you will need to check out the
source from SVN - see the wiki page for all the gen on what to do. I use Ubuntu and development is very easy, all you need is a recent JDK and ant. If you get
stuck post to the dev mailing list and I will answer.

To convert osm to mp use http://code.google.com/p/osm2mp/

I don't store "loads" of data locally. My current local area OSM file is about
12MB. The version control software compresses the data so well that keeping the
history is no problem. I am using git which like most "modern" version control
systems allows you to put any directory tree under version control without having to set up a repository. It makes keeping local history trivial.

I use JOSM to edit locally and then upload. I keep local copies and use a
version control program to save each major version so if it gets trashed on
the server, I still have my local copy. You don't have to be a computer wiz
to do that (but it helps!)