New answers tagged

0

The best way to deal with this seems to be by following the advice Microsoft gives about how to compare two doubles: https://msdn.microsoft.com/en-us/library/ya2zha7s(v=vs.110).aspx Here's how I ended up implementing it in my code for ArcMap: If I want to select a line based on its SHAPE.len value I would set the "where clause" of the query to be: "ABS(...


0

I found a post with essentially the same question here No answer is given but the comment section provides good insight and possible workrounds. This problem is related to "False Precision" and "failure to bracket floating-point comparisons". I decided to use the rounding of value pairs workaround. I also posted a question on the ESRI Forums here where ...


0

geonet.esri.com/thread/40373 has the working code here.


0

You could look at: var jsonSerializer = new NetTopologySuite.IO.GeoJsonSerializer(); jsonSerializer.Deserialize(...)


0

The first requirement to speed up the search code is to make sure that the feature class has an attribute index on any fields that are searched by the Query Filter or Definition Query. Anytime you use a LIKE statement with wildcards at both the beginning and the end of a string it will be slow. My queries only use wildcards at the end of the string, which ...



Top 50 recent answers are included