Question for Scottb613

**scottb613** · 09-16-2026, 10:29

Originally posted by weichenpfleger

Hi Scott!
Unfortunately, LIDEX doesn’t work at all with my huge power grid (Western Germany).
I’ve attached the log file.

Greetings

Franz

Hi Franz,

Thanks for the log. The size of your route doesn’t appear to be the problem, but the reported coordinates extend well beyond western Germany. There may be some outlying tiles, or LIDEX may be interpreting their positions incorrectly.

There’s also a limitation in my scan—it checks one selected tile for elevation coverage. If that tile falls somewhere without coverage, it can block the entire run.

Please make a separate TEST COPY of your route first and point LIDEX at that copy. Do not run this test on your working route.

On that TEST COPY, enable Scan Override, uncheck OSM / Map Tiles, and leave it in Append mode. Then click Run. This will let LIDEX try the elevation sources for each tile, while skipping terrain that already contains valid heights.

For a closer look, please send me:

The resulting Run log, even if it fails.
The route’s .trk file.
A list of the .t filenames in the TILES folder—just the filenames, no need to send the entire route.

The filename list will let me check for outlying tiles, and the .trk file will help me check how LIDEX is interpreting the route’s geography.

Regards,
Scott

**eric** · 09-16-2026, 14:03

Is there a dependency for the core app to launch? I can't get the executable to open, and yes, I gave permission to run the app. It just black-hole's after running as administrator.

(nevermind... Powershell is apparently a dependency)

**scottb613** · 09-16-2026, 14:54

Originally posted by eric

Is there a dependency for the core app to launch? I can't get the executable to open, and yes, I gave permission to run the app. It just black-hole's after running as administrator.

(nevermind... Powershell is apparently a dependency)

Hi Eric,

I had an issue with Malwarebytes - I had to make an exception for my copy - because it suspected ransomware - I believe this is because I am an unknown developer manipulating a large volume of files. It kept quarantining the executable when I tried to run it.

Regards,
Scott

**derekmorton** · 09-16-2026, 16:32

Hi Scott,

Its not the user, it's the uncompressing of files that gets its attention.

**scottb613** · 09-16-2026, 16:50

Originally posted by derekmorton

Hi Scott,

Its not the user, it's the uncompressing of files that gets its attention.

Hi Derek,

Gracias amigo - good to know - I do publish my full source code with the application if anyone has any questions.

Regards,
Scott

**eric** · 09-17-2026, 00:00

Well, that's frustrating.... it's errored out twice on one of my routes for memory. Trying again without doing Route Tiles but instead using TDB and a radius of 3 tiles. I had a lot of extra tiles in the quadtree for future expansion...

Code:

RUN SETTINGS
------------
  OPERATION: Run
  ROUTE: r:\packerland
  VERSION: v1.401
  MODE: Overwrite
  TERRAIN OUTPUT: Normal - 8m Tiles
  SELECTION: Use Route Tiles

  OUTPUTS
  -------
    • Route Tiles: No
    • Distant Mountains: No
    • OSM / Map Tiles: Yes
    • HD Map Tiles: No
    • HD Mesh Tiles: No

  OPTIONS
  -------
    • Tile Radius: 2
    • DM Radius: 1
    • Clean Tile Wipe: No
    • Scan Override: No
    • Geo Bias N/S: 0 m
    • Geo Bias E/W: 0 m

  DATA SOURCES
  ------------
    • USGS: 1m, 5m~, and 10m DEM tiers as enabled by Scan
    • Global fallback: 30m Copernicus DEM GLO-30 Public | anonymous AWS Open Data | low-resolution DSM

  LOG: E:\OneDrive\Desktop\SCOLIDEX.log

================================
SCO LIDEX TERRAIN RUN
================================


ROUTE SUMMARY
-------------
  ROUTE: r:\packerland
  TERRAIN TILES: 1,897
  WORLD FILES: 1,863
  ROUTESTART TILE: X=-11553, Z=14624
  MARKER BOUNDS: lon -92.791725..-82.421330, lat 41.709020..46.728200
  PROJECTION TAG: TsreGeoProjection not found; using standard route projection

  TERRAIN STORAGE
  ---------------
    HEIGHT STORAGE: external *_y.raw height grids
    SELECTED OUTPUT: Normal - 8m Tiles | 256x256 int16 samples | not inline text heights

  GEOGRAPHIC PROJECTION
  ---------------------
    DEM BOUNDS: lon -88.601224..-87.021900, lat 42.962751..46.185881
    MODE: MSTS/Open Rails interrupted Goode homolosine world-tile projection
    DETAILS: TsreGeoProjection not detected; using standard MSTS/Open Rails tile geography with the TSRE map compatibility correction: terrain east=11m, south=16m.

RUNTIME INITIALIZATION
----------------------
  GDAL: initializing bundled geospatial engine

RUN DATA SOURCE STATUS
----------------------

  PASSED: OpenStreetMap regional extract
    SOURCE: Local Geofabrik PBF cache
    DETAILS: cached map extract will be used; Geofabrik will not be polled

Route tile generation skipped by option.
Using current route Geofabrik extract.

Creating 1,897 TSRE terrain map tile(s) from US Midwest...
PBF cache: r:\packerland\osm_data\geofabrik\us-midwest.osm.pbf

OSM / POLYVEG PROCESSING
------------------------
  • This is a time-intensive operation.
  • Completed work is checkpointed; long operations report every five minutes.

  OSM SOURCE READING
  ------------------
  [22:04:30] Using current compact route OSM cache: r:\packerland\osm_data\route-osm-working.gpkg

  ROUTE FEATURE PROCESSING
  ------------------------
  [22:04:30] Route OSM derivative is missing or stale; rebuilding it for the active route.
  [22:04:30] PolyVeg output: r:\packerland\osm_data\polyveg-polygons.geojson
  [22:04:30] Route coverage: 1,897 terrain tiles; 1,863 object-bearing world files.
  [22:04:31] Relation-safe read; completed geometry limited to route coverage.
  [22:04:31] Reading and classifying OSM features...
    • [22:09:31] Still processing: Reading and classifying OSM features.
    • [22:12:01] OSM source read: 25% (358,804 route features classified).
    • [22:12:02] OSM source read: 50% (359,623 route features classified).
    • [22:14:31] Still processing: Reading and classifying OSM features.
    • [22:19:31] Still processing: Reading and classifying OSM features.
    • [22:24:31] Still processing: Reading and classifying OSM features.
    • [22:29:31] Still processing: Reading and classifying OSM features.
    • [22:34:31] Still processing: Reading and classifying OSM features.
    • [22:36:26] OSM source read: 75% (1,307,466 route features classified).
    • [22:36:27] OSM source read: 100% (1,312,396 route features classified).
  [22:36:27] Reading and classifying OSM features complete.

  PERMANENT EXCLUSIONS
  --------------------
  [22:36:27] Sources: 30,819 PolyVeg; 870,154 polygon masks; 308,528 line masks.
  [22:36:27] Combining 1,179,117 permanent exclusion polygons...
    • [22:41:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [22:46:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [22:51:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [22:56:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:01:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:06:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:11:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:16:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:21:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:26:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:31:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:36:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:41:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:46:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:51:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [23:56:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [00:01:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [00:06:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [00:11:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [00:16:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [00:21:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
    • [00:26:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
  [00:28:50] Combining 1,179,117 permanent exclusion polygons complete.

  POLYVEG SURFACE BUILD
  ---------------------
  [00:28:50] Building final PolyVeg surfaces...

  SOURCE NORMALIZATION
  --------------------
    • [00:28:52] PolyVeg sources normalized: 3,082 / 30,819.
    • [00:28:53] PolyVeg sources normalized: 6,164 / 30,819.
    • [00:28:53] PolyVeg sources normalized: 9,246 / 30,819.
    • [00:28:54] PolyVeg sources normalized: 12,328 / 30,819.
    • [00:28:54] PolyVeg sources normalized: 15,410 / 30,819.
    • [00:28:54] PolyVeg sources normalized: 18,492 / 30,819.
    • [00:28:54] PolyVeg sources normalized: 21,574 / 30,819.
    • [00:28:54] PolyVeg sources normalized: 24,656 / 30,819.
    • [00:28:55] PolyVeg sources normalized: 27,738 / 30,819.
    • [00:28:55] PolyVeg sources normalized: 30,819 / 30,819.

  TERRAIN-SECTION STACKING
  ------------------------
    • [00:28:55] Processing 1,897 terrain sections with a one-foot overlap halo.
    • [00:33:50] Still processing: Building final PolyVeg surfaces.
    • [00:34:53] Terrain sections processed: 190 / 1,897.
    • [00:36:39] Terrain sections processed: 380 / 1,897.
    • [00:38:50] Still processing: Building final PolyVeg surfaces.
    • [00:39:34] Terrain sections processed: 570 / 1,897.
    • [00:41:42] Terrain sections processed: 760 / 1,897.
    • [00:43:50] Still processing: Building final PolyVeg surfaces.
    • [00:44:00] Terrain sections processed: 950 / 1,897.
    • [00:45:58] Terrain sections processed: 1,140 / 1,897.
    • [00:47:35] Terrain sections processed: 1,330 / 1,897.
    • [00:48:50] Still processing: Building final PolyVeg surfaces.
    • [00:49:54] Terrain sections processed: 1,520 / 1,897.
    • [00:51:41] Terrain sections processed: 1,710 / 1,897.
    • [00:53:11] Terrain sections processed: 1,897 / 1,897.

  POLYVEG FEATURE ASSEMBLY
  ------------------------
    • [00:53:12] PolyVeg features assembled: 3,082 / 30,819.
    • [00:53:15] PolyVeg features assembled: 6,164 / 30,819.
    • [00:53:17] PolyVeg features assembled: 9,246 / 30,819.
    • [00:53:17] PolyVeg features assembled: 12,328 / 30,819.
    • [00:53:18] PolyVeg features assembled: 15,410 / 30,819.
    • [00:53:20] PolyVeg features assembled: 18,492 / 30,819.
    • [00:53:24] PolyVeg features assembled: 21,574 / 30,819.
    • [00:53:26] PolyVeg features assembled: 24,656 / 30,819.
    • [00:53:28] PolyVeg features assembled: 27,738 / 30,819.
    • [00:53:33] PolyVeg features assembled: 30,819 / 30,819.
  [00:53:33] Building final PolyVeg surfaces complete.

  POLYVEG VALIDATION
  ------------------
  [00:53:33] Validating final PolyVeg surfaces...
    • [00:53:36] PolyVeg properties validated: 1,564 / 15,639.
    • [00:53:36] PolyVeg properties validated: 3,128 / 15,639.
    • [00:53:36] PolyVeg properties validated: 4,692 / 15,639.
    • [00:53:36] PolyVeg properties validated: 6,256 / 15,639.
    • [00:53:36] PolyVeg properties validated: 7,820 / 15,639.
    • [00:53:36] PolyVeg properties validated: 9,384 / 15,639.
    • [00:53:36] PolyVeg properties validated: 10,948 / 15,639.
    • [00:53:36] PolyVeg properties validated: 12,512 / 15,639.
    • [00:53:36] PolyVeg properties validated: 14,076 / 15,639.
    • [00:53:36] PolyVeg properties validated: 15,639 / 15,639.
    • [00:53:39] PolyVeg geometries validated: 1,564 / 15,639.
    • [00:53:40] PolyVeg geometries validated: 3,128 / 15,639.
    • [00:53:40] PolyVeg geometries validated: 4,692 / 15,639.
    • [00:53:41] PolyVeg geometries validated: 6,256 / 15,639.
    • [00:53:41] PolyVeg geometries validated: 7,820 / 15,639.
    • [00:53:42] PolyVeg geometries validated: 9,384 / 15,639.
    • [00:53:42] PolyVeg geometries validated: 10,948 / 15,639.
    • [00:53:42] PolyVeg geometries validated: 12,512 / 15,639.
    • [00:53:43] PolyVeg geometries validated: 14,076 / 15,639.
    • [00:53:43] PolyVeg geometries validated: 15,639 / 15,639.
    • [00:53:43] Exclusion and overlap topology validated within bounded terrain sections.
  [00:53:43] Validating final PolyVeg surfaces complete.

  POLYVEG EXCLUSIONS
  ------------------
  [00:53:43] Writing PolyVeg exclusions...
    • [00:54:20] PolyVeg exclusions written: 105,085 / 1,050,849.
    • [00:54:51] PolyVeg exclusions written: 210,170 / 1,050,849.
    • [00:55:14] PolyVeg exclusions written: 315,255 / 1,050,849.
    • [00:55:23] PolyVeg exclusions written: 420,340 / 1,050,849.
    • [00:55:32] PolyVeg exclusions written: 525,425 / 1,050,849.
    • [00:55:40] PolyVeg exclusions written: 630,510 / 1,050,849.
    • [00:55:50] PolyVeg exclusions written: 735,595 / 1,050,849.
    • [00:56:01] PolyVeg exclusions written: 840,680 / 1,050,849.
    • [00:56:12] PolyVeg exclusions written: 945,765 / 1,050,849.
    • [00:56:20] PolyVeg exclusions written: 1,050,849 / 1,050,849.
  [00:56:23] Writing PolyVeg exclusions complete.
  [00:56:23] Validating PolyVeg exclusions...
Error: Insufficient memory to continue the execution of the program.

RUN TOTALS
----------
  ELAPSED: 2:53:50
  USGS DATA READ: 0 bytes
  COPERNICUS DATA READ: 0 bytes

**scottb613** · 09-17-2026, 05:56

Originally posted by eric

Well, that's frustrating.... it's errored out twice on one of my routes for memory. Trying again without doing Route Tiles but instead using TDB and a radius of 3 tiles. I had a lot of extra tiles in the quadtree for future expansion...

Code:

RUN SETTINGS
------------
OPERATION: Run
ROUTE: r:\packerland
VERSION: v1.401
MODE: Overwrite
TERRAIN OUTPUT: Normal - 8m Tiles
SELECTION: Use Route Tiles

OUTPUTS
-------
• Route Tiles: No
• Distant Mountains: No
• OSM / Map Tiles: Yes
• HD Map Tiles: No
• HD Mesh Tiles: No

OPTIONS
-------
• Tile Radius: 2
• DM Radius: 1
• Clean Tile Wipe: No
• Scan Override: No
• Geo Bias N/S: 0 m
• Geo Bias E/W: 0 m

DATA SOURCES
------------
• USGS: 1m, 5m~, and 10m DEM tiers as enabled by Scan
• Global fallback: 30m Copernicus DEM GLO-30 Public | anonymous AWS Open Data | low-resolution DSM

LOG: E:\OneDrive\Desktop\SCOLIDEX.log

================================
SCO LIDEX TERRAIN RUN
================================


ROUTE SUMMARY
-------------
ROUTE: r:\packerland
TERRAIN TILES: 1,897
WORLD FILES: 1,863
ROUTESTART TILE: X=-11553, Z=14624
MARKER BOUNDS: lon -92.791725..-82.421330, lat 41.709020..46.728200
PROJECTION TAG: TsreGeoProjection not found; using standard route projection

TERRAIN STORAGE
---------------
HEIGHT STORAGE: external *_y.raw height grids
SELECTED OUTPUT: Normal - 8m Tiles | 256x256 int16 samples | not inline text heights

GEOGRAPHIC PROJECTION
---------------------
DEM BOUNDS: lon -88.601224..-87.021900, lat 42.962751..46.185881
MODE: MSTS/Open Rails interrupted Goode homolosine world-tile projection
DETAILS: TsreGeoProjection not detected; using standard MSTS/Open Rails tile geography with the TSRE map compatibility correction: terrain east=11m, south=16m.

RUNTIME INITIALIZATION
----------------------
GDAL: initializing bundled geospatial engine

RUN DATA SOURCE STATUS
----------------------

PASSED: OpenStreetMap regional extract
SOURCE: Local Geofabrik PBF cache
DETAILS: cached map extract will be used; Geofabrik will not be polled

Route tile generation skipped by option.
Using current route Geofabrik extract.

Creating 1,897 TSRE terrain map tile(s) from US Midwest...
PBF cache: r:\packerland\osm_data\geofabrik\us-midwest.osm.pbf

OSM / POLYVEG PROCESSING
------------------------
• This is a time-intensive operation.
• Completed work is checkpointed; long operations report every five minutes.

OSM SOURCE READING
------------------
[22:04:30] Using current compact route OSM cache: r:\packerland\osm_data\route-osm-working.gpkg

ROUTE FEATURE PROCESSING
------------------------
[22:04:30] Route OSM derivative is missing or stale; rebuilding it for the active route.
[22:04:30] PolyVeg output: r:\packerland\osm_data\polyveg-polygons.geojson
[22:04:30] Route coverage: 1,897 terrain tiles; 1,863 object-bearing world files.
[22:04:31] Relation-safe read; completed geometry limited to route coverage.
[22:04:31] Reading and classifying OSM features...
• [22:09:31] Still processing: Reading and classifying OSM features.
• [22:12:01] OSM source read: 25% (358,804 route features classified).
• [22:12:02] OSM source read: 50% (359,623 route features classified).
• [22:14:31] Still processing: Reading and classifying OSM features.
• [22:19:31] Still processing: Reading and classifying OSM features.
• [22:24:31] Still processing: Reading and classifying OSM features.
• [22:29:31] Still processing: Reading and classifying OSM features.
• [22:34:31] Still processing: Reading and classifying OSM features.
• [22:36:26] OSM source read: 75% (1,307,466 route features classified).
• [22:36:27] OSM source read: 100% (1,312,396 route features classified).
[22:36:27] Reading and classifying OSM features complete.

PERMANENT EXCLUSIONS
--------------------
[22:36:27] Sources: 30,819 PolyVeg; 870,154 polygon masks; 308,528 line masks.
[22:36:27] Combining 1,179,117 permanent exclusion polygons...
• [22:41:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [22:46:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [22:51:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [22:56:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:01:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:06:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:11:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:16:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:21:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:26:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:31:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:36:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:41:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:46:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:51:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [23:56:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [00:01:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [00:06:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [00:11:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [00:16:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [00:21:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
• [00:26:27] Still processing: Combining 1,179,117 permanent exclusion polygons.
[00:28:50] Combining 1,179,117 permanent exclusion polygons complete.

POLYVEG SURFACE BUILD
---------------------
[00:28:50] Building final PolyVeg surfaces...

SOURCE NORMALIZATION
--------------------
• [00:28:52] PolyVeg sources normalized: 3,082 / 30,819.
• [00:28:53] PolyVeg sources normalized: 6,164 / 30,819.
• [00:28:53] PolyVeg sources normalized: 9,246 / 30,819.
• [00:28:54] PolyVeg sources normalized: 12,328 / 30,819.
• [00:28:54] PolyVeg sources normalized: 15,410 / 30,819.
• [00:28:54] PolyVeg sources normalized: 18,492 / 30,819.
• [00:28:54] PolyVeg sources normalized: 21,574 / 30,819.
• [00:28:54] PolyVeg sources normalized: 24,656 / 30,819.
• [00:28:55] PolyVeg sources normalized: 27,738 / 30,819.
• [00:28:55] PolyVeg sources normalized: 30,819 / 30,819.

TERRAIN-SECTION STACKING
------------------------
• [00:28:55] Processing 1,897 terrain sections with a one-foot overlap halo.
• [00:33:50] Still processing: Building final PolyVeg surfaces.
• [00:34:53] Terrain sections processed: 190 / 1,897.
• [00:36:39] Terrain sections processed: 380 / 1,897.
• [00:38:50] Still processing: Building final PolyVeg surfaces.
• [00:39:34] Terrain sections processed: 570 / 1,897.
• [00:41:42] Terrain sections processed: 760 / 1,897.
• [00:43:50] Still processing: Building final PolyVeg surfaces.
• [00:44:00] Terrain sections processed: 950 / 1,897.
• [00:45:58] Terrain sections processed: 1,140 / 1,897.
• [00:47:35] Terrain sections processed: 1,330 / 1,897.
• [00:48:50] Still processing: Building final PolyVeg surfaces.
• [00:49:54] Terrain sections processed: 1,520 / 1,897.
• [00:51:41] Terrain sections processed: 1,710 / 1,897.
• [00:53:11] Terrain sections processed: 1,897 / 1,897.

POLYVEG FEATURE ASSEMBLY
------------------------
• [00:53:12] PolyVeg features assembled: 3,082 / 30,819.
• [00:53:15] PolyVeg features assembled: 6,164 / 30,819.
• [00:53:17] PolyVeg features assembled: 9,246 / 30,819.
• [00:53:17] PolyVeg features assembled: 12,328 / 30,819.
• [00:53:18] PolyVeg features assembled: 15,410 / 30,819.
• [00:53:20] PolyVeg features assembled: 18,492 / 30,819.
• [00:53:24] PolyVeg features assembled: 21,574 / 30,819.
• [00:53:26] PolyVeg features assembled: 24,656 / 30,819.
• [00:53:28] PolyVeg features assembled: 27,738 / 30,819.
• [00:53:33] PolyVeg features assembled: 30,819 / 30,819.
[00:53:33] Building final PolyVeg surfaces complete.

POLYVEG VALIDATION
------------------
[00:53:33] Validating final PolyVeg surfaces...
• [00:53:36] PolyVeg properties validated: 1,564 / 15,639.
• [00:53:36] PolyVeg properties validated: 3,128 / 15,639.
• [00:53:36] PolyVeg properties validated: 4,692 / 15,639.
• [00:53:36] PolyVeg properties validated: 6,256 / 15,639.
• [00:53:36] PolyVeg properties validated: 7,820 / 15,639.
• [00:53:36] PolyVeg properties validated: 9,384 / 15,639.
• [00:53:36] PolyVeg properties validated: 10,948 / 15,639.
• [00:53:36] PolyVeg properties validated: 12,512 / 15,639.
• [00:53:36] PolyVeg properties validated: 14,076 / 15,639.
• [00:53:36] PolyVeg properties validated: 15,639 / 15,639.
• [00:53:39] PolyVeg geometries validated: 1,564 / 15,639.
• [00:53:40] PolyVeg geometries validated: 3,128 / 15,639.
• [00:53:40] PolyVeg geometries validated: 4,692 / 15,639.
• [00:53:41] PolyVeg geometries validated: 6,256 / 15,639.
• [00:53:41] PolyVeg geometries validated: 7,820 / 15,639.
• [00:53:42] PolyVeg geometries validated: 9,384 / 15,639.
• [00:53:42] PolyVeg geometries validated: 10,948 / 15,639.
• [00:53:42] PolyVeg geometries validated: 12,512 / 15,639.
• [00:53:43] PolyVeg geometries validated: 14,076 / 15,639.
• [00:53:43] PolyVeg geometries validated: 15,639 / 15,639.
• [00:53:43] Exclusion and overlap topology validated within bounded terrain sections.
[00:53:43] Validating final PolyVeg surfaces complete.

POLYVEG EXCLUSIONS
------------------
[00:53:43] Writing PolyVeg exclusions...
• [00:54:20] PolyVeg exclusions written: 105,085 / 1,050,849.
• [00:54:51] PolyVeg exclusions written: 210,170 / 1,050,849.
• [00:55:14] PolyVeg exclusions written: 315,255 / 1,050,849.
• [00:55:23] PolyVeg exclusions written: 420,340 / 1,050,849.
• [00:55:32] PolyVeg exclusions written: 525,425 / 1,050,849.
• [00:55:40] PolyVeg exclusions written: 630,510 / 1,050,849.
• [00:55:50] PolyVeg exclusions written: 735,595 / 1,050,849.
• [00:56:01] PolyVeg exclusions written: 840,680 / 1,050,849.
• [00:56:12] PolyVeg exclusions written: 945,765 / 1,050,849.
• [00:56:20] PolyVeg exclusions written: 1,050,849 / 1,050,849.
[00:56:23] Writing PolyVeg exclusions complete.
[00:56:23] Validating PolyVeg exclusions...
Error: Insufficient memory to continue the execution of the program.

RUN TOTALS
----------
ELAPSED: 2:53:50
USGS DATA READ: 0 bytes
COPERNICUS DATA READ: 0 bytes

Hi Eric,

Thanks for the log - let me look at the code - I'll probably have to do memory management like I did on the terrain mesh - processing data in smaller chunks - then clearing memory.

Regards,
Scott

**weichenpfleger** · 09-17-2026, 06:08

Hello Scott,
Please find attached the requested analysis of my route. I had to compress the SCOLIDEX log file as it was too large. I hope you can find the error,
so that I can make use of your brilliant innovations too.

Greetings

Franz

Attached Files

**scottb613** · 09-17-2026, 06:39

Originally posted by weichenpfleger

Hello Scott,
Please find attached the requested analysis of my route. I had to compress the SCOLIDEX log file as it was too large. I hope you can find the error,
so that I can make use of your brilliant innovations too.

Greetings

Franz

Hi Franz,

Thanks so much - I'll work on this and see if I can identify the root cause. Given Eric's reported memory issue - I clearly need to dive into this again. The biggest routes I tested this on were about 600 tiles - I just don't normally run massive routes.

I'll post here when I figure this all out. Sorry for the inconvenience.

Regards,
Scott

**scottb613** · 09-17-2026, 07:39

Originally posted by weichenpfleger

Hello Scott,
Please find attached the requested analysis of my route. I had to compress the SCOLIDEX log file as it was too large. I hope you can find the error,
so that I can make use of your brilliant innovations too.

Greetings

Franz

Hi Franz,

Thanks for sending the files—they helped me identify the problem.

Your route contains one terrain tile, -1843a864.t, whose coordinates place it in the Indian Ocean, thousands of kilometres from Germany. LIDEX tries to create nine distant-mountain tiles around it, and all nine fail because there is no elevation data available there. The other 131 distant-mountain tiles generated successfully, so your route’s size isn’t the cause.

Please work only on your TEST COPY for now. Move these two files out of its TILES folder into a separate backup folder:

-1843a864.t
-1843a864_y.raw

Then try Scan again. Keep the files so they can be restored, and leave your working route unchanged.

I also found a weakness in LIDEX’s Scan: it checks one tile for elevation coverage, and this misplaced tile happens to come first. I’ll include a fix in the next release to check several locations and clearly warn about isolated tiles, so one unusual tile won’t block the entire route.

Thanks again for helping me track this down!

Regards,
Scott

**tarrant75** · 09-17-2026, 08:38

Ran it through Lidex, gave me an exception error on one tile (frustrating, but what can you do?). It still won't let me select Unrestricted, so not sure what's going on

**scottb613** · 09-17-2026, 08:53

Hi Chris,

The only time you can't select "UNRESTRICTED" is when the exclusion data is missing.

Can you post your last run log from LIDEX - the one with the error - should be on your desktop unless removed.

Perhaps I need another option to ignore OSM Data - and leave it to the end user to control placement?

Thanks.

Regards,
Scott

**weichenpfleger** · 09-17-2026, 09:29

Hi Scott,
Now that the faulty tile has been removed, the scan looks much better. But OSM still isn’t working.

Thanks for all your hard work!

Greetings

Franz

Attached Files

SCOLIDEX.log (4.2 KB, 2 views)

**scottb613** · 09-17-2026, 09:49

Originally posted by weichenpfleger

Hi Scott,
Now that the faulty tile has been removed, the scan looks much better. But OSM still isn’t working.

Thanks for all your hard work!

Greetings

Franz

Hi Franz,

Thanks for the new log. Removing that tile has corrected the terrain bounds, and Scan now enables terrain and distant-mountain generation using Copernicus. The USGS warnings are expected for Germany.

I also checked your remaining 5,333 terrain tiles against Geofabrik’s current coverage information. The Germany download doesn’t cover every tile, but the Europe download covers all of them. So suitable OSM coverage exists, and I’m investigating why LIDEX reports that it cannot find a covering download.

Could you send a filename list from your route’s WORLD folder, similar to the TILES list you already supplied? Just the .w filenames are enough. LIDEX also checks those locations when selecting its OSM download. This will help me narrow down the cause; it doesn’t mean those files are faulty. Please leave the remaining files unchanged.

The improved terrain Scan will be included in the next release. I’m also testing changes that process OSM data in smaller sections to reduce memory use on large routes.

I'm working on Eric's memory issue on massive routes - now. I also remembered I have Doug's TriState route on my drive - which if 4600 tiles - I'll test with that to represent massive routes.

We’re making progress! Thanks for your patience and for helping me work through this—we’ll get you there.

Regards,
Scott

**eric** · 09-17-2026, 10:04

Originally posted by scottb613

The biggest routes I tested this on were about 600 tiles - I just don't normally run massive routes.

Nah, all good. Geographically Packerland is probably the second largest of my routes, about 300 miles north to south from Marquette to Milwaukee. Gila Sub is only 240 miles but includes tiles for the branch to Nogales and the Phoenix Sub, so it's "fatter"...

Question for Scottb613

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment