Coordinate grid maps explained — graticules, UTM zones, MGRS squares and State Plane, and how to read a grid reference

A coordinate grid map is a map with a reference network drawn over it, so a reader can turn a spot on the page into numbers and numbers back into a spot. There are two kinds of network. A graticule is made of angles: lines of latitude and longitude. A grid is made of distances: straight lines of eastings and northings in meters on a map projection, as in UTM, MGRS, the U.S. National Grid and State Plane. Choosing the right one comes down to extent and purpose, and a common source of error is mixing up the zone, the band or hemisphere letter, or the datum.

This post defines each system from its governing authority (NGA, USGS, FGDC, NGS), shows how to read a grid reference digit by digit, and lists the mix-ups worth guarding against. It then covers how ArcGIS Pro draws grids and how Pro and the ArcGIS Maps SDK for JavaScript convert coordinates. The Maps SDK sample was run on SDK 5.1.26 and 5.0.19 on October 7, 2026. The post closes with our own Grid Viewer, a free web app you can use to look at graticules, UTM zones and State Plane zones on a 2D map or a 3D globe, and with what that app still gets wrong.

Graticule or grid: angles versus distances

NGA draws the line cleanly. A graticule, or geographic reference system, references locations “using a system of angles”, and a geographic coordinate “is usually expressed in angular units of latitude and longitude.” A grid, or grid reference system, references locations “using a two dimensional Cartesian coordinate system referenced to a map projection”, and a grid coordinate “consists of and is written as an ordered pair of x and y values expressed in linear units.”

Why add a grid at all, when every point already has a latitude and longitude? Because latitude and longitude are hard to read off a flat sheet. The FGDC standard for the U.S. National Grid says it plainly: “it is difficult for humans to accurately determine a location coordinate from paper maps when latitude and longitude are used because they do not appear square on the flat map.” So, as a USGS fact sheet puts it, cartographers “superimpose on the map a rectangular grid consisting of two sets of straight, parallel lines, uniformly spaced, each set perpendicular to the other.”

ArcGIS Pro uses the same split for its layout elements. A graticule shows “location in geographic coordinates (degrees of latitude and longitude)”, and a measured grid shows “location using projected coordinates.” And since every place has a latitude and longitude, Pro notes that you can add a graticule “to a map in any projection.”

UTM: sixty zones, twenty latitude bands

Universal Transverse Mercator is the grid MGRS and USNG are built on. The facts below are NGA’s unless marked.

• 60 zones, each 6° of longitude wide, “with the exception of a few non-standard-width zones for Svalbard and southwest Norway.”
• Numbering starts at 180° and runs east. Zone 1 runs from 180°W to 174°W with its central meridian at 177°W; zone 2 runs from 174°W to 168°W, and so on.
• Coverage is 80°S to 84°N. Beyond that, Universal Polar Stereographic (UPS) coordinates are used.
• 120 projections, not one. UTM is “a family of 120 Transverse Mercator map projections (two for each UTM zone, with one for each N/S hemisphere).”
• 20 latitude bands, lettered C through X northward from 80°S, omitting I and O. All are 8° high except band X, which is 12°. A zone number plus a band letter, such as 15S, is the Grid Zone Designator, and the cells it names are generally 6° by 8°.
• The conterminous United States spans zones 10 to 19 (USGS): “from Zone 10 on the west coast through Zone 19 in New England.”

Coordinates inside a zone are eastings and northings in meters. The easting is 500,000 m at the zone’s central meridian. The northing is 0 m at the Equator for the northern hemisphere and 10,000,000 m at the Equator for the southern hemisphere. Those offsets are called false easting and false northing, and they exist, in USGS’s words, “to avoid negative numbers for locations south of the Equator.”

Snyder’s USGS projection manual describes the scale on the central meridian as reduced “to 0.9996 of true scale (a 1:2,500 reduction).” The lines of true scale lie about 180 km east and west of the central meridian, and the variation “reaches 1 part in 1,000 from true scale at the Equator.”

Working out a zone and band yourself

The arithmetic for a standard zone and band is short. This is the sample as we ran it in Node (selected lines of its output follow); it ignores the Norway and Svalbard exceptions on purpose:

// Sample A: naive UTM zone number + MGRS latitude band letter from WGS84 lon/lat.
// Ignores the Norway and Svalbard non-standard zones on purpose.
export function utmZone(lon) {
  // zone = floor((lon + 180) / 6) + 1, clamped so lon = 180 lands in zone 60
  return Math.min(60, Math.floor((lon + 180) / 6) + 1);
}
const BANDS = "CDEFGHJKLMNPQRSTUVWX"; // 20 letters, I and O omitted
export function latBand(lat) {
  if (lat < -80 || lat > 84) return null; // outside UTM: use UPS
  return BANDS[Math.min(19, Math.floor((lat + 80) / 8))]; // X is 72-84 (12 deg)
}

letters: 20 has I: false has O: false
west edge of zone 1                           lon=-180 lat=0 -> 1N
zone 1/2 boundary                             lon=-174 lat=0 -> 2N
Washington DC                                 lon=-77.0365 lat=38.8977 -> 18S
antimeridian +180                             lon=180 lat=0 -> 60N
Bergen, Norway (official zone 32V)            lon=5.3 lat=60.4 -> 31V
Longyearbyen, Svalbard (official zone 33X)    lon=15.6 lat=78.2 -> 33X
band X bottom                                 lon=0 lat=72 -> 31X
beyond 84N -> UPS                             lon=0 lat=84.5 -> 31 (no band: UPS)

Read that output with its limits in view, because each one is a way this formula goes wrong:

• It ignores the exceptions. Bergen comes out 31V; the Maps SDK’s coordinate formatter puts it in 32V (sample below). Longyearbyen matches 33X only by coincidence. The “official zone” labels in the output above come from the Maps SDK’s formatter (the sample under “Converting a point in code”), not from an NGA document: it returns 32V for Bergen and 33X for Longyearbyen.
• Longitude 180 needs the clamp. Without Math.min(60, …) it returns zone 61.
• A point exactly on a zone boundary goes east. At −174 the formula picks zone 2. That tie-break is this formula’s choice, not a sourced rule.
• “1N” means band N, not north. The letter here is a latitude band. More on that trap below.
• The top edge is unsettled. NGA says UTM covers the area “between 84°N and 80°S”; whether exactly 84.0°N counts as UTM is not settled by the sources we read.

That is why Sample A is a teaching aid, not production code. In an app, let coordinateFormatter (below) or ArcGIS Pro work out the zone.

MGRS and the U.S. National Grid

The Military Grid Reference System is “an alpha-numeric system for expressing UTM/UPS coordinates”, and “a single alpha-numeric value references a position that is unique for the entire earth.” It is built in three layers, with one polar exception:

• Grid Zone Designator — the zone number and band letter, such as 18S. MGRS writes zone numbers with a leading zero, so zone 9 is 09.
• 100,000-meter grid square — the fourth and fifth characters, “a pair of letters identifying one of the 100,000-meter grid squares within the grid zone (or UPS area).”
• Numeric location — an easting and a northing inside that square, with the same number of digits each.
• The polar exception: polar areas use A and B near the South Pole and Y and Z near the North Pole in place of zone numbers.

The U.S. National Grid (USNG) is, per NGA, “functionally equivalent to the Military Grid Reference System (MGRS). The main difference between the two systems is in the method for specifying the datum.” The FGDC standard that defines it (FGDC-STD-011-2001) sets the datum as NAD 83 or its international equivalent, WGS 84, and marks NAD 27 values with a (NAD 27) suffix. It targets mapping “at scales of approximately 1:1,000,000 and larger” and defines how to present UTM coordinates at various levels of precision.

Digits are precision, not accuracy

The FGDC standard’s own example shows how the digit count sets the size of the square a reference names:

Precision is not accuracy, and the standard keeps them in separate sections. On accuracy: “Paper maps using the USNG grid shall conform to the National Map Accuracy Standard.” On precision, USNG “provides a flexible numbering scheme to accommodate variable precision from tens of kilometers to one meter or higher”, and “for general field applications, a precision of one hundred or ten meters will be typical.” A ten-digit reference names a 1 m square. It does not make the position behind it good to 1 m.

How to read a grid reference

Two rules from the FGDC standard do most of the work. Read “from left with Easting first, then Northing”, and “an equal number of digits shall always be used for E and N.” The memory aid it gives is “right (Easting) and up (Northing).” So split the numeric part down the middle: the first half is the easting, the second half is the northing.

Plotting a point on a gridded map works the same way. In the USGS fact sheet’s worked figure, the nearest grid line west of point P is 357,000 mE and the nearest line south is 4,276,000 mN. The point sits 800 m east and 750 m north of those lines, so its coordinates are 357,800 mE, 4,276,750 mN. The rule, verbatim: “The northing of the point is the value of the nearest grid line south of it plus its distance north of that line; its easting is the value of the nearest grid line west of it plus its distance east of that line.”

Converting a point in code

In the Maps SDK for JavaScript, coordinateFormatter converts a geographic point to MGRS, USNG and UTM strings. Its reference page sets three conditions: load() must be called first if isLoaded() is false, “the browser must support WebAssembly for this module to work”, and the formatting methods expect the point’s spatial reference to be geographic. It is not deprecated at 5.1.26. This is the core of the sample we executed from the CDN in headless Chromium, on 5.1.26 and on 5.0.19, with identical output:

const [coordinateFormatter, Point] = await $arcgis.import([
  "@arcgis/core/geometry/coordinateFormatter.js", "@arcgis/core/geometry/Point.js"]);
await coordinateFormatter.load();
const p = new Point({ longitude: -77.0353, latitude: 38.8895 });
coordinateFormatter.toMgrs(p, "automatic", 5, true);   // "18S UJ 23478 06483"
coordinateFormatter.toMgrs(p, "automatic", 1, false);  // "18SUJ20"
coordinateFormatter.toUsng(p, 4, false);               // "18SUJ23470648"
coordinateFormatter.toUtm(p, "latitude-band-indicators", true); // "18S 323478 4306483"
coordinateFormatter.toUtm(p, "north-south-indicators", true);   // "18N 323478 4306483"

Run it inside a <script type="module"> on a page that already loads https://js.arcgis.com/5.0/; the comments show what each call returns. The input point is our approximation of the Washington Monument. It is not the point behind the FGDC table above: the SDK’s 10 m reference is 18SUJ23470648, one digit off FGDC’s 18SUJ23480647 in each axis. The two inputs are only about 5 m apart east-west and 4 m north-south (compare the 1 m references), and truncation turns that into a full 10 m step. $arcgis.import is the no-build CDN pattern; an npm app would use static imports. The same run put Bergen at 32V KN 96191 01684, which is where the Norway exception shows up.

The conversion mode argument ("automatic") does two jobs. Its allowed values are "automatic", "new-180-in-zone-01", "new-180-in-zone-60", "old-180-in-zone-01" and "old-180-in-zone-60". The zone 01 versus 60 part matters only when writing MGRS for a point at exactly 180° longitude. The new versus old part picks the 100 km lettering scheme. The JavaScript page does not explain it, but Esri’s .NET reference for its MgrsConversionMode does: automatic uses the new (AA) scheme for new datums such as WGS 84 and the old (AL) scheme for older datums. That is the WC versus WN difference in the datum examples below.

The datum in code

Formatting a WGS 84 point is the easy half. Parsing a reference someone typed is where the datum goes missing, because the formatter’s parsers fall back to WGS 84. fromMgrs and fromUtm assume WGS 84 when no spatial reference is given. With no spatial reference given, fromUsng reads a string as NAD 27 only when it ends in (NAD 27), and as WGS 84 otherwise. Going the other way, the reference page shows toUsng writing a (NAD 27) suffix when the point’s spatial reference is based on NAD 27; we did not run that case. And if you need to move legacy coordinates between datums in the browser, note the projectOperator limit: it “currently only supports equation-based geographic transformations”, and “grid-based transformations are not supported.” Check which transformation your datum pair needs before you plan on doing it client-side.

State Plane, briefly

The State Plane Coordinate System (SPCS) is the National Geodetic Survey’s family of zones built from three projections: Lambert Conformal Conic, Transverse Mercator and Oblique Mercator. NGS’s manual: Lambert “was used for States that are long in the east-west direction”, Transverse Mercator for states or zones long north-south, and Oblique Mercator “in one zone of Alaska when neither of these two was appropriate.” Referred to NAD 83 or NAD 27, the system is SPCS 83 or SPCS 27.

NGS describes SPCS as “a system of large-scale conformal map projections originally created in the 1930s to support surveying, engineering, and mapping activities throughout the U.S. and its territories.” The design criteria for SPCS 27 included keeping scale distortion under one part in 10,000, covering each state with as few zones as possible, and drawing zone boundaries along county lines.

Two unit facts matter in practice. NGS publishes SPCS 83 coordinates in meters (ten states defined which foot to use when converting). And since January 1, 2023, NIST says, the U.S. survey foot “is deemed obsolete and superseded by the international foot”, 0.3048 m exactly. The same page adds that the survey foot “should be avoided, except for historic and legacy applications.” So new State Plane work belongs in meters or international feet, while existing data defined in survey feet keeps that definition. Convert it if you must; never just relabel it as international feet, because the two feet are not the same length.

State Plane is also in transition. NGS’s policy page, read on October 7, 2026, says SPCS2022 “is being developed as part of the transition from the North American Datum of 1983 (NAD 83) to the 2022 Terrestrial Reference Frames.” It “will replace the State Plane Coordinate System of 1983”, but, technically, “SPCS 83 policies are still in effect, since SPCS2022 has not yet been fully defined or adopted.” The next sentence reads: “But in practical terms those policies are now defunct, since there will be no further changes to SPCS 83.” The NAD 83 reference frames themselves are slated to be replaced by four plate-fixed terrestrial reference frames. We give no date for either; the pages we read do not.

Which grid for which job

The authorities say a few things directly about who uses what, and we quote those. The rest of this section is our guidance, reasoned from the facts above.

What the sources say.

• USGS: “Many experienced users prefer UTM over latitude/longitude when using 7.5’ topographic quadrangle maps. Ocean-going sailors and other marine users almost always use latitude/longitude because navigation charts are optimized for this method.” And on accuracy: “One system is no more or less accurate than the other. They are just two different ways of positioning a point.”
• FGDC on USNG: it exists to establish “a nationally consistent grid reference system” for location services and printed maps, and “the USNG is interoperable with the MGRS. This will be of critical importance to safety of life during times of disaster relief operations.”
• FGDC on surveying: “The USNG is not designed for surveying.” SPCS “is specifically designed to meet the requirements of surveyors and engineers in determining location and boundaries.”
• ArcGIS Pro on graticules (quoted above): they can be added “to a map in any projection.”

Our guidance. A graticule is the natural choice when a map spans many UTM zones or reaches the poles, since UTM stops at 80°S and 84°N and a graticule works in any projection. UTM suits regional work inside one zone, where its distortion stays small. MGRS or USNG suits anything where a person has to say or type a location as one short string that names a single square worldwide, once sender and receiver agree on the datum. That is why we would reach for it in a public-safety or field app. State Plane suits survey and engineering work inside one state, which is what it was designed for. And as USGS notes for UTM and latitude/longitude, the choice is not about accuracy.

Mix-ups worth guarding against

The letter after the zone

NGA’s warning, verbatim: “In many systems, the letter after the zone number designates a latitudinal band, not a hemisphere.” And: “Caution must be used to not confuse the letter ‘S’ band letter for a hemisphere designation and vice versa.” The SDK sample above shows it on one point: Washington is 18S 323478 4306483 in band format and 18N 323478 4306483 in hemisphere format. Band S is in the northern hemisphere. Read 18S as “south” and the northing is measured from the wrong origin. ArcGIS Pro’s Convert Coordinate Notation tool spells it out for its band format: “N or S does not designate a hemisphere.” Always know which format a UTM string is in.

The datum behind the reference

The same ground point has different grid references on different datums. Two worked examples from the sources, with our arithmetic, and each applies to that one point only:

• FGDC: 18SUJ23480647 on NAD 83 is 18SUJ23450626 (NAD 27). At 10 m digits that is about 30 m east-west and 210 m north-south.
• NGA: 15SWC8081751205 on WGS 84 becomes 15SWN8083350993 on NAD 27. The 100,000-meter square letters change (WC to WN), because, per NGA, one lettering scheme is generally used for WGS 84 and the other for older ellipsoids, and the northing differs by about 212 m.

Of the NAD 27 to NAD 83 change, NGS writes that “the ellipsoid change is the major contributor of the coordinate shift.” We do not quote a general size for the shift, because none of our sources gives one. Treat the two figures above as examples, not a rule.

Shortening a reference: round or truncate?

The standards disagree, so name the one you follow. NGA’s example shortens 15SWC8081751205 (1 m) to 15SWC80825121 (10 m), which is rounding. The FGDC USNG standard says “A uniform system of truncation is adopted for the USNG.” The Maps SDK’s formatter truncates: in our sample the 1 m digits 23478 06483 became 2347 0648 at 10 m.

One grid, one coordinate system

In ArcGIS Pro, “a grid is associated with a single coordinate system. To create a map with a grid showing multiple UTM zones, each clipped to the UTM zone boundary, you need to create a grid for each zone.”

Units

As noted under State Plane, a value in U.S. survey feet uses a unit NIST has kept only for historic and legacy applications since the start of 2023. The mix-up to guard against is the label, not the unit: legacy survey-foot data must stay labeled as survey feet, and new work should use meters or international feet.

Doing it in ArcGIS

ArcGIS Pro. Pro offers “five types of grids that can be added to a map frame: graticules, measured grids, MGRS grids, reference grids, and custom grids.” To add one, select the map frame in an active layout view, then on the Insert tab, in the Map Frames group, click Grid. Pro ships two MGRS grid styles, one at 1,000 m gridline intervals and one at 10,000 m for smaller-scale maps. For coordinates stored in a table, the Convert Coordinate Notation tool converts between DD, DDM, DMS, GARS, GEOREF, UTM, USNG and MGRS, and it is available at the Basic, Standard and Advanced license levels.

Maps SDK for JavaScript. The arcgis-coordinate-conversion component shows a location in several notations; its reference states that “the default formats are basemap, dd, ddm, dms, mgrs, usng, utm, and xy.” (The intro list on the same page omits USNG; the formats sentence is the complete one.) It documents a headingLevel property that you may need to adjust for proper heading semantics, which the page calls important for meeting accessibility standards.

Two 5.1 changes are worth knowing before you build on it. Release 5.1 added a beta arcgis-coordinate-conversion-next component, and Esri says that “in version 6.0, the implementation of arcgis-coordinate-conversion will be updated under the hood to that of arcgis-coordinate-conversion-next.” And five properties of the current component have been deprecated since 5.1 and will be removed in that migration: expanded, hideCaptureButton, hideExpandButton, hideInputButton and hideSettingsButton. Do not start new code on them. Both points depend on a beta and the 6.0 schedule, so re-check them when 6.0 ships.

Cost. coordinateFormatter runs in the browser in WebAssembly; the pe-wasm download, as we measured it on 5.1.24, is 660,623 bytes brotli (2,844,903 decoded), and the coordinateFormatter reference page documents no per-call charge. Load it once, when the first conversion is needed, rather than at app start. One obligation does apply: Esri’s licensing page requires attribution “in all applications that use Esri technology, whether or not they contain a map.” We have not measured whether arcgis-coordinate-conversion makes network requests for any format, so we make no cost or offline claim for the component.

Try it in Grid Viewer

Our Grid Viewer draws three of the systems in this post. It needs no sign-in and ships no API key at load. It is a learning tool, and it has known defects, listed below.

• Graticules (lat/lon) at 30, 15, 10, 5 or 1° spacing, or just the Equator and Prime Meridian. Click a line to see whether it is latitude or longitude and its value.
• UTM grid: the 6° zone boundaries from 80°S to 84°N and the band boundaries. Click to highlight a zone and band and read its zone, band letter, west and east boundaries and central meridian. Pick a zone from the list and the app drops two dots for the same easting and northing (321,246 mE, 4,663,338 mN), projected from that zone’s northern and southern UTM systems, which shows why the hemisphere label carries the meaning.
• State Plane (SPCS): pick a state and a zone to see its central meridian, standard parallels, latitude of origin, origin and “Grid Zero (0,0)” point. Use it to see the shape of a zone, not as a source of parameters (see below).
• 2D map or 3D globe, toggled from the map.

What it is and is not. The grid lines are computed by the app’s own arithmetic and drawn as WGS 84 polylines in a graphics layer; the SDK’s projection engine is used only for the two UTM sample dots. It has no MGRS or USNG mode: the grid type list offers exactly the three systems above. Inspection is by pointer click, with no keyboard equivalent yet, the page blocks pinch-zoom on mobile, and it loads Google Tag Manager.

Known defects. Writing this post, we checked the app against the rules above, and it breaks some of them:

• State Plane panel values. A review of the app flagged 8 of its 121 State Plane entries. We re-checked those 8 against the published projection definitions for their WKIDs, and all 8 are wrong. WKIDs 26988, 26989 and 26990 are Michigan North, Central and South, but the app labels them Minnesota; 26991 and 26992 are Minnesota North and Central, but the app labels them Mississippi East and West. The false easting shown for Alabama East (26929), Michigan North (102688) and Michigan Central (102689) does not match the published value. We have not re-checked the other 113, so do not copy a WKID or parameter from the panel.
• Units. The help text describes all State Plane zones as “US Survey Feet,” although the app’s own data lists several zones in meters, and survey feet belong only to legacy data.
• UTM exceptions. Its UTM lines are plain 6° zones with no Norway or Svalbard exception, so a click at Bergen reports zone 31, not the formatter’s 32V. It also draws an extra parallel at 80°N, inside band X.

If you need a published grid in a web map instead, Esri’s World UTM Grid and World Latitude and Longitude Grids are public feature services owned by Esri; queried at Bergen, World UTM Grid returns zone 32, row V. For a side-by-side of UTM, State Plane and latitude/longitude on one map, see our coordinate systems explainer.

The short version

• A graticule is angles (latitude and longitude); a grid is meters on a projection (UTM, MGRS/USNG, State Plane).
• UTM: 60 zones of 6°, 80°S to 84°N, false easting 500,000 m, false northing 10,000,000 m in the south. A few zones near Norway and Svalbard are non-standard.
• MGRS and USNG: zone, band, 100 km square, then equal-length easting and northing. Read right, then up. More digits mean more precision, not more accuracy.
• Before using any grid reference, know the zone, whether its letter is a band or a hemisphere, and the datum.
• Label State Plane units explicitly: meters or international feet for new work, survey feet only for legacy data. Expect SPCS2022 to replace SPCS 83 once NGS finishes defining it.

References

• NGA — Coordinate systems (grids, graticules, UTM, UPS, MGRS, USNG) (grid and graticule definitions, UTM zones and bands, the Grid Zone Designator, MGRS lettering, and the band-versus-hemisphere warning)
• USGS Fact Sheet 077-01 — The Universal Transverse Mercator (UTM) grid (why grids are superimposed, zones 10 to 19 for the conterminous US, false northing, and the worked reading of a point)
• USGS Professional Paper 1395 — Map Projections: A Working Manual (Snyder) (the 0.9996 central-meridian scale factor and the lines of true scale)
• FGDC-STD-011-2001 — United States National Grid (digit precision, easting-first reading, truncation, datum, accuracy versus precision, and the standard’s purpose and scope)
• NOAA Manual NOS NGS 5 — State Plane Coordinate System of 1983 (the three SPCS projections, the 1927 design criteria, metric publication, and the ellipsoid change as the major contributor to the NAD 27 to NAD 83 shift)
• NGS — SPCS policy (read October 7, 2026) (SPCS2022 being developed, replacing SPCS 83, not yet fully defined or adopted, and SPCS 83 policies in practice defunct)
• NGS — new datums naming convention (the NAD 83 frames being replaced by plate-fixed terrestrial reference frames)
• NIST — The U.S. survey foot (the survey foot deemed obsolete from January 1, 2023, except for historic and legacy applications)
• USGS FAQ — Is UTM better or more accurate than latitude/longitude? (neither is more accurate, and who tends to use which)
• ArcGIS Pro — Grids and graticules (the five grid types, and graticule versus measured grid versus reference grid)
• ArcGIS Pro — MGRS grids (one coordinate system per grid, one grid per UTM zone, and the shipped MGRS styles)
• ArcGIS Pro — Convert Coordinate Notation (supported notations, band versus hemisphere letters, and license levels)
• Maps SDK for JavaScript — coordinateFormatter (load(), the WebAssembly requirement, geographic input, the conversion modes, and the WGS 84 default of the parsers)
• Maps SDK for JavaScript — arcgis-coordinate-conversion (the default formats, headingLevel, and the 6.0 note on the -next implementation)
• Maps SDK for JavaScript — release notes for 5.1 (the beta arcgis-coordinate-conversion-next and the five properties deprecated since 5.1)
• Maps SDK for JavaScript — arcgis-grid-controls (a snapping grid whose spacing does not correspond to real-world measurements)
• Maps SDK for JavaScript — projectOperator (equation-based geographic transformations only; grid-based transformations not supported)
• Maps SDK for JavaScript — licensing and attribution (attribution required in every app that uses Esri technology, map or not)
• ArcGIS Maps SDK for .NET — MgrsConversionMode (the new (AA) and old (AL) MGRS lettering schemes chosen by the conversion mode)
• Esri — World UTM Grid (a public UTM zone layer that applies the Norway exception)