Skip to content
This repository was archived by the owner on Aug 28, 2024. It is now read-only.

Adding symbol id codes to the output feature class #317

Open
15 tasks
topowright-zz opened this issue Oct 13, 2018 · 4 comments
Open
15 tasks

Adding symbol id codes to the output feature class #317

topowright-zz opened this issue Oct 13, 2018 · 4 comments

Comments

@topowright-zz
Copy link
Contributor

Tasks to be done:

2525D

  • Add symbol id code to feature class schema
  • auto populate symbol id code for each symbol into feature class
  • Verfiy changes

APP6D

  • Add symbol id code to feature class schema
  • auto populate symbol id code for each symbol into feature class
  • Verfiy changes

2525 C

  • Add symbol id code to feature class schema
  • auto populate symbol id code for each symbol into feature class
  • Verfiy changes

APP6B

  • Add symbol id code to feature class schema

  • auto populate symbol id code for each symbol into feature class

  • Verfiy changes

  • Add to whats new

  • Add to issues addressed

  • Verify documentation changes

Background

Currently when a user creates a symbol in MSE they do not get a symbol id code in the created feature table

Expected Results

The output feature class has a symbol id code in the feature table

@topowright-zz
Copy link
Contributor Author

Being that this is a new capability I am logging this as a new feature even though it is a issue reported by customers. @lfunkhouser

@csmoore
Copy link
Member

csmoore commented Jun 4, 2019

Just a note that it might be best to defer this issue until our minimum supported version is Pro 2.3 and we can use attribute rules to calculate the SIDC at the feature/database level so this works even if the database is edited outside of the Symbol Editor.

@joebayles
Copy link
Contributor

This is imperative for interoperability for our customers to work with other systems.

@dfoll
Copy link
Collaborator

dfoll commented Jun 4, 2020

Just an fyi, Was having a convo with @jfrygeo and Armando today and this requirement came up again.

Also, is this a duplicate of #184, or vice versa?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants