Hi.

Having a few problems with editing and displaying areas above chart datum. We have a tidal range of up to 40ft here so many areas are drying. These areas show as green in Raster maps with a secondary band of green below the datum as well. The map shows as expected in Vector format. In the editing screen I cant edit the track as all the points (above datum) are green. Have updated to V1.7 and still same problem. (images attached)






What am I doing wrong.

The area below is mostly all drying at low water, the tide goes out for about 2nm.








Also is it possible to shift the height of a background map up say to -15m so it does not sit down below my drying areas in 3D?

Great software, much better than DrD.

Thanks

Ed

Hi Ed,

I'm not sure I understand the problem precisely. What exactly do you want the finished map to look like? Is this an issue with the palette for the vector/raster map, or a problem with the depths that are assigned to the shoreline? What is the issue with editing track-points with negative depths?
I have noticed an issue with some track-points becoming invisible at negative depths (looking into it now) - is this the issue?

Negative depths combined with shorelines might be a tricky area - let me know what you need and hopefully we can work out a way to do it.

Matt

Hi Matt,

Not a problem with the palette, I get the green areas in the define map view and contour/ 3D view screens (in raster mode) regardless of palette even with greyscale (see below). Is it possible to define a second palette for areas with negative depths? (have I done this without knowing?)





In the define map view editing tracks is a problem because areas with negative depth values (drying) are shaded green and impossible to work with in terms of removing bad data points or adjusting depths to match up with other data (pics 1/4 in OP). This also happens in a band in deeper water (see pic 2 in OP). Track points don't become invisible.

The green drying areas and band are only visible in contour/ 3D views if I am using raster mode, vector seems unaffected (pic 2/3 in OP, same map area just raster and vector modes). Although if I try to change from raster to vector I get bathy lines with no fill until I have regenerated the map.

I am also having problems whereby I am unable to edit single track points when I import certain .csv files. Delete the file and I can edit again. Working on a way round this though.

I attached another image which better shows what I mean about the shoreline. I have set the main shoreline (RHS) at -10m to better show what I mean. To the LHS you can sort of see an island which is set to no depth. The background image sits at 0 depth.

Many thanks

Ed

Ed,
The way we handle -ve depths for the palette is a little flaky, and something of a hangover from the raster-only days (and before editable palettes).

We have just made a maintenance release that was required for another issue, so I took the chance to remove the hard-coded green -ve depth colour scheme completely (from projects and tracks). It is still possible to get something similar though the use of a user-defined palette or by editing a user map.
I also updated the 3D view to use the lowest map depth as the shoreline depth, if this depth is < 0 (otherwise it still uses zero). This should help with the issue you are seeing.

With your shorelines, I would consider un-checking "provide depth" if the depth is variable along the edge (as it might be with a sea wall). You'll still get a boundary, but you won't get depths from it that contribute to the project.

Let me know how you go,

Matt

hi all,

im having a head scratch with contours between 0 and -1 which ive added to this post.

As the isobath below shows, the contours between -1 to +1 have been grouped together, whereas all other groups are individualy assigned a colour.





Now, if I make the coastline -3, I get the correct colour / groupings EXCEPT, once again -1 to +1 has been grouped together (see second attachment).





The 3rd screen grab shows that if i then create a user map sending over the isobaths, i get all the groupings except -1 to 0. i.e. i get -3 to -2, -2 to -1 NO -1 to 0, 0 to 1, 1 to 2 etc.



Am I doing something daft here, or is there a bug involving values -1 to 0??

hi all,

im having a head scratch with contours between 0 and -1 which ive added to this post.

As the isobath below shows, the contours between -1 to +1 have been grouped together, whereas all other groups are individualy assigned a colour.





Now, if I make the coastline -3, I get the correct colour / groupings EXCEPT, once again -1 to +1 has been grouped together (see second attachment).





The 3rd screen grab shows that if i then create a user map sending over the isobaths, i get all the groupings except -1 to 0. i.e. i get -3 to -2, -2 to -1 NO -1 to 0, 0 to 1, 1 to 2 etc.



Am I doing something daft here, or is there a bug involving values -1 to 0??

The User Map thing looks like it could be a bug - I'll look into it tomorrow and report back.

With the "grouping"; it looks like you have an AT5 palette, which uses a "nearest colour" interpolation when determining the colour for a depth range. It's possible in this case for contiguous depth ranges to share the same colour, depending on the number of colours in the palette and the spread of the depth values. It would be interesting to see if you get the same effect when using an RGB palette, which will interpolate colours over the depth range.

Matt

Hi Matt, sorry - should have mentioned it, but i've tried with several RGB pallettes and the same happens ( colour groups -1 to +1 together). I see what you are saying about the AT5 pallete but i don't think this is the cause ( ive tried different data sets with different spread of depth values, different values applied to the coastline (and not providing a depth to a coastline), & different AT5 / RGB palletes. In all cases, the contour group -1 to +1 is grouped together. After looking at the user map edit data for isobaths and seeing the group -1 to 0 missing, im thinking that perhaps something odd is going on with the way the software handles my data from 0 to -1 for vector contours??

cheers

There is an issue here with a missing isobath on one side of the zero level (the side with the issue can vary).
We're planning a maintenance release at the end of this week anyway (due to some issues with older Elite7 sonar files), so hopefully we can include a fix in for this as well.

cheers,
Matt

Sounds good - I've got quite a few tracks going over drying areas.

This issue is fixed in the latest maintenance release.

perfect....
thanks for such a quick fix! Have a nice weekend.