Setup Guide for Op Tracker

Transcription

1 Setup Guide for Op Tracker

2 Contents 1 Welcome to Op Tracker Data Overview Block Boundary Feature Layer Block Tracking Feature Layer Ancillary Data Feature Layer Block Tile Packages Creating the Feature Layers Creating the Block Boundary Feature Layer Creating the Block Tracking Feature Layer Creating a New Harvest Block Adding the Harvest Block Boundary Polygon Manual Feature Addition using ArcGIS Online Manual Feature Addition using ArcMap or ArcGIS Pro Automated Feature Addition through Scripting Update Harvest Block Attributes Update Harvest Block ServiceURL Add Ancillary Data Layers Creating Block Tile Packages Identify Supported Layers Create Tile Package Upload Tile Package to Op Tracker Device ios Loading Tile Packages using itunes Android Loading Tile Packages using a File Explorer Setup Op Tracker Application Guide Version: July 21,

3 1 Welcome to Op Tracker Welcome to the Op Tracker setup documentation! This guide will walk you through the steps required to get your application up and running. The Op Tracker app requires the following items: An ArcGIS Online Organizational Account for each Op Tracker unit A valid license for Op Tracker purchased (or trialed) through ArcGIS Marketplace Op Tracker installed on a valid ios, Android or Windows device. 2

4 2 Data Overview Op Tracker is powered by feature layers stored in ArcGIS Online. These feature layers inform the application about which harvest blocks are available for tracking, provide a location to store tracking data, and make ancillary data available for offline display. The feature layers used in Op Tracker are: 2.1 Block Boundary Feature Layer A polygon feature Layer where each polygon feature is a harvest block available for tracking. Each polygon feature powers the Op Tracker Alerting System to warn the user when they are approaching or have left the harvest area boundary. A single Block Boundary Feature Layer is required for Op Tracker to function. 2.2 Block Tracking Feature Layer A point feature layer where each point feature is a tracking location for a specific user. All Op Tracker users who are tracking in the same harvest block will show up in this single feature layer. Each feature in the Block Boundary Feature Layer (above) is required to have a corresponding Block Tracking Feature Layer. 2.3 Ancillary Data Feature Layer One or more feature layer representing the ancillary data (roads, lakes, streams, etc.) that should be displayed in the application. These layers will always be displayed in the application, and will be available even when the application is offline. Op Tracker will display these layers using the symbology defined in the feature layer. Use of Ancillary Data Feature Layers is optional in Op Tracker. Op Tracker can also use tile packages to display imagery and raster data in the application: 2.4 Block Tile Packages An offline-ready cache of imagery or raster data that will be visible as the basemap of Op Tracker. One tile package must be created for each imagery type and for each block. To reduce bandwidth usage, tile packages are loaded onto the device using a wired connection and file transfer. Tile packages can be prepared using ArcMap 10.1 and above. Use of tile packages is optional in Op Tracker. 3

5 3 Creating the Feature Layers Op Tracker requires that a Block Boundary Feature Layer be set up before the application can be used. Once the Block Boundary Feature Layer is created, each block within it must also have a Block Tracking Feature Layer defined. Follow these steps to create these layers. 3.1 Creating the Block Boundary Feature Layer The easiest way to create the Block Boundary Feature Layer is to base it on the Lim Geomatics public example. To do this: 1. Login to ArcGIS Online, open the My Content tab, click Create, and select Feature Layer from the menu. FIGURE 1. CREATE A NEW FEATURE LAYER. 2. In the New Hosted Feature Layer window, select the From URL tab. Enter the following Lim Geomatics Public Block Boundary Feature Layer example URL and click Next Ensure Op_Tracker_Sample_Block_Boundary layer is selected, rename if desired, and click Next. (Note: Capture GPS receiver information should not be selected) 4. Pan and Zoom the map to an area that will encompass all harvest blocks and click Next. 5. Enter a title for this feature layer. Op_Tracker_Block_Boundary (or similar) is suggested. 4

6 6. Enter the tag Op Tracker Block Boundary. This Op Tracker Block Boundary tag is required for the application to identify the Block Boundary Feature Layer. FIGURE 2. ENTER A TITLE AND THE TAG "OP TRACKER BLOCK BOUNDARY". 7. Enter a summary, select a folder to save the feature layer to, and click Done. 8. Once the feature layer is created and the overview page is displayed, ensure that Attachments are enabled by locating the Disabled Attachments button (shown in Figure 3 below). If this button shows Enabled Attachments then click the button to enable attachments. FIGURE 3. THE DISABLE ATTACHMENTS BUTTON INDICATES ATTACHMENTS ARE ENABLED FOR THIS FEATURE LAYER. 5

7 9. The feature layer needs to be shared with the appropriate users before they can use it in Op Tracker. If all AGOL users who purchased a license for Op Tracker are part of your AGOL Organization, this feature layer only needs to be shared with your organization. a. To share a layer with your organization, click the Share button from the feature layer overview page. Check the [Your Organization Name] button and click OK. FIGURE 4. SHARING A FEATURE LAYER WITH YOUR ORGANIZATION. If any AGOL users who purchased a license for Op Tracker are outside of your AGOL Organization, then this feature layer needs to be shared using a Group. A group must be created, all external AGOL users must join that group, and this feature layer needs to be shared with that group. b. To share a layer with a group, click the Share button from the feature layer overview page. Check the appropriate group name and click OK. FIGURE 5. SHARING A FEATURE LAYER WITH A GROUP. 6

8 10. The feature layer also needs to be configured as editable. To set the editing properties of the feature, click the Settings tab in the feature layer overview page. Ensure that Enable editing and Enable Sync (disconnected editing with synchronization) are checked, and that What kind of editing is allowed? has Add, update, and delete features selected. FIGURE 6. ENABLING EDITING AND DELETE PROTECTION. 11. While in this settings screen, it is suggested that Delete Protection be enabled as well. 12. The layer is now set up and ready for harvest block features to be added to it. 7

9 3.2 Creating the Block Tracking Feature Layer A Block Tracking Feature Layer needs to be created for every harvest block that Op Tracker will be tracking in (the entire harvest block creation process is outlined in the Creating A Harvest Block section of this guide). Each Block Tracking Feature Layer should be created in the exact same manner as the Block Boundary Feature Layer. Follow all the steps outlined for Creating the Block Boundary Feature Layer, but with the following changes: 1. In the New Hosted Feature Layer window, use the following Lim Geomatics Public Block Tracking Feature Layer example URL instead of the Block Boundary URL: 2. Enter a title for this feature layer. ot_blockid_tracking (or similar) is suggested. 3. Do not include the Op Tracker Block Boundary tag with this feature layer. FIGURE 7. TITLE, TAGS AND SUMMARY FOR A BLOCK TRACKING FEATURE LAYER 8

10 4 Creating a New Harvest Block Preparing a new harvest block for use in Op Tracker requires a GIS manager to create a polygon feature in the Block Boundary Feature Layer. This involves: 1. Adding the harvest block boundary as the polygon feature 2. Updating the feature s attributes 3. Creating and defining the Block Tracking Feature Layer and ServiceURL 4. (optional) Updating the Base Layer information Please note that each harvest block should be represented by a single, multipart polygon feature. 4.1 Adding the Harvest Block Boundary Polygon There are multiple methods for adding the harvest block polygon to the Block Boundary Feature Layer. While each of these methods are valid, the latter methods are more complex but also more powerful Manual Feature Addition using ArcGIS Online The easiest way to add new features to an ArcGIS Online feature layer is to use the Edit functionality in the online map viewer. While this method provides very simple tools for vertex based polygon creation (and vertex based editing), it may not provide the robust precision required for accurate block boundaries. This option is recommended for testing or very simple shape edits only. FIGURE 8. MANUAL FEATURE ADDITION USING ARCGIS ONLINE Manual Feature Addition using ArcMap or ArcGIS Pro The ideal method for manually adding features is to edit the feature layer in ArcMap or ArcGIS Pro. These programs allow a user to access the full suite of robust editing tools to create and modify harvest block polygons. In particular, copying and pasting features from a source dataset (a shapefile, geodatabase feature class, or another feature layer) into the Block Boundary Feature Layer while in an edit session is a quick way to manually migrate complex geometries. 9

11 This option is recommended for most manual feature additions or edits, and for any cases that cannot be scripted. *Note: Editing a feature service from ArcMap requires a Standard or Advanced license. FIGURE 9. MANUAL FEATURE ADDITION USING ARCMAP Automated Feature Addition through Scripting The most complex yet powerful way to add new features to a feature layer is to create a Python script to automate the process. This would be ideal for looping through a large dataset of features for addition or for creating a small parameterized script tool. While scripting provides the most flexibility and power for automating the feature addition process, it also requires some knowledge of Python, Feature Layer Rest Endpoints, and scripting in general. This option is recommended for users who have experience with Python scripting and would benefit from an automated solution. The high-level steps to automate adding a dataset to a feature layer are as follows: 1. Use ArcPy or the ArcGIS API for Python library to read an input shapefile/file geodatabase/feature and return a geometry for each feature. 2. Parse the geometry (or geometries) into JSON 3. Use urllib or urllib2 library get an AGOL access token and make a REST endpoint call to the feature layer s applyedits end point. See this for a simple example. 10

12 4.2 Update Harvest Block Attributes The Block Boundary Feature Layer provides a set of fields to define each Harvest Block feature, some of which are required for Op Tracker to function. Editing feature attributes can be done in ArcGIS Online, ArcMap, ArcGIS Pro, or using Python scripting. After a harvest block polygon feature has been added to the Block Boundary Feature Layer, please update the feature attributes as follows: Name Status Description Block_ID Required The name of the harvest block. This name may be alphanumeric but cannot contain any special characters or spaces. This attribute should be used when naming any corresponding tile packages. Forest Required The name of the forest which this harvest block is in. OTName Optional Alternate to Block ID (not currently displayed). Company Required Company in charge of this block. This name may be alphanumeric but cannot contain any special characters or spaces. This attribute should be used when naming any corresponding tile packages. Status Required The status of the harvest block. Only blocks marked with Ready will be available on Op Tracker devices. All other blocks should be marked Pending PercentComplete Required Used by Op Tracker Web Application to calculate harvest percentage complete. It must be given an initial value of 0 RequestedBy Optional The name of the individual who requested the harvest block to be prepared. ServiceURL Required The URL of the Block Track Feature Layer created for this harvest block. Please note this must start with See below for more explanation. BlockPreparedDate Required The date the block was prepared on. GlobalID (Do not use) Unique database identified used in Op Tracker. Shape_Area Optional The area of the block calculated by the layer service. This may or may not be used depending on how the layer was created. Shape_Length Optional The length of the block perimeter calculated by the layer service. This may or may not be used depending on how the layer was created. TABLE 1. BLOCK BOUNDARY FEATURE LAYER ATTRIBUTES. 4.3 Update Harvest Block ServiceURL Each new harvest block feature must have a Block Tracking Feature Layer created for it (see 3.2 Creating the Block Tracking Feature Layer for instructions on how to do this). Once this feature layer is created, the associated harvest block feature must have its ServiceURL attribute set to the URL of this Block Tracking Feature Layer. To do this: 11

13 1. Open the Block Tracking Feature Layer overview page in ArcGIS Online 2. Click the Service URL button to open the service URL FIGURE 9. OPENING THE SERVICE URL FOR A BLOCK TRACKING FEATURE LAYER. 3. Copy the URL from the browser address bar a. Note: all text after /FeatureServer/0 should be removed from the URL b. Ensure that the URL starts with ends in /FeatureServer/# and that the feature layer is appropriately shared with all AGOL users who will use Op Tracker. 4. Paste the URL into the ServiceURL field for the new harvest block feature a. Note: The URL should end with /FeatureServer/0 and have a similar format to the Lim Geomatics examples provided in section 3.2 Please view the Lim Geomatics Public Block Boundary Feature Service for an example: Add Ancillary Data Layers All harvest blocks in Op Tracker can be configured to display additional feature layers such as roads, lakes, streams, areas of concern, etc. These layers will be available offline in the application and will be displayed in the exact symbology defined in the feature layer itself. Configuring these ancillary layers is as simple as adding an attachment to each harvest block feature in the Block Boundary Feature Layer. Adding Ancillary Data Layers is optional and Op Tracker will function without these services. Attachments can be added to features in ArcMap, ArcGIS Pro, or through Python scripting. However, we will cover adding attachments using ArcGIS Online. 12

14 1. Create a BaseLayerURLs.xml file with all of the ancillary feature layers that will be displayed in Op Tracker: a. Open a text editor and create an XML file by copying the sample below: <LayerCollection> <Layer ID="Proposed Roads"> <Layer ID="Lakes"> <Layer ID="Streams"> </LayerCollection> b. Update the ID to a unique layer name and the Feature Layer Service URL to point to the feature layers you wish to display in Op Tracker. Ensure that these URLs start with https, end in /FeatureServer/#, and that these feature layers are appropriately shared with all AGOL users who will use Op Tracker. c. If you would like to add more ancillary data layers, copy one of the existing <Layer> lines and modify as needed. d. The last defined layer is the top most in the layer order. In the example above, Lakes will be on top of Proposed Roads, and Streams will be on top of Lakes. e. Save the file locally as BaseLayerURLs.xml. 2. From the Block Boundary Feature Layer overview page, open the Data tab. Find the feature you would like to configure Ancillary Data Layers for and scroll the table to the right until the Photos and Files column is visible and click Add. FIGURE 10. ADDING A FILE ATTACHMENT TO A FEATURE IN ARCGIS ONLINE. 13

15 3. In the Photos and Files window, click Choose File. Select the BaseLayerURLs.xml file previously created and click Upload. FIGURE 11. CHOOSE THE BASELAYERURLS.XML FILE. 4. Once the file has been added, press Close. These ancillary layers will be available for use in Op Tracker. 14

16 5 Creating Block Tile Packages Op Tracker uses tile packages to display imagery and raster data in an offline environment. Tile packages are optional for use in Op Tracker, but True Color Imagery, a LiDAR derived Hillshade, or a DBH map powered from AFRIDS LiDAR surfaces can provide greatly increased situational awareness for the operator. If you would like to include tile packages for offline imagery and raster display, please follow these steps: 5.1 Identify Supported Layers Each harvest block in Op Tracker supports the following tile package imagery types: Type ID Description RGB Imagery rgb Imagery in Red/Green/Blue band combination. Near Infrared nir Imagery in Near Infrared band combination. False Color fc Imagery in False Color band combination. True Color tc Imagery in True Color band combination. Hillshade hs A hillshade layer from any source. Top Height topht An AFRIDS LiDAR derived top height surface. Gross gmv An AFRIDS LiDAR derived gross merchantable volume surface. Merchantable Volume Quad Mean DBH qmdbh An AFRIDS LIDAR derived quad mean DBH surface. DBH dbh An AFRIDS LiDAR derived DBH surface. Basal Area ba An AFRIDS LiDAR derived basal area surface. Canopy Height chm An AFRIDS LiDAR derived canopy height model surface. Model SGM Canopy Height Model sgmchm An AFRIDS imagery derived semiglobal matching canopy height model surface. TABLE 2. SUPPORTED OP TRACKER TILE PACKAGE TYPES. If one (or more) of these imagery/raster surfaces are available for a new harvest block feature, a tile package can be created and displayed in Op Tracker for that feature. 5.2 Create Tile Package Tile packages can be created using ArcMap 10.1 (and above). 1. Follow ESRI s guidelines to create a tile package for each available supported layer for the block. Normally this tile package should only contain the single imagery/raster as defined above, as the block boundary and ancillary layers will be displayed using feature layers defined previously in this setup guide. 15

17 Clipping imagery can reduce the size of a tile package. It is recommended to clip any imagery or rasters to a 300m buffer of the harvest block boundary, as this matches the default boundary buffer setting in Op Tracker and provides a little external context for the operator. Note: Tile packages can become very large in size if a large extent and high level of zoom is required. While Op Tracker can display tile packages of any size, be aware of device storage, creation time, and file transfer limitations. 2. Op Tracker uses a specific naming convention to identify and display tile packages in the application. When saving a tile package, please use the following naming convention: op_tracker_company_blockid_imagerytypeid.tpk where company and blockid are defined in the corresponding feature attributes of the Block Boundary Feature Service, and imagerytypeid matches one of the supported imagery IDs outlined above. An example would be: op_tracker_limgeomatics_block123_topht.tpk 5.3 Upload Tile Package to Op Tracker Device Tile packages can have a large file size, therefore a wired connection and file transfer is used to upload the files onto the Op Tracker device. Please follow the device specific steps below to load tile packages into Op Tracker: Note: Tile Package loading is currently unavailable on Windows devices. This functionality will be available in a future version of Op Tracker ios Loading Tile Packages using itunes Tile packages can be loaded onto ios devices using itunes: 1. Prepare all tile packages for a harvest block as outlined above. 2. Plug your device into your computer. 3. Open itunes, select your device, and click the Apps tab. 4. Scroll to the bottom of the window and choose Op Tracker in the File Sharing section. 5. Drag the tile packages into the Op Tracker Documents section. 6. Click Sync to copy the tile package to your device. 7. Restart Op Tracker on your device. 8. The associated tile packages will be available when that block is opened in Op Tracker. 16

18 5.3.2 Android Loading Tile Packages using a File Explorer Tile packages can be loaded onto Android devices using a normal file explorer: 1. Prepare all tile packages for a harvest block as outlined above. 2. Plug your device into your computer. 3. Using a file explorer on your computer, browse to ExternalStorage/Op Tracker folder on your device. 4. Copy the tile packages to the Op Tracker folder. 5. Restart Op Tracker on your device. 6. The associated tile packages will be available when that block is opened in Op Tracker. 17

19 6 Setup Op Tracker Application Once the Block Boundary Feature Layer is created and populated with a few harvest block features (with corresponding Block Tracking Feature Layers created and referenced as well), the Op Tracker application can be fully configured. 1. Open the Op Tracker application on your device and ensure you are connected to the internet. If this is the first time using the application, you will be prompted to login. FIGURE 11. SETTING UP OP TRACKER FOR THE FIRST TIME. 2. You will be prompted to sign in with your ArcGIS Online account information. Please enter your information and press Sign In. FIGURE 12. SIGN IN TO ARCGIS ONLINE. 18

20 3. Next you will need to enter some information: Company Name The company that will be using Op Tracker. This should be the same as the company defined in the harvest block attributes and all tile packages. User Name A custom user name for identifying a user s tracks in the Block Tracking Feature Layer. Note: this does not need to be the same as the AGOL account user name. Block Boundary Service Select the Block Boundary Feature Layer configured in 3.1 Creating the Block Boundary Feature Layer. 4. Once this data has been entered click OK. FIGURE 13. SETTING UP OP TRACKER FOR THE FIRST TIME. 19

21 5. Next you will be brought to the Add Block screen. The list of blocks in this screen will correspond to all harvest block features that were prepares as Ready in section 4 Creating a New Harvest Block. Select a block and press Add Block. FIGURE 14. ADD A BLOCK TO OP TRACKER. 6. Once the block is added, press the Back button in the top right. Op Tracker is now ready for use. 20

22 For questions, comments and technical support, Contact Lim Geomatics Inc. 343 Preston Street, 11th Floor Ottawa, Ontario, Canada K1S 1N4 21 Phone: Local: Fax: