Skip to content

Tracking: UTM and MGRS grids and coordinate readouts #1042

Open

Description

@flight1973

Tracking issue for the roadmap item "UTM and MGRS grids and coordinate readouts" (Self-contained, any time). Each piece below is its own pull request and can land on its own; this issue keeps the order and links them. I'm taking pieces 1 to 3 first.

What exists

Pieces

  1. UTM conversion in rustgis-geom: longitude/latitude to and from zone, hemisphere, easting and northing on WGS 84, by Karney's Krüger series (accurate to nanometers, no new dependency), with the Norway and Svalbard zone exceptions. Tested against GeographicLib's values.
  2. UPS in rustgis-geom: Universal Polar Stereographic north of 84°N and south of 80°S, where MGRS leaves UTM. Needs 1.
  3. MGRS in rustgis-geom: encoding (grid zone designator, 100 km square letters, 1 m to 100 km precision) and parsing. Tested against GeographicLib and NGA examples. Needs 1 and 2.
  4. Status bar readout: decimal degrees, DMS, UTM or MGRS, in place of the DMS switch, kept in settings. Needs 1 and 3.
  5. UTM and MGRS input: the search box and map.goToXY take 33U 455123 5411234 and 33UUP5512311234. Needs 1 and 3.
  6. A conversion command between longitude/latitude, UTM and MGRS, for the CLI, Python and the AI Assistant. Needs 1 and 3.
  7. UTM grid on the map: zone and latitude-band lines, and eastings and northings at an interval that suits the scale, reusing feat(layouts): measured grids, eastings and northings in a projected system, beside the graticule #1012's measured-grid drawing. Needs 1.
  8. MGRS grid on the map: 100 km squares with their letters, and finer lines as the map zooms in. Needs 3 and 7.
  9. MGRS labels on layout grids: feat(layouts): measured grids, eastings and northings in a projected system, beside the graticule #1012's measured grid labeled in MGRS, with grid-zone designations. Needs 3.

As far as I can see, none of them changes the data model, a dependency, a command's id or parameters, or the project format; pieces 4 and 7 add a setting and a View option, placed by the ribbon guidelines.

Two questions before pieces 4 and 7: should the readout format be a per-map setting or an app preference? And should the map grids be a type of View › Graticule (as layout grids have a Type) or a command of their own?

Activity

  1. pick2510 commented on Nov 10, 2026

    @pick2510
    Contributor

    Pieces 1, 3, 4 and 5 landed with #1429 (readouts, search, copy).

    On piece 7: why only UTM? #1012 already draws a measured grid in any projected system on layouts. I'd do the same on the map:

    • Default: the map's own system when it is projected, otherwise the UTM zone at the centre.
    • "UTM, all zones" as its own mode, for maps across zone boundaries. MGRS (piece 8) builds on it.

    People mostly read coordinates off national grids (LV95, British National Grid, State Plane), so UTM alone doesn't help them much.

    That also answers the second question: a Type under View › Graticule (degrees, projected, UTM zones, MGRS), the same as layout grids have.

    I'm taking pieces 7 and 9, since #1012 is mine.

  2. flight1973 commented on Nov 11, 2026

    @flight1973
    ContributorAuthor

    Thanks @pick2510, agreed. The map's own projected system as the default makes more sense, with "UTM, all zones" as its own mode and MGRS on top of it. A Type under View › Graticule answers the second question too. Pieces 7 and 9 are yours.

    Two things I found checking main:

    • Piece 5 is only half done. The search box takes UTM and MGRS, but map.goToXY and the By Coordinates dialog still take decimal degrees only. Considerations regarding RustGIS and a proposal for improvements #1157 asks for the same thing. I'll pick that up.
    • Piece 2, UPS, isn't in yet. utm.rs refuses polar references with GridError::Polar, so MGRS stops at 84°N and 80°S, and the MGRS grid (piece 8) will need UPS near the poles. I'll take piece 2.
  3. flight1973 commented on Nov 16, 2026

    @flight1973
    ContributorAuthor
  4. pick2510 commented on Nov 16, 2026

    @pick2510
    Contributor

    Fine for me.

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

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions