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!



Easily Share Workflows With the Analytics Repository

Easily Share Workflows With the Analytics Repository

10/27/2025

With the recent release of ENVI® 6.2 and the Analytics Repository, it’s now easier than ever to create and share image processing workflows across your organization. With that in mind, we wrote this blog to: Introduce the Analytics Repository Describe how you can use ENVI’s interactive workflows to... Read More >

Deploy, Share, Repeat: AI Meets the Analytics Repository

Deploy, Share, Repeat: AI Meets the Analytics Repository

10/13/2025

The upcoming release of ENVI® Deep Learning 4.0 makes it easier than ever to import, deploy, and share AI models, including industry-standard ONNX models, using the integrated Analytics Repository. Whether you're building deep learning models in PyTorch, TensorFlow, or using ENVI’s native model creation tools, ENVI... Read More >

Blazing a trail: SaraniaSat-led Team Shapes the Future of Space-Based Analytics

Blazing a trail: SaraniaSat-led Team Shapes the Future of Space-Based Analytics

10/13/2025

On July 24, 2025, a unique international partnership of SaraniaSat, NV5 Geospatial Software, BruhnBruhn Innovation (BBI), Netnod, and Hewlett Packard Enterprise (HPE) achieved something unprecedented: a true demonstration of cloud-native computing onboard the International Space Station (ISS) (Fig. 1). Figure 1. Hewlett... Read More >

NV5 at ESA’s Living Planet Symposium 2025

NV5 at ESA’s Living Planet Symposium 2025

9/16/2025

We recently presented three cutting-edge research posters at the ESA Living Planet Symposium 2025 in Vienna, showcasing how NV5 technology and the ENVI® Ecosystem support innovation across ocean monitoring, mineral exploration, and disaster management. Explore each topic below and access the full posters to learn... Read More >

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 >

1345678910Last
«November 2025»
SunMonTueWedThuFriSat
2627282930311
2345678
9101112131415
16171819202122
23242526272829
30123456
17167 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.