{"id":306,"date":"2023-04-02T10:18:45","date_gmt":"2023-04-02T15:18:45","guid":{"rendered":"https:\/\/sites.owu.edu\/geog-192\/?p=306"},"modified":"2023-04-02T10:36:07","modified_gmt":"2023-04-02T15:36:07","slug":"krygier-week-4","status":"publish","type":"post","link":"https:\/\/sites.owu.edu\/geog-292\/2023\/04\/02\/krygier-week-4\/","title":{"rendered":"Krygier – Week 4"},"content":{"rendered":"

\"\"<\/p>\n

Ah, two more delightful chapters in Getting to Know Web GIS.<\/p>\n

Chapter 3: ArcGIS Experience Builder<\/strong><\/h2>\n

Note the increasing functionality (increasing options, complexity, time it takes) as we move from StoryMaps to Instant Apps to Experience Builder (this chapter).<\/p>\n

Basics\u00a0<\/strong><\/p>\n

Using Experience Builder to Create Web Experiences<\/strong><\/p>\n

“Web experiences” (mleh)<\/p>\n

Workflow<\/strong><\/p>\n

\u2022 Premade template or from scratch
\n\u2022 Theme
\n\u2022 Source data
\n\u2022 Add and configure widgets
\n\u2022 Refine layouts
\n\u2022 Save, preview, publish, share<\/p>\n

Basic components<\/strong><\/p>\n

\u2022 at least one page, pages and windows are building blocks
\n\u2022 widgets added to pages and windows
\n\u2022 one theme per WE and each page can have a template
\n\u2022 pages have headers footers and body (this is like HTML)
\n\u2022 menu widget can be added to alow navigation between different pages
\n\u2022 windows only have body content
\n\u2022 each page or window has an outline view, showing all widgets<\/p>\n

Widgets<\/p>\n

\u2022 JavaScript and HTML components with specific functions
\n\u2022 basic widgets: app tools. Map, legend, layers, query, filter, edit, chart…
\n\u2022 layout widgets: containers helping to organize widgets. Section, row, column<\/p>\n

Settings for Widgets:
\n\u2022 content (data sources, links, etc,);
\n\u2022 style (size, position, color, etc.);
\n\u2022 actions
\n\u2022 message: listens to tiggers and automatically does something
\n\u2022 triggers
\n\u2022 targets
\n\u2022 actions
\n\u2022 data actions: click and do something (export data)<\/span><\/p>\n

Editions of Experience Builder (EB)<\/p>\n

Tutorial 3<\/strong><\/h2>\n

\u2022 pg. 86: after you add the “Views Navigation” widget, make sure it is not blocked by the white top of the image. It said “please add a section to use this widget”. I dragged the image down and the navigation widget worked<\/p>\n

\u2022 pg. 89: Preview button is at top, near left, a right pointing triangle in a circle.<\/p>\n

\u2022 pg. 92: If the Dynamic Content Pane menu is not showing up, move the text block a bit to the right and down.<\/p>\n

\u2022 pg. 102: for step 9: you have to include the HTTPS: https:\/\/bit.ly\/3pGylar<\/p>\n

\u2022 pg. 103: for step 17 “Regular tab” seems now to be “Default”<\/p>\n

Well, here it is. The end of chapter 3<\/p>\n

\"\"<\/p>\n

\n

Chapter 4: Mobile GIS<\/strong><\/h2>\n

Moblie GIS: Concepts & Advantages
\n\u2022 mobility (devices)
\n\u2022 locational awareness
\n\u2022 ease of data collection
\n\u2022 near real-time information
\n\u2022 large volume of users
\n\u2022 versatile communication options<\/p>\n

Requires mobile devices, OS, wireless communication, positioning tech<\/p>\n

Feature Layer Issues
\n\u2022 need to make feature layers open to editing, adding, removing data, attachments
\n\u2022 editor tracking
\n\u2022 full access to a subset of editors; fewer access options to public
\n\u2022 Feature Template: what can be done to a feature layer (data integrity & ease of editing)<\/p>\n

Mobile App Development Strategies
\n\u2022 browser-based
\n\u2022 native-based: via an app on a phone, tablet
\n\u2022 hybrid:<\/p>\n

API: Application Programming Interface<\/p>\n

ArcGIS native apps
\n\u2022 suite of native apps provided by ESRI<\/p>\n

\"\"<\/p>\n

ArcGIS Field Maps
\n\u2022 Fieldwork, project owner, dispatchers, mobile workers
\n\u2022 map-centric data capture<\/p>\n

ArcGIS Survey123
\n\u2022 ArcGIS QuickCapture:
\n\u2022 ArcGIS Indoors
\n\u2022 ArcGIS AppStudio<\/p>\n

Other stuff
\n\u2022 LBS, VGI, VR, AR<\/p>\n

Tutorial 4<\/h2>\n

4.1: Design a survey for ArcGIS Survey123<\/strong><\/p>\n\n\n\n
\"\"<\/td>\nhttps:\/\/arcg.is\/0nWrHe0<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

\"\"\u00a0The survey.<\/p>\n

\n

4.2 Survey123 to collect & review data<\/strong><\/p>\n

\"\"<\/p>\n

The survey after I added two incidents via my phone using Survey 123<\/p>\n

\n

4.3. Create an Editable Feature Layer with Domains<\/strong><\/p>\n

Step 4: it’s not Blank Layer<\/strong> but instead Define your own layer<\/p>\n

Step 13: “Typed text style” should (I think) be Incident Type<\/p>\n

Step 17: Change style icon is the tiny icon with the triangle\/circle\/square under the layer name<\/p>\n

\"\"<\/p>\n

\n

4.4 Configure a web map and a form with conditional visibility<\/strong><\/p>\n

Step 2: no Community Map base map. Choose a different one.<\/p>\n

Got stuck at step 13 (see below). It’s possible the “Conditional Visibility” option (which is not there) has been moved to the Logic tab, where you use Arcade to create the expression. Saved and shared. Skipping to next section for now.<\/p>\n

\"\"<\/p>\n

\n

4.5 Collect data using the ArcGIS Field maps mobile app<\/strong><\/p>\n

Just collecting data with FieldMaps app from phone<\/p>\n

\n

4.6 Create an ArcGIS QuickCapture Project<\/strong><\/p>\n

Step 7: the App Launcher is the 9 tiny boxes icon upper right corner. Quick Capture is under this menu.<\/p>\n

\"\"<\/p>\n

\n

4.7 Collect Data using QuickCapture<\/strong><\/p>\n

Just collecting data with Quickcapture app from phone<\/p>\n

\n

4.8. Prepare data for use with AuGeo<\/strong><\/p>\n

Some puttering with augmented reality<\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

Ah, two more delightful chapters in Getting to Know Web GIS. Chapter 3: ArcGIS Experience Builder Note the increasing functionality (increasing options, complexity, time it takes) as we move from StoryMaps to Instant Apps to Experience Builder (this chapter). Basics\u00a0 Using Experience Builder to Create Web Experiences “Web experiences” (mleh) Workflow \u2022 Premade template or from scratch \u2022 Theme \u2022 Source data \u2022 Add and configure widgets \u2022 Refine layouts \u2022 Save, preview, publish, share Basic components \u2022 at least one page, pages and windows are building blocks \u2022 widgets added to pages and windows \u2022 one theme per WE and each page can have a template \u2022 pages have headers footers and body (this is like HTML) \u2022 menu widget can be added to alow navigation between different pages \u2022 windows only have body content \u2022 each page or window has an outline view, showing all widgets Widgets \u2022 JavaScript and HTML components with specific functions \u2022 basic widgets: app tools. Map, legend, layers, query, filter, edit, chart… \u2022 layout widgets: containers helping to organize widgets. Section, row, column Settings for Widgets: \u2022 content (data sources, links, etc,); \u2022 style (size, position, color, etc.); \u2022 actions \u2022 message: listens to tiggers and automatically does something \u2022 triggers \u2022 targets \u2022 actions \u2022 data actions: click and do something (export data) Editions of Experience Builder (EB) Tutorial 3 \u2022 pg. 86: after you add the “Views Navigation” widget, make sure it is not blocked by the white top of the image. It said “please add a section to use this widget”. I dragged the image down and the navigation widget worked \u2022 pg. 89: Preview button is at top, near left, a right pointing triangle in a circle. \u2022 pg. 92: If the Dynamic Content Pane menu is not showing up, move the text block a bit to the right and down. \u2022 pg. 102: for step 9: you have to include the HTTPS: https:\/\/bit.ly\/3pGylar \u2022 pg. 103: for step 17 “Regular tab” seems now to be “Default” Well, here it is. The end of chapter 3 Chapter 4: Mobile GIS Moblie GIS: Concepts & Advantages \u2022 mobility (devices) \u2022 locational awareness \u2022 ease of data collection \u2022 near real-time information \u2022 large volume of users \u2022 versatile communication options Requires mobile devices, OS, wireless communication, positioning tech Feature Layer Issues \u2022 need to make feature layers open to editing, adding, removing data, attachments \u2022 editor tracking \u2022 full access to a subset of editors; fewer access options to public \u2022 Feature Template: what can be done to a feature layer (data integrity & ease of editing) Mobile App Development Strategies \u2022 browser-based \u2022 native-based: via an app on a phone, tablet \u2022 hybrid: API: Application Programming Interface ArcGIS native apps \u2022 suite of native apps provided by ESRI ArcGIS Field Maps \u2022 Fieldwork, project owner, dispatchers, mobile workers \u2022 map-centric data capture ArcGIS Survey123 \u2022 ArcGIS QuickCapture: \u2022 ArcGIS Indoors \u2022 ArcGIS AppStudio Other stuff \u2022 LBS, VGI, VR, AR Tutorial 4 4.1: Design a survey for ArcGIS Survey123 https:\/\/arcg.is\/0nWrHe0 \u00a0The survey. 4.2 Survey123 to collect & review data The survey after I added two incidents via my phone using Survey 123 4.3. Create an Editable Feature Layer with Domains Step 4: it’s not Blank Layer but instead Define your own layer Step 13: “Typed text style” should (I think) be Incident Type Step 17: Change style icon is the tiny icon with the triangle\/circle\/square under the layer name 4.4 Configure a web map and a form with conditional visibility Step 2: no Community Map base map. Choose a different one. Got stuck at step 13 (see below). It’s possible the “Conditional Visibility” option (which is not there) has been moved to the Logic tab, where you use Arcade to create the expression. Saved and shared. Skipping to next section for now. 4.5 Collect data using the ArcGIS Field maps mobile app Just collecting data with FieldMaps app from phone 4.6 Create an ArcGIS QuickCapture Project Step 7: the App Launcher is the 9 tiny boxes icon upper right corner. Quick Capture is under this menu. 4.7 Collect Data using QuickCapture Just collecting data with Quickcapture app from phone 4.8. Prepare data for use with AuGeo Some puttering with augmented reality                              <\/p>\n","protected":false},"author":138,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[3],"tags":[],"class_list":["post-306","post","type-post","status-publish","format-standard","hentry","category-course-student-work"],"_links":{"self":[{"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/posts\/306","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\/138"}],"replies":[{"embeddable":true,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/comments?post=306"}],"version-history":[{"count":10,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/posts\/306\/revisions"}],"predecessor-version":[{"id":333,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/posts\/306\/revisions\/333"}],"wp:attachment":[{"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/media?parent=306"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/categories?post=306"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sites.owu.edu\/geog-292\/wp-json\/wp\/v2\/tags?post=306"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}