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.<\/p>\n
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.<\/p>\n
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.<\/p>\n","protected":false},"excerpt":{"rendered":"
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.<\/p>\n","protected":false},"author":2366,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-3082","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/posts\/3082","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\/2366"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/comments?post=3082"}],"version-history":[{"count":1,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/posts\/3082\/revisions"}],"predecessor-version":[{"id":3083,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/posts\/3082\/revisions\/3083"}],"wp:attachment":[{"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/media?parent=3082"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/categories?post=3082"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/tags?post=3082"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}