Matt,
First of all do u have an idea as to when interpolation might see an increase?
(this would solve my issues)
What i plan to do is to create an isobath shapefile from old DRdepth data which has a higher interpolation limit...then use QGIS to edit the isobath shapefile i have created....
PS...my exsisting shapefile i created is very similar to what is created by RM but i wonder if u could give advice as to setting in a couple of columns?
first of all i see the first difference is you have created a VALUE 2 column
is this how the depth areas are defined?
also can u comment on attribution of type and layer for an isobath and what appropiate setting might be?
DS

Hi Dave,
Sorry - I thought I'd answered this one but then I noticed that my reply wasn't there - not sure what happened.

The interpolation change will go into the next minor release - probably a month or so away.

Attributes for AT5 generation are described in detail in the IMC documentation, so I would suggest taking a look at that. Briefly:

• VALUE, VALUE2 are the two depth values associated with a depth area.
• LAYER refers to the Z-order of area features and is a number between 1-100 with lower numbered features rendering on top of higher numbered features.
• You will need L_LIMIT and U_LIMIT attributes that determine at which zoom level the feature is visible. We typically use 1 - 19.
• TYPE is for export to GPSMapEdit and you don't need to worry about this if you are using the IMC directly.

Another idea, which is probably easier, is to use your DD generated contours as an input to the RM map project. Save your DD contours in GPX or Humminbird native track format, and import into ReefMaster as tracks. Edit the tracks to include just the contours from your missing area(s), and add them to your project. The map will use the depth data from the contours as part of the map generation process, and fill out your missing areas.

Matt

matt
i tried ypour suggestion to export map from drdepth as gpx
and then i imported gpx file to RM but the data contains no depth information?
what did i do wrong?
it shows lots of waypoints ...
but all the data i imported to RM assests shows as( drdepth isoline )with all tracks showing 0 feet as depth??
DS

Hi Dave,
If you want, send through the DD generated GPX file to This email address is being protected from spambots. You need JavaScript enabled to view it. and I will take a look. Could be that DD doesn't include depth information, in which case my suggestion won't work - I am not that familiar with DD. Also try exporting as Humminbird tracks (.HT) to see if that works.
Matt

Do you still have the drd-files? If so, export these to csv in DrD and import in RM.

Don't think DrD gpx includes depth, but am not sure.

Martin wrote:
That will work, but it won't solve Daves problem. The DD files exported as csv files are the input files in DD - maybe logs or drawn ones. Dave will need an export of the rendered files, beause DD at this moment has a wider interpolation limit than RM.

To render with DD and exporting as a Humminbird file works. You could set in DD the min and max depth to obtain modified depth contours. Just set your view setting to iso lines and play around.

How about simply exporting the iso / contourlines from DD as a shapefile (tools - iso contour lines etc...) , then importing the shapefile into RM as a GPS asset ?

T

matt .....update.....the gpx and shp files work dont for me ....
(they dont display any depth data in tracks once imported to RM)
but i the HB (HT) extension works with proper depth info :)
thanks patiently waiting for incresed interpolation though as it will be a lot less work..
DS

Good stuff Dave. We don't ever get depth from Shapefile import, as there is no standard attribute that holds it. We would get the depth from GPX if it was in there using either Garmin or HB GPX extensions, but it seems DD does not export depth in GPX, so HT is your only option for now.

Incidentally, there is another "trick" you can use to fake depth points in a map project. Add a map boundary, and un-check "is boundary" and "show in map" but leave "provide depth" checked. Then set the depth to your known depth. This could work with a shapefile contour import, but you'd have to import the contours one-by-one (as boundaries), and set the depth for each. You don't actually need a lot of points in an empty area - just enough to "bridge the gap" between populated areas. So even a single depth point placed at the centre of a circle of points with 399m diameter could (theoretically) be enough.

The increased interpolation is coming..

I understood, as did Hubert, that you were exporting rendered files ? The isobath lines exported from DD as shapefiles contain labels indicating depths.

T

drdepth has map size limitations that RM does not ,
and being a novice with QGIS im struggling with setting attribution on my created shapefile to show isobath colors like displayed in RM isobath generation...(still working on it)
as opposed to just making map vector blue polygon background and black contour lines with depth labels overlayed.
i guess i may just need to wait for increased interpolation as matt says coming soon or figure out this attribution for my files :(
ds

Dave,

size doesn't matter. Its how you use it that makes the difference. It is a simple matter to export iso lines from an area of up to 7km x 7km, then move the export area, and export again. RM is not be without limitations either, so this kind of editing will always be a requirement if you want to construct a bathy chart for long shorelines, or massive lakes. Working in small chunks makes the workflow much faster too. If you are working with a coastal shoreline you have no choice either.
There are alternatives to QGIS if you don't get on with it, GPSMapedit does it all for you.

T