Latest Contributions by PaulLohr

It would be helpful if we spoke about the level of "support" rather than limiting ourselves by generally saying a product supports this or that. As an example, Field Maps "supports" relationships but in a certain case Collector on Android is the only app that supports what we are doing. But we are supposed to be using the latest version of Field Maps? The important detail is that ArcMap does not fully support the direct editing of feature services. A local copy has to be created, which does not satisfy our requirements. If someone knows of an out of the box way to directly edit feature services, I'd appreciate it if you could educate me. The answer is always the same: "If it doesn't work, switch to Pro." Never mind system or user requirements.   ... View more

If you don't have a data model figured out, I'd get that worked out first. We have been doing this for about 5 years using ArcGIS Server, ArcGIS Desktop and ArcGIS Online. We are having to use Collector on Android since Field Maps and Collector on iOS do not fully support relationships. DanGruber's idea is helpful in that a related table is a good way to handle your inspections. I use 1:M relationships for this kind of thing. A field named something like Date Last Inspected is key to a lot of this. You can probably see why. You may want to symbolize power lines using Date Last Inspected (and maybe another attribute). We have to put this field in both the parent feature class and child table since messaging isn't built into ArcGIS Server or Desktop. The root cause for having to add this duplicate field is mentioned later. We would like the Date Last Inspected value entered into the child table to set the Date Last Inspected in the parent feature class but that's not easily accomplished. So the same information is being stored in two places (not a good practice). You might use Editor Tracking to set the Date Last Inspected value in the child table so it is only being set once by the end user but it still will be stored twice (although the values won't be identical). This is necessary since ESRI software in general cannot symbolize through 1:M relationships. The root cause for this shortcut: we want to symbolize using Date Last Inspected from the child table, but the software won't do that. So we have to put that field in the parent feature class. In our environment, the software is barely capable of handling this type of thing. mejohnson22 had a good idea: Can you symbolize your power lines using Arcade to query for related inspection records created within the last 30 days or so? That could be a big help. I would thoroughly test that if it does work.   ... View more

@KellyGerrow  Doesn't each AGOL user have a single role assigned for all content in the organization? In other words, a user can't be assigned one set of privileges to one hosted layer and a different set of privileges to another, correct? Thanks for any help. ... View more

Thanks for your help, Craig. Server version 10.7.1. Web services are stored as proxy items in AGOL so the user doesn't have to log in for a second time. Assuming the "related record form element" had to be created in Map Viewer, I tried to do that. Documentation for Map Viewer says it only works for hosted content. So this won't work since we are using ArcGIS Server. Would it be correct to say that relationships are supported in Web Editor and Map Viewer only for hosted content? ... View more

@kmsmikrud This is my overall impression. Field Maps can be ok for simple tasks but when I've tried to use more complex features such as snapping, relationships and offline editing, there are problems. Lots of wasted time trying to make this stuff work. Tech support can't figure it out in a few weeks time. If there's any way you can run Collector on iOS, that should get you snapping. You may find some phones or tablets that still have it installed. If not, trying to get it installed will be difficult. Shouldn't be this difficult if Field Maps were made to work properly. By the way, there's no support for snapping on Collector for Android. If you find Collector 20.2.2 on an Android device, you may want to save the APK file somewhere for future use. That has saved us a tremendous amount of time and given us the ability to use relationships (which will not work on Field Maps). I am going to look into using ArcGIS Desktop on a Windows 10 or 11 tablet to support complex editing such as snapping, relationships and offline editing. External GNSS receivers may be an issue on Windows 10 / 11. A feature service from ArcGIS Server can be used for editing and display. This will not be the best user interface for editing in the field but it can probably be made to work and reliably so. ... View more

I compared the documentation pages for "Prepare Feature Services for Online Use" between Server version 10.8 and 11.1. 10.8 mentions the limitation but 11.1 does not. Maybe the limitation has been removed? 10.8 documentation: https://enterprise.arcgis.com/en/server/10.8/publish-services/windows/prepare-data-for-offline-use.htm (Search for the heading "Map Layers" in the 10.8 documentation to find the limitation.) 11.1 documentation: https://enterprise.arcgis.com/en/server/11.1/publish-services/windows/prepare-data-for-offline-use.htm   ... View more

Outside of the ESRI world, stored procedures and triggers are used in the database (Oracle, SQL Server, etc.) instead of webhooks.  This is a more direct solution which doesn't have to leave the database for execution. ... View more

Have you tried WKID 6318 for GNSS Coordinate System in  the Field Maps Location Profile? It corresponds to NAD 1983 / 2011 (unprojected). I don't know how to address MYCS2. NY DOT might be able to help with MYCS2. WKID 2261 for your map coordinate system in Field Map Location Profile? That would be "NAD 1983 State Plane New York Central FIPS 3102 feet". This needs to match the coordinate system of your published map. This coordinate system uses the original realization of NAD 1983, which is 1986. Might want to check to be sure your map data actually uses the 1986 realization of NAD 1983. I would think NAD 1983 (2011) (EPOCH:2010) would be correct for TMM GNSS output. But again, I don't know about MYCS2. GNSS source reference frame in TMM NTRIP setting might use the same as above: NAD 1983 (2011) (EPOCH:2010). But again, I don't know about MYCS2. Make sure to get some check points against NGS monuments or similar before calling it good. ... View more

At what point should we give up on such a reasonable request? How long should we wait on this and numerous other issues which are still unresolved? This request was submitted 4.5 years ago. If something as basic as file pathing does not work correctly, how can this product be relied on for daily work? And I am supposed to have our organization switch over to this product? ... View more

You're welcome. I don't think changing the WKID to one that doesn't match that of the ImageServer service will work. You could try it though.  If the aerials actually use WKID 3438 (rather than 3857 / 102100), the imageServer service could have its coordinate system changed (data frame) then recreate the service. Chances are those aerials use State Plane coordinates (rather than WGS 1984 Web Mercator; WKID 3857 / 102100). You may need to remove and re-add the basemap to force the change. The key is to get that WKID to change to 3438 in the JSON code. ... View more