Preserve Table State when switching between Layers
If the user sorts Column 1 in ascending order on Layer A, and is working on row 7777(is selected/highlighted), and then the user switches to Layer B(to check attributes on an element in that layer for example), and then switches back to Layer A, unfortunately, the sorting has disappeared, and the record on row 7777 is not longer visible/selected.
When editing table attributes, often times the user is working with two or more layers/data sets. For example, I have two layers.. Roads A and Roads B. Both sets share many of the same elements/records, but they are different, which is to say Layer A may have a Road that was created by Joe Smith, whereas Layer B may have the same Road created by Jain Plain, and although both represent the same Road(or stretch of road), each is unique in terms of geometry and table attributes. Joe Smith created a Road on Layer A that is 20 meters long, and has 10 vertices, whilst Jane Plain created a Road that is 25 meters long, and has 15 vertices. Joe Smith named the Road CALLE SOMEPLACE, and Jane Plain named the Road CALLE SOMEPLACES. Layer A happens to have the correct geom, whereas Layer B happens to have the correct name, however, the only way this is determined, is by visually comparing the two, which means the user must switch between layers, and herein is the problem/issue at hand.
The EASIEST way to edit records such as the above mentioned, is to sort the records, like in this example sorting them using the ROAD NAME. If 5000 roads need to be checked, then going about the process in alphabetical order works well. But if the user sorts each fo the two layers in alphabetical order, only to have that sorting disappear each time s/he switches between the two layers, it means the user must resort the layer each time s/he switch back and forth between them, and after sorting again, the user must then scroll to the row s/he was working on, or use the search feature to locate it, and this is made even more tedious because the search feature wil only display the column names in their order of creation, so there is no way to set a default column for a given layer, then means the user must click the search magnifying glass, and select the correct column, and then enter the search string. Either way, it more then doubles the amount of work time that is required.
Ideally, the state of each layer should be preserved based on its last state... so if the user sorts Layer A, and then switches to Layer B, then over to Layer C, D, E, and F, and then goes back to layer A, the table view should be the exact same as it was when the user had last left it... just like the map view currently behaves. Imagine for a moment if te map view changed each and every time the user switched between layers... that would really suck. well, the attributes view is just as important as is the map view, and when it changes, it sucks. :-)
Please sign in to leave a comment.