You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On the May 2nd faceted search call there was discussion around how intuitive (or lack of) the relation between the facets, map, and table is.
Currently, the map will display information about the rows that are currently displayed in the table. This means if there are 200 results and only 20 are shown in the table-only 20 of them will be shown on the map.
There wasn't a clear idea on what the map looks like, but the desired behavior was to at least
Filter the results when the map is zoomed in and out
Show all results on the map
It's likely that the current map interface will have to be significantly changed if we want to show more data because this style won't be super useful because we'd have balloon buttons all over the map.
The text was updated successfully, but these errors were encountered:
On the July 11 faceted search call, Rui pointed out that there are S2 libraries we can use to determine cell hierarchy so that we don't have to do it through SPARQL. This should be a time saving operation that can enable better zooming support to the map.
On the May 2nd faceted search call there was discussion around how intuitive (or lack of) the relation between the facets, map, and table is.
Currently, the map will display information about the rows that are currently displayed in the table. This means if there are 200 results and only 20 are shown in the table-only 20 of them will be shown on the map.
There wasn't a clear idea on what the map looks like, but the desired behavior was to at least
It's likely that the current map interface will have to be significantly changed if we want to show more data because this style won't be super useful because we'd have balloon buttons all over the map.
The text was updated successfully, but these errors were encountered: