coordinate-parser for UTM coordinates #10
Description
What a great library.
First I want to let you know we began using coordinate-parser in Georap to allow users to quickly jump to the coordinates they read on various documents like area development plans. I have also recommended coordinate-parser in a related StackOverflow answer and in a blog post.
Although coordinate-parser deals latitude-longitude pairs gracefully it fails to parse UTM formatted coordinates, which is of course expected behaviour because the lib is targeted for lat-lng. However, most UTM coordinates have very similar if not identical syntax to some of the formats accepted by coordinate-parser but different meaning. For example coordinate-parser treats 400722.8N 740722.8W as geographical milliseconds, whereas in the UTM the same string is interpreted as metres from zone origin. At least for me, it took a while to recognize the difference at the first time.
To parse UTM coordinates and being inspired by coordinate-parser, I released utm-coordinate-parser. The lib readme also mentions coordinate-parser and recommends it for latitude-longitude pairs.
Could it be helpful for coordinate-parser users to be aware of utm-coordinate-parser? Maybe mention it next to the exotic formats? I know this sounds like a shameless promotion for utm-coordinate-parser and partly it is. Yet, I feel that coordinate-parser users might benefit from clarification that UTM coordinates are handled differently although they might look the same as the ones in coordinate-parser documentation.
Let me know if you have some thoughts. Thank you.