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

Can attribute table results be limited to map extent by default?

MikeMartin

I do not want all records of a layer's attribute table to be loaded into the attribute table. Can the config_Attribute Table.json be modified to limit results to the map extent by default, and only when the layer's scale range has been reached? Thanks.

Finde mehr Beiträge mit dem Tag

Accepted answers

RobertScheitlin__GISP

Mike and Rebecca,

There is not configuration option for this but it is a really simple one line code change if you are using the WAB Dev version.

client\stemapp\widgets\AttributeTable\widget.js line 185.

this.matchingMap = false;

change to:

this.matchingMap = true;

All comments

GeorgeKatsambas

oops, i should have read the whole thread, thanks.

RobertScheitlin__GISP

George,

In more recent versions like 2.10 you do not need to make any code change this is an option in the widgets settings page.

GeorgeKatsambas

In WAB 2.11 where is this option?

this.matchingMap = false;

change to:

this.matchingMap = true;

MichaelRobb

Nope, does not work.

Line numbers dont match either. There is only 1601 lines in the apps\##\widgets\AttributeTable\Widget.js

MichaelPotter1

Thanks Nick,

I did change this and it does work for only displaying data in your current extent by default.

However, if the data has a scale dependency and is not currently visible at that particular scale or is turn off in your layer list then the data is still listed in the Attribute Table.

Ideally, similar to how the Flex version of the Attribute Table works, if a layer is not turned on then the tab for that layer does not display in the Attribute table and if the layer is not at the visible scale then no data for that layer displays in the Attribute Table(fields are greyed out and "Layer is out of scale range" is displayed"), see image below.

Hope this makes sense.

Regards

NicholasBarger

Yes it can…. Change the following lines of code to default the attribute table to visible extent

*Check the filter by Map Extent by default.

1. Attribute Widget.js

2. Change Line 198 this.matchingmap= true

3. Change line 1963 this.matchingcheckbox=true

~ Nick

image001.jpg

Angle Calculation.pdf

MikeMartin

I see the same results as you, Michael. The attribute table displays all records within the map extent, regardless of scale dependency or layer visibility. I'll leave it to experts (of which I am not) to say whether or not that can be adjusted.

MichaelPotter1

Does the Attribute Table widget limit the results when the layer's scale range has not been reached?

Regardless of whether I am using a Web Map or Local Layers, my Attribute Table displays all features in that extent, even if the layer is turned off and not yet at a visible scale range.

NicholasBarger

You can also change the following line of code so that the box appears checked.

line 1963 this.matchingcheckbox=true

This will keep the functionality consistent... i.e. you won't have to check the box and uncheck the box to turn off the spatial filter

MikeMartin

That is beautiful! Thank you Robert. Worked like a charm. I appreciate your help. Thanks also Rebecca.

RebeccaStrauch__GISP

Robert, that worked great.

Note: Of course it does not transfer forward to existing apps, so if anyone else uses this, remember to also update your \server\apps\<app#>\widgets\AttributeTable\widget.js

Interesting observation of odd behavior, even though it definitely works, the Options checkbox started off as unchecked. Checking didn't seem to change anything the first time...but doing it a few times did. So, the togle timing is a bit strange, but not an issue in my opinion, since I would rather have it always filtered.

EDITED: Not totally strange behavior, its just the initial checkbox isn't checked. After code modification, firing up the app and revieiwing attribute table:

- filter box unchecked, but table filtered (minor graphical issue)

- manually check the box - table filtered, as expected

- manualy uncheck the box - table goes back to being unfiltered.

so, just a very minor checkbox thing.

I can't mark your answer as "correct", but hopefully Mike will after he's tested.

RobertScheitlin__GISP

Mike and Rebecca,

There is not configuration option for this but it is a really simple one line code change if you are using the WAB Dev version.

client\stemapp\widgets\AttributeTable\widget.js line 185.

this.matchingMap = false;

change to:

this.matchingMap = true;

RebeccaStrauch__GISP

I have the same question....specifically in the WAB dev edition for me. And using some of Robert Scheitlin, GISP‌ custom widgets.

Nimm an der Unterhaltung 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.