nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Possible to un-deprecate AGSFeatureLayer init?

MichaelDavis3

It is possible to keep the init function for AGSFeatureLayer around? Or baring that, is there an actual time line to remove it?

I find creating empty AGSFeatureLayers to be occasionally useful when I need to do some fancy footwork with "behind the scenes" data layers that I don't want exposed to the app user. I know that's not probably a super valid use case but it has come in super handy on a couple of occasions.

Find more posts tagged with

Accepted answers

MichaelDavis3

Like I said, it might not be a particularly valid use case but here's an example:

We have a construction monitoring app for a large port construction project. This includes a huge number of map layers for each utility, layout, basemap, etc... Rather than present them with a giant layer list to manage we present a table of contents with "fake" AGSFeatureLayers that we might name "Potable Water" or "Topo". When users tap on a layer we might toggle a whole group on/off but also might re-set some definition queries or kick off other activity.

As I'm typing this I've just discovered that AGSGroupLayer is a thing and has been since 100.5. This looks like it might do 90% of what we are looking for.... so never mind --- cary on! 🙂

All comments

Nicholas-Furness

Can you explain a little more how you're using it this way that makes it useful for you? Not sure I follow.

Thanks!

Nick.

MichaelDavis3

Like I said, it might not be a particularly valid use case but here's an example:

As I'm typing this I've just discovered that AGSGroupLayer is a thing and has been since 100.5. This looks like it might do 90% of what we are looking for.... so never mind --- cary on! 🙂

Nicholas-Furness

Reading your response I was going to suggest Group Layers (or else using Feature Collection Layers as your placeholders). I think Group Layer is your friend here.

Note also the new AGSSubtypeFeatureLayer that was released with 100.7. That's very helpful where you have a single feature service layer with multiple subtypes that you want to treat separately. It's conceptually like an automated group layer: It'll give you a sub-layer per subtype, but is smart about how it queries back to the server when it needs to get data for those sub-layers.

Join the Conversation

Signed in members can post, follow updates, and more. New here? Register a free account.

Quick Links

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.