Geometry complexity and generalization

Question

This has been bothering me for many days and hope someone here may have an answer.

Is it mandatory to generalize a ("complex") geometry before feeding it to the intersection operation of geometry service? I was told so, but couldn't find any documentation about this. For example, we may have to reduce the number of vertices of a geometry to <250(??)  in order for the intersection to work. But this sounds really strange to me. ArcGIS server cannot even handle geometries over 250 vertices? But I do see intersection doesn't seem to return anything for complex geometries. I am surely missing something. Any advice is much appreciated.

Thanks a ton!

Jian

BjornSvensson · Answer

It could be the data or the version of ArcGIS Server.  So some things to test:

* does it work with a more recent version of ArcGIS Server?
* does it work with other layers?

You could probably use http://sampleserver6.arcgisonline.com/arcgis/rest/services/ to test this.

JianLiu · Answer

Bjorn,

I've tested simplifying the donut polygon before intersecting, but still the same result -- returns nothing.

In fact, I am not using geometryservice.intersect. I use FeatureLayer.queryFeatures(query,..) and query.spatialRelationship = "esriSpatialRelIntersects". I assume simplify is also required before using this spatial query? Any other thing you might think of that could cause this (no points returned even though they are there)?

Thank you and it's much appreciated.

BjornSvensson · Answer

Yes, my guess is that incorrect drawing order would need to be fixed, for example with "simplify".