Global Mapper v26.0

Workspace load terminates with IMPORT WMS error. How to fix or disable the WMS?

NEV
NEV Global Mapper UserTrusted User

Error running script command IMPORT_WMS AUTO_CONTRAST="NO" BAND_RANGE="-32000.000000000,32000.000000000,ALL,0" CLIP_COLLAR="NONE" CONTRAST_MODE="NONE" CONTRAST_SHARED="NO" HIDDEN="YES" LABEL_FIELD_FORCE_OVERWRITE="NO" LABEL_FORMAT_NUMBERS="YES" LABEL_PRECISION="-1" LABEL_REMOVE_TRAILING_ZEROS="YES" LABEL_USE_SCIENTIFIC_NOTATION="NO" LAT_LON_BOUNDS="145.22031957,-42.03839871,148.17811922,-40.99640260" LAYER_GROUP="Basemaps" METADATA_URL="https://listdata.thelist.tas.gov.au/opendata/" SAMPLING_METHOD="BILINEAR" SOURCE_DESC="Tasmap 250K" TEXTURE_MAP="NO" WMS_IS_TILED="YES" WMS_LAYER="Basemaps_Tasmap250K" WMS_REFRESH_TIME="20160" WMS_SERVER_URL="https://services.thelist.tas.gov.au/arcgis/rest/services/Basemaps/Tasmap250K/MapServer/WMTS/1.0.0/WMTSCapabilities.xml" WMS_SERVICE="WMTS" WMS_STYLE="" in F:\remNWTD_2021_2024\2024\GIS_2024\NOV_2024_UPDATE_Rem_NWTD.gmw

Read access violation at data address 0x0000000006D46B40, program address 0x0000000140DEDEA8.

Version: v22.1.1 (131) (64-bit)

Build Time: Mar 8 2021 00:18:30

Thread: Main UI Thread

Stack Trace:

0000000140DEDEA8 (global_mapper)

0000000140BEF54D (global_mapper)

000000014104AB3B (global_mapper)

000000014105EC7D (global_mapper)

0000000140FEE40B (global_mapper)

00000001405B0A3C (global_mapper)

00000001405AFE46 (global_mapper)

00007FF9FB8C5F5C (mfc140)

00007FF9FB905B42 (mfc140)

00007FF9FB9627F1 (mfc140)

000000014064E4E1 (global_mapper)

0000000140CD96EE (global_mapper)

00007FF9FB98948C (mfc140)

00007FF9FB74A6A2 (mfc140)

0000000140A21AAF (global_mapper)

... (18 Additional Stack Items Hidden)

Windows 10 Pro (64-bit) Memory: 3,491,913,728 of 8,518,742,016 available, GDI Usage: 410 GDI (Peak 541), 194 User (Peak 323)

Answers

  • NEV
    NEV Global Mapper User Trusted User

    I found (myself) that the issue can be ovecome (well, worked around) by locating the WMS in the list of "Download Online Imagery/..., COUNTRY DATA,,,etc,,, "Connect" to the errant layer, and when it is displayed then load the Workkspace that attempts/includes that layer. As. GM does not allow the user to delete the problem layer in the "Download" option,, it becomes a (tedious) process every time. Even if that layer is deleted and saved as a new "Save Workkspace" with the same or different name, one encounters the same issue when loading. Must be a better way.