Skip to main content
  • EN

Greetings!

I wanted to start using FME 2019 today with a new workflow I'ven been tasked to create. It's pretty simple: read polygons from a DWG file and store them in a SHAPE file.

The source file has many layers, so my idea was reading all the layters except one (it contains texts I don't want). I have checked the "Single Merged Feature Option" and in the "Feature types to read" parameter I have picked the ones I want:

0684Q00000ArFQRQA3.png

When I try to run this, I get the following error:

ERROR |ACAD reader: The encoded string is not a valid fme-wwjd string: 'ELC.02 - AREA DE EXPANSI\xC3\x93N OESTE'

It seems the Reader doesn't like the accents in the layer names.

If I use "Single Feature Types" instead of merged ones, FME is capable of reading all the features.

I still have FME 2018.1 installed, so I have tried the same steps in that version and it works fine with merged features.

Could this be a bug of FME 2019 (19238) or is there something new about that reader that I am missing?

Hi all. Good news. I am told that this issue is fixed. The fix is in FME 2019.2 as of build 19806. You may have to re-add the reader (I'm not sure) and if for some reason it still causes a problem, then please let us know.

Regards

Mark

When is going to be available? Right now I can download build 19801

When is going to be available? Right now I can download build 19801

Oops. Yes. You are right. I looked it up and this version will be 2019.2.1 and it should be available next Tuesday (3rd December). That's the plan anyway, and I don't see any issues stopping that from happening.

So, sorry about that, but it will be available very shortly.

Oops. Yes. You are right. I looked it up and this version will be 2019.2.1 and it should be available next Tuesday (3rd December). That's the plan anyway, and I don't see any issues stopping that from happening.

So, sorry about that, but it will be available very shortly.

Hi Mark,

it seems the error is fixed in 19813 indeed but (at least for me) the Reprojector does not work correctly anymore. I have a workspace based on 19801 where my dwg file was reprojected properly but now its completely wrong. Can you look into this? I can not share the data used but the workspace should reproject from AUT-GK28-5 to WGS 84

Oops. Yes. You are right. I looked it up and this version will be 2019.2.1 and it should be available next Tuesday (3rd December). That's the plan anyway, and I don't see any issues stopping that from happening.

So, sorry about that, but it will be available very shortly.

Nevermind - the problem was a shapefile located in the same folder with the same filename as the dwg. I guess the shapefiles prj file was somehow associated with the dwg. When I put the dwg in another folder everything went fine.

same problem on FeatureReader with Excel file with subdirectory it begin with _

exemple "_name"

Reply


Community Stats

30,122
Posts
114,331
Replies
37,750
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.