X

NV5 Geospatial Blog

Each month, NV5 Geospatial posts new blog content across a variety of categories. Browse our latest posts below to learn about important geospatial information or use the search bar to find a specific topic or author. Stay informed of the latest blog posts, events, and technologies by joining our email list!



Monitoring Illegal Mining in the Amazon: Turning Persistent Data Into Actionable Insight

Monitoring Illegal Mining in the Amazon: Turning Persistent Data Into Actionable Insight

5/28/2026

Illegal mining over decades has constituted one of the most persistent and complex socio-environmental problems in the Brazilian Amazon. In recent years, with the increasingly intensive use of mechanized extraction, the associated environmental impacts—such as deforestation, intense soil disturbance, river siltation, and mercury... Read More >

From Answers to Action: Why ENVI and IDL Agents Go Beyond General AI

From Answers to Action: Why ENVI and IDL Agents Go Beyond General AI

4/20/2026

As generative AI tools like Claude and Gemini continue to gain traction, many organizations are asking the same question: Can general purpose AI actually support real geospatial workflows, or does it stop at surface-level answers? That question was front and center in our recent webinar, Meet Your New Partners in Science: ENVI... Read More >

Mapping Earthquake Deformation in Taiwan With ENVI

Mapping Earthquake Deformation in Taiwan With ENVI

12/15/2025

Unlocking Critical Insights With ENVI® Tools Taiwan sits at the junction of major tectonic plates and regularly experiences powerful earthquakes. Understanding how the ground moves during these events is essential for disaster preparedness, public safety, and building community resilience. But traditional approaches like field... Read More >

Comparing Amplitude and Coherence Time Series With ICEYE US GTR Data and ENVI SARscape

Comparing Amplitude and Coherence Time Series With ICEYE US GTR Data and ENVI SARscape

12/3/2025

Large commercial SAR satellite constellations have opened a new era for persistent Earth monitoring, giving analysts the ability to move beyond simple two-image comparisons into robust time series analysis. By acquiring SAR data with near-identical geometry every 24 hours, Ground Track Repeat (GTR) missions minimize geometric decorrelation,... Read More >

Empowering D&I Analysts to Maximize the Value of SAR

Empowering D&I Analysts to Maximize the Value of SAR

12/1/2025

Defense and intelligence (D&I) analysts rely on high-resolution imagery with frequent revisit times to effectively monitor operational areas. While optical imagery is valuable, it faces limitations from cloud cover, smoke, and in some cases, infrequent revisit times. These challenges can hinder timely and accurate data collection and... Read More >

1345678910Last
«June 2026»
SunMonTueWedThuFriSat
31123456
78910111213
14151617181920
21222324252627
2829301234
567891011
22117 Rate this article:
3.0

Getting information about the last error message

Anonym

Dave Hulslander is teaching a Scientific Programming with IDL class this week, and this morning he passed along a question from a student: when a runtime error occurs, how can you programmatically get the name of the file and the line number where the error occurred?

 

For example, let's say I have the following program:

pro throw_error
   compile_opt idl2
   
   print, a ; #fail
end
	

When called, THROW_ERROR will fail at the PRINT statement because you can't print an undefined variable in IDL:

IDL> throw_error
% PRINT: Variable is undefined: A.
% Execution halted at: THROW_ERROR         4 C:\Users\mpiper\blog\posts\20130823-get-last-er
  ror-message\throw_error.pro
%                      $MAIN$   	

You can see that IDL gives you the file and line in the file where the error occurred. But how can we get this programmatically?

Unfortunately, this information isn't included in !ERROR_STATE, the system variable that contains information on the last error that occurred, and also the place where I'd expect to find this information. Luckily, there a couple ways to get it. Here's one: use HELP with the LAST_MESSAGE and OUTPUT keywords:

IDL> help, /last_message, output=err_txt
IDL> help, err_txt
ERR_TXT         STRING    = Array[3]
IDL> print, err_txt
% PRINT: Variable is undefined: A.
% Execution halted at:  THROW_ERROR         4 C:\Users\mpiper\blog\posts\20130823-get-last-error-message\throw_error.pro
%                       $MAIN$ 
      

This is a little sloppy, but you can now use string processing routines to parse the error information out of the variable err_txt.

1 comments on article "Getting information about the last error message"

Avatar image

David Fanning

Or, you could just use cgErrorMsg from the Coyote Library. :-)

Catch, theError

IF theError NE 0 THEN BEGIN

Catch, /Cancel

void = cgErrorMsg()

RETURN

ENDIF

This will print out a nicely formatted traceback message with the line number where the error occurred.

Please login or register to post comments.