Best Like Content
The zoom to location feature could certainly be useful, and I have opened an enhancement request for this (22618).
We are currently in the early planning phases of Global Mapper Mobile 2.0. We would be very interested to know more about what features you, and others, would find useful and how you would like to use the application in your work. You may post your suggestion here or submit them to directly to BMG support via email (firstname.lastname@example.org).
The GPS keeps working after exiting GMM, is it supposed to be that way?. The location icon only disappears when I force close the app from android menu.
This was done so that accurate location data would be available immediately once the app is brought to the foreground. We are considering adding some options that would give the user more control over how the location services are used. Disabling while the app is in the background, and not recording track data, is among these.
there has been a quite (quite) big time lag here, but in regards to your above answer, actually my question at the time was not really answered.
I have prepared two more screenshots from a current project, which might help to illustrate what I am looking for. Basically we are installing large scale solar systems and in such case the North- and South-facing slopes are very important factors. Apart from the shadowing effect (I have some other questions I sent you guys about this right now) it is also about the installation of the system. I am basically using the topo-analysis functions of GM to give me a better idea of how long I need to make the poles that support the system. As the poles are usually installed in two rows, one front and one back pole, I need to now the N-S slope of the ground in order to now how long I need to make those poles. The E-W inclination is only secondary in that regard, as the structure on top can be adjusted accordingly.
What I am currently doing is what you can see in the screenshot, which is basically just creating section views in NS-direction to check the change in inclination. This is fine, but it is time consuming because I need to analyse each section individually and arbitrary because I have to estimate myself based on the contours which areas I best divide. So if I could color the area only based on the northern slope aspect I would have a very clear picture.
As an example, the section 1 runs through an embankment of the site, which has an inclination of about 29° in EW direction, but in NS direction it is almost flat.
The slope direction function does not really help me here either, because it basically colors everything that is facing even slightly in northern direction, but it does not tell me how much.
So maybe with this information you can let me know one more time if the existing functionality of GM may be able to do something or if you might be able to add something like this without too much effort.
Thanks and regards, Jakob
It may help to visualize what GM is trying to deliver when generating your contours. The image below is from your data where I have created a 0m user contour and compared it to your gridded surface when clamped out to a maximum elevation of 0m. What GM does is generate a reasonable contour along fragmented pixel data as shown. Therefore I assume that when you confine the process to a different area the second time around, that each contour might start at different points and therefore take slightly different routes than before. Note that your pixels are 10m and that you are generating 0.5m contours with it.
First, make sure you have the latest version of Global Mapper. If the problem persists in the latest version, please send a description of your workflow, a copy of your data (if possible), and the results to Blue Marble Geographics Support (email@example.com). This will ensure that the support team will be notified of the problem and can work on a solution.
I am currently wondering about the analysis of cast shadows based on the the terrain.
My background is, that I am trying to simulate the near shading effects by trees, buildings and other elevated objects onto lower terrain to see if the terrain behind / below will be shaded during specific hours of the day.
I figured out, that the shaded relief function allows for setting of different sun angles and azimuth and so I tried to work with this. However, it appears to me, that this functionality will only display, whether or not a specific area would in theory receive direct sunlight but it does not cast / show the shadow, which an object will throw.
So for example, I am attaching a view from a 3D model, where I overlaid three hill shading options. The model is located in Yamagata, Japan.
Option 1 (10:00 am)
Sun angle 24.5°
Option 2 (12:00 pm)
Sun angle 28.5°
Option 3 (14:00 pm)
Sun angle 20°
I am aware, that the above numbers are not 100% correct, but it is accurate enough for my purposes.
My point is, that the programm just creates dark areas, where there is no direct sunlight, but it does not cast shadows. In this case, there are two buildings in the centers, which are roughly 30m and 40m high and they would probably cast quite far shadows behind them.
Is there a way to do this? I would like to see, how far shadow is reaching but right now it seems that the programm is not doing that.
Thanks for response, Katrina. I have seen the excellent webinar. The issue seems to be with the higher point densities of the photo generated point cloud. I will continue to work with smaller sections. I don't know if there are any recommended settings for such a file as a starting point. Using '1 point' spacing for the gridding seems to tight, and 1 or 2 meters may be to large. There are so many settings, it is a little daunting. I know there is personal training available; however, is there a chance to just talk with someone on the phone for a short conversation? BTW, the link for the case study above did not work.
I'm running this technically under a script, but it's also happening in gui mode so under here it goes. Version is 17.2; can provide dongle details if required.
I'm creating a bunch of buffer areas that have to be precisely on the whole metre. I find, though, that when I create a buffer - be it from the little button or LAYER_BOUNDS_EXPAND, it's always up to 35cm or so out (yes, when checking metadata, not just zooming). My original areas are showing up as precisely on the metre. What's happening?
We have a bunch of huge projects coming in that require this not to be happening so help would be very very much appreciated, even if just to see what I am missing.
Alternatively, a way to make elev grids etc line up with the metre is also welcome
I’ve been playing with the hydro-flattening and have another problem I’m not quite understanding. I’m testing the functionality of different gridding methods and am having some problems when I combine the bin methods with hydro-flattening polygons (note this is just test data). As you can see in the screenshots, the TIN method respects the boundaries of my polygon, whereas the bin method connects parts of the polygon. You see in the screenshot that the bin method has cut part of my data off. The bin parameters are set to only 1m while the gap it is bridging is about 75m.