You could try to read the features through an HTTPCaller. You can point to the specific layer. You'll only need to create features from the output using JSON-transformers. I once created a blog about how to do such things for ArcGIS Online, but it works for ArcGIS Server as well.

You can find the blog here.

Hello @aaron,

I believe the issue here was as a result of a bug, that has since been addressed. If you are able to upgrade to either the last official release of 2016 or upgrade to FME 2018, I suspect this issue has been addressed.

Maybe I should log a different call, but at the same time don't want to create any duplication. I am trying to read all the layers using an Esri ArcGIS Server Feature Service reader, but getting exactly the same error as @aaron, yet I am using FME Desktop 2019.0 and 2020.beta:

https://maps.london.gov.uk/gla/rest/services/apps/planning_data_map_03/MapServer

Has the bug returned, or is this a different issue?

Hi @arnold_bijlsma,

I tried the above URL in the ArcGIS Server Feature Service Reader and was able to successfully read the following features: Areas of Intensification, Article 4 Directions: Office to Residential, and Brownfield Register. This was tested in B19643 2019.1.

Thanks for looking into this. It's the Designated Open Space ones that cause me issues, using B19643. I presume it could be something to do with the name difference being within the brackets...?:

PS: I can log a different call if this is something different

Works for me with a FeatureReader and Single Output Port. When I switch to "One per Feature Type" I can reproduce the errors.

sample.fmwt

It's the second, third and fourth Designated Open Space datasets that are falling over

Ah, try the following values for Feature Types to Read:

"Designated Open Space (201)" "Designated Open Space (GreenBelt) (201)" "Designated Open Space (Metropolitan Open Land) (201)" "Designated Open Space (Other Open Space) (201)"

"Designated Open Space (201)" "Designated Open Space (GreenBelt) (201)" "Designated Open Space (Metropolitan Open Land) (201)" "Designated Open Space (Other Open Space) (201)"

That worked using a FeatureReader, and also works if I manually manipulate the Layer List on the normal Reader. Excellent! However, they should not all have had (201) as suffix, but (201), (210), (211) and (212):

"Designated Open Space (201)" "Designated Open Space (GreenBelt) (210)" "Designated Open Space (Metropolitan Open Land) (211)" "Designated Open Space (Other Open Space) (212)"

For my future self and anyone else coming across this thread: you can get the layer name with the layer ID by opening the MapServer link in your internet browser:

@trentatsafe: Going back to the original question at the very top of this page: Isn't this pretty much the same problem that you said was fixed? And is this the recommended solution: manually manipulating the layer list by appending the layer IDs?

I am experiencing the same issue using the latest FME Desktop build:

FME(R) 2022.2.4.0 (20230303 - Build 22792 - WIN64)