search

Esri / coordinate-conversion-addin-dotnet

Addin for ArcMap and Pro for convenient coordinate conversion in Desktop.
Apache License 2.0
45 stars 20 forks source link

Support for custom DMS format of DD-MM-SS.SS #468

Closed topowright-zz closed 5 years ago

topowright-zz commented 6 years ago

Support FAA format by creating a custom configuration

Background

Supporting this format thru the use of our configuration options of a DMS coordinate will allow this addin to support the FAA format.

https://community.esri.com/thread/207791-faa-oeaaa-latitudelongitude-coordinates

Current State

Input image

Output image

Expected behavior

All coordinate types should accept all characters to allow users to configure the output format. This can be tested on DDM and DMS which currently are not supporting dashed (-) symbols.

lfunkhouser commented 6 years ago

@karlterrey Can you follow up with this user on GeoNet if possible to gather any requirements for this format?

karlterrey commented 6 years ago

Will do

karlterrey commented 6 years ago

@lfunkhouser @topowright Customer feedback from Hannah Shepherd at Apex Clean Energy, in VA. hannah.shepherd@apexcleanenergy.com

The FAA has a mandated protocol for locations that are electronically filed with them. Hannah’s organization is a wind developer and files locations of facilities with the FAA using the FAA’s OEAAA E-Filing system. Specifically they have issues with the DMS format needing to be in DD-MM-SS.SS for Lat and Lon of each facilities location. This can sometimes be in batches of 150 – 200.

A second important factor in their workflow is the elevation at each specific point. ESRI’s Extract Values to Points tool helps with that currently.

This would help in reinforcing that our work is non ITAR _FAA_Template for coord conversion.xlsx

topowright-zz commented 6 years ago

This should be able to be done by configuring the DDM output.

topowright-zz commented 6 years ago

@saip please let me know if the updated content in the issue description clarifies the requirments.

lfunkhouser commented 6 years ago

added CT-fixed label since it was developed/delivered in #518. added working labels for testing and doc

dfoll commented 6 years ago

Recently rebuilt CC build 19 and MT build 122 to test

BobBooth commented 6 years ago

MGRS and USNG are not supporting dashes, or other special characters in Pro 2.3. https://github.com/Esri/coordinate-conversion-addin-dotnet/issues/528 Special character format support seems to vary by hemisphere. https://github.com/Esri/coordinate-conversion-addin-dotnet/issues/527

kgonzago commented 6 years ago

Using MT build 126, I confirmed FAA format for custom DMS notation is supported.

I also confirmed, as reported by @BobBooth, the add-in does not support dashes for MGRS and USNG notations.

kgonzago commented 6 years ago

Added new test for checklist

dfoll commented 6 years ago

This issue represents a subset of cases for #347 and #348. This is is satisfied given the initial issue. A new issue needs to be logged as a response to this, as this issue does not account for Northern/Southern or Eastern/Western hemisphere coordinates. image

dfoll commented 6 years ago

542 was opened to clarify the proper formatting for FAA coordinates.

lfunkhouser commented 6 years ago

@dfoll if the coordinates are not in the proper location, this issue has not been delivered. Reassigning to @CTLocalGovTeam . @saip please work with @dfoll for the guidance.

dfoll commented 6 years ago

@lfunkhouser we need to find time to understand this format better, or have connected with someone who already does before any meaningful work can be done

lfunkhouser commented 6 years ago

Support for custom FAA format by using the map point tool was delivered. Issue #542 will need to be addressed in a future release to support the input/importing of FAA coordinates.

csmoore commented 5 years ago

This issue was reintroduced with fix for #527, https://github.com/Esri/coordinate-conversion-addin-dotnet/issues/527#issuecomment-494955592 PRs #602 , #612 that disallowed "+/-" in formatting - Reopening.

dfoll commented 5 years ago

@saip the proposed fix for this is to improve the parsing logic that was put into place to fix issue #527. Details of proposed improvement listed in #527

dfoll commented 5 years ago

CC build 145 brought back the ability to use a "-" as a separator between DD-MM or MM-SS.SS when creating custom formatting . A "-" in front of the DD is not allowed to be used when creating custom formatting. When using custom formatting the "-" will still be placed for S and W hemisphere if the "Show - for S/W hemisphere" check box is marked. See #600 for more details.

dfoll commented 5 years ago
lfunkhouser commented 5 years ago

@dfoll Let's talk about this one...Thinking the doc should be removed. and original version labels put on. This was a regression issue that was reintroduced/reopened. This functionality was released in January 2019.

dfoll commented 5 years ago

i thought about this. the reason i put new labels on it and listed it again is in case a user has or does encounter with like 3.4

lfunkhouser commented 5 years ago

verified doc on MT 317, CC 154, and 3 topics on solutionsstg.