Pages<\/p>\n\n\n\n
I started off using a single main page which meant that all functionality was present right at the start screen. I completely underestimated the potential of multiple pages, and I really am happy that I recognize it now, as it allows for much clearer view of the data. The current development allowed me to create a version of Catalog that I am happy about. I really want the information about trees to be displayed clearly, and having a small sidebar or pop-up windows really does not encourage engagement with the app. So, being able to use the entirety of the screen dimensions (since there is no need to display the map) I set up a large list widget with a fixed panel on the right side. While there is a lot of development left to do when it comes to specific information being show, I think that it is better to have more space (where new information will be added in the future) than stack up too much information in confined space.<\/p>\n\n\n\n Views<\/p>\n\n\n\n Another feature of ArcGIS Experience that I recently took advantage of is the View widget. Similarly to Pages, it allows me to offload the screen from displaying too much information. While Pages change the display of the entirety of the screen, Views only changes the contents of a specific Section of the screen. I thought it would be a reasonable choice to have the section be a form of sub-menu, additional to the Pages one to the left. The menu of Views appears only on the page that contains View-operated Section, making it accessible only when needed, and thus not adding more clutter to the screen. General Conclusion<\/p>\n\n\n\n The use of both Pages and Views is a true renaissance for Tree Map interface. Acting together they behave as a menu with sub-menus, making the functionality of the experience much clearer visually but also conceptually for the potential users. It is also much more straight-forward to work with the map from the developer’s perspective, as every page\/view is independent from others, allowing for more experimentation and results that are much more visible.<\/p>\n\n\n\n ArcGIS Experience Throughout February I focused on improving my project, the Tree Map, when it comes to design ideas. I previously tried to set the interface of the ArcGIS Experience application to allow users to filter through tree data, and it technically worked well, but was not aesthetically pleasing. It also felt somewhat “busy” on […]<\/p>\n","protected":false},"author":1,"featured_media":542,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-535","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/gabrielaroznawska.sites.grinnell.edu\/index.php\/wp-json\/wp\/v2\/posts\/535","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/gabrielaroznawska.sites.grinnell.edu\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/gabrielaroznawska.sites.grinnell.edu\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/gabrielaroznawska.sites.grinnell.edu\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/gabrielaroznawska.sites.grinnell.edu\/index.php\/wp-json\/wp\/v2\/comments?post=535"}],"version-history":[{"count":2,"href":"https:\/\/gabrielaroznawska.sites.grinnell.edu\/index.php\/wp-json\/wp\/v2\/posts\/535\/revisions"}],"predecessor-version":[{"id":543,"href":"https:\/\/gabrielaroznawska.sites.grinnell.edu\/index.php\/wp-json\/wp\/v2\/posts\/535\/revisions\/543"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/gabrielaroznawska.sites.grinnell.edu\/index.php\/wp-json\/wp\/v2\/media\/542"}],"wp:attachment":[{"href":"https:\/\/gabrielaroznawska.sites.grinnell.edu\/index.php\/wp-json\/wp\/v2\/media?parent=535"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/gabrielaroznawska.sites.grinnell.edu\/index.php\/wp-json\/wp\/v2\/categories?post=535"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/gabrielaroznawska.sites.grinnell.edu\/index.php\/wp-json\/wp\/v2\/tags?post=535"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
The present development includes four different pages that the user can switch between. One of the main reasons why I initially did not consider to explore the multi-page functionality is because of the ability to show entirely different screens, which breaks the illusion of different forms of interaction with the map. To avoid that I maintained the left-side page menu through all the pages, and used the same map for all pages interacting with it — “Map”, “Special Trees” and “Paths”. This allows the users to feel as if they simply change the settings, while in reality the entire setup of the interface changes. Most importantly, the information is categorized, so the screen does not feel as “busy” as it did before.<\/p>\n\n\n\n![\"A](\"https:\/\/gabrielaroznawska.sites.grinnell.edu\/wp-content\/uploads\/2026\/04\/Screenshot-2026-04-05-at-7.41.14-PM-1024x612.png\")
![\"A](\"https:\/\/gabrielaroznawska.sites.grinnell.edu\/wp-content\/uploads\/2026\/04\/Screenshot-2026-04-05-at-7.56.03-PM-1-1024x518.png\")
I really appreciate this feature because it allows me to categorize the type of information within the application, and not create unnecessary pages that won’t have a significant difference in functionality. Also, it provides a rather clear setup for the users to understand – for example, only when you select “Paths” you are able to browse the different “Paths” available to take. If using only Pages, the display of Page menu would make it so that all the paths would be visible from any part of the site, which is just unnecessary and counterintuitive.
<\/p>\n\n\n\n![\"A](\"https:\/\/gabrielaroznawska.sites.grinnell.edu\/wp-content\/uploads\/2026\/04\/Screenshot-2026-04-05-at-8.09.11-PM-1024x524.png\")