Autor Thema: 2 IMC feature requests  (Gelesen 67 mal)

Offline SteeevO

  • Jungbrut im Schwarm
  • *
  • Beiträge: 31
  • My/Mein Echo Equipment: HDS-10 G2, HDS-7 G2T, HDS-7 G3, HDS-16 Carbon, HDS-9 Live. Software- QGIS, GDAL, Linux, WINE, Global Mapper,
2 IMC feature requests
« am: 12 September 2019, 02:07:54 »
I think a couple seemingly simple features should be added to the IMC for those of us working with large datasets and to keep from having to reprocess areas that overlap between projects.
1) I think there should be an option to retain Unbound AT5's and be able to use them as source files in a later project.
2) be able to set raster options with command line switches.

These 2 things would help me a lot. I'm sure others would benefit from it as well.

Offline gregory

  • Insight Map Creator
  • *
  • Beiträge: 721
Re: 2 IMC feature requests
« Antwort #1 am: 12 September 2019, 16:29:43 »
1) On vector, this wouldn't work because features are serialized on the fly.  Additional runs incorporating new data or data in a new order would use different encoding names which would result in incongruities during the bind phase.  The base map functionality is the closest to an intermediate vector state as the IMC will go.

On raster, this is beyond the scope of the application.  The regular raster toolkit (Tier3) is intended for production environments.  IMC saving intermediate raster states would be impractical both from the practice being beyond the technical capabilities of many of its users and the toolkit being required to bind the intermediate files together.  Any functionality similar to this approach would be added into the regular toolkit (e.g - deconstruction into major blocks).

2) The IMC limits command line arguments by design.  The complexity of the many project settings make the usage of command line arguments impractical.  Adding command line arguments for project variables bloats the design, adds additional points of failure, and circumvents the designed methods of control.