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; } } }

Gibt es in AGOL-Webkarten-Layern eine Feldbegrenzung, durch die die Funktion zum Ändern der Symbolisierung nicht mehr funktioniert?

AdamDaily

Ich habe einer Webkarte einen Punkt-Layer hinzugefügt und möchte die Symbolisierung ändern und die Punkte anhand von Attributen farblich kennzeichnen. Unter Schritt 1 „Attribut zum Anzeigen auswählen“ ist das Dropdown-Menü leer. Es stehen keine Felder zur Auswahl. Ich kann nicht mit Schritt 2 „Darstellungsstil auswählen“ fortfahren, wenn in Schritt 1 nichts ausgewählt ist. Als einzige Möglichkeit scheint es, die meisten meiner Felder auszublenden, bevor ich das Menü zum Ändern des Darstellungsstils öffne.

Es scheint, als könne AGOL nur eine bestimmte Anzahl von Feldern in einem Layer verarbeiten, um die Attributliste zu erstellen, bevor ein Fehler auftritt. Weiß jemand, wie hoch dieses Limit ist?

Finde mehr Beiträge mit dem Tag

Accepted answers

JaredPoe1

Unfortunately from what I can see, there doesn't seem to be a set limit on the number of fields allowed in a feature layer as there are many factors that go into these issues. This includes not only the number of fields, but the number of total records, points/lines/polygon features, storage size of the layer, etc.

While it is not a cutoff limit (as many layers can have many fields and work), ideally we would want hosted feature layers to have well below 100 fields in order to ensure the layer functions as expected.

I apologize that there isn't a more clear and concise answer here. Please let me know if you have any further questions and I'd be happy to look more into this.

All comments

JaredPoe1

Hi Adam,

It seems AGOL can only handle a certain number of fields in a layer to generate the attribute list before it fails. Does anyone know what that limit is?

This very well could be the case. Do you know how many total fields there are in the layer? I am not sure if there is a specific limit, but I have run into issues myself with other AGOL functionality when too many fields are active. I think you're right with there being an issue handling the amount of fields in the drop down.

We usually recommend removing all unneeded/unused fields in the feature layer to minimize issues. If all fields are needed, have you attempted some other troubleshooting steps including clearing your browser cache, trying on a different internet browser, different computer, etc.?

Best,

Jared

AdamDaily

I have tried clearing the cache, different browsers, and machines. Same result every way.

This particular layer is huge, nearly 500 fields. I certainly don't need many of those and turning off fields can work. But, it this is a known limitation and the only way to edit layer symbology in a web map, it would be nice to see a mention of that in the documentation and to know what the magic cutoff number is. 20, 50, 200, etc. With layers this big, its a lot of time deciding what fields to keep and turn off and then going back and forth wondering if the drop down menu will work now.

JaredPoe1

I apologize that there isn't a more clear and concise answer here. Please let me know if you have any further questions and I'd be happy to look more into this.

AdamDaily

It makes sense there are a number of factors involved. Thanks for the quick response. Good info to be aware of moving forward.

Nimm an der Diskussion teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

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