For related Q&A at StackOverflow see generic-javascript-parser-for-user-supplied-coordinates. for WGS84, see coordinate-parser and magellan-coords. For conversions from a coordinate system to another, see Proj4js and Proj.įor latitude and longitude flavoured parsing e.g. See the utm-coordinate-parser at NPM as well as axelpale/utm-coordinate-parser at GitHub for further details. Programmatic usage of the package is simple: > const utm = require('utm-coordinate-parser') Thanks to utm-coordinate-parser, users may type and even paste UTM coordinates successfully regardless the exact format. For many travellers, mobile devices are the only possibility. Manual conversion can be a pain and especially so with tiny keyboards of mobile devices. If Georap or any other end-user GIS application supports only single input format, users would have to convert their coordinates to it. Universal Transverse Mercator (UTM) projections such as NZTM in New Zealand and ETRS89 TM35 in Finland are widely used in their respected zones and thus often faced on the field. Users often want to input coordinates they have found in paper maps, info boards and books, as well as in forums and message boards. Portions of the library (particularly the geodesic routines) have also been implemented in a few other languages. Simple and robust textual coordinate input became a desirable feature in Georap GIS project. conversions between geographic, UTM, UPS, MGRS, geocentric, and local cartesian coordinates gravity (e.g., EGM2008) and geomagnetic field (e.g., WMM2020) calculations. Therefore I created an open source Node.js package utm-coordinate-parser that manages exactly that, parsing the easting and northing values from the various formats. It is not a trivial task to extract the numeric values from them. There are many ways to write geographical coordinates in UTM coordinate systems in the wild: 327874 12345
0 Comments
Leave a Reply. |