Problems with elevations of 3D vector features

dcoggin
Global Mapper UserTrusted User
Mike,
I continue to have problems that creep up where I've found the elevations on 3d features have been incorrectly changed. I have found two particular sets of steps that cause incorrect elevations:
1)
- Create a 4-sided area feature on the User Created Features layer
- Select layer options and change elevation units to feet
- Edit the feature and assign vertex elevations (1 foot)
- Join two of the vertices to form a triangle
- Check the vertex elevations and the joined vertices now display elevations of .304 ft
2)
- Open the two attached shapefiles in GM
- There is one area feature and one line feature. Both have vertex elevations in feet.
- Check the elevation of the vertex at the intersection of the area and line features. The elevation is -2.21 feet on both features.
- Use Advanced Feature Creation Options to create a line feature on the User Created Features layer from the imported area feature. The elevation of the vertex of the newly created line feature at the intersection with the existing line now says -0.674 m.
- Copy (Ctrl-C) the original line feature and paste it using the “Paste to new layer append [COPY] . . .” option
- Now check the elevations of the line created from the area. The intersection vertex value is -0.674 ft.
Interestingly, if you create a workspace using the two attached features, save and open the workspace, then when you create the line from area the elevations remain in feet -- the same as the original area feature.
I have “Native Overlay Units” selected in the “Elevation Display/Export Units” box on the Vertical Options tab of Configuration, and I'm using 15.1 (b040114) 64-bit. Thanks for looking at this.
David
I continue to have problems that creep up where I've found the elevations on 3d features have been incorrectly changed. I have found two particular sets of steps that cause incorrect elevations:
1)
- Create a 4-sided area feature on the User Created Features layer
- Select layer options and change elevation units to feet
- Edit the feature and assign vertex elevations (1 foot)
- Join two of the vertices to form a triangle
- Check the vertex elevations and the joined vertices now display elevations of .304 ft
2)
- Open the two attached shapefiles in GM
- There is one area feature and one line feature. Both have vertex elevations in feet.
- Check the elevation of the vertex at the intersection of the area and line features. The elevation is -2.21 feet on both features.
- Use Advanced Feature Creation Options to create a line feature on the User Created Features layer from the imported area feature. The elevation of the vertex of the newly created line feature at the intersection with the existing line now says -0.674 m.
- Copy (Ctrl-C) the original line feature and paste it using the “Paste to new layer append [COPY] . . .” option
- Now check the elevations of the line created from the area. The intersection vertex value is -0.674 ft.
Interestingly, if you create a workspace using the two attached features, save and open the workspace, then when you create the line from area the elevations remain in feet -- the same as the original area feature.
I have “Native Overlay Units” selected in the “Elevation Display/Export Units” box on the Vertical Options tab of Configuration, and I'm using 15.1 (b040114) 64-bit. Thanks for looking at this.
David
Comments
-
David,
I was able to fix the first issue with the elevation units not converting properly when joining vertices. I have placed a new build at http://www.bluemarblegeo.com/downloads/global-mapper/global_mapper15.zip with the latest changes for you to try. Simply download that file and extract the contents into your existing v15.xx installation folder to give it a try. If you are using the 64-bit v15 version there is a new build at http://www.bluemarblegeo.com/downloads/global-mapper/global_mapper15_64bit.zip .
I have not however been able to reproduce the second issue, although perhaps my fix for the other one fixed the issue before I could test it, so can you see if it is ok now?
Thanks,
Mike
Global Mapper Guru
geohelp@bluemarblegeo.com
Blue Marble Geographics for Coordinate Conversion, Image Reprojection and Vector Translation -
Mike,
Thanks for fixing the first issue. It works for me with the new version. I'm still seeing the same problem with the second issue. It only occurs if you import the shapefiles into a new session of GM (rather than loading them as part of a workspace), and if when copy and pasting the line feature, you paste it using the option with appending [COPY] to the new layer name. The line feature to copy is the original imported line feature, not the line feature created from the area feature.
Thanks,
David -
David,
Ok I'll try a bit harder to reproduce this tomorrow. Once I can reproduce it should be easy to fix.
Thanks,
Mike
Global Mapper Guru
geohelp@bluemarblegeo.com
Blue Marble Geographics for Coordinate Conversion, Image Reprojection and Vector Translation -
David,
I believe I have found the problem and fix it. The 'Vertical Display/Export Units' option on the Configuration dialog also affected it. I have placed a new build at http://www.bluemarblegeo.com/downloads/global-mapper/global_mapper15.zip with the latest changes for you to try. Simply download that file and extract the contents into your existing v15.xx installation folder to give it a try. If you are using the 64-bit v15 version there is a new build at http://www.bluemarblegeo.com/downloads/global-mapper/global_mapper15_64bit.zip .
Thanks,
Mike
Global Mapper Guru
geohelp@bluemarblegeo.com
Blue Marble Geographics for Coordinate Conversion, Image Reprojection and Vector Translation -
Mike,
I'm seeing a problem that is very similar to the problem mentioned in 1) above. I'm attaching a workspace with two one-segment lines. When you join the two close vertices from the different lines, the elevation on one of the vertices converts to meters (-.03 to -0.098) even though the lines are both on layers designated as using feet for elevations.
Thanks for looking at it.
David -
David,
I've fixed the issue. I have placed a new build at http://www.bluemarblegeo.com/downloads/global-mapper/global_mapper15.zip with the latest changes for you to try. Simply download that file and extract the contents into your existing v15.xx installation folder to give it a try. If you are using the 64-bit v15 version there is a new build at http://www.bluemarblegeo.com/downloads/global-mapper/global_mapper15_64bit.zip .
Thanks,
Mike
Global Mapper Guru
geohelp@bluemarblegeo.com
Blue Marble Geographics for Coordinate Conversion, Image Reprojection and Vector Translation
Categories
- 12.5K All Categories
- 5.5K Features Discussion
- 314 Downloading Imagery
- 1.3K Elevation Data
- 377 Georeferencing Imagery Discussion
- 611 GM Script Language
- 50 User Scripts
- 112 GPS Features
- 397 Projection Questions
- 803 Raster Data
- 1.3K Vector Data
- 6.5K Support
- 161 Announcement and News
- 893 Bug Report
- 557 SDK
- 1.2K Suggestion Box
- 3.7K Technical Support
- 542 Other Discussion
- 128 GIS Data Sources
- 26 Global Mapper Showcase
- 229 How I use Global Mapper
- 104 Global Mapper Forum Website