Crs.TryParseMgrs Method
Parses a Military Grid Reference to a LongLat point.
TryParseMgrs(GeodeticDatum geodeticDatum, MgrsLetteringScheme letteringScheme, System.String mgrs, out Point longLat)
Parses a Military Grid Reference to a LongLat point.Syntax
public static System.Boolean TryParseMgrs (
GeodeticDatum geodeticDatum,
MgrsLetteringScheme letteringScheme,
System.String mgrs,
out Point longLat
)Parameters
The geodetic datum used, for both input and output.
The MGRS lettering scheme used: new or old. The old one may be used only if the datum ellipsoid is Bessel 1841, Bessel Namibia, Clarke 1866, Clarke 1880 or Clarke 1880 (IGN).
The MGRS reference.
The resulting position expressed in LongLat. This is an output parameter, and it will only be valid if the return value is True.
Return Value
In C# and C++ this method returns True if the MGRS reference could be parsed, and False otherwise. In Java and Python, the actual point is returned, or null (Java) or None (Python) if the MGRS reference could not be parsed.
Remarks
This method differs from ParseMgrs in that it will not throw an exception if it fails to parse; it will just return False, null (Java) or None (Python). A drawback is that you will not get the useful exception message that explains why the parsing failed.
Note that the method does not transform between geodetic datums: For example, if the geodeticDatum parameter represents ED50 (European Datum 1950), then the method parses ED50 MGRS into ED50 LongLat.
In strict usage, an MGRS reference must have no spaces, dashes or other separators. Example:
32VPK7664100252
In more informal usage, spaces or tabs may separate the four main parts. Example:
32V PK 76641 00252
This method can parse the informal usage, too, as long as the whitespace consists of only space characters and/or tab characters, and occurs only between the four main parts (the grid zone designator like 32V above, the 100 000 m square identifier like PK above, and the two halves of the numerical location like 76641 and 00252 above).
The number of digits used for the numerical location (which must be 0, 2, 4, 6, 8, 10, 12, 14 or 16) is noted and stored as the z coordinate of the result, where the application can inspect it. (Using 12, 14 or 16 digits is allowed only in US National Grid, the civilian version of MGRS, so a military application may want to complain if the z is larger than 10.)
The method can also accept an MGRS reference that consists only of a grid zone designation, like 30U. In this case, the number of digits in the numerical location is considered to be -2 (by extrapolation).
The number of digits gives the resolution used:
number of digits | example (with spaces) | resolution |
|---|---|---|
-2 | 30U | 6° * 8° (usually) |
0 | 30U XC | 100 km |
2 | 30U XC 9 1 | 10 km |
4 | 30U XC 99 10 | 1 km |
6 | 30U XC 992 102 | 100 m |
8 | 30U XC 9923 1023 | 10 m |
10 | 30U XC 99237 10233 | 1 m |
12 | 30U XC 992379 102338 | 1 dm |
14 | 30U XC 9923796 1023387 | 1 cm |
16 | 30U XC 99237963 10233872 | 1 mm |
Platforms
Windows, Linux, Android
See Also
Reference
Crs Class
Core Module
ParseMgrs
ParseMgrsAsArea
FormatMgrs
FormatUtmUps
UtmGridGenerator