# Example which highlights the limitations of NetCDF-style coordinates for large geospatial rasters

**URL:** <https://discourse.pangeo.io/t/example-which-highlights-the-limitations-of-netcdf-style-coordinates-for-large-geospatial-rasters/4140>\
**Category:** Uncategorized\
**Created:** [April 3, 2024, 4:05pm UTC](https://discourse.pangeo.io/t/example-which-highlights-the-limitations-of-netcdf-style-coordinates-for-large-geospatial-rasters/4140 "2024-04-03T16:05:39Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![rabernat](https://yyz2.discourse-cdn.com/flex030/user_avatar/discourse.pangeo.io/rabernat/32/22_2.png) [@rabernat](https://discourse.pangeo.io/u/rabernat)\
**Post date:** [April 25, 2024, 2:53pm UTC](https://discourse.pangeo.io/t/example-which-highlights-the-limitations-of-netcdf-style-coordinates-for-large-geospatial-rasters/4140/26 "2024-04-25T14:53:14Z")

</div>

I have proposed a very concrete task that could be used to advance this issue in this discussion:

> **[How can I implement a simple "Range Index" using custom Indexes? ·...](https://github.com/pydata/xarray/discussions/8955#discussioncomment-9226372)**
>
> Motivated by discussions in the GeoZarr spec and Pangeo Discourse, I've convinced myself that it's important for Xarray to be able to represent "analytic" coordinates, i.e. coordinates defined via ...

> _Try to modify RioXarray’s [`generate_spatial_coords`](https://github.com/corteva/rioxarray/blob/bf6cbda6728977651987c7ba31e0848e927a825e/rioxarray/rioxarray.py#L120-L133) to create a custom Range index from the affine parameters instead of a explicit x, y coordinate variables._

Is anyone here susceptible to nerd swiping? 🤓

---

_[View the full topic](https://discourse.pangeo.io/t/example-which-highlights-the-limitations-of-netcdf-style-coordinates-for-large-geospatial-rasters/4140)._