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!



New ENVI Agent, IDL Agent, and GeoAgent Quick Guides

New ENVI Agent, IDL Agent, and GeoAgent Quick Guides

6/9/2026

The recent release of ENVI® Agent, IDL® Agent, and GeoAgent™ revolutionize how users interact with geospatial software. These agentic AI applications act as partners to plan, simplify, and execute complex workflows. Knowing where to start can be challenging for new users. To this end, we developed three new quick guides to... Read More >

Introducing NISAR Data Support

Introducing NISAR Data Support

6/5/2026

The release of ENVI® SARscape 6.3 in April 2026 includes preliminary support for NASA-ISRO SAR (NISAR) data. The NISAR mission is a joint Earth-observing satellite project between NASA and the Indian Space Research Organization designed to monitor changes in the planet’s land and ice surfaces using advanced radar imaging. It... Read More >

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 >

1345678910Last
«June 2026»
SunMonTueWedThuFriSat
31123456
78910111213
14151617181920
21222324252627
2829301234
567891011
20090 Rate this article:
No rating

Re-projection Over the 180th Meridian

Anonym

With certain data formats, especially those with large swaths like AVHRR, NPP VIIIRS, and MODIS, there are times when the spatial extent of the data crosses over the 180th meridian. When measuring longitude in degrees for a projection, this can present a problem since the longitude is not continuous as it goes from -180 to 180 degrees. There are a few ways to correct for this anomaly in the data using ENVI and IDL in order to re-project it properly. For the examples below, let's say that we have the variables "lat","lon", and "data" read from an AVHRR HDF4 file. One way to get these variables using IDL:

e = envi(/current)

hdf_id = hdf_sd_start('my_hdf_file.hdf')

hdf_sd_fileinfo, hdf_id, numData,atts

dataset_names = strarr(numData)

for i=0, numData-1 do begin

 hdf_sd_getinfo, hdf_sd_select(hdf_id, i),name=name

 dataset_names[i] = name

endfor

  

index = where(dataset_names eq 'avhrr_band1')

lon_index = where(dataset_names eq 'longitude')

lat_index = where(dataset_names eq 'latitude')

  

dataset_id=hdf_sd_select(hdf_id, index)

hdf_sd_getdata, dataset_id, data

hdf_sd_endaccess, dataset_id

  

lon_id=hdf_sd_select(hdf_id, lon_index)

hdf_sd_getdata, lon_id, lon

hdf_sd_endaccess, lon_id

  

lat_id=hdf_sd_select(hdf_id, lat_index)

hdf_sd_getdata, lat_id, lat

hdf_sd_endaccess, lat_id

; Close the file:

hdf_sd_end,hdf_id

 

How can I tell if my data crosses the 180th meridan?

Depending on your dataset, there are few ways to test if you will need to correct for the extent crossing over from -180 degrees to +180 degrees. If you are working in a certain area, the US and Hawaii for example, you can test to see if your longitude is over a certain threshold. If you know that you are looking at data in North America, you can test to see if you have any longitude values near 180 degrees by taking the maximum of your longitude grid:

if max(lon)gt 179 then ...

A more robust way to check if your data set crosses the180th meridian is to take the difference between the minimum and maximum longitude. If the data does cross over the 180th meridian, the max will be ~180 and the minimum will be ~-180. It is unlikely that your data will wrap around the entire globe, like in the case of data around the North and South Poles, but that I'll save for another entry. So we can assume that if the difference between the max and min longitude is close to 360 degrees, the 180th meridian has been crossed:

if (max(lon)- min(lon)) gt 359 then ...

 

What can I do to correct for this case?

If you want to use the GLT reprojection tool available in ENVI to get the data on a regular grid, and your data crosses the 180th meridian, you are in luck! The engineers at here at Exelis put in the time to correct for this case automatically. If your data crosses the 180th meridian, the resulting image will be on the right side (+180 degrees) of a standard WGS-84 world map. If you'd rather it be on the left side of a WGS-84 map (-180 degrees), just subtract 360 degrees from the "lon" variable before doing GLT reprojection:

lon -= 360

Here is an example display in ENVI – in one image I applied the 360 shift. In the other I left it as is.

Please login or register to post comments.