Creating Point at end of line
Hi,
I've created a MapTool that creates a line and places point features at the to/from point of the line. I use code like this to accomplish this....
I use this to get the sketch geometry to create the from point (connectionPoint) and to point (plugPoint):
var pointCollection = ((Multipart)geometry).Points;
MapPoint connectionPoint = pointCollection[0];
MapPoint plugPoint = pointCollection[pointCollection.Count - 1];
I then create the plugPoint like this:
var plugAttributes = new Dictionary<string, object>
{
{"SUBTYPECD", 4 },
{"DIAMETER1", 200 },
{"Shape", plugPoint.Clone() }
};
editOp.Create(waterFittingsLayer, plugAttributes);
Does using plugPoint.Clone create an EXACT clone?? Is there a more preferred way of doing this??
I'm finding that most of the time it does create the point correctly, but then other times the point created is not exactly the same. I cannot figure out why this is happening. Here are some screenshots of the values I am seeing. The first value is the TO point of the line and the second value is the 'cloned' point.
Hi Brian Bulla
I setup and tested the SQL Server enterprise geodatabase configuration and was not able to duplicate your issue. I even used your projection to no avail. So i made a new test add-in (GeoNet259853-v2.zip) for you that 'captures' and saves the geometries that are causing the issue. Please use the test add-in with your data (i think all layer names should be the same as on your map). Follow these steps:
- Build the new test add-in
- Open Pro with your water service map.
- Make sure that the "selection settings" are only checked for WaterService and Fitting:
- From the add-in tab use the "Create Service Connection" tool to create a service connection
- Once you create a service connection you can then click the 'Rectangle' button and select the 'end point' of the newly created service connection
- Once the end point (and the service line) are selected, you then click 'Selection Coincidence' to check for the error.
- Once you duplicate the 'coincident: false' error, click the "Export Geometry" button to save the "serialized geometries" in a json file.
- Send me the json file so that i can take a look at the geometries myself.
I hope we'll get a duplicatable case from this.
Hi Wolfgang Kaiser,
I've run your updated test and here is what I have found:
1. The first connection I made came up 'False' with different End/Plug points. I've attached the file FALSE.json.
2. The second connection I made also came up as 'False' but the End/Plug points are actually the same. See the screenshot below. I noticed this the other day too, figuring it was just an error in the code that displayed the True/False notification, but perhaps there is also something else funky going on here. I've attached the file FALSE_NEGATIVE.json for this one.
I'm not sure why toPoint.IsEqual(pntFitting) is always coming out False.
Thanks Brian Bulla,
I am not able to duplicate the problem even with your geometry (that I loaded into the same app i sent you). I am using 2.6.0 (not patched), what version of Pro are you using? I also don't see the additional digits for the coordinates you are seeing. What version of Visual Studio are you using?
