Base Data URL: file:///C:/testdata/level_03/%quad.jpg

Inside the level_03 directory I have 000.jpg 001.jpg.... up through 333.jpg

The tiles are all 256x256 and I have the max zoom level set to 3.

Is there something I am missing because every time I go to import it says "No working tiles could be found based on the provided base URL."

As a temporary workaround, I’ve been masking the raster using a coverage-area feature selected in the “Export Bounds” tab. Once the raster is fully masked, the XYZ export completes within seconds.

I also tested this with the latest build (GM 26.2, b111825), but the issue remains.

Is anyone else experiencing this? Could there be a setting I’m overlooking?

Thanks!

Specifically, I have made airborne maps of snow depth at 25 cm postings over 1000s of square kilometers and what I would like to do is impose a 5 km x 5 km grid over this to interrogate the snow depths within each of those 5km grid cells, answering questions such as "do more than 10% of pixels within this grid cell have less than 6" of thickness"? Then I'd like to color those 5km grid cells by the answer (say green for Yes and red for No) and create a new raster map at 5 km posting over those 1000s of square kilometers.

Is this possible?

Thanks!

Matt

I load the raster, then the area through which I cropp it.

I then export this raster to JNX, also using the crop.

However, in the JNX file viewer I see this:

Please tell me how to remove this malaria frame. 

Thank you!

I am working on a project that analyzes erosion and deposition within a stream network using LiDAR change detection. My goal is to determine the volumes of erosion and deposition within a 10m buffer around each stream segment (5m on each side). Here’s what I’ve done so far:

1. Used the Combine Compare Tool to calculate elevation differences between my LiDAR grids.
   • Negative values indicate erosion, positive values indicate deposition, and 0 indicates no change.
2. Selected the relevant stream line segment (watershed).
3. Navigated to Analysis/Measurement > Volume.
4. Used the Cut and Fill Volumes tool along the selected line feature, with a 10m corridor around the line.
5. Set the "Use same base height value for all vertices (0m)" option.

Attached is a screenshot showing the area I’ve analyzed, with erosion shown in blue, deposition in orange, and no change (0m) in grey.

When I run the analysis, I get the following volumes for cut (deposition) and fill (erosion):

• Cut (deposition) = 286 cubic meters
• Fill (erosion) = 184 cubic meters

These values seem inconsistent, as most of the stream segment is in areas with negative elevation. Therefore, I would expect the fill volume to be higher than the cut volume.

I also tried calculating the volume using a buffer polygon of the same size (5m on both sides of the stream). I set the parameters to calculate both cut and fill volumes within the area feature and used the "same base height for all vertices (0m)" setting.

When I ran the volume calculation for the buffer polygon, I got the following results:

• Cut (deposition) = 61 cubic meters
• Fill (erosion) = 289 cubic meters

As we can see, the cut volume is much smaller in this case.

My main questions are:

1. Why do the volumes differ between these two methods if they are essentially calculating the same thing?
2. Which method should I use for this specific analysis?

Any help would be appreciated

Thank you

I have a map(JPG+ref. File). I export it to RMaps SQLite Database.

Here is the export result:

Please help me understand my mistake.

The attachment contains the source and received files.

I'm wanting to be able to select these images individually with the map window

and also batch export the images within the black boundary block individually. Is this possible?

Thank you

We took the images from a drone where we imported to Pix4Dmapper to input our GCP's and export our orthomosaic & DSM as .tif files to import to global mapper which we then exported as an ecw file because exporting a jpg was not possible without decreasing photo quality but when we cross reference our data taken from the ground it does not match to the orthomosaic image even though the Co-Ordinates seem to be in the right position from Global Mapper and from the ground is there any reason for this small shift and how to fix it.

Any help is much appreciated,

Thank you

Many thanks

"moving a picture point will update the location information in the image's EXIF to reflect the new location. This affects the original file outside of Global Mapper." It doesn't. The EXIF file locations of the original photos are unaltered.

I have enabled Backup Picture Point Image on Update EXIF

A "BACKUP" sub folder in the image file's location was not created.

Can anyone help with this?

What users consoder the best guides for making refief maps with raster overlays that are directly applicable to Global Mapper 22?

Any afvice on how to set the Raster calulator up would b emuch appreciated!

A client has sent me a bunch of geotagged photos from site taken on an iPhone. Unfortunately they are in .HEIC format and they won't directly register when I import them into GM. I've tried converting them to jpeg and tif format but I seem to lose the geo-tag info and I only get the option to manually rectify. I've had no problems previously when clients have sent me geotagged jpegs, tifs etc.

Has anyone else had this problem or know of a workaround?

I've attached a zipped image which should roughly be at the location shown below if you want to try...

Any help is much appreciated.

Cheers,

/al

I would like to export images at each of these points to end up with something like the below. Multiple closeups based on point data i have loaded.

Is this possible within Global mapper?

https://github.com/rouault/cog_validator

Global Mapper Pro v23.0.1 (b100721) (647) [64-bit]- REGISTERED

example of an error:

The following errors were found:

 - The offset of the main IFD should be 8. It is 132618208 instead

 - The offset of the first block of overview of index 2 should be after the one of the overview of index 3

 - The offset of the first block of overview of index 1 should be after the one of the overview of index 2

 - The offset of the first block of overview of index 0 should be after the one of the overview of index 1

 - The offset of the first block of the main resolution image should be after the one of the overview of index 3

Cog now run out of a simple command, is there a solution to export a valid COG from GM directly?

gdal_translate original.tif original-cog.tif -of COG -co COMPRESS=LZW -stats

Also, as a follow up, is there a way to keep the Lidar Points as points and have them inherit the imagery color and then have this draw in 3d?

Thank you!

I have no trouble exporting to .ecw file with 10:1 compression. I do this all the time.

Client wants a 2 foot resolution jpg. (from a 0.25’ resolution)

When I try to export a jpg file, as shown with below settings (default to RGB)…the file is a black and white jpg file. I need the RGB image.

Thoughts on what i need to change

I have two 4 bands ortomosaics, and I would like to make a 3rd one, in which each pixel would contain the average value for each band ...

I think this happens on the raster calculator ... but I did not find the right formula ...

Anyone could help ? thank you very much !

THANK YOU!

I exported some JPEG2000 imagery to ECW. The original imagery contained some black regions that I was hoping would be removed in the ECW export process since I selected the option to "Make Background (Void) Pixels Transparent" in the "ECW Export Options". Unfortunately, that did not work to get rid of the black.

Is there another way to remove black regions in the exported ECW raster?

Thanks in advance...

I've been breaking my head trying to figure out a way to do this.

Essentially I have a DTM/DEM, customer wants to know how much of the land is below 23 degrees (45%) slope, so ive done some shaders and its done, simple enough.

Now he asks if i can tell him EXACTLY how much of that land is below 23 degrees... well it should be a simple matter of counting how many pixels are in total in the raster, then subtracting those that are red (over 23 degrees) and what ever is left in pixels multiplied by the pixel resolution should give the correct answer.

The problem is it does not seem to be as straight forward as that, even when i tell global mapper to do the cut-off areas in a sharp binary matter there's still some "blurriness" caused by the compression around the edges of the red, this throws off the whole math

Is there any better, proper way to do this? I guess someone here should know how

Here's an image of the raster, basically I'm being asked to find out how much of it is black and how much is red

Any help on this would be greatly appreciated.

I have been trying to create a Mesh DTM but whenever l export it, the mesh has no elevation values. How do l go about it?

is there any way that Global Mapper can correctly visualize a wall in a DTM? I always have the problem that house walls or smaller walls are not visualized evenly (see screenshot). Ground points are sufficiently available, but the wall just doesn't look like a wall. I observe the same again and again with house walls. Is there a suggested solution for this? You can also find an part of the data I am talking about in the attachment. 

I was excited when histogram matching was added to GM. But now a bit disappointed. The match went well and looked great on the screen in GM but the Geotif result did not, as the attached comparison shows. Any advice welcome. Thanks.

PS I have posted here because the New Question form would not opn

When I export TIFF files, I use No Resampling (Nearest Neighbor) which ensures this kind of problem can't happen. But there is no resampling option in the Export Web Format dialog. I had hoped it would respect the resampling option I set the Export Raster Imagery dialog, but that doesn't seem to be the case.

Here's an example, shown in Photoshop and zoomed 3200% so you can see the individual pixels. The problem only appears in areas of high contrast. For example, in the TIFF file there are pixels with RGB values of (1,139,255) next to pixels with values of (1,140,0). The exported PNG map tiles contain a pixel with RGB values of (1,139,117) between the original pixels. This creates a big problem in my app when decoding RGB values in these tiles.

Is there some workflow that allows creation of PNG map tiles with no resampling (nearest neighbor)? The source TIFF file was created at a resolution of 1.2 meters with Web Mercator projection and the tiles were exported at Level 17. I am NOT using the option to create 8-bit pallete files.