Category: Uncategorized

Chapter 3: 

In the very beginning, the chapter starts off with information and details about the experience builder app, which is what we would be using for pretty much the rest of the chapter. I thought it was interesting because it talked about it as if it were the “end all be all” of webGIS. I think it was somewhat of an understandable explanation because it has overall been pretty easy to use, quite similar to ArcGIS Pro, but quite a bit easier to use. Throughout the beginning of this chapter, it reminded me quite a lot of working with Adobe, which is a system that I always struggled to use, but with the detailed tutorials for this section, it wasn’t too hard to work through. I did have a slight hiccup at the beginning while trying to add the data for the map. I think GIS has definitely continued to be very tedious, and as I add in both the maps for the beginning sections of chapter 3, it was not a very complicated process, but I did accidentally skip over the parts where I needed to actually select the maps, which made it a little confusing, but I eventually figured it out.

Chapter 4: 

Throughout the beginning of the chapter, it talks a lot about the advantages of mobile GIS and the avenues that allow for the system to be used and curated in such a way. It mentions how beneficial it is, including how a wider range of people are able to use it, also with the wide range of technologies curated for it as well, mentioning the several apps and systems that were created to support it. On the other hand, it does mention how this creates some technological limitations for the systems as well. In my experience in this course, having a web GIS system has definitely made it quite a lot easier to do the work in this course. 

It was also really interesting to learn about the mobile aspects of field work and GIS, which I thought was just fun to learn about since I hope to do field work in the future. It was also interesting learning about Survey123 because I hadn’t really expected there to be a surveying component of GIS, although it makes sense. Also, the differences between web design and Connect that allow for different levels of complexity for the surveys themselves. Tutorials: I was a little confused working on the tutorials for this chapter, especially during 4.3, because the instructions were a little different from what they actually looked like, so I was kind of just clicking around trying to find different stuff in the instructions. 

Ideas: 

An idea I have, using mainly chapter 3, would be to use the mapping style to track rising water altitudes to also watch the impacts they have on communities, agriculture, etc., in the areas close to such.  

Chapter three talks about the Experience Builder app. This app can work with 2D and 3D data, has a lot of pre-made widgets, and is very customizable. To make a web experience, you pick a template and theme, add data, add and customize widgets, and then share it. A web experience has a single theme, and each page has a template. A window can be added to a page, and it only has body content. A widget is a JavaScript or HTML component that executes specific functions. Basic widgets perform as app tools such as map, query, and survey. A layout widget helps organize widgets such as sections, rows, and a sidebar. A widget can perform message or data actions. A message action performs actions automatically when triggered, while data actions require users to click and select an action to perform. A message action has a trigger, a target, and an action. The tutorial for this chapter took me much longer to complete. There were a lot more discrepancies in the textbook versus the actual interface. I had an especially hard time figuring out the triggers, but I eventually did. Besides the setbacks, I had a fun time creating a web experience.

Chapter 4 talks about mobile GIS, how to build mobile apps, and use Survey123. Phones do not need wires and can be used anywhere. Feature layers are read-only on Mobile GIS. To be able to edit them, you have to enable editing on the feature layers. You can make a view layer from a hosted feature layer, which allows you to have specific people able to edit, so the public sees any edits immediately. A feature layer can contain a feature template, which makes editing easier and ensures data integrity. You can have preset symbols, data, and default attribute values, which help make sure that no invalid values are entered. Mobile app development includes a browser-based approach, a native-based approach, and a hybrid-based approach. A browser-based approach uses HTML, Java, and CSS. This costs less but has a limited number of features. A native-based approach requires development skills. They are more expensive, cannot run on multiple platforms, but have deep-level access to the hardware of the device. A hybrid-based approach combines browser-based and native-based. Field maps capture locations. Track viewer allows administrators to manage the security of those locations. Survey123 provides two ways to design forms: Survey123 Web Designer and Survey123 Connect. The web designer is easier to use, but connect supports more advanced questions. LBS provides information or entertainment. VGI is spatial data produced by citizens rather than data producers. VR is a computer-generated simulation of a 3D map that can be interacted with. AR overlays computer-generated information on the live view. I had a lot of trouble with tutorial 4.4.

Idea: I could use chapters 3 and 4 to create a survey for people hiking in Colorado to report Mountain Pine Beetles. Chapter 4 can be used to create the survey and map with POIs, and chapter 3 can be used to make an infographic about Mountain Pine Beetles and include maps of where they are located.

Chapter 3

This chapter focuses on Web AppBuilder for ArcGIS, one of the most user-friendly tools that allows individuals to create interactive web applications without coding. Instead, Web AppBuilder uses a visual, real-time editing interface with many premade widgets. It further explains how users can build apps by selecting a theme, adding a web map, and configuring various widgets that provide functionality such as navigation, data visualization, filtering, and analysis. Through this system, it is the most flexible and configurable of all the other apps. Regarding widgets, the chapter highlights the importance of them and distinguishes between those that require data and those that do not. The tutorial at the end shows you how to create a web app displaying data on hurricanes and earthquakes. Also included were quick mini-tutorials on how to configure various widgets, like data-independent widgets, chart-type widgets, and filter-type widgets. I liked exploring all the different widget options and drawing graphics with different pre-made symbols.

Chapter 4

Similar to the previous chapter, this one focuses on another app- this time Mobile GIS. This chapter explains how necessary it is to have mobile geographic information system functions in a world that is very smartphone-heavy. After an introduction of the main mobile concepts, the chapter discusses three approaches to building mobile apps. I noticed that this organizational approach was similar to chapter 2’s process of making a configurable app in that it was another three-step process. I guess processes come in threes! There are browser-based, native-based (downloadable and installed), and hybrid-based (combination of browser and native) approaches to developing a mobile app. There are a handful of Esri mobile apps and their different purposes are described. The tutorial also relates to these apps, particularly Collector, Survey123, and ArcGIS.

Potential Future Applications

Sticking to last week’s bird theme, I could create a web app to display bird migration tracking data. This is especially important right now, as birds are beginning to migrate north for the breeding season. Using Web AppBuilder from Chapter 3, I could create an interactive web app that displays bird sightings on a 2D or 3D map allowing users to see where different species have been observed. The app could include widgets like filters to sort by bird species, date, or location, and chart tools to show trends in sightings over time. Using chapter 4 concepts, I could make this app compatible in a mobile setting. It would be much more convenient to be able to observe bird activity from your phone when you’re outdoors. This would probably use the location-based services (LBS) and volunteered geographic information (VGI). It might be best to use a hybrid-based approach to build the mobile app for easier access via download or browser. I’d need to look further into it.

In chapter 3 I used web maps building and adding layers and just learned how to use them overall. It was cool to play around with this and add themes and stuff. I found where I could add data and themes from the organization and had tons of options made by other OWU students. I thought some of the visuals you could create and add were very cool too. The work for this chapter was fairly easy to follow along with and could get around and simple problems.

Chapter 4 was more covering making web apps. Like the past chapters there was a lot of playing around and trying different things to see what they do. It taught how to use widgets like search and legend which was cool to see. I thought it was interesting there was a part where you would use your mobile app. Overall, I learned a little how to publish and configure web applications while adjusting them to what I need. 

An application that could be used through these 2 chapters is mapping fish habitat. You could chart their spawning grounds or nursing habitats. You could separate these using lake depths or places the fish prefer. Other applications in fishing might be to map environmental conditions, fish pressure tracking, angler report apps, or surveys like fish or bait stockings. There are a lot of different possibilities in fishing to use stuff learned in these chapters.

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.