Wikidata:Property proposal/Military Grid Reference System ID
Military Grid Reference System
[edit]Originally proposed at Wikidata:Property proposal/Place
| Description | geocoordinate standard used by NATO militaries for locating points on Earth |
|---|---|
| Data type | alphanumeric-invalid datatype (not in Module:i18n/datatype) |
| Example 1 | 30UXE2463781484 |
| Example 2 | 4QFJ15 |
| Example 3 | MISSING |
Motivation
[edit]Q1922471 Military Grid Reference System (Q1922471) [1] en:Military Grid Reference System is the geocoordinate standard used by NATO militaries for locating points on Earth. It is not the same as the national grid reference systems used in Great Britain or Ireland, or the more commonly used latitude and longitude system. They can be used to locate a place on the https://geonames.nga.mil/geonames/GeographicNamesSearch/
- Clifton can be found at GEOnet Names Server, at this link http://geonames.nga.mil/namesgaz/ by opening the Advanced Search box, entering "-2592768" in the "Unique Feature Id" form, and clicking on "Search Database".
Text from English Wikipedia article:
The Military Grid Reference System (MGRS)[1] is the geocoordinate standard used by NATO militaries for locating points on Earth. The MGRS is derived from the Universal Transverse Mercator (UTM) grid system and the Universal Polar Stereographic (UPS) grid system, but uses a different labeling convention. The MGRS is used as geocode for the entire Earth.
An example of an MGRS coordinate, or grid reference, would be [[[:Template:Coor URL]]21_18_34.0_N_157_55_0.7_W_&language=en 4QFJ12345678], which consists of three parts:
- 4Q (grid zone designator, GZD)
- FJ (the 100,000-meter square identifier)
- 1234 5678 (numerical location; easting is 1234 and northing is 5678, in this case specifying a location with 10 m resolution)
An MGRS grid reference is a point reference system. When the term 'grid square' is used, it can refer to a square with a side length of Template:Convert, 1 km, Template:Convert, 10 m or 1 m, depending on the precision of the coordinates provided. (In some cases, squares adjacent to a Grid Zone Junction (GZJ) are clipped, so polygon is a better descriptor of these areas.) The number of digits in the numerical location must be even: 0, 2, 4, 6, 8 or 10, depending on the desired precision. When changing precision levels, it is important to truncate rather than round the easting and northing values to ensure the more precise polygon will remain within the boundaries of the less precise polygon. Related to this is the primacy of the southwest corner of the polygon being the labeling point for an entire polygon. In instances where the polygon is not a square and has been clipped by a grid zone junction, the polygon keeps the label of the southwest corner as if it had not been clipped.
- 4Q ......................GZD only, precision level 6° × 8° (in most cases)
- 4Q FJ ...................GZD and 100 km Grid Square ID, precision level 100 km
- 4Q FJ 1 6 ...............precision level 10 km
- 4Q FJ 12 67 .............precision level 1 km
- 4Q FJ 123 678 ...........precision level 100 m
- 4Q FJ 1234 6789 .........precision level 10 m
- 4Q FJ 12345 67890 .......precision level 1 m – The preceding unsigned comment was added by Eastmain (talk • contribs) at 15:39, July 30, 2024 (UTC).
References
- ↑ DMA Technical Manual 8358.1, Chapter 3. Datums, Ellipsoids, Grids, and Grid Reference Systems
Discussion
[edit]
Comment Your examples need fixing - see other recent property proposals - you should have a Wikidata item for which the value is the ID you show. Also I think you want "string" datatype. There's no special "alphanumeric" type here. ArthurPSmith (talk) 14:27, 31 July 2024 (UTC)
Oppose Even if all the issues with the proposal are fixed, this seems to contain pretty much exactly the same information as coordinates and should be easily convertible, thus is redundant. Uniwah (talk) 17:50, 4 August 2024 (UTC)
- Oppose Agree, a quick google suggests lots of converters out there. If there were merit to have it in WD, it would be better to have a converter as a SPARQL function, rather than apply to all items. Vicarage (talk) 17:48, 5 August 2024 (UTC)
- Oppose I agree. There are many similar global geocode systems (like Maidenhead Locator System (Q2121349)), and it doesn't make sense to include such redundant data here. If a wiki needs this type of geocodes that could done with a module calculating them based on coordinates (and in the future with Wikifunctions). –Samoasambia ✎ 11:29, 7 August 2024 (UTC)
Not done, no support for creation. Regards, ZI Jony (Talk) 01:54, 9 August 2024 (UTC)
