Category: Uncategorized

Chapter 3:

Chapter 3 covers the basics of creating a web experience, which consists of multiple pages and or windows. I think the level of customization is cool, as you can add different aspects such as widgets. There are two types of widgets, basic ones, which act out app functions such as legends and layers. The other type of widget is called a layout widget, which spreads the widget out across different pages. The web experience can also display widgets consisting of 2D or 3D features, and they can be set to perform their actions either automatically, or manually through the use of a button. The format of the web experience is quite user friendly in the way that one can create them using templates, preset themes, and can access data from ArcGIS online, which offers a very large selection of datasets to choose from. The platform that the experience is created on is called an experience builder, which can come in the form of multiple different versions. The chapter goes into these different types of experience builders in a very general sense, but I wonder what the differences would be like if I tested them all out on my own. My time with the web experience creation was quite smooth, and the tutorial was quite clear. The web experience builder made it very easy to download and import data to manipulate it. Overall, I liked the web experience creation, and I like how visually clean the widgets turn out.  

Chapter 4:

The fourth chapter delves into the existence of a mobile application of ArcGIS, which I think is really interesting to offer, as last semester I knew GIS as a hefty software that required a PC just to run. To me, it begs the question of the overall benefit of desktop ArcGIS over ArcGIS Online, which has struck me as much more user friendly and convenient in terms of its extreme mobility. The features that ArcGIS Online offers are pretty cool too, as you can pinpoint your exact location on a map, increase efficiency when conducting data collection by replacing paper datasheets, up to date special monitoring, and an easy mode of communication. I really liked that the chapter included the limitations of this seemingly perfect convenient platform, which makes a lot of sense that it does have limitations, as it is adapted from such a large application. Some of these limitations include CPU speed, network connection, and limited screen size. On online GIS, one can still edit layers, delete layers, and make general actions as allowed by the organization owner of the map or dataset. This chapter also reinstates how the different modes of ownership work within an ArcGIS map, as public, and different levels of city staff have differing amounts of accessibility. I remember this concept being brought up from the introductory tutorial from week 1. There are also different types of approaches that can be used for the ArcGIS mobile apps, such as browser based approach, native based approach, and hybrid based approach. 

Applications: 

I could use the formats covered in chapter 3 and 4 to potentially create a map that features the distribution of monarch butterflies around different urban agricultural plots versus natural growing pollinator gardens, as I think it would be interesting to see what kinds of areas their adaptability can be seen. Monarch butterflies are heavily migratory species, and I was curious to see if their migratory patterns change over time based on the development of agriculture, and if so, how drastic that change is. In order to measure that change, I could even compare newer data with data recorded from a much longer time ago. Another idea of mine was to capture the distribution deer roadkill reports and their adjacence to different dense urban areas, because I think that it would be a valuable display of data in the context of land management, and conservation of predators. It would also presumably be an easy project to obtain data from, as drivers are instructed to report a vehicular deer kill whenever they occur, and I would assume that data is public domain. I probably would have to include the landmarks of the cities for reference, so the only data I would be manually entering would be the deer roadkill data.

Chapter 3: 

Chapter 3 introduces ArcGIS Experience Builder, which is a more flexible tool for creating web applications. To be more specific, it allows users to design apps with customizable layouts and to integrate multiple types of content (like maps, charts, and text) into the app. Users can control how the app looks and behaves across different devices. This makes it possible to create interactive experiences tailored to specific audiences or purposes, depending on what data you are displaying. What stood out to me is how customizable it is compared to other tools. You can organize an entire interface of info relating to your map, instead of simply creating the map. You can choose from different pre-made templates and widgets, allowing for room for creativity when deciding the best way to display your information. I also thought it was interesting that there are both layout widgets (that organize content) and functional widgets (that perform tasks). As previously mentioned, the app can be displayed across different devices, including mobile phones. This makes the apps being created much more accessible and versatile. As someone who has experience with graphic design, I appreciated how Experience Builder encourages well thought out design. Sometimes, when scientific data is displayed, it can come off as boring to the average person due to the lack of visual flair. ArcGIS Experience Builder negates this by allowing freedom for design. It’s more than just showing data; it’s guiding users through a visual experience so they can explore the information effectively. 

Chapter 4: 

Chapter 4 introduces ArcGIS Web AppBuilder and expands on the idea of mobile GIS. In particular, Chapter 4 highlights the advantages that mobile GIS provides. This being an avenue to easy data collection, real-time updates, and the ability to access these GIS tools/data from virtually anywhere. Everything previously mentioned makes it much simpler for users to gather and update data directly in the field without needing to return to a desktop computer.  Web AppBuilder is another tool for creating web GIS applications that happens to be effective when used on mobile devices. It is more template-based, meaning it is quicker and easier to build these applications. However, it offers less customization and fewer options for organizing compared to Experience Builder. This tradeoff is important depending on what the app you’re creating is trying to achieve. For example, the simplicity of Web AppBuilder may make it easier for the general public to use, or just easier to access in general. As well as a quicker application production time when time and resources are limited in specific cases. Despite the simplicity of Web AppBuilder when compared to Experience Builder, it still provides a variety of built-in widgets. These include search tools, measurement tools, and filters. All of which allow users to interact with the map/data without needing an extensive knowledge of GIS programming or cartography.  Overall, both chapter tutorials were understandable and simplistic to perform. 

Applications: 

I could create an interactive web application involving water quality. I am very interested in hydrology, and the concepts discussed in these two chapters could aid in displaying/gathering data related to hydrology and water quality. Let’s say I find and use data from local streams and ponds collected by scientists. I could design an app to show maps of sampling locations, and input filters that let users focus on specific bodies of water. First, I would need to decide if I want to use Experience Builder or Web AppBuilder. Experience Builder could allow me to design a highly detailed and fully customized interface, effective for scientists and other academics to study water quality patterns. On the flipside, Web AppBuilder would allow me to design a simpler, more user friendly version of the previous app that could be easily accessed and understood by the general public. 

Chapter 1:

Chapter 1 is primarily focused on the basic fundamentals of Web GIS and some differences it has to other GIS systems, as well as its functions. One idea that stood out to me is how GIS has shifted from being a private software with projects conducted on private computers to something that is interactive and collaborative on the web through Web GIS. The chapter highlighted the importance of this. It allows GIS data to become much more accessible to whoever may need it. As well as provide a place to store and collect said GIS data. It is very convenient to have all of this data so easily accessible. In my eyes, the system seems to be structured around content (data and maps), possible capabilities (tools and analysis), and its users (people interacting with the system in different roles/ways). All of these topics were mentioned or detailed in Chapter 1.  Another key takeaway from Chapter 1 is the importance of layers. Of course, we are able to manipulate and view the different layers within the actual ArcGIS platform. However, the ability to also perform this action on the web without any complex software is valuable. Being able to stack different types of information and turn them on or off makes maps much more powerful, as it changes maps from a boring static visual into a tool for analysis. So the fact that this is available through the web without needing to access any complex GIS programs is invaluable for accessibility reasons previously mentioned. All of this was highlighted in chapter 1. 

Chapter 2:

Chapter 2 builds on the fundamentals of the previous chapter by focusing more on how data is presented. There is an extremely wide range of possible ways to present data within Web GIS.  This chapter introduces Smart Mapping. Smart mapping is the idea to design maps in a way that matches the type of data being shown, ensuring the visual effectively communicates the information wanting to be displayed. It is a key idea, because it guides users toward appropriate visual styles based on their data. For example, if you want to display numerical data, it is often best represented with a color gradient. I am still thinking about how different visualization choices (like using a categorized map versus a heat map) can lead people to draw different conclusions from the same dataset. With Smart Mapping aiding the user, they do not need to be an expert in order to properly display their data in the most efficient way.  I also found the explanation of system components and data types useful, in particular, the difference between hosted layers and non-hosted layers.  Hosted layers are already existing data within the layer being published, and is managed online and already ready for users to use. Non-hosted layers are controlled by users, where the users manage the data. Chapter 2 explains the difference well. Overall, both chapter tutorials were understandable and simplistic to perform. 

Applications: 

I am very interested in plants and the ecosystems they live in. As previously mentioned, Smart Mapping could allow you to effectively display numerical data through a color gradient map. It would be cool to create a gradient map to show variation in plant growth across different areas. I could collect data by measuring plant height/density in several locations, with each location being assigned a number value based on the measurement I collected. Using a color gradient map, areas with higher plant growth could be shown in darker shades. While areas with lower growth could be shown in lighter shades. This would make it easy to identify patterns in length. Using smart mapping would help ensure this is done correctly. 

Chapter 3 introduces the ArcGIS Experience Builder, aka ArcGIS Webapp builder. This platform is designed to be an all-encompassing tool for GIS creation, enabling flexible, easy production of visual aids for a wide variety of cases. ArcGIS Experience Builder is defined in a few simple steps, including choosing options from pre-made templates and layouts or creating your own to suit your situation. This tool, like ArcGIS Online, also has a sharing function and can be designed to work with a variety of different devices, including mobile phones. I find this really neat, as I feel, or have always thought of, GIS tools as needing heavy software or desktop computers to function properly, but this opens up a whole new world of GIS capabilities and use cases. It was interesting working with this area of GIS, as it is not something I typically think of when I think of “GIS,” but the presentation and digital uses of GIS mapping are just as important.

Chapter 4 goes on more with this topic, explaining why GIS accessibility, especially on mobile devices, is important and how it can be used for a slew of different cases. Interestingly, I have always thought of GIS as some kind of big, scary program, but things we use daily and carry around with us in our pockets, like smartphone GPS apps, are GIS too. I’m surprised at just how many simple things that I would not have thought of before include GIS programs and are a utilization of GIS results. Chapter 4 reviews some of these uses and how GIS can be implemented using mobile devices flexibly and conveniently, allowing for GIS production on the go. ArcGIS Online on mobile devices allows for simple editing and layering, which is a very neat and convenient tool. I think these tools can be very useful for things like environmental scientists tracking landforms and future business owners marking possible shop locations.

Chapter 3 ArcGIS Experience Builder:

Completing the chapter 3.1-3.6 tutorials was actually really fun to do. I liked seeing the difference between 2D and 3D maps side by side; it gave me a much better perspective on how these kinds of apps can be useful to the public or for charting info. I ran into a small issue with my 3D map failing to download, and had to back track a lot to find a step I missed in order to fix it, but after that it was smooth sailing. I really liked seeing how natural disaster patterns can be charted. I would’ve never thought they could be displayed like this until I saw them for myself in this chapter. I also thought it was cool how many options for widgets there was, not just maps but a ton of different options for both basic things and layout, and even adding the text widget. I like how much info can be thrown into these apps and are able to be articulated to make complete sense to a user by the end.

Application:

From chapter 3, I could use Experience Builder to make a type of interactive map to visualize previous and real-time data on nutrient levels (like nitrogen and phosphorus), and bacteria counts across public ponds in Delaware. The app could have a whole ‘Health Index’ for each pond to help local residents here understand if the water is safe for fishing, boating, swimming, or anything like that. Maybe combine maps + charts + text + widgets? Dashboard style interphase? Also, by adding in data from the Surface Water Quality Monitoring Program, this app would allow its users to track how water quality changes seasonally and identify which ponds are most affected by runoff or algae blooms. (It was easy to pick this topic since I’m doing a research project over the summer that would tie into this data, too.)

Chapter 4 ArcGIS Web AppBuilder:

It first explains the advantages that Mobile GIS has over the traditional desktop version. These include mobility (being able to take the device anywhere), location awareness through GPS and cellular data, easy data collection, real-time information, more users, and being overall more versatile. Tutorial 4.1 4.9- first, I designed a survey, which was super cool and taught me a lot about Survey123 as well. I thought the section where I created a webmap using the line layer from before was helpful to learn and to see how different tutorials tie together. QuickCapture was really easy to understand and I could definently apply it’s use to my everyday life. I thought QuickCapture reminded me a lot of an app I have called “picturethis” which allows you to upload or take photos of any plant and will upload it to a data system that identifies what specicies it is, where its located, health, etc. These photos can be uploded to a group and be shared, similiar to the data in these tutorials. Overall I learned a lot from both of these chapters, and I think the fact they are so much more available to mobile users makes them all the more advanced. Both ArcGIS pro and ArcGIS Web have their pros, but the web version caters to a much larger audience and I can already see myself using a ton of these tutorials for other types of projects.

 

Chapter 3 and 4 primarily documented introductions for ArcGIS mobile and ArcGIS Experience Builder.

I found experimenting with these to be rather a redundant experience as I didn’t quite understand the advantage to using those apps over the base ArcGIS website. Nonetheless, as I continue experimenting and playing around with the features on the web GIS, I am now finding it to be significantly easier then the desktop GIS software as it feels like the majority of the features which I found to be rather useless in the  desktop GIS are removed allowing for a greater and more streamlined experience.

The story maps are also a huge upgrade to the cold, soulless maps I used in the previous GIS class. It is honestly a really interesting experience to add photos and details in the pop ups. I hope to get my story map done as my final exam in this class.

Chapter 3:

ArcGIS Experience Builder was made to be more configurable and flexible than other apps. This chapter introduces the terminology of the software as well as the layout and templates, etc. A web experience contains at least one page but can also have multiple pages or windows. A page is a document rhat is the foundation for the app’s layout, you can choose from a template. Windows are complimentary to pages and only have body content. A web experience has one theme and each page can have one template. Experience Builder has two types of widgets: basic and layout. Basic widgets are functional and can perform as app tools. Layout widgets are containers that help to organize widgets. 

Chapter 4:

This chapter provides an overview of Mobile GIS and three options for building apps. It introduces Esri mobile apps, and discusses the popular types of apps and frontiers. Some advantages of Mobile GIS are mobility, location awareness, ease of data collection, near-real-time information, large volume of users, and a versatile means of communication. Mobile app development includes many different approaches, browser-based, native-based, and hybrid-based. ArcGIS Field Maps is a new product that combines several previous products. It is an all-in-one solution that can support the different phases of field workflow. 

Application:

I think it would be interesting to use this software to create apps that display environmental quality indicators, such as water quality, air pollution, and proximity to resources. This would be helpful for scientists and policymakers to identify areas and populations that are at risk or at future risk for environmental hazards. This would also be a great tool for the public as they could create buffer zones around their homes and they can see the highest risks in their local area. 

Week 1

Hi all, my name is Luke, and I am a Junior ENVS Major here at OWU. Having already taken the 291 course, I was already familiar with the layout of the class page and website. I did, however, go into the settings and change the theme to “coffee”, which I thought looked nice, and also added a short biography to my profile. 

While reading through the “Get Started” article, one thing that stood out to me about ArcGIS Online was how much easier it is to share maps and data with the Online version compared to the Pro version. Being able to collaborate and share information seems like a very useful aspect of ArcGIS Online. Another aspect I read about in this article was that ArcGIS Online is also available on iPhones and tablets, which seems like another very useful feature. Overall, ArcGIS Online appears to be a more accessible software, with more emphasis on collaboration and sharing than the Pro version. 

In the ArcGIS Online Basics training course, I learned about the sharing capabilities within the software, such as the private, group, organization, and public sharing options. These options allow users to limit access to maps that might be private and share them with their desired audience. I also learned about the different types of layers, such as features, tiles, and map images, and how to identify whether a layer is a basemap layer or an operational layer. 

Two courses I found that might be interesting to complete were the “Forest-Based Classification and Regression Analysis Using ArcGIS Pro” and “Analyze Imagery with Raster Functions Using ArcGIS Online.”

One article I read came from the ArcGIS blog and explained how mapping can be used to display urbanization patterns and the expansion of urban areas. This can be done in a variety of ways, but the most common is measuring green space within an area and calculating NDVI, as shown in the image below. 

https://www.esri.com/arcgis-blog/products/arcgis/imagery/use-imagery-and-demographics-to-address-rapid-urbanization 

Another study I found interesting came from a parks district in my home state of Minnesota, which used aerial drone imaging to take pictures of deer, then used ArcOnline to create deer zones to better understand local deer populations. 

Week 2

Chapter 1 emphasizes the sharing capabilities of ArcOnline and how it can be used at any level of experience with GIS mapping. In short, the online version makes GIS more available to everyone, allowing GIS users to share information with peers in other professions and the general public. Content types were also highlighted in this chapter, such as data, layers, web maps, scenes, tools, and apps. It also explains the difference between basemaps and operational layers, in which basemaps provide reference or context, and operational layers can be edited by users for whatever purpose they need. I also learned about the difference between hosted and non-hosted feature layers, where hosted layers use data stored within the ArcGIS software, and non-hosted data comes from outside sources that a user or organization uploads. Attachments can also be uploaded to Arc and used to include more information or a visualization of a location on a map. 

The Chapter 1 tutorial showed how to create a map, upload imagery and files, and do basic edits to it, such as editing data within a point. It also explained how to share a completed map and how to create a web app from a web map. 

Chapter 2 dives deeper into the many types of layers and how to publish them. It also introduces the concept of smart mapping, which allows users to style their layers so that their maps display an intended purpose. Some examples of this are heat, color, and size, relationship, dot density, and type and size map styles. Pop-ups can also be useful for creating a more detailed map. When a location is clicked, a default pop-up shows the list of attributes and values for that location. Users can also add images, charts, and other external data to pop-ups to create a more interactive map. This chapter also highlights the different ways that users can explore and preview maps, such as map tour blocks and slideshows.

The chapter 2 tutorial showed how to edit layers using the styles pane, and how data can be displayed in a way that is visually appealing and makes sense. Using storymaps was a little complicated with how many options there were to add different types of text, images and animations. I found the express maps to be useful in creating a quick and simple visual. 

One application I thought of was to use data from colleges and universities to visualize changes in student enrollment over a period of time. This could be used to see trends in the preferences of college students when selecting schools, which could be used by schools to make changes to meet their enrollment goals. This could also be further developed into a web app that allows prospective students to suggest where they should go to college, based on how their interests and educational needs line up with those of students currently attending those schools.

Ch. 3: The map portion of this chapter went very well and I was able to easily create the maps needed. I can see how this would be useful in displaying all sorts of data. However, I had several issues with the data summary portion. First of all, I found out that using the link given in the tutorial does not work on a MacBook, so I had to go to the link in my browser, download the image, and upload it manually. Secondly, the views navigation widget would not work, which might be why I could not get the dynamic content widget to work later on, even though I made sure I was following the instructions.

Ch. 4: I had several issues with this chapter as well, most notably that the URL that had our data for the chapter would not load when I typed it into my browser. I skipped the first and second  tutorials because I could not obtain the data for them, though I was able to get the gist of it from reading the instructions. On the third tutorial, I noticed that a number of the instructions did not exactly line up with the website. I assume this is because the book was made in 2022 and the website has been updated since then. Because the website is similar enough to how it must have been when the book was published, I was still able to do these tutorials. This part of the book was really useful for getting some experience in using some of the apps ArcGIS has to offer.

I think that an interesting way of implementing what we learned in these chapters would be to make a map of forest density across the U.S.. The data could be displayed similar to how it was in the tutorial for the chapter 3 map, though in the case of the 3D map the entire region would need to be a raised data point as opposed to the skinny data ‘poles’ used to describe the buildings and their height.

Chapters 3 and 4 discuss the use of Web GIS for developing applications instead of just maps. One of the key ideas discussed in these chapters is that the map is just part of the whole application, and the application is what allows us to work with the data. Both chapters discuss the need for applications to be developed for specific purposes. In Chapter 3, ArcGIS Experience Builder is discussed as an application builder for the web. One of the key ideas discussed is that Experience Builder allows us to create applications by organizing different elements like maps, text, and tools in a specific way. This allows us to control the way users use the application. Another key idea discussed is the use of widgets. This is important because widgets provide tools like searching, filtering, and viewing the map. Another key idea discussed is the use of different screen sizes because users can use different types of devices like phones, tablets, or computers.

In Chapter 4, ArcGIS Web AppBuilder is discussed. This is another tool for building applications on the web. This tool is based on templates, which allows us to build applications quickly. This is important because we can build applications quickly by using the template. This tool is less flexible compared to Experience Builder, but it is easier to use. One of the key ideas discussed is the use of this tool for sharing the map with other people by adding tools for better interaction.

Another key concept in the two chapters is that web applications involve the integration of maps with tools that can be used by the users in the exploration of the data. The tools used will be determined by the purpose of the application. For example, the tools used in an application targeting the general public will be different from those used in an application used in the process of analysis.

An application idea based on the two chapters using my own data is the creation of a web application that can be used in the visualization of the patterns associated with sleep and the use of smartphones. The application can be created using the data obtained through the survey process. The users can be allowed to interact with the application by filtering the data based on different variables.

From the two chapters, I still have a few issues that I need clarification on. The first issue is the conditions under which it is best to use the Experience Builder instead of the Web AppBuilder. The two tools seem to be performing the same functions, although with different levels of flexibility. The two chapters have provided more understanding of the application of the Web GIS in the creation of applications that can be used in the exploration of the data in the best way possible.

One idea I have about the application of the concepts learned in Chapters 3 and 4 is the creation of a web application that will show the location of daycare centers in my area along with their ratings and capacity. I will be using the data I have about daycare centers in terms of their location, the number of children they can accommodate, and the ratings of their staff. I can create such an application using Experience Builder.