Latest Contributions by DougGreen

‎11-29-2022

I guess I read the original question as "Can these two buffers be saved in the same layer?" and not as "Can these two buffers be saved in the point layer?". In which case, you can create a model with two buffer tools chained together with one set to buffer at 500 meters and one at 1,000 meters. Set the input to the first buffer as a model parameter. Then run the second buffer off of the result of the first buffer. Then add the merge tool to combine the two buffers into one layer. Set the output feature class of the merge as a model parameter as well. Then follow instructions in the documentation for how to publish a Geoprocessing Service. Hope that helps.

‎08-11-2022

@ZacharyUhlmann1, I have not received any additional info. My initial concern was that ESRI indicates that generally the software will project on-the-fly for data that does not match the basemap; but cautioned "Although it is possible to edit data that is in a different coordinate system from the data frame, when high levels of accuracy are critical, it is better to project the data to a common coordinate system before editing." So I was trying to determine how much error could be introduced by not heading that caution. I have since discovered a simpler way to eliminate the project-on-the-fly step. I can use ArcGIS Pro to generate a vector tile package with very simple reference data in the projection I'd like to collect in and then share it to my ArcGIS Online Organization and use that as the basemap. This way, I'm only doing one project/transform from the coordinate system of my NTRIP provider to the coordinate system of the map and this method is known. I still don't know which on-the-fly transformation method ESRI is using under the hood when you use a one of ESRI's Basemaps. I'd love to just use theirs since they are wonderful and then I could just report on the methodology of projection/transformation. As of right now, I'll have to use this method.

‎07-20-2022

I'm tying to understand what's going on under the hood with projections and transformations when I use Field Maps for high-accuracy data collection. I've read through this article in detail with the lure of being able to walk away from post-processing workflows by being able to collect in high-accuracy using external Bluetooth GNSS receivers and mobile devices. I've noticed that I can publish a hosted FeatureLayer in a variety of coordinate systems and enable them for editing so that I can add them into a map used for data collection in Field Maps. However, when setting up a location profile in the settings, the documentation indicates that the Map coordinate system is determined by the basemap it uses. So that leads to my first question, if my layer is in a projection other than that of the basemap, and my NTRIP provider is in yet another coordinate system, is my data being projected/transformed twice? Specific example. Let's say I have a hosted FeatureLayer that was published from pro in GCS NAD 1983 2011 (EPSG: 6318) and then I add it to a map with a basemap that is in WGS 1984 Web Mercator Auxiliary Sphere (EPSG: 3857). Then, I set up a location profile in Field Maps using EPSG 6318 as the GNSS coordinate system (the one used by my NTRIP correction service that I don't have ability to change) and EPSG 3857 as the Map coordinate system (because that's what the ESRI basemaps are in), and the horizontal datum transformation as ~WGS_1984_(ITRF08)_To_NAD_1983_2011. In my understanding of this, the following steps would occur when I collect a point: Corrected location is received from the receiver in EPSG 6318 Field Maps uses the transformation supplied in the location profile to project the point to that of the basemap (EPSG 3857) Field Maps sends the point to the FeatureLayer service ArcGIS Online receives the point in EPSG 3857 and detects that it does not match the coordinate system of the FeatureLayer This is the point at which I'm unsure of what's happening and I'm wondering if someone could answer my second question: Does ArcGIS Online use the top transformation from the list to project the point back to the coordinate system of the FeatureLayer (EPSG 6318) or does it use some other default? Without knowing what's going on under the hood, I can't truly report my accuracy or the method in which my data was projected. Thanks in advance for supplementing the available documentation so I can make this switch to more efficient data collection without loosing some of the important details.

‎02-18-2022

Hi @Anonymous User, I don't know why I didn't pick up on this before but of course you're wanting this to happen regularly. This solution that was provided here works whenever you go in and calculate the field. So Calculating a field in this way is a "one-and-done" type of thing. It's not setting up an automatic default value of sorts on the field. So as new records are added or any information changes on the record, you'd have to calculate the field to show the changes. I don't think you're going to want to do that regularly but you could set up a minimal python script to run once or twice a day that would calculate that field for you https://pro.arcgis.com/en/pro-app/2.8/tool-reference/data-management/calculate-field.htm.

‎01-14-2022

Yep, don't go off of mine ;). That was T-SQL for SQL. Didn't realize it was only a subset of SQL in that window.

‎01-14-2022

Oh, ok. You might be able to pull the feature class into Pro and perform a field calculation on it using the previous python but i think @jcarlson had the right idea then. Only catch there is that if any of the values are NULL, you would get a NULL. So you could use this to change any empty strings to NULL and add 1 if not NULL. IIF(NULLIF(complaint1, '') IS NULL, 0, 1) + IIF(NULLIF(complaint2, '') IS NULL, 0, 1) + IIF(NULLIF(complaint3, '') IS NULL, 0, 1) + IIF(NULLIF(complaint4, '') IS NULL, 0, 1) + IIF(NULLIF(complaint5, '') IS NULL, 0, 1) + IIF(NULLIF(complaint6, '') IS NULL, 0, 1) + IIF(NULLIF(complaint7, '') IS NULL, 0, 1) + IIF(NULLIF(complaint8, '') IS NULL, 0, 1) + IIF(NULLIF(complaint9, '') IS NULL, 0, 1) + IIF(NULLIF(complaint10, '') IS NULL, 0, 1)

‎01-14-2022

Hi @Anonymous User, I'm thinking this isn't exactly a SQL question with a "def" statement. I think that's a Python function. You could use something like this as a field calculate function: def getComplaintCount(complaint1, complaint2, complaint3, complaint4, complaint5, complaint6, complaint7, complaint8, complaint9, complaint10): compCount = 0 compCount += 1 if complaint1 != None else 0 compCount += 1 if complaint2 != None else 0 compCount += 1 if complaint3 != None else 0 compCount += 1 if complaint4 != None else 0 compCount += 1 if complaint5 != None else 0 compCount += 1 if complaint6 != None else 0 compCount += 1 if complaint7 != None else 0 compCount += 1 if complaint8 != None else 0 compCount += 1 if complaint9 != None else 0 compCount += 1 if complaint10 != None else 0 return compCount This simply checks if each value is null and adds 1 to the compCount variable if it is not null. If your complaint fields are not nullable strings, you'd want to replace the "None" with a ''.

‎01-14-2022

This is called "Importing" since it has to convert it to a different format. The GDB doesn't store files like a directory in windows. It stores Feature Classes, Tables, Datasets, etc. So, importing a shapefile into a GDB creates a feature class. The link @CarlMorrison posted above explains how to import various formats.

‎01-14-2022

I think you were asking why the data in the map wasn't imported into the project GDB right? Pro lets you do this work. You could choose to import the data or leave it where it is as @CarlMorrison indicated but you're wondering how to import an MXD as a map in the new Pro project without having to repoint every single layer. This isn't built in behavior. You'll even notice that if you copy a map from one project to another within Pro, it will retain the data connections to the old Project.

‎01-05-2022

Ok, with graticules, you can set all the interval details and things in the settings as described in the link I provided. Check the original map to determine what interval you need to use. However, it sounds like your graticule might be using the same interval but they are about 200 ft off from the original map. This sounds like a different projection may have been used on the original map.

‎12-29-2021

That is perplexing. I think the weekend could be solved by checking the weekday of the forecasted date and if weekday is 6 or 7, add 1 or 2 days respectively. About the holiday question, that's a bit harder to tackle. There are a variety of Holiday calendars. This post has a known list and then checks against that list to add days if needed. You could create a hosted layer that contains all of the holidays for your locality and add the dates for a year at a time before the first day of the year and then use it in a FeatureSet to check for Holidays.

‎12-29-2021

When you say "grids" are you talking about a "graticule" that you have set up in the map layout? If so, you can use the instructions at that link to change the interval (the number of degrees or map units) between each grid line and adjust other settings to see if you can get it to more closely match. Another thought, if you already show a graticule on the map you're trying to overlay your new transparency on, you could print yours without the graticule or "grid" showing. As long as the comments by others about 100% print scaling are followed, the features on your map should align and you wouldn't need the "grid".

‎12-29-2021

Have you updated the password in the connection set up in your ArcGIS Pro project? Right-click > Connection Properties.

‎12-29-2021

Kristin, I'm not sure what's going on with yours and I just realized yours is a hosted feature layer. We have a non-hosted enterprise feature layer. But here's what just fixed it for us. Remove the defaults on the layer and save Add the defaults back and save For us, we had to republish, but with yours being hosted, I'm not sure you can republish. But you could simply try removing the defaults and re-adding them.

‎12-28-2021

We are just experiencing the same issue after upgrading our ArcGIS Enterprise to 10.9.1. It was working before the upgrade in Field Maps and is no longer working. This post indicates that it might be an issue with Editing Templates and that templates are only going to be supported for hosted feature layers. We have a lot of benefits of managing our own data in an enterprise GDB and don't like the thought of moving all of our enterprise data to the hosted environment. However, in my opinion, if it was working before, and now it's not, this would have needed a deprecation notice since we have lot's of workflows built on our enterprise feature services. Therefore, I think this feels like a bug.

Online Status	Offline
Date Last Visited	‎04-09-2026 08:22 AM

My Ideas

Latest Contributions by DougGreen

Re: Create "buffer" in same layer

Re: What Projections and Transformations Happen Under The Hood

What Projections and Transformations Happen Under The Hood

Re: Perform a SQL Count in Calculate Field

Re: Perform a SQL Count in Calculate Field

Re: Perform a SQL Count in Calculate Field

Re: Perform a SQL Count in Calculate Field

Re: Having trouble discerning how data is stored in pro vs arcmap

Re: Having trouble discerning how data is stored in pro vs arcmap

Re: Scaling a layout that is printed on a transpancey to match a paper map

Re: Arcade: Return a date in the future not including weekends and holidays

Re: Scaling a layout that is printed on a transpancey to match a paper map

Re: Unable to connect Geodatabase

Re: Default Values not working in Field Maps Mobile

Re: Default Values not working in Field Maps Mobile

Re: Solving SSL Errors in Python Requests

Change Default Behavior of Opening Map Package

Re: Add a layer to a hosted feature layer

Re: How to Associate Documents with Polygon Featur...

Re: Add a layer to a hosted feature layer