Layers are consistent cross-At5 as long as they are processed with the same version of the IMC.

Are the maps of different geometry types? Generally speaking, points of all layers will always display above lines which will always display above areas.

Are you exporting vector or raster data from Reefmaster?

What chart plotter are you trying to display it on? Some chart plotters will only pull charts for any given block from a single At5. This can lead to one thinking the issue is layering. This is only applicable to older budget chart plotters.

It's also possible, that you have a problem, if a few layers are not donut polygons, instead area polygons, that lying over each other.
But the depth polygons self are all donuts.

Hi! The depth charts I’m having troubles with are downloaded from www.dybdekart.no and are most likely created in version 10 or 12, while my own thematic charts are version 13, this might be the problem? I need to use the same at5 version for all charts?

Ok, yes my layers are mostly ordinary area polygons, however this has not caused any issues on my own depth charts. I’m hoping that usinge same version at5 on all charts will solve the issue.

Oh, i forgot to write, issues are with areas. I’m aware thar points and lines draw on top of areas. Only exporting vectordata, no raster.

Atlas Version doesn't matter.

The "Layer" Attribute is a simplification of the actual system. While the front end is consistent, it's not necessarily consistent on the back end across IMC versions.

As long as you're running on a NOS chart plotter, my expectation is that the layering issue is on the chart you didn't create.

Hi, I read the documentation for the IMC once more and are getting a bit confused. It says that the "layer" attribute is not used on the NOS OS which HDS and NSS are based on. I'm running the charts on a Simrad NSS Evo2. If the layer attribute is not used on NOS OS, how can you control the layer priority? I can see a zorder attribute on my features, but cannot find any documentation in the IMC manual for that attribute.

I don't recall that section being in there but it's sounds worded poorly and is irrelevant for most IMC users.

The "LAYER" IMC shapefile attribute controls the layering on all systems. The way it actually maps is complex.

Hi, thanks for the quick reply. Ok, then that's not the problem. I got the shapefile export of the depth maps and the isobaths have the "layer" attribute value set to 5 and the "zorder" attribute set to 0. My maps are set with the "layer" attribute set to 1 but still they are drawn below the depth map...
Any other suggestions?

Investigating why it isn't layering correctly is going to be above the level of the IMC.

It's possible to find out but it's involved and I don't have resourced hours to look at it in depth.

Contacting that data repository to see how the data is structured or to get access to the raw data may be the best path forward.

If you wish, you also can clip a small area from your problematic chart as a set of small polygons and put in into the next post. It's better to see, what you mean.

Thanks for the help guys, I think I might have figured out what's causing the issue. I'm usin FME to create custom attributes/categories and it seems that when writing to shape the attributes are encoded as "windows-1252" while the corresponding attributes that are created when exported directly from Reefmaster are encoded as "string". This is the case for amongst L_LIMIT, U_LIMIT, LAYER and COLOR (and some more). When forcing FME to format these attributes as STRING the maps are at least read correctly on my Elite emulator (they would not read at all on the emulator before I made this change even though they were read on my NSS unit). The Elite emulator however does not seem to support displaying multiple maps simultaneously so I will have to wait to test and confirm that the issue is solved until I get back home and test on my NSS unit. (On easter holidays now).