Why is the MOVE_TO_NEW_LAYER Parameter not keeping the original layer's projection?
In my script, I am importing the same shapefile of a statewide contour map and using EDIT_VECTOR to crop it to a MBR layer created earlier in the script. I am also using the MOVE_TO_NEW_LAYER parameter and NEW_LAYER_NAME to separate the cropped contours from the original so that I can unload the original with all of the deleted features. (All of this is done in a DIR_LOOP). However, every time I run the script, the new contour layer seems to be created with a different projection than the original so that all of the contour features show up in a very small collection far from the original location. I have tried to use NEW_LAYER_PROJ, but none of the PROJ values inputted seemed to work.
Here is my script (the relevant section)
Any help would be appreciated. I'm mainly wondering how the NEW_LAYER_PROJ parameter is meant to be used.
Answers
-
Recently encountered a similar defect. Used a polygon to create a new data set, copied to clipboard, pasted to a new layer. The data shifted a small bit. I had to rectify it, but it should not have shifted.
Categories
- 13K All Categories
- 5.8K Features Discussion
- 349 Downloading Imagery
- 1.3K Elevation Data
- 385 Georeferencing Imagery Discussion
- 652 GM Script Language
- 56 User Scripts
- 115 GPS Features
- 421 Projection Questions
- 835 Raster Data
- 1.4K Vector Data
- 6.7K Support
- 181 Announcement and News
- 939 Bug Report
- 562 SDK
- 1.2K Suggestion Box
- 3.7K Technical Support
- 579 Other Discussion
- 132 GIS Data Sources
- 27 Global Mapper Showcase
- 244 How I use Global Mapper
- 110 Global Mapper Forum Website

