Latest Contributions by ThomasHamill

What's the process for publishing Survey123 XLSForm designs to or getting them approved for the "Community" section shown in Survey123 Connect?   ... View more

@RobertVerheggen1, in the latest  beta version of the XLSForm design, many of the drop-down choices (for things like Cowardin Classifications,  soil textures, soil indicators, etc.) are coded under the choices sheet and I'm using the autocomplete setting under the appearance column in the survey for those autofills. At this stage, the Feature Report template (for batch printing survey submissions to PDF) is incomplete, though partially drafted.  I think I need more feedback on the beta XLSForm design (to inform revisions, fine-tuning) before it would make sense to complete a draft of the Feature Report. ... View more

@KansasDASC, what I've done for this in the past is configure a blank Field Map from scratch and simply bring in the feature service/layer (you may need to search for it with the Add --> Search for Layers menu) from the existing Survey123 deployment.  Then save the Field Map with a name similar to what's being used for the Survey123 Form name.  This sets things up such that observations can be submitted within the Survey123 app and allows users to then just pivot over to Field Maps for additional viewing/editing of the submissions.   ... View more

@MarkWilkinson1, take a look at this generic form (attached) showing use of  multiple geometries, two geopoints and one geoshape, in a single survey.  I learned how to do it from this thread.  In my demo example, the geopoint named "Device_Location" is a "primary feature" of sorts, meaning the subsequent geometries (which have to be listed under repeats)—a geoshape named "Feature_Boundary_Polygon" and a geopoint named "Feature_Center"—will be related to the  "Device_Location" point.  One could configure the parent/child geometries differently, depending on what's needed for the survey design.  For example, one could use a geoshape (for a polygon) as the primary geometry and then have a geopoint, a geotrace, and another geoshape be in the form (all related to the first geoshape).  Note that there will always need to be at least one geometry outside a repeat if multiple geometries will be used in one form.  Note that I put a "1" under the repeat_count (Column P) for the secondary features, because I want only one boundary polygon and boundary center point per survey device point. ... View more

@bryandhughes, by any chance did you try to implement that with Survey123 Connect to obtain Z-Values from the tablet? ... View more

@MarkWilkinson1, it seems like you want to use geopoint for signs and booms, then geotrace for fences, gates, barricades, is that correct?  Do you have any features you need to collect with geoshape (polygon) representation? I might suggest implementing a "featureType" or "structureType" select_one to provide an option for different features in a single Survey123 XLSForm.  Then you could use relevant functionality to show/hide the questions and fields that pertain to the item selected during one survey instance.   It's possible to use two or more different geometries (geopoint, geotrace, geoshape for points, lines, polygons) in a single Survey123 XLSForm as well, with some caveats.  See this tech page for more info about that.   ... View more

@bryandhughes, I'm not sure how to configure this in web designer, but in S123 Connect, there's a Sample form called 'Calculate Location from Geopoint' that shows this quite well.     ... View more

@Studenthas, take a look at some of tools in the Overlay Toolset.  Based on what you're describing, you could run the Erase tool using the old layer as the input features layer and the new layer as the erase features layer. ... View more

@RachaelMurtaugh, a few best practices I can suggest (hopefully not obvious things you've already put into practice): Organize your incoming (one subfolder) and outgoing (another subfolder) transmittals of data or figures with timestamps (YYYYMMDDHHMM) and source name/organization in the file/folder names Use a "Library" v. "Development" subfolder dichotomy to distinguish "development data" or workspace geodatabases from ones that serve as base layer and that should not be edited/modified NEVER use a suffix of "final" in file naming—Nothing is ever final. A two-digit decimal filename suffix (like vX.Y) works well as a versioning substitute. Start working with v0.0, increment Y between stages of internal revisions, and increment X for stages of revisions after feedback from third parties or external users. The "final" (latest) version will be obvious by the highest X.Y decimal value. Not my idea, adapted from principles of Semantic Versioning (https://semver.org/) I'll try to post a few more as I remember them.  I hope these will be helpful! ... View more

@aam, keeping information (e.g., Inactive or Retired) as a "Legacy" attribute (like "Legacy_Material," "Legacy_Diameter," Legacy_Manufacturer," etc.) within the operational Feature Class(es) would work well if only the attributes were subject to change.  In my experience it becomes a suboptimal (and confusing) solution when new feature geometry is introduced, like with a hydrant being relocated across the street or a water main replacement having shifted slightly in relation to the old one.  My approach used to be to just make an archive/backup copy of the feature geodatabase (with a YYYYMMDDHHMM timestamp suffix before the .gdb file extension) prior to a major "campaign" of edits/revisions, but I realize that this isn't a very sophisticated approach. Perhaps there are some special versioning tools or other functionality in you enterprise GIS system that would support a simple archiving-aware workflow. ... View more

@Kaj, are you using a text question type?  You should be able to do this using a Regex expression in the Constraint column.  I recommend you use two separate entries, one for genus and one for species.  If your list of possible answers isn't incredibly long (like, if you're working within a relatively small region or extent), you might even want to consider using select_one question types instead of text and build in the genus and species options under the choices sheet. Input Mask Survey123 Quick Reference ... View more

@StephanieParadis, were you able to work through the problem with your DEM? ... View more

@StephanieParadis, this usually happens if the Pixel Type (8 Bit unsigned integer, 32 Bit float, etc.) Projection, or File Format with Extension (Erdas Imagine/.img, GeoTiff/.tif, Jpeg/.jpg) changes between the source datasets and the final result during a mosaic.   Have you checked to make sure your resulting mosaic raster has the same properties as the input datasets?   ... View more