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.

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

Give the possibility to the RA to define the header his organization wants to see being used for each attribute in the exported shape file #891

Open
SteeveEbener opened this issue Mar 30, 2023 · 0 comments
Labels
enhancement New feature or request

Comments

@SteeveEbener
Copy link

User stories

  1. As a RA I want to have the possibility to define the header that is going to be included for each attribute in the exported attribute table of the shape files associated with a given geo-object type

Problems this relates to

  1. The possibility to correctly interpret the content of the shape file attribute tables hosted in the GPR
  2. Facilitate the link between the different products generated by the GPR (list, spatial data) and the corresponding data dictionary (see ticket Mismatch between list column header and data dictionary in exported spreadsheet and shape file #869)

Proposed solution

  1. Allow the RA to define the header to be used for each attribute at the geo-object type level
  2. To avoid any issues, the headers in question should not contain more than 12 characters

Considered alternatives

  1. None

Additional context

Linked to ticket #869 (the issue here above was initially included in that ticket)

@SteeveEbener SteeveEbener added the enhancement New feature or request label Mar 30, 2023
@SteeveEbener SteeveEbener changed the title Give the possibility to the RA to define the header his organization wants to see being used for each attributet in the exported shape file Give the possibility to the RA to define the header his organization wants to see being used for each attribute in the exported shape file Jul 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
Status: No status
Development

No branches or pull requests

1 participant