mgrs: Converting to and from MGRS and Decimal Degrees
GeoTrans provides C code for converting to and from MGRS, but well, it’s C code :). This is a simple ctypes wrapper around two of the MGRS-related functions in GeoTrans.
This library has an internal copy of some of the files from GeoTrans 2.4.2.
Usage
In a nutshell:
>>> import mgrs >>> latitude = 42.0 >>> longitude = -93.0 >>> m = mgrs.MGRS() >>> c = m.toMGRS(latitude, longitude) >>> c '15TWG0000049776' >>> d = m.toLatLon(c) >>> d (41.999997975127997, -93.000000000000014) >>> y = '321942.29N' >>> yd = m.dmstodd(y) 32.328414 >>> d, m, s = m.ddtodms(32.328414) >>> d, m, s (32.0, 19.0, 42.290400)
You can also control the precision of the MGRS grid with the MGRSPrecision arguments in .toMGRS(). Other than that, there isn’t too much to it.
Metadata
Release files for mgrs 1.3.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| mgrs-1.3.0.tar.gz | 27.0 kB | Without provenance | Details for mgrs-1.3.0.tar.gz |
Release files / mgrs-1.3.0.tar.gz
| Download URL | mgrs-1.3.0.tar.gz |
|---|---|
| Size | 27.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5c8512a38be493d13b2030eeff2613688109c66dfb5c5feb3bb927d74c931d68
|
|
BLAKE2b-256 checksum How to use checksums |
60ff714474ba70c258c3ee72a76f99a41935dd456499d1e1e5f04898a9d01273
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for mgrs 1.3.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.