Destination input

[gradzevicius]

There is a need to set destination not only in Decimal degrees (Latitude/Longitude) but also in Meters.

[defiantgoat]

@gradzevicius Yes, this is definitely in the backlog to add to the application.

[marikavertzonis]

see MyUSNG coordinate parser for this: Coordinate.parse

[marikavertzonis]

@gradzevicius - I know its been sometime since this request, but we are considering how this could be implemented. Your original request stops at asking for '...Meters'. Are you expecting that you would be selecting a projected coordinate system to work with, from a list? Would support for just WGS 84 Web Mercator (as an example) be enough?

[dominikargast]

@marikavertzonis test with 3.0.7

[marikavertzonis]

testing with 3.0.8 on windows phone 10, windows desktop 10, iphone 6 (ios 10.3.3), trimble tdc (android 6)

• when you manually enter coordinates in one format, then switch to another, they appear as expected (good)
• when you copy / paste coordinates (see #56), the contents of the fields are not updated until you switch format (bad)
• when you delete coordinates in one format, then switch to another format, the previous coordinates are returned (bad)

[marikavertzonis]

testing with 3.0.9 on ios and windows, retesting the elements of the previous comment

• when you manually enter coordinates in one format, then switch to another, they appear as expected (good)
• when you copy / paste coordinates, the contents of the fields are updated (good!)
• when you delete coordinates in one format, then switch to another format, the previous coordinates are returned (same as in previous testing). based on the behavior in the last point (ie: 'paste' effectively pastes over the content of all forms of the coordinates), then i would expect that delete to also delete all forms of the coordinates.

[dominikargast]

Concerning the last point raised in the comment above: Any coordinate input will be validated against know coordinate formats. An empty string is not a valid coordinate and will be rejected by the validator. In this case, the last known valid coordinate is persisted and will be displayed if the coordinate format is changed.

[marikavertzonis]

have split off the delete behavior to new issue. Not a priority for 3.0 release but keen to see if this really is an issue at all once the app is in wider use. The original request in this issue is now complete - you can enter coordinates in decimal degrees, degrees minutes seconds, degrees decimal minutes, utm (wgs84) or mgrs.