Walz – Week 3

Aiden Walz – Week 3

Chapter 3:

Chapter 3 went over the ArcGIS experience builder and how it’s a hodgepodge of multiple features and apps together that the user can customize to include more functionality than any individual ArcGIS instant app.

• Able to create 2D and 3D web apps for multiple devices
• Includes multiple widgets for different functions and allows for customization
• Has flexible layouts to build maps that are map/non-map centered and can be viewed as multiple or single pages
• Can select a premade template  or start from scratch
• Allows ability to select a theme and add source data 
• Basic widgets include things like map, legend, layers and more
• Layout widgets include things like section, column, row and more
• Widget settings include; content, style, action
• Content defines the data sources
• Style defines the how it appears basically
• Action defines how widgets interact with one another
• Experience builder has three editions: One in ArcGIS Online, one in portal for ArcGIS, one  in developer edition
• Portal and developer allow for customization of widgets, online doesn’t 
• Tutorial 3 went over developing a public web experience to view data about historical earthquakes and hurricanes
• Web app was able to display the earthquake data as a 2D and 3D map using map widgets
• I personally think the 2D map looked better visually than the 3D
• I added a text widget to the Data summary view to show some basic information about the earthquakes and hurricanes layer
• Then I used a table widget to display attributes of the earthquakes
• Overall a I used a lot of different widgets to visualize or showcase information about the data source

 

Chapter 4:

Chapter 4 went over the mobile GIS part of ArcGIS online as mobile devices are one of the most common tools people have to view data

• Choosing mobile app strategy depends on your approach: Browser vs native vs hybrid
• Browser approaches looks at user using apps thru mobile web browsers
• Native requires some of type of IOS to develop the app, and hybrid is a both browser and native 
• Mobile GIS related to many other types of apps and frontiers: LBS, VGI, VR, AR
• LBS (Location based service): Provide info based on user location
• VGI (Volunteered Geographic Information): Things like Waze
• VR (Virtual reality), & AR (Augmented reality)
• ArcGIS Mobile Apps: Collector: Field data collection using GPS/maps, Survey123: Form-based surveys, Workforce: Assigns and tracks field tasks, Explorer & Navigator: Map viewing and navigation, AppStudio: Builds cross-platform native apps without coding
• Tutorial 4 went over these topics and items: Designing a smart form on Survery123 and collecting Survery123 mobile app. Then using ArcGIS Quick Capture I made an editable layer  and configured a web map to view things like street cracks (wasn’t entirely sure at what the data was). And then lastly I prepared data to use for AuGeo, basically ArcGIS in AR, it was a bit weird using the camera to view things but I could easily see why this would be useful for visualizing things

 

For an application idea for chapter 4 I could make a mobile app about local tree health in a certain area.  I could use Survey123 and have users record location, species and condition of trees in a certain area directly from their mobile devices. The app would allow them to attaches photos and note any signs of damage or possibly disease if I want the app to focus on that approach, and then submit them in real time. This app could help city staff and groups track the health of a tree population and visualize patterns on a web map.

 

I think the app I will make for my final from chapter 1-4 will be a ArcGIS story map over local art museums in Columbus, Ohio. Would allow tourists or residents to look at where these art museums are, along with have a photo of what they look like and a description of what these museums hold.