Is it possible to use Data Pipelines to generate a circular buffer polygon around a point?

[DBRCoordinator]

I would like to create a pipeline that automatically checks for new points created in one point layer daily and creates a circular buffer at a defined distance around each of those points in a new layer. I have tried to the "create geometry" tool, which does have polygon listed as an option under "geometry type" but am lost on what type of "geometry format" to use and what should be contained in the "geometry field" of the point layer. All points will be buffered to the same distance so that field can be a default value in the point field when the point is created. 

I've done a little research on community and over a year and a half ago there was mention of adding the ability to buffer points to pipeline but I can not find any newer references than that. 

[VenkataKondepati]

Hi @DBRCoordinator 

As far as I know, you can use a custom step in your pipeline to create a buffer.

You can try with Arcade expression using Calculate Field. 

Calculate field—ArcGIS Data Pipelines | Documentation

Geometry functions | ArcGIS Arcade | Esri Developer
Buffer($record, 0.5, 'miles')

Please let me know if you have further questions.

[DBRCoordinator]

Thank you for the response Venkat! I constructed the calculate field tool to create a polygon and inserted the arcade code for a 200 meter buffer. I used it on a point layer I created for this that contains two points. The tool does seem to run and complete, outputting two features. However, those features do not have anything contained in the fields and the buffers do not show up around the points on the map. When I add the layer it takes me to 0,0 because neither point contains any information. I also tried @rob_hewy's suggestion and had it only select the polygon shape field, I ran the tool before and after this and got the same result. I also tried "use default geometry" and "choose coordinate system" both with the same results. Screen shots below. @rob_hewy do you have any suggestions, seems like you may have been successful in getting this to work! Thanks in advanced! 

[BethanyScott]

Hi @DBRCoordinator ,

Thank you for reaching out with your question and for providing screenshots!

In the screenshot of the Calculate field tool, I see that you used an expression as follows: Buffer($record,200,'meters')

I believe this is what is causing the issue. The expression should be specified like so:

Buffer($record.<geometry field name>,200,'meters')

The difference is changing $record to $record.<geometry field name> . For example, if the feature layer has a geometry field named "shape", specify an expression as follows:

Buffer($record.shape,200,'meters')

Unlike feature layers or feature classes, datasets in Data Pipelines can have multiple geometry fields. With that, we require the geometry field is explicitly specified, rather than operating on the entire record and assuming the geometry.

Please let me know whether this change in expression helps, or if you have any further questions. 

Thanks again,

Bethany Scott

[DBRCoordinator]

Hi @BethanyScott, I gave this a try and it worked at generating the circular buffer which is fantastic! However, When I measured the distance of the buffer it came out to 148 meters, not the 200 meters that I had programed. I checked and changed the spatial reference but that did not solve the problem. Not sure what the problem is, I believe I changed the spatial reference to the correct coordinate system. I opened the layer in Pro and checked the spatial reference there before changing it in pipelines. Any ideas? 

Very happy that it worked though, getting closer!

[DBRCoordinator]

@BruceHarold  or @BethanyScott would you be able to look this over and see if there is a solution?

[BethanyScott]

Hi @DBRCoordinator ,

Apologies for the delayed response and thank you for following up!

I was not able to reproduce this on my side, but it could be data or spatial reference specific and I am missing a step. Some questions to help clarify:

1. Which spatial reference does your input point geometry use?
2. In the Calculate field tool, there is an Environment settings parameter group with a Spatial reference parameter within it. Which spatial reference did you specify there? By default, it is set to the same spatial reference as the first geometry field in the input dataset. I'd make sure this was set to the same spatial reference as the geometry field you buffered.
3. When you measured the distance of the resulting buffer in Pro, did you change the coordinate system of the map to match your buffer layer? This can be done using the Map properties dialog box (https://pro.arcgis.com/en/pro-app/latest/help/mapping/properties/set-map-properties.htm)

If all of these spatial references were the same across the board (i.e. no projections were applied to the buffers after calculating them), then I'd expect the resulting buffers to measure as 200m. 

Additionally, if none of the spatial reference checks above resolve the issue, it is worth submitting a ticket with Esri Technical Support so they can get an exact repro case to share with us.

Please let me know your findings or if you have any additional questions. 

Thanks again,
Bethany

[rob_hewy]

Hi,

Not sure if it matters but I added a select fields to remove the original shape field that had the point

[VenkataKondepati]

Hi @rob_hewy,

The null geometry means that there could be a co-ordinate system mismatch.

Is your source and target CS matching?

Do you have time for a quick call? If yes, you can book a meeting from my signature.
  

[BruceHarold]

The Data Pipelines team at Esri should be able to help with a recommendation @BethanyScott ?  You might be hitting an issue found elsewhere, namely that when ArcGIS creates a circle it is modeled as an ellipse with constant start and end radii and the same start and end axes, and hosted feature services are fussy about what clients can edit true curves.