Sorry if this has been answered before, but I tried to figure it out on my own and couldn’t find answers, so I’m asking here.
- Style, TYP and map content
Here are some statements, this is how I understood things work. A simple yes or no (maybe the latter with an explanation) is enough
- style determines what is displayed on which zoom level; correct?
- TYP determines how things look like; correct?
Question: Does style actually change content of the map, e.g. if I don’t have a style for a certain Element, it won’t be compiled in the resulting .IMG files?
Question: If I want to change a certain format (i.e.: change the TYP file) and don’t know how to reference it, what is the easiest way? For now, I’m using the OSM editor, search for the element and look at its properties. Isn’t there an easier way? For example, I couldn’t figure out yet how to change the behaviour of POI symbols, they always appear on the highest zoom levels (most zoomed “in”).
Question: Is it OK to keep my formatting (TYP) similar (or even identical) to the original mapsource styles (given I don’t copy styles from them, creating them on my own) if I plan to publish my maps? I want to create a map that “feels” like a City Navigator so you won’t have to adapt too much.
No matter what I do, coastline always looks “edgy” in wider zoom levels. If you zoom in enough, everything looks OK. I tried to use precompiled sea from navmaps.eu but it didn’t chage anything. Is this a normal behaviour?
There are always gaps between sea tiles… sometimes just a line, but the gaps are there. - Is this OK?
Workflow / Tools
For now, I work like this:
- Change style
- Compile IMG
- Make .gmapi from IMG
- Install .gmapi
- Check results in BaseCamp
- (edit TYP, if applicable; restart BaseCamp and check again)
- if not done yet, start over from the beginning
Isn’t there a more straightforward approach? Like some sort of WYSIWYG-Editor that would allow you to test your settings (on a small sample) on the fly?
Or are there sample maps that contain (almost) all elements and compile very quickly so you can at least minimize compiling time?
Unfortunately, I couldn’t find either of those.
- Map information
I’m missing every information about my map on my Garmin Oregon 450. I’ve set all descriptive options (like almost all *name options and copyright-message), but nothing is displayed on the Garmin, not even the map name. This is OK if you have only one OSM map, but if you have several OSM maps, you can’t distinguish them.
Sorry for all those questions. I’m excited about the possibilities, but also a little lost in the complexity of the tools.