GeometryEngine.Project() Arguments

JensBuchta — Fri, 10 Dec 2021 21:09:14 GMT

What do you think about this API method?

public static Geometry GeometryEngine.Project(Geometry geometry, SpatialReference spatialReference)‍

In my opinion, this method is to generic and involves to many casts when it's used, e.g.

var mapPoint = new MapPoint(...)
var projectedPoint = (MapPoint)GeometryEngine.Project(mapPoint, anySpatialReference);‍‍

If we had a finite list of supported overloads, like:

public static MapPoint GeometryEngine.Project(MapPoint mapPoint, SpatialReference sr) {}
public static LineSegment GeometryEngine.Project(LineSegment lineSegment, SpatialReference sr) {}
public static Polygon GeometryEngine.Project(Polygon polygon, SpatialReference sr) {}
...‍‍‍‍

...use of the API would be easier and more clear.

What do you think about this?

Re: GeometryEngine.Project() Arguments

dotMorten_esri — Wed, 19 Jul 2017 18:55:55 GMT

Thank you for the feedback. However there is actually no guarantee that projecting a geometry of a certain type will return that same type. There are cases where a polygon can collapse to a line or a point, or a line to a point, and Envelopes will almost always return as Polygons.

Projecting points will however always return a point or null, so I could see an argument for adding a point-specific overload.

topic Re: GeometryEngine.Project() Arguments in .NET Maps SDK Questions

GeometryEngine.Project() Arguments

Re: GeometryEngine.Project() Arguments