topic Re: javascript 4.6 and labeling FeatureLayer in ArcGIS JavaScript Maps SDK Questions

javascript 4.6 and labeling FeatureLayer

CynthiaKozma — Tue, 09 Jan 2018 22:59:33 GMT

I am new to javascript, but I am trying to put together a fairly simple application with v4.6. I have a contour layer that I am adding with new FeatureLayer(), but I am having a hard time getting it to label with elevation. I have tried using a Map Service hosted on our server, as well as, a hosted Feature Layer on AGOL (where the contours are already labeled in both). No luck with either. I have read that you can't label a 2D map, does this mean that it is virtually impossible to label the contours?? Is there any work around? A label would be so much better than a pop-up. Thanks for the help.

Re: javascript 4.6 and labeling FeatureLayer

RobertScheitlin__GISP — Tue, 09 Jan 2018 23:15:34 GMT

Cynthia,

That is correct if you need to label on the client then you have to use 3.x currently. If you have the mxd label the contours then when you add the MapImageLayer you will see the labels in 4.x though.

Re: javascript 4.6 and labeling FeatureLayer

CynthiaKozma — Tue, 09 Jan 2018 23:27:59 GMT

That's it! I used the MapImageLayer instead, and I got my labels. If that is what it takes for now. Thank you!

Re: javascript 4.6 and labeling FeatureLayer

ChrisSmith7 — Fri, 17 Aug 2018 19:12:44 GMT

Are there any updates on when this might come down the pipe?

Re: javascript 4.6 and labeling FeatureLayer

RobertScheitlin__GISP — Fri, 17 Aug 2018 19:31:39 GMT

Currently (4.8) labeling is supported for Point and Polygon Feature coming from a FeatureServer service on 10.6.1 server (not a MapServer service).

Re: javascript 4.6 and labeling FeatureLayer

ChrisSmith7 — Fri, 17 Aug 2018 19:40:49 GMT

I'm currently trying to label a MapServer FeatureLayer (kind of like this example - Add labels to a FeatureLayer | ArcGIS API for JavaScript 4.8 ), but I'm not having much luck. So far, I have:

1) Labeled on the MXD (the service now shows Has Labels: true)

2) Set-up a labelClass, as per the example referenced

3) Set labelsVisible: true in the FeatureLayer instantiation as per FeatureLayer | API Reference | ArcGIS API for JavaScript 4.8

4) Set labelingInfo: [labelClass], as per the example referenced

5) Set dojoConfig "esri-featurelayer-webgl": 1

6) Double and triple checked spelling for things like the labelingExpressionInfo expression, e.g. "$feature.AreaName", which refers to the field labeled in the MXD

There are no JS errors; I am attempting to label a polygon FeatureLayer. Any ideas for anything I might be missing?

Re: javascript 4.6 and labeling FeatureLayer

RobertScheitlin__GISP — Fri, 17 Aug 2018 20:06:44 GMT

Like I said ONLY FeatureServer services are supported that come from ArcGIS Server 10.6.1 or AGOL It will NOT work with a MapServer url.

Re: javascript 4.6 and labeling FeatureLayer

ChrisSmith7 — Fri, 17 Aug 2018 20:10:35 GMT

I kinda figured that would be the answer after re-reading the thread. It wasn't abundantly clear in the known limitations section of the example. Thank you.

Re: javascript 4.6 and labeling FeatureLayer

RobertScheitlin__GISP — Fri, 17 Aug 2018 20:12:12 GMT

A MapServer will work in 4.9

Re: javascript 4.6 and labeling FeatureLayer

ChrisSmith7 — Fri, 17 Aug 2018 20:16:27 GMT

Great! You'd think that would have been available much sooner as a core function...

Re: javascript 4.6 and labeling FeatureLayer

RobertScheitlin__GISP — Fri, 17 Aug 2018 20:19:01 GMT

The team has years of work to re-produce to get the 4.x API up to par with 3.x... Think about how many years the 3.x API has been out.

Re: javascript 4.6 and labeling FeatureLayer

MichaelLodes2 — Wed, 29 Aug 2018 14:38:33 GMT

Hi Robert,

I dont understand if labeling (for example with angle) is possible for a "hosted feature layer" on AGOL in 4.8. Could you tell me? (Sorry I am not able relate the word "FeatureServer service".)

Thank you,

Michael

Re: javascript 4.6 and labeling FeatureLayer

RobertScheitlin__GISP — Wed, 29 Aug 2018 14:41:30 GMT

Michael,

A hosted featurelayer will be a FeatureService. What is meant by FeatureService is "FeatureService" in the url Vs. MapService that you might have on your own ArcGIS Server.

Re: javascript 4.6 and labeling FeatureLayer

WWalker — Thu, 01 Nov 2018 18:17:37 GMT

I'm using 4.9 with a FeatureService on Server 10.5.1. I can render labels, but it seems that the 'where' property of the LabelClass does not work properly. Is this a known issue, or am I missing something? See below:

const classificationClass = {

labelExpressionInfo: {

expression: "$feature.SPACECLASS + TextFormatting.NewLine + $feature.SPACEID"

minScale: 100,

labelPlacement: "always-horizontal",

symbol: brnTxtSym, // defined elsewhere

where: "SPACECLASS = 'Office'" // <-----This does not work

};

Re: javascript 4.6 and labeling FeatureLayer

Noah-Sager — Fri, 02 Nov 2018 16:40:04 GMT

Hi William. Currently, the `where` property only has limited support. We are hoping to expand it's usage at the next release.

https://developers.arcgis.com/javascript/latest/api-reference/esri-layers-support-LabelClass.html#where

For now, I would recommend using Arcade for the labeling logic in the labelExpression or labelExpressionInfo.

-Noah

Re: javascript 4.6 and labeling FeatureLayer

WWalker — Tue, 06 Nov 2018 17:18:20 GMT

I am using Arcade for the textual logic, however I would like to symbolize features based on attributes.

Similar to this example:

ArcGIS API for JavaScript Sandbox

But for whatever reason, my where clause (for a string type field) does not work.

If, for example, I change my where clause to "OBJECTID > 120", it works.

Re: javascript 4.6 and labeling FeatureLayer

WWalker — Sun, 12 Dec 2021 16:32:24 GMT

I found a partial solution. Text field comparisons do not require text to be wrapped in single quotes.

For instance, from the link Noah provided:

labelClass.where = "CITYNAME = 'Redlands'";

should be:

labelClass.where = "CITYNAME = Redlands";

EDIT: This does not seem to apply to strings with spaces - i.e. "CITYNAME = Redlands North" - does not work, with or without single quotes.

Another undocumented limitation.