Skip to main content
Archived

Add "character encoding" importation to "Choice with Alias" user parameter

Related products:Integrations
  • September 8, 2017
  • 1 reply
  • 28 views

mathieu_ambrosy
Contributor
Forum|alt.badge.img+5

Hi,

The "Choice with Alias" user parameter is great because we are able to import coordinate systems, readers and writers.

Why not the ability to import "Character Encoding" items too ?

It would be great ie for a shapefile writer. We could import easily a selection of character encoding in a user parameter.

Mathieu.

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

1 reply

rylanatsafe
Safer
Forum|alt.badge.img+14
  • Safer
  • September 12, 2017

@mathieu_ambrosy - Great idea! I think I may have found a "workaround"... emphasis on the quotation marks.

Step1: Create new User Parameter > Choice with Alias > Configuration > Import from Dataset.

'

Step2: Select CSV Reader, select the encodings.db (located in the FME installation folder).

Step3: Select Parameters and set "Delimiter Character" to | and set "Data Start Line" to 11. (Note: This value may be different for different FME versions...)

Step4: Select Continue and set "Import from" to Attribute Values.

Step5: Select Continue and set "Display Alias" to col2 and "Value" to col0. Select Import.

'

Step6. Voila! Now vote for this Idea because that was too much overhead.

'

Hopefully this is what you meant. If not, I had a fun journey with FME!

Please note that this is completely untested if this can actually be passed into Readers and Writers.

 

stepx_2.png