Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Add support for structured lat-lon grids

Open
#109 1 comment 0 reactions 1 assignee View on GitHub

@berkgeveci is already working on this.

Since Aug 10, 2026.

Assessment

This issue has not been assessed yet.

Description

discuss with users version 3

A common analysis workflow of the EAM developers/users includes calculating time averages and then remapping the simulation output from a cubed-sphere to a (structured) lat-lon grid. The resulting data files are often referred to as "climo" files. An example can be found at this URL.

In such files, the ncol dimension in an unstructured data file is replaced by a pair lat, lon. For example, the variable float AODDUST(time, lat, lon) in a climo file corresponds to float AODDUST(time, ncol) in the data file on the cubed sphere. The climo files typically contain the following 1D arrays that describe the structured mesh:

        double lat(lat) ;
                lat:long_name = "Latitude of Grid Cell Centers" ;
                lat:standard_name = "latitude" ;
                lat:units = "degrees_north" ;
                lat:axis = "Y" ;
                lat:valid_min = -90. ;
                lat:valid_max = 90. ;
                lat:bounds = "lat_bnds" ;
        double lon(lon) ;
                lon:long_name = "Longitude of Grid Cell Centers" ;
                lon:standard_name = "longitude" ;
                lon:units = "degrees_east" ;
                lon:axis = "X" ;
                lon:valid_min = 0. ;
                lon:valid_max = 360. ;
                lon:bounds = "lon_bnds" ;

@berkgeveci , can we add support for such files? (We could treat the variables as point data or cell data - I should ask whether there is a preference.) Thanks!

Dominant language
JavaScript
Stars
3
Forks
4
Avg merge
10h 10m
Merged PRs (30d)
7

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Kitware/QuickView

All issues in Kitware/QuickView

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.