{"id":1667,"date":"2025-04-04T13:54:21","date_gmt":"2025-04-04T18:54:21","guid":{"rendered":"https:\/\/sites.owu.edu\/geog-292\/?p=1667"},"modified":"2025-04-04T13:54:21","modified_gmt":"2025-04-04T18:54:21","slug":"white-week-3","status":"publish","type":"post","link":"https:\/\/sites.owu.edu\/geog-292\/2025\/04\/04\/white-week-3\/","title":{"rendered":"White Week 3"},"content":{"rendered":"<p><span style=\"font-weight: 400\">In Chapters 3 and 4, I learned about two powerful tools for creating interactive GIS applications: ArcGIS Experience Builder and ArcGIS Web AppBuilder. Both platforms allow users to create custom web applications, but they differ in terms of flexibility, functionality, and user interface.<\/span><\/p>\n<p><span style=\"font-weight: 400\">Experience Builder felt like a more modern and customizable tool, especially with its drag-and-drop interface and responsive design features, making it well-suited for creating apps that work across devices. I found the widgets library to be highly versatile and liked that you can integrate dashboards, maps, and charts all into one seamless app.<\/span><\/p>\n<p><span style=\"font-weight: 400\">Web AppBuilder, while slightly older, still offers strong tools for fast map-based application development. I appreciated its ready-to-use templates and the large collection of widgets, which are very helpful for creating simple, functional web apps without coding.<\/span><\/p>\n<h3><span style=\"font-weight: 400\">Application Idea (Based on Chapters 3 &amp; 4)<\/span><\/h3>\n<p><span style=\"font-weight: 400\">For my application, I plan to use Delaware Data from Geog 291 to create a web app highlighting Delaware flood risk zones using Experience Builder. The app will allow users to view flood-prone areas, compare them with demographic data, and access links to emergency preparedness resources. By using interactive widgets, users will be able to filter the map by county, flood zone severity, and population characteristics. This app will be helpful for both public awareness and local decision-making.<\/span><\/p>\n<h3><span style=\"font-weight: 400\">Delaware Data Inventory<\/span><\/h3>\n<p><span style=\"font-weight: 400\">I have already completed the Delaware Data Inventory assignment previously in Geog 291.<\/span><\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>In Chapters 3 and 4, I learned about two powerful tools for creating interactive GIS applications: ArcGIS Experience Builder and ArcGIS Web AppBuilder. Both platforms allow users to create custom web applications, but they differ in terms of flexibility, functionality, and user interface. Experience Builder felt like a more modern and customizable tool, especially with its drag-and-drop interface and responsive design features, making it well-suited for creating apps that work across devices. I found the widgets library to be highly versatile and liked that you can integrate dashboards, maps, and charts all into one seamless app. Web AppBuilder, while slightly older, still offers strong tools for fast map-based application development. I appreciated its ready-to-use templates and the large collection of widgets, which are very helpful for creating simple, functional web apps without coding. Application Idea (Based on Chapters 3 &amp; 4) For my application, I plan to use Delaware Data from Geog 291 to create a web app highlighting Delaware flood risk zones using Experience Builder. The app will allow users to view flood-prone areas, compare them with demographic data, and access links to emergency preparedness resources. By using interactive widgets, users will be able to filter the map by county, flood zone severity, and population characteristics. This app will be helpful for both public awareness and local decision-making. Delaware Data Inventory I have already completed the Delaware Data Inventory assignment previously in Geog 291. &nbsp;<\/p>\n","protected":false},"author":2298,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-1667","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/posts\/1667","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/users\/2298"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/comments?post=1667"}],"version-history":[{"count":1,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/posts\/1667\/revisions"}],"predecessor-version":[{"id":1668,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/posts\/1667\/revisions\/1668"}],"wp:attachment":[{"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/media?parent=1667"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/categories?post=1667"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/tags?post=1667"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}