Get Polygon Interior Point shows as error using feature geometry but does run - is this expected?
As noted, the Get Polygon Interior Point activity shows as an error when passing in a feature geometry, however it does still work, even with the error message. It's looking for type esri.Polygon but you can pass it a feature.geometry and it runs fine. This is somewhat misleading - is this expected behavior? This seems to be the only activity available at present to return a "point IN polygon".
-
It *shouldn't* be, but it is. There are a variety of activities pocketed around the library which have a similar problem, for example the Reverse Geocode activity in onw of my current projects.
The activities are written to accept "point" class inputs, not "geometry", but will run if that geometry is indeed a point. This is a little extra amusing in the case of Get Interior Points, since the input label is literally "Geometry" but throws an error when provided a geometry. If you really want that error to disappear, you can use the "new Point()" syntax to generate a point from your geometry, but this is unnecessary. I just have a note next to the activity explaining what's going on to the next guy (probably myself in a few months).
0 -
The general idea with the validation of the inputs is to guide you towards the preferred types to be used. In some cases, depending on how the activity is implemented internally, it might still work if you give it an object that's similar enough.
In response to Zack's observation about creating a Point, we do also have the "Create Point" activity, which will give you an esri.Point.
0
Du måste logga in om du vill lämna en kommentar.
Kommentarer
2 kommentarer