Best Recent Content
Sorry, for the delay. It's been pretty busy here. It looks like the points are not in a valid location this file has this global rectangle.
mGlobalRect.mMaxX == 440230.32666000008
mGlobalRect.mMaxY == 4588327.3269700008
mGlobalRect.mMinX == 439857.01470000006
mGlobalRect.mMinY == 4587304.1915500006
Blue Marble Geographics will provide support before you buy a license. I suggest that you send them your question directly via e-mail (email@example.com). If you are trying to resolve a problem, be sure to include a detailed description of your work flow, and the data that you used. This will ensure a faster response.
It looks like your problem is here:
gM_AreaVolumeParams_T.mSize = 3;
gM_AreaVolumeParams_T.mPoints = intPtr;
gM_AreaVolumeParams_T.mNumPoints = 4;
mSize is the size of the structure if you can get that size yourself or if you set it to 0 then I believe it will be calculated internally. Also mNumPoints should be 3 as you only have 3 points.
I hope this helps
- Make sure you have assigned the elevations first then (Vertex Editing > Edit Feature Vertices)
- Select the lines
- Advanced Feature Creation Options > Create Point Features Spaced Along Selected Features
Alternatively, if you have reasonably clean contours you may be able to convert them to lines by creating area features based on the contour colour values and then converting those to center lines:
- Right-click the raster layer
- Create Area Features from Equal Values in Selected Layer
- Choose Only Create Areas for Selected Colors and enter the RGB value of your contour e.g. 0,0,0 for black
- Select the newly created area features
- Right-click > Move/Reshape Feature(s) > SIMPLIFY
- Right-click > Move/Reshape Feature(s) > SMOOTH
- Right-click > Advanced Feature Creation Options > Create Area Skeletons/Center Lines
- Join any gaps in the new contour lines:
- Right-click > Crop/Combine/Split Functions > COMBINE
- Repeat steps 5 & 6 to reduce the points and smooth
This is an example I created using the above workflow - took around 10-15 minutes. Using the Image Swipe Tool I have shown the original raster on the right and the results of the process above on the left. The image below that shows the raster below the new contour lines.
When processing LiDAR data in the past with other software, I have had the option of choosing how the LiDAR data is rectified based on the trajectory of the platform (IMU) collecting the data. This adjustment of the trajectory is then applied to the LiDAR point cloud. I know GM does not use the trajectory, but does "Fit LiDAR to Control Points" function follow one of the following:
1. non-rigid, with translation - all the lidar points or shifted globally, then the LiDAR points around the control points are shifted locally and all LiDAR points in between are interpolated.
2. non-rigid, no translation - there is no shift globally, the LiDAR points around the control points are shifted locally and there is NO interpolation.
3. Rigid, with translation - all the lidar points or shifted globally, there is are no local adjustments made around the control points.
Global Mapper 18.2 + LiDAR module
Intel Core i7-5960X @ 3.00Ghz
I haven't timed it, but mine starts in about 20 seconds. I'll have to time it the next time I'm at that computer. Am running Win7 64-bit with 8Gb RAM, and the latest daily build. The time for GM to start has been similar for a long time, probably years. I'm not bothered since it stays open once I have opened the program. I have a single license, the only one in this office, and I'm the only one that uses it. I am on the company network, and normally using files stored on our server, but the GM-open time is the same whether I open it with a workspace file (network) or simply start it on my computer without any files initially.
Yes, I frequently have mail and browsers open when I start GM. I don't think it affects the speed required for GM to open. You have more of my gory details in a problem being worked by the programmers, concerning the pixel-to-point beta code.
I will report on Monday after I do some testing. Holler if you would like specific details while I test.
Hello, I am trying to display features to scale under the ocean surface. I need to show that my features are floating well above the ocean floor. I have bathymetry data for the ocean floor and I have 3D vector features representing my pens. The pens are 30m in depth from the ocean surface. The features have elevation attribute (0m) and Height attribute (-30m), but when I view them in 3D they are stuck to the ocean floor, rather than the ocean surface. How do I tell my features to be relative to ocean surface?