Skip to content

MY 33 observations missing from region_names lookup #12

Description

@michaelaye

Problem

The v3.1 catalog contains 13 MY 33 observations, and they are present in the coverage file (FnotchCoverage_v3.1.csv). However, io.get_region_names() does not include them, so they are dropped from any analysis that joins on ROI.

Details

The 13 unmapped MY 33 observations fall into two spatial clusters:

Lat N obs Likely ROI
-86.39 5 Manhattan Classic
-85.05 to -85.15 8 Macclesfield / Ithaca area

Ls range: 182–305°, providing good seasonal coverage.

Suggested fix

Assign ROIs to these 13 obsids by nearest-neighbor matching against the existing regions table (same method used for MY 28–32), then regenerate the region_names data file.

Obsids

ESP_046642_0935  Ls=182.4  lat=-86.39
ESP_046769_0950  Ls=188.0  lat=-85.14
ESP_046770_0950  Ls=188.1  lat=-85.14
ESP_046862_0950  Ls=192.2  lat=-85.07
ESP_046971_0935  Ls=197.2  lat=-86.39
ESP_047103_0935  Ls=203.3  lat=-86.39
ESP_047327_0935  Ls=213.9  lat=-86.39
ESP_047363_0950  Ls=215.6  lat=-85.06
ESP_047653_0950  Ls=229.7  lat=-85.05
ESP_047696_0935  Ls=231.8  lat=-86.39
ESP_048431_0950  Ls=268.1  lat=-85.05
ESP_048576_0950  Ls=275.2  lat=-85.06
ESP_049209_0950  Ls=305.2  lat=-85.15

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions