Latest Contributions by JeffShaner

@AbiDhakal let me clarify. - the location tracking layer you have been using in Collector classic is a hosted feature layer that supports sync. When you work in a disconnected environment, the tracks are stored locally in your map. - the location sharing layer used in ArcGIS Field Maps is a feature layer but it does not support sync. Even though it does not support sync, when you work in a disconnected environment, the tracks are stored locally on your device but not in a specific map. Very important here is that in the setup process, do not add the location sharing layer to your map. Please see the help topic I mentioned above and consider reading the ArcGIS Online help that discusses how to Enable location sharing in your organization.  - regarding the licensing, if the user type that signs into Field Maps is a Mobile Worker user type, no license is required. For other user types, Viewer, Creator, GIS Professional it is required. If you have additional questions about licensing, please work with your account manager to guide you through. - the location sharing layer is best used in web apps like ArcGIS Dashboards, Experience Builder apps, or Instant apps that are used for overall operational awareness. Important here are the security/privacy considerations for who can see the location of other users. If you would like, you can add that location sharing to a map and open the map in Field Maps. You will not be able to download the map, but you could use the map while connected to view the location of others. ... View more

Hi @AbiDhakal, Thank you for posting this question. The location sharing capability supports offline use today and with ArcGIS Field Maps, it's independent of the web map itself. You don't need to add the layer to a map. If you want to see the tracks of other people and have the privilege to do so, then you can add that layer to a map. But as you've found, it does not support sync and needs to be used when connected. You'll notice that on the maps screen there is a My Tracks card and you can enable/disable location sharing without ever opening a map. Also, regardless of the map used, you will see the Tracks layer in the layers tool and if you turn it on you can tap on your tracks to see them (connected or disconnected). Here is the documentation topic on location sharing for more information: https://doc.arcgis.com/en/field-maps/android/help/track.htm Coming from Collector Classic, you may be interested in the background capability as well. You don't need to keep the Field Maps app in the foreground for it to record, store and share locations anymore.  Give it a spin in airplane mode without the layer in the map! ... View more

Yes Andrew, we can confirm that this is resolved in 11.1. ... View more

Hey @DougBrowning and @JUANGARCIADELMORAL - they did sneak in but we are not officially supporting them in this beta cut (we just didn't hide the functionality). Feel free to try at your own risk, but know that we are planning a beta update in September where we will update both the web and mobile apps and provide documentation as well.  ... View more

Here you go Brittany. Though not really needed if the point is geometrically coincident with the line, I added in a buffer as well just for fun: var measureBuff = Buffer($feature, 2, 'meters'); var routeID = Intersects(measureBuff, //Make sure you use the layer name in your web map FeatureSetByName($map,"Routes")); if (Count(routeID) == 1){ //if multiple routes found you are not going to get a result //ROUTE_ID is the field name for the "Routes" layer return First(routeID).ROUTE_ID }; Also, you might want to bookmark this blog article. We are going to continue updating this with new examples as we come across them: https://www.esri.com/arcgis-blog/products/field-maps/field-mobility/common-calculated-expressions-for-arcgis-field-maps/ Oh and make sure that the field you are calculating the expression for has editing unchecked. It should do that for you but best to measure twice and cut once (pun intended).   ... View more

Hey @BrittanyBurson - thanks for following up. When you use Collect Here, from the interpolated location, it will take the m-value from the graphic and store it inside the m-value of the new point feature you create. Note we don't expose a way to set the m-value at a vertex level in Field Maps (yet) so it's really only valuable for point features. In the video I did use calculated expressions as well: I stored the m-value in a field (which was just taking the m-value from the geometry and shoving it into a double field). I converted the m-value to a station value and stored it in a string field (hardcoded using US Survey foot from this github repo). I used featuresets to grab the RouteID field off the route feature and store it for reference as well. I have then been trying to model offsets from the point on the route to say a culvert or sign by leveraging the copy capability in Field Maps with calculated expressions. It's a fairly complicated workflow that I think we can simplify over time but there are a lot of possibilities with Arcade today. Calculated expressions do require a portal update unfortunately as there are a lot of pieces to it. They are coming in ArcGIS Enterprise (11.0) (current estimated ship date for Windows/Linux is end of July). If it is all a possibility, I would consider a hybrid approach where your "portal" and web maps are stored in ArcGIS Online and your services are either ArcGIS Server feature services or hosted using replication (10.9.1 introduced bi-directional replication). Again, only if it is possible for your organization. The benefit being that you can stay up to date with all the new capabilities we bring (where there are other dependencies like this). Thank you too for linking to your post. I must have missed that post from last year. We did not implement stationing notation (display or edit) with this release. In part, we have the challenge that measures are void of any unit and we can't hard code to US Survey Foot or Meters. We'll likely need to introduce settings in the web app to pull it off. Also, we use the native keyboard from iOS/Android and do not implement our own like S123 does. That introduces concerns with accessibility and a host of other things too. We do see stationing notation for display and entry as a candidate for future updates and would like to go after it later this year! If possible, could you reach out to me directly via your account manager or a DM in Esri Community? We've really just started down this path of LRS support and I want to make sure we ground our future enhancements based on workflow conversations we have with customers like yourself!! Thanks! ... View more