Hot answers tagged arcobjects
I suspect the error is related to how you set your input features. Have a look at How to use multiple inputs, it gives examples in c# and vb.
You can't add you own message to this dialog but you can create an event listener to watch for the start editing event to fire. When this event occurs you can then run some code and display your own message dialog. There are several ways to implement the event listener. One way would be to create a custom extension that tracks events when it is turned on. ...
I'm not sure if I would recommend ArcObjects/.NET if you have no experience with either ArcMap or .NET. But if you decide to go this way, start small, e.g. by creating an addin based on the Visual Studio templates that come with the ArcObjects SDK. After you do that a few times, throw everything away and do it again in the proper way ;-) An addin built with ...
Faced similar siutation and resolved using ScaleText option. ITextSymbol pTextSymbol = new TextSymbolClass(); pTextSymbol.Size = Convert.ToDouble(size); pTextSymbol.Font = pFontDisp; pTextSymbol.HorizontalAlignment = esriTextHorizontalAlignment.esriTHACenter; pTextSymbol.VerticalAlignment = esriTextVerticalAlignment.esriTVACenter; pTextElement.ScaleText = ...
For what it's worth, I've not found a method of creating a GeoTransformation using nothing but the information in a Map, so I've not been able to get ProjectEx() to work. Using Project(), on the other hand, is simple: double x; double y; var success = this.projectLonLat(this.axMapControl1.SpatialReference, -84.3880, 33.7490, out x, out y); if (success)...
This model assumes the world is spherical, but earth's radius changes with the latitude. If the distance covers about 1/10 of a degree, and Earth's radius ranges from 6353-6384km, then the error can be over 400m. This might cause 10km to come out as 9km if you are aggressively rounding.
It sounds like you need to refresh the TOC, you can do this through the IMXDocument interface using UpdateContents() method.
I found a post with essentially at Row.Value returns rounded SHAPE.area and SHAPE.len values? 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 ...
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(...
Only top voted, non community-wiki answers of a minimum length are eligible