darrellmccauley wrote:
Thank you for the pointers. In addition to the memory errors, I have run into the endless loop mentioned in that other post.
Does the company monitor this forum? I was hoping for input on my memory questions (e.g., a rough formula).
Is there some other mechanism to report bugs like that endless loop?
I need to create bathymetry maps (contours and isobaths, not raster maps) weekly or monthly for several areas, some on the order of 8000 km^2 with 30 million points, and I was hoping to avoid several manual steps like the tacklefever post. Is Reefmaster the right product for this sort of work?
Hi and sorry for late reply. The answer to your last question is no, ReefMaster really isn't designed for building maps of this sort of size. The focus has always been on producing small, high resolution maps using data collected by the user themselves - 8000km2 is a very large map area in this context and way beyond anything that we test internally. Although there are ways of getting around this size limitation, as mentioned in this thread and others, I would probably suggest using something more professionally targeted such as GlobalMapper or ARCGis.
As far as memory use is concerned, RM is much more sensitive to the overall map size than the number of data points. Unfortunately due to the current implementation it doesn't matter how much PC memory you have above a certain theshold, as the limitation is the number of data points within the map grid that can be addressed using 32 bit values (even if the application itself is running in 64 bit). That is unlikely to change in the short term.