Geoprocessing Task: Result Appears but no Labels

639
4
02-02-2011 03:06 PM
DossDingli
New Contributor
ArcGIS Server 10
Windows Server 2008 R2

I have a custom geoprocessing task that is being deployed from a tool layer.  My result is appearing in my map, but it is not being labeled. 

Before publishing, the tool was run as a tool layer and the symbology and labeling were applied to the output.  After that, it was all saved and then published.  The output of the tool is appearing, but there are no labels (simple labels using the standard labeling engine).

Any help or ideas would be appreciated.
Tags (2)
0 Kudos
4 Replies
TonyContreras
Occasional Contributor
It is possible to define the symbology for the output features, however the help topic does not mention anything about labels. It may be worth testing though.

Defining output symbology for geoprocessing tasks:
http://help.arcgis.com/en/arcgisserver/10.0/help/arcgis_server_dotnet_help/index.html#/Defining_outp...
0 Kudos
DossDingli
New Contributor
Thank you Tony.

I switched over to Result Map and labels now work.  Oddly though, they still don't seem to want to appear as normal output (drawn by client).  This was not an issue in 9.3.1 (at least not for me).  I can work with the Result Map service, but I'd still like to know why the other one is refusing to label properly.

I'll keep updating if I find what is causing the issue.  If anyone has any more suggestions, feel free to add.
0 Kudos
TillSchmid
New Contributor II

I have the same problem: I am getting the result of my geoprocessing service with the correct symbology, but the labels are missing.

Same issue has been reported here: https://community.esri.com/thread/110710 

Doss Dingli‌: Can you explain how you solved the problem? Thank you!

0 Kudos
TillSchmid
New Contributor II

In my case the problem could be solved as follows:

The uploaded python script contained «MakeQueryLayer_management» (https://pro.arcgis.com/de/pro-app/tool-reference/data-management/make-query-layer.htm).

In order to display labels on the resulting mapservice, the "QueryLayer" had to be saved as a feature class first («FeatureClassToFeatureClass_conversion»; http://desktop.arcgis.com/de/arcmap/10.3/tools/conversion-toolbox/feature-class-to-feature-class.htm).

0 Kudos