Skip to main content
  • EN

Hi,

I´m trying to extract data using an ArcGIS Server Feature service reader which is going okay. For some of the layers I´m getting the following error:

Python Exception <UnicodeDecodeError>: 'ascii' codec can't decode byte 0xe5 in position 10: ordinal not in range(128)

I´m guessing the problem relates to some characters in the tabel of the layer which can´t be read by the ArcGIS reader? Or could the problem relates to the transformer being programmed in Python 2 instead of Python 3 (which i´ve been told is handling encoding-problems better)?

I only need the geometries (and the layer names), so is there a way for me just to be able to read the those?

If that´s not possible is there a way for me to encode the tables so that I wont get the error-message?

Thanks in advance :)

 

Christian

Which version of FME is this?

Can you try using FME 2017 RC, I know there's been quite a few changes in the AGOL reader/writers in the latest versions. Download: http://www.safe.com/support/support-resources/fme-downloads/beta/

Hi,

I´m not that experienced with the ArcGIS Server formats so I´ll excuse my lack of knowledge if that´s the problem 🙂.

It´s the latest FME 2017 RC that I´m using.

And it´s not the AGOL reader I´m using, it´s the "Esri ArcGIS Server Feature Service" reader I´m using.

Christian

Hi,

I´m not that experienced with the ArcGIS Server formats so I´ll excuse my lack of knowledge if that´s the problem 🙂.

It´s the latest FME 2017 RC that I´m using.

And it´s not the AGOL reader I´m using, it´s the "Esri ArcGIS Server Feature Service" reader I´m using.

Christian

Thanks for the info. Sounds like you should be contacting Safe support about this. Be sure to give them everything necessary to reproduce the error on their side.

Hi @rkcha. The issue you encountered has been reproduced by development and problem report PR# 76052 filed. I'll let you know when it has has been addressed. I'm sorry that you encountered this problem.

Hi @rkcha. The issue you encountered has been reproduced by development and problem report PR# 76052 filed. I'll let you know when it has has been addressed. I'm sorry that you encountered this problem.

Hi,

 

 

I can see that the problem should have been solved with b17255. Unfortunately I´m still getting the same error (using 2017.0.0.0 - 20170228 - build 17259). I would like to send you the workbench and URL if that would be helpfull?

 

 

Christian

 

 

Hi,

 

 

I can see that the problem should have been solved with b17255. Unfortunately I´m still getting the same error (using 2017.0.0.0 - 20170228 - build 17259). I would like to send you the workbench and URL if that would be helpfull?

 

 

Christian

 

 

Hi Christian - yes, if you can provide us a URL we can access, that would be very helpful. Please submit it to our support staff.

Reply


Community Stats

30,126
Posts
114,374
Replies
37,765
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.