Best Recent Content
The easiest way to get a good IMPORT command is to have Global Mapper do it for you as follows:
- Load your data into Global Mapper
- Use the Elevation Options | Alter Elevation Values tab to set the Maximum Valid Elevation and Minimum Valid Elevation
- Save a workspace
- Open the workspace file in a text editor such as Notepad.
- Copy the IMPORT command (you will likely also want the DEFINE_PROJ ... END_DEFINE_PROJ lines also so you will have the correct projection information) to your script file.
Is there any way to customize how GM creates area skeletons? Lots of times, I only want a center line, but it creates all these other lines along with it, and if the polygon is very irregular, it tends to hang up for a long time figuring out all the skeleton parts. It would be nice if I could have it resolve at a coarser resolution than what it's automatically set for.
Thanks for any help...
To export one layer, right-click on the layer in the Control Center and choose Layers | EXPORT - Export Layer(s) to New File...
To export one zoom level, on the KML/KMZ Options window, remove the check next to "Automatically Grid Export of Large Data Sets...(etc.)"
To get transparency, specify the PNG format (as you already know) in combination with these other options.
I am trying to filter some noise out of a lidar dataset and need more details on how the "Height Above Ground Filtering" setting works. Specifically, what defines the "Ground" that is being referenced? Some average of the points selected? Only ground classified points? I select points using the digitizer edit tool and then want to unselect out the ones falling say 1ft below the ground level. I am trying to do this on a fairly uniformed sloped site - not flat - and getting very unexpected results depending on the values I enter.
Any help explaining the intended use of this would be exceptionally helpful.
Note: I have found using the automated ground classification routine does not filter noise below the surface because it thinks it is the lowest elevation. Similarly - playing with the reduce noise routine doesn't help.
As often, I found a solution right after asking the question !So, in case someone is looking for the answer :You must have a file with right format, e.g. :N3134.6008131;W0312.1044602;16.800457
N3134.6003947;W0312.1048163;15.119999Import the file using "open generic text file", select right coordinate order and forma, check "treat 3rd coordinate value as elevation", press OKExport > Export Vector / Lidar Format, select Lidar LAS file.Reimport the LAS file. You should have a nice set of color dots.And if you want to change to color scale, go to tools -> configure -> shader options and define the shader you want.You can then apply you new shader by selecting it from the dropdown menu at the top right of your screen.HTHAlex
I have problem, when exporting Google Tiles. After export boundaries of tiles getting visible. I wish to remove them, as they make the map less clear. It's not visible on the Global Mapper window, so it's not vector layer I could switch off. Which setting I need to change by export?
I met that problem only when exporting vector data (but not always!), I never met that issue when exporting rasters.
Global Mapper provides for entering a EPSG code number for data (datums) that are not listed.Search for "Qatar" and for "QND" to list those that have been defined. I see around ten different dates and descriptions that may be useful.For example, two for Qatar National Grid are:EPSG::4614EPSG::2932Use care which one you use, some are designed for geographic coordinates and others for projected coordinates. So you need to understand the data that you have to select the appropriate one. There are others that are designed for older data.
Upon further review, there is a way to avoid this when loading <filename>.pdf:1) On the first rectification dialog, after creating control points, save a .gcp or .pfw file named <filename>.gcp or <filename>.pfw (this is the default action when you choose File | Save ... on the rectification dialog.)2) On the first projection selection dialog, select the projection and put a check next to "Use Selected Projection for All Selected Files"The import will proceed without asking for any more information.
gghiggini said:Wouldn't be possible to useCALC_ATTR_FORMULA NEW_ATTR="newattr_2" FORMULA="Min(existingattr_1)"
The Max and Min functions used in the CALC_ATTR_FORMULA command do not operate on the entire data set. They return a result from the items in the list. For example,
CALC_ATTR_FORMULA NEW_ATTR="newattr_2" FORMULA="Min(existing_1, existing_2, existing_3)"will return the minimum value of the three attributes in the list.
If you are using the COPY_ATTRS command, MULTI_AREA=MIN or MULTI_AREA=MAX would copy the smallest or largest value of the attribute when multiple features intersect the area being copied.
You can now use the following parameters to limit the import bounds on the IMPORT_SPATIAL_DB command:
I have placed new builds with the latest changes at http://data.bluemarblegeo.com/downloads/global-mapper/dailybuilds/. Simply download the appropriate installer and run it to install the latest build.
- LAT_LON_BOUNDS - specifies the bounds to import in latitude/longitude degrees relative to the WGS84 datum. There should be 4 values in a comma-delimited list following the parameter name. The values should be in order of westmost longitude, southernmost latitude, easternmost longitude, northernmost latitude.
- LAYER_BOUNDS - specifies that the import should use the bounds of the loaded layer(s) with the given filename. For example, to import to the bounds of the file "c:\test.tif", you would use LAYER_BOUNDS="c:\test.tif". Keep in mind that the file must be currently loaded.
- LAYER_BOUNDS_EXPAND - specifies that the operation should expand the used LAYER_BOUNDS bounding box by some amount. The amount to expand the bounding rectangle by should be specified in the current global projection. For example, if you have a UTM/meters projection active and want to expand the bounds retrieved from the LAYER_BOUNDS parameter by 100 meters on the left and right, and 50 meters on the top and bottom, you could use LAYER_BOUNDS_EXPAND="100.0,50.0". You can also specify a single value to apply to all 4 sides, or supply 4 separate values in the order left,top,right,bottom.