Skip to main content
  • EN

Hello,

 

I make a Workspace to import CAD Data in Oracle Spatial.

 

 

In my CAD file, i have some layer with accented character like 3.1 MP - A désaffecter.

 

 

When FME read Autocad Writer i have the error : "ACAD reader: The encoded string is not a valid fme-wwjd string: '3.1 MP - A d\\xC3\\xA9saffecter'"

 

 

In other workspace, I met same problem with parameters which contains accented character or with excel files with accented character.

 

 

Can you help me?

 

With FME 2018, i hadn't this problem.

 

 

Thanks

 

 

Bernard Dinon

 

Hello @bernarddinon - it looks like this is the same issue as here: https://knowledge.safe.com/questions/89891/fme-2019-acad-reader-error-the-encoded-string-is-n.html

There is already a report for the problem (reference FMEENGINE-59779) and I will follow up with the developers and product managers to see if we can get this one fixed quickly, as there are a lot of users affected.

The workaround is to have each feature type (layer) listed separately in the workspace and not to use the Feature Type Merge Filter. It will take up more space in the workspace, but you can put a bookmark around it and collapse it, and that would help.

Apologies for the inconvenience, and thank you for your patience.

Hi @mark2atsafe . Thank you for your answer. I will try the workaround.

 

 

Thank you

Hello @bernarddinon - it looks like this is the same issue as here: https://knowledge.safe.com/questions/89891/fme-2019-acad-reader-error-the-encoded-string-is-n.html

There is already a report for the problem (reference FMEENGINE-59779) and I will follow up with the developers and product managers to see if we can get this one fixed quickly, as there are a lot of users affected.

The workaround is to have each feature type (layer) listed separately in the workspace and not to use the Feature Type Merge Filter. It will take up more space in the workspace, but you can put a bookmark around it and collapse it, and that would help.

Apologies for the inconvenience, and thank you for your patience.

So I got in touch with the development team responsible for this. Ironically (if that's the word) I missed their weekly meeting this morning by a few minutes, so we'll have to wait until next week for them to look at the issue - but I'm told it is now a "priority fix" and we'll see some action on it shortly.

So I got in touch with the development team responsible for this. Ironically (if that's the word) I missed their weekly meeting this morning by a few minutes, so we'll have to wait until next week for them to look at the issue - but I'm told it is now a "priority fix" and we'll see some action on it shortly.

Thanks. I'm waiting your feedback :)

So I got in touch with the development team responsible for this. Ironically (if that's the word) I missed their weekly meeting this morning by a few minutes, so we'll have to wait until next week for them to look at the issue - but I'm told it is now a "priority fix" and we'll see some action on it shortly.

I tried your workaround and it works, but if we hava a lot of feature (Layer), it's take place even with bookmark 😞

Hi @mark2atsafe . Thank you for your answer. I will try the workaround.

 

 

Thank you

Do you need to specify the feature types/layers to read? If you don't specify, it appears to read layers even with accented characters with no issues.

It also doesn't appear to be a problem for the FeatureReader even if specifying feature types to read, so you could use that with the generic port

Do you need to specify the feature types/layers to read? If you don't specify, it appears to read layers even with accented characters with no issues.

It also doesn't appear to be a problem for the FeatureReader even if specifying feature types to read, so you could use that with the generic port

Yes. It's better because i have a lot of layer, but i can put a testfilter after reader where i don't specify the feature. I'm goint to test your idea and i let you know the result.

 

 

Yes. It's better because i have a lot of layer, but i can put a testfilter after reader where i don't specify the feature. I'm goint to test your idea and i let you know the result.

 

 

The FeatureReader option that I just edited my answer to include may be better in that case
The FeatureReader option that I just edited my answer to include may be better in that case

Thank. I will try the FeatureReader solution and i'm tell you the result.

Reply


Community Stats

30,159
Posts
114,480
Replies
37,804
Members
Terms & ConditionsCookie settings
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.