MetOffice / MetOffice/CSET

Data crossing 0 degrees lon ends up plotting the enitre globe

Open
#1,987 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Python
Stars
33
Forks
19
Avg merge
1d 22h
Merged PRs (30d)
30

Description

### Describe the bug

Data crossing 0 degrees lon ends up plotting the entire globe. This may be due to the underlying data being 340ish - 373 ish. as the longitude degrees. Example below.

Image

### How to reproduce

Steps to reproduce the behaviour:

1. Use some data that crosses the 0degree lon line.
2. Request a spatial plot.

### Expected behaviour

Data should be constrained and pick the appropriate project for the coordinates rather than splitting them and plotting lots of empty data.

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

Start by reproducing a spatial plot with longitude values around 340–373 that cross the 0-degree longitude line. Trace how the plotting path selects the appropriate project for those coordinates; done means the data remains constrained to the relevant region instead of producing an empty-data plot of the entire globe.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
data-visualization
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.