Latest Contributions by SarahOstertag

@IsmaelChivite any updates on this? I have the same issue/question as the users above. With Microsoft Forms and Google Forms, even for surveys set to allow "Anyone can edit" i.e., submit responses, the only way to find and access such forms is with a direct link to the survey. So essentially, these public forms cannot be found through internet search engine results, thereby only individuals who have been provided the link can submit responses. I wish Survey123 had a check-box in the form settings Collaborate tab to allow a Creator to specify "Prevent Survey123 Form from being Web Searchable" or similar. My use case is similar to Brandon's; we have a client that needs ~500 of their employees (outside of my organization) to have access to 1 survey form, with no other GIS privileges. However, the only option currently is either to 1) host the survey publicly, which the client will not allow due to potential for bad actors to access the survey form and submit responses through search engines or 2) create an AEC site with fieldworker licenses for all 500 employees, which would cost ~$200K and is therefore not viable (and is also way more functionality for the users than they need). There is a difference in making the data collected from a public survey private and the ability to limit who can respond to a public survey (i.e., ideally by requiring a direct link to the survey form). ... View more

Hi Carla,  I built a model builder (you could also do this in ArcPy) to clean up the raster data. I've tried to outline the steps below. Iterator: for XYZ.tif in folder (in my case, I made 1 folder with my GeoTIFF rasters, and there were 38 rasters spanning the study period inside of this folder).  If you set this up in Model Builder or ArcPy, you can then run this same process on each of your rasters (screenshot of model attached): Build Raster Attribute Table Add FILENAME Field (field_name="FILENAME", field_type="TEXT", field_alias="FILENAME") Calculate FILENAME field (Calculate Field): expression FILENAME: "%Name%" Add Year STR Field (Add Field): field_name="Year_STR", field_type="TEXT", field_alias="Year_STR" Calculate Year (Calculate Field): field="Year_STR", expression YEAR_STR = !FILENAME![-4:] Add Year Date Field (Add Field): field_name="Year", field_type="DATE", field_alias="Year") Calculate Field (Calculate Field): field="Year", expression Year = datetime.datetime.strptime(!Year_STR!, '%Y')")   You might need to adjust the python scripts in the Calculate Field steps to match your input raster naming conventions. Then you can create and add these rasters to a mosaic dataset and go from there. Good luck! ... View more

Great idea! Could see a variety of uses for this new tool if it gets implemented. ... View more

Hi all - I have been working through a very similar issue and may have found a possible solution. I am trying to work with 37 years worth of annualized burn mosaics (Monitoring Trends in Burn Severity or MTBS), which are served as GeoTIFF thematic rasters (i.e., single-band rasters with a colormap defined, instead of RBG or other band combo, 8-bit unsigned integer data). I first used model builder to run a raster iterator through my folder of TIFFs to build raster attribute tables and add fields including the acquisition year (extracted from my filenames), since I need this as the time dimension later. I also converted the colormap that was pre-assigned to my data to values in my attribute table so I could de-code my Raster pixel values. Then I ran the Create Mosaic Dataset tool with a Custom Product Definition and set it to 1 band, since the "None" option defaults to multi-band. This setting allowed my output mosaic dataset to have only 1 band as required due to the input rasters having a colormap present. After adding my rasters to the mosaic dataset, I edited the raster attribute table (attached to Footprint) to add a year field and the calculate the "ProductName" column value as "burn severity" (e.g., the appropriate variable name that corresponds to the raster pixel values in my data). This is equivalent to the "Surface Reflectance" variable field  in the video above. I was then able to run the Build Multidimensional Info tool and set Variable as ProductName, which now had "burn severity" as a drop down option, and used my calculated Year field as the Dimension (time). I also went into the mosaic raster Properties from the Catalog and changed the default to enable Time with my new Year field. Doing all of these steps enabled me to use multidimensional tools on my custom mosaic dataset of images from a non-standard source. I sure hope this helps since it took a lot of trial and error! 🙂 ... View more

Thanks James! Moving the conditional statements to the preceding line and their closing placeholders (${/}) to the end of the condition line (instead of having this on its own line) worked. Repeating this action by placing subsequent conditional statements immediately after the ${/} on the same line was the trick. Below are some snips so others can see an example of the solution. I failed to mention that my template uses tables to maintain consistent formatting - the solution below is within the same cell of the table. Template: Report: ... View more

I think I am having similar issues as described by Tory and Olivia. When using conditional statements in my template, blank lines are showing up when the conditions are not met and corresponding to where the conditional statements are written in the word document (even when the conditions are met). I would like there to be no space where conditions are not met so that there are not gaps in text/blank rows in tables in the report. Example template section in Word (condition is highlighted): Example where condition is not met (red shows extra lines): Example where condition is met and there are spaces corresponding to Word template location of conditional statements (see red lines): Any help with this is greatly appreciated! ... View more