Hexagon Geospatial
MENU

ERDAS IMAGINE

Discuss and share topics of interest using ERDAS IMAGINE the world’s leading geospatial data authoring system.
Showing results for 
Search instead for 
Do you mean 
Reply
Occasional Contributor
Posts: 5
Registered: ‎08-15-2016
Accepted Solution

Ground control points issue

Hi,

I am trying to geo-reference my image using a collected set of ground control points using a polynomial transformation. After I try to export said image into a .tiff file, I get the following error:

 

Parse error; Illegal character, ETXT_LCHAR('/'), at start of
<OptFileNodeSubList> in position 26

 

Any thoughts? I have created below the steps I took to get the point of my error:

1) Open a given .img file

2) Raster > Multispectral > Transform & Orthocorrect > Control Points

3) Select polynomioal geometric model > OK > Select GCPs from ASCII file (.txt)

4) Tab delimited separator/Skip 1 header row, x=5,y=4,z=3 > Ok

5) Custom Projection  > UTM > WGS84 > Spheroid and Datum both in UTM Zone 14N

6) Reference Map information box > close

7) Polynomial order 3 > close

8) Display Resample Image Dialog > Output file name as .tiff > Bilinear Interpolation > OK

 

In the process list, I get two copies, one that says done wiht a 100% green box, and one that says done with a 100% red box. Thanks.

 

Frequent Contributor
Posts: 153
Registered: ‎10-27-2015

Re: Ground control points issue

This error message refers typically a failed file export. Your TIF is not fully completed. It may have nothing to do with rectification - it can be just failed TIF write. Do following tricks

 

1) Look Session log - does it write something more there (File-Session- Session log)

 

2) Try writing output to .img instead of tif

 

 

timo

 

ps. The thing that has nothing to do with issue is that does it really make sense use 3rd degree polynomial? Would there be some smarter rectification method? I use very rarelt more than 1st polynomial order and if better is needed then solution is some ortho-rectification where terrain is used. So adding degrees just adds twisting in image - not neccessarily make it any more correct.

Anonymous
Posts: 0

Re: Ground control points issue

Hi,

What is your output file name?  A parse error can also indicate that you are using a character that the software does not like or one that is reserved for software only.

 

Occasional Contributor
Posts: 5
Registered: ‎08-15-2016

Re: Ground control points issue

Hi Timo,

Please see below:

 

16/08/16 16:11:46 SessionMgr(21932): Error when exiting program, not removing temporary input xform
16/08/16 16:11:46 SessionMgr(21932): ERROR: #1191 from resample
16/08/16 16:11:46 SessionMgr(21932): ERROR: ResampleLayer failed.
16/08/16 16:11:46 SessionMgr(21932): ERROR: #1771 from ResampleLayer
16/08/16 16:11:46 SessionMgr(21932): ERROR: Could not create output file for: image (directory omitted for security reasons)
16/08/16 16:11:46 SessionMgr(21932): ERROR: #10979 from eimg_LayerStackCreate
16/08/16 16:11:46 SessionMgr(21932): ERROR: efnp_FileNodeListGet failed
16/08/16 16:11:46 SessionMgr(21932): ERROR: #773 from efnp_FileNodeListGet
16/08/16 16:11:46 SessionMgr(21932): ERROR: FileNodeListParse failed
16/08/16 16:11:46 SessionMgr(21932): ERROR: #1623 from FileNodeListParse
16/08/16 16:11:46 SessionMgr(21932): ERROR: Parse error; Illegal character, ETXT_LCHAR('/'), at start of <OptFileNodeSubList> in position 76
16/08/16 16:11:46 SessionMgr(21932): resampleprocess.exe exited with status 1.
16/08/16 16:11:46 SessionMgr(21932): resampleprocess.exe exited normally.
16/08/16 16:11:48 SessionMgr(21932): ERROR: #773 from efnp_FileNodeListGet
16/08/16 16:11:48 SessionMgr(21932): ERROR: FileNodeListParse failed
16/08/16 16:11:48 SessionMgr(21932): ERROR: #1623 from FileNodeListParse
16/08/16 16:11:48 SessionMgr(21932): ERROR: Parse error; Illegal character, ETXT_LCHAR('/'), at start of <OptFileNodeSubList> in position 76

Frequent Contributor
Posts: 153
Registered: ‎10-27-2015

Re: Ground control points issue

There is the answer:

 

"Could not create output file for: image (directory omitted for security reasons)"

 

So your output folder is locked and nothing can be written there. Try output to some other folder where you have enough user rights to write or change folder permissions.

 

 

timo

Occasional Contributor
Posts: 5
Registered: ‎08-15-2016

Re: Ground control points issue

That was something I wrote on - I didn't feel comfortable listing my directory.

Occasional Contributor
Posts: 5
Registered: ‎08-15-2016

Re: Ground control points issue

I should also add that when I go to File>Save input to image node, I get the same error, mainly: "Parse error; Illegal character, ETXT_LCHAR('/'), at start of <OptFileNodeSubList> in position 26"

Staff
Posts: 585
Registered: ‎02-02-2016

Re: Ground control points issue

[ Edited ]

Hi Greg,

 

This error may be caused a data directory name that ends with an open parentheses. For example:  C:\data(

 

Or it could be a file name that contains an open parentheses followed by a slash. For example:  input.img(/image)

 

What is the name of your image file? Can you provide an example of your directory path that may contain symbols such as open parentheses and slashes? You can change the alphanumeric characters to protect your actual directory name for security reasons.

 

Please try removing any symbols from the file name and directory names before attempting to resample the image.

 

Regards,

 

Stephen Bent

Hexagon Geospatial Support

 

Occasional Contributor
Posts: 5
Registered: ‎08-15-2016

Re: Ground control points issue

This seemed to be the problem Stephen, thank you. Indeed the file directory was such that it was an open parentheses followed by a backslash.

Occasional Contributor
Posts: 5
Registered: ‎03-26-2019

Re: Ground control points issue

Hi sbent, 

Thnaks for your reply. I myself was getting this error so when I changed the name of my out file as well as output directory (now its on desktop) it worked. 
I have used several application softwares but Erdas Imagine needs to rectify these errors itself. Anything that is a obstacle to your workflow should be removed in newer versions of software so please fix this issue of just a filename like this "abc (165208)". This should not be an issue. 

Do you need immediate support?
If you encounter a critical issue and need immediate assistance please submit a Service Request through our Support Portal.