Convert Coordinate Notation Tool - USNG Field Length

[JasonBalmut]

Problem:
The USNG field that is created with this tool has a length of 255 characters when it only needs 18.  The reason this is a problem is that it doesn't match most other feature classes that have a 18-character USNG field already which makes it difficult to use any other tool that has field mapping options such as Spatial Join (Analysis), Append (Management), Merge (Management), Feature Class To Feature Class (Conversion), and Table To Table (Conversion).



Solution:
Reduce the length of the USNG field created by the Convert Coordinate Notation tool to 18 characters.

Note:
I realize this doesn't address a fully-qualified USNG value which normally has the datum at the end (i.e. (NAD83) ), but the tool returns a USNG parsed value with spaces between the GZD, 100k-m square ID, and the individual grid coordinates.

[DrewFlater]

It is unclear how having a field with the length 255 matters in the workflows described. If a field with only 18 characters but length of 255 is field mapped to a target field with length 18, the first 18 characters from the field with length 255 will automatically be transferred into the field with length 18. Given the lack of significant support in the last 6 years this will not be prioritized. If a case is uncovered where the field length 255 with 18 characters is not correctly mapped to a field with length 18, we will treat that as a bug and fix it.