Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Distance unit in feature tables is not based on resource value #608

Closed
csmoore opened this issue Jun 14, 2018 · 5 comments
Closed

Distance unit in feature tables is not based on resource value #608

csmoore opened this issue Jun 14, 2018 · 5 comments
Assignees
@lfunkhouser
Labels
A-bug CT-Fixed Feature delivered/Issue has been fixed CyberTech E-verified V - MT 3.5 V - Pro 2.2
Milestone
2019 JUN Sprint 13

Comments

@csmoore
Copy link
Member

csmoore commented Jun 14, 2018 •
edited by dfoll

The addin is placing the non-localized/resource version of the Enumeration string in the table/feature attribute vs. using the localized/resource value.

As a result the values will always be the same value (Enumeration) regardless of the Resource Value.

In the example below the resource value is "Nautical Miles"(with space in Addin UI on left) but the Enumeration Value of "NauticalMiles" (no space on table at bottom) is placed in the Table/FeatureClass attribute for DistUnit

image

Expected result:

the unit in the DistUnit attribute should match the units selected in the Distance/Length drop-down on the Distance and Direction pane
@csmoore csmoore mentioned this issue Jun 14, 2018
Closed
saip added a commit that referenced this issue May 15, 2019
@saip
#608 - Distance Unit in Feature Tables is not based on Resource Value
123594f
@saip saip mentioned this issue May 15, 2019
Merged
saip added a commit that referenced this issue Jun 5, 2019
@saip
#608 - missing code
a182719
@csmoore
Copy link
Member Author

csmoore commented Jun 6, 2019 •
edited

Seeing the "Nautical Miles" correctly in PR #658 (Note: Pro only issue since only Pro addin writes to feature class)

image

@lfunkhouser lfunkhouser added the CT-Fixed Feature delivered/Issue has been fixed label Jun 17, 2019
@dfoll dfoll self-assigned this Jun 19, 2019
@dfoll dfoll changed the title Distance Unit in Feature Tables is not based on Resource Value Distance unit in feature tables is not based on resource value Jun 19, 2019
@dfoll
Copy link
Collaborator

dfoll commented Jun 19, 2019

  • DD june release topic updated
  • MT june release topic updated

@dfoll
Copy link
Collaborator

dfoll commented Jun 19, 2019 •
edited

G-Doc (CMS) label can be removed when publishing/building tasks are completed

@dfoll
Copy link
Collaborator

dfoll commented Jun 19, 2019

@dfoll dfoll removed the G-Doc (CMS) label Jun 19, 2019
@dfoll dfoll removed their assignment Jun 19, 2019
@lfunkhouser lfunkhouser self-assigned this Jun 20, 2019
@lfunkhouser
Copy link
Member

Verified doc updates on solutionsdev for MT and DD and PDFs for MT (dev build 3.5.0.308) and DD (dev build (88).

@lfunkhouser lfunkhouser added this to the 2019 JUN Sprint 13 milestone Jun 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lfunkhouser lfunkhouser

Labels
A-bug CT-Fixed Feature delivered/Issue has been fixed CyberTech E-verified V - MT 3.5 V - Pro 2.2
Projects
None yet
Milestone
2019 JUN Sprint 13
Development

No branches or pull requests
4 participants
@CTLocalGovTeam @csmoore @lfunkhouser @dfoll