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!



Monitor, Measure & Mitigate: Integrated Solutions for Geohazard Risk

Monitor, Measure & Mitigate: Integrated Solutions for Geohazard Risk

9/8/2025

Geohazards such as slope instability, erosion, settlement, or seepage pose ongoing risks to critical infrastructure. Roads, railways, pipelines, and utility corridors are especially vulnerable to these natural and human-influenced processes, which can evolve silently until sudden failure occurs. Traditional ground surveys provide only periodic... Read More >

Geo Sessions 2025: Geospatial Vision Beyond the Map

Geo Sessions 2025: Geospatial Vision Beyond the Map

8/5/2025

Lidar, SAR, and Spectral: Geospatial Innovation on the Horizon Last year, Geo Sessions brought together over 5,300 registrants from 159 countries, with attendees representing education, government agencies, consulting, and top geospatial companies like Esri, NOAA, Airbus, Planet, and USGS. At this year's Geo Sessions, NV5 is... Read More >

Not All Supernovae Are Created Equal: Rethinking the Universe’s Measuring Tools

Not All Supernovae Are Created Equal: Rethinking the Universe’s Measuring Tools

6/3/2025

Rethinking the Reliability of Type 1a Supernovae   How do astronomers measure the universe? It all starts with distance. From gauging the size of a galaxy to calculating how fast the universe is expanding, measuring cosmic distances is essential to understanding everything in the sky. For nearby stars, astronomers use... Read More >

Using LLMs To Research Remote Sensing Software: Helpful, but Incomplete

Using LLMs To Research Remote Sensing Software: Helpful, but Incomplete

5/26/2025

Whether you’re new to remote sensing or a seasoned expert, there is no doubt that large language models (LLMs) like OpenAI’s ChatGPT or Google’s Gemini can be incredibly useful in many aspects of research. From exploring the electromagnetic spectrum to creating object detection models using the latest deep learning... Read More >

From Image to Insight: How GEOINT Automation Is Changing the Speed of Decision-Making

From Image to Insight: How GEOINT Automation Is Changing the Speed of Decision-Making

4/28/2025

When every second counts, the ability to process geospatial data rapidly and accurately isn’t just helpful, it’s critical. Geospatial Intelligence (GEOINT) has always played a pivotal role in defense, security, and disaster response. But in high-tempo operations, traditional workflows are no longer fast enough. Analysts are... Read More >

1345678910Last
«September 2025»
SunMonTueWedThuFriSat
31123456
78910111213
14151617181920
21222324252627
2829301234
567891011
16669 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.