Latest Contributions by AlexanderGleyzer

Adrian, Actually, there are DWG files, that do show feature class attributes. For instance, I have a DWG containing a "CELLNO" feature class with attributes - CELLNO, CODE, AREA. Interestingly, it's the only feature class in the DWG. Maybe this issue persists only when there are 2 or more feature classes? ... View more

Adrian, We've tried the same DWG both in version AC1027 (AutoCAD 2013) and version AC1015 (AutoCAD 2000). We're using ArcGIS for Desktop 10.4.1, which is supposed to support both of the above formats. For both formats we're getting no attribute fields. Alexander. ... View more

Hello, Asser. We're using Static mode for all our Graphic layers. Unfortunately, we cannot create a simple app reproducing the problem, since the business logic and the data flows are quite complex. Can you still estimate what could be the problem? For instance, what could be the reason for HItTestAsync crash? Thanks, Alexander. ... View more

Hi, Michael. Attached is a C# project reproducing the problem. When zooming out a little - some labels disappear. Thanks, Alexander. ... View more

Hi, Asser. Thanks for the workaround. Please, let me know when this issue is fixed in either the next ArcGIS Runtime or ArcGIS Server release. Alexander. ... View more

Hi, Asser. I've upgraded ArcGIS Server from 10.2.2 to 10.3, but, unfortunately, the problem still persists . I'm still experiencing an "exact match" behavior (i.e. "contains=false") whenever the "contains" parameter is omitted from the respective REST URL. I'm really lost here. Please, let me know, whether there is any workaround for this: how can I use ArcGIS Runtime's "Find" task with a partial match? Maybe it's because my underlying service data is stored in FGDB? Alexander. ... View more

Hi, Asser. Do you mean - ArcGIS Server 10.3? ... View more

Hello, Asser. I am able to reproduce this behavior using ArcGIS Online public map service "World_Topo_Map" (against the single service layer 0 - "Citations"): I am searching for "Coun" string and expecting REST's Find operation to match all partial "Coun" strings like "County" etc. Here are the results: 1. Explicitly specifying "contains=true": http://server.arcgisonline.com/arcgis/rest/services/World_Topo_Map/MapServer/find?searchText=Coun&contains=true&layers=0&returnGeometry=false&f=pjson Result: many results, each one with the partially matched "Coun" string in one of the fields. 2. Explicitly specifying "contains=false": http://server.arcgisonline.com/arcgis/rest/services/World_Topo_Map/MapServer/find?searchText=Coun&contains=false&layers=0&returnGeometry=false&f=pjson Result: no results, since no feature in the queried layer contains the exact string "Coun" in any of its fields. 3. Omitting "contains" parameter entirely: http://server.arcgisonline.com/arcgis/rest/services/World_Topo_Map/MapServer/find?searchText=Coun&layers=0&returnGeometry=false&f=pjson Result: no results, same as in case 2 above. Conclusion: omitting "contains" parameter implicitly applies the default value of "contains=false", contrary to REST's Find operation documentation, which clearly states: contains Description: If false , the operation searches for an exact match of the searchText string. An exact match is case sensitive. Otherwise, it searches for a value that contains the searchText provided. This search is not case sensitive. The default is true . Again - am I missing something? Please, advise. Alexander. ... View more

Hi, Asser. I've been able to reproduce this behavior both on ArcGIS Server 10.1 & 10.2.2. For clarification: the underlying data source of the map service's layer is a FGDB, registered appropriately with ArcGIS Server (registeted under "Registered folders" under "Data store"). For example, I'm searching for the partial string "hel". Here's what I'm getting in response to REST request with the "contains" parameter explicitly set to "true". Request URL: http://[Map service REST URL]/MapServer/find?searchText=hel&contains=true&searchFields=&sr=&layers=2&layerDefs=&returnGeometry=true&maxAllowableOffset=&geometryPrecision=&dynamicLayers=&returnZ=false&returnM=false&gdbVersion=&f=pjson Response JSON: { "results": [   {   "layerId": 2,   "layerName": "Major lakes",   "displayFieldName": "name",   "foundFieldName": "name_abb",   "value": "L. Chelan",   "attributes": {   "OBJECTID": "1130",   "Shape": "Polygon",   "featurecla": "Reservoir",   "scalerank": "5",   "name": "Lake Chelan",   "name_abb": "L. Chelan",   "name_alt": " ",   "note": " ",   "delta": " ",   "dam_name": " ",   "year": "1927",   "admin": " ",   "DontShow": "0"   },   "geometryType": "esriGeometryPolygon",   "geometry": {   "rings": [      ],   "spatialReference": {   "wkid": 102139,   "latestWkid": 3067   }   }   },   {   "layerId": 2,   "layerName": "Major lakes",   "displayFieldName": "name",   "foundFieldName": "name_abb",   "value": "Mitchell L.",   "attributes": {   "OBJECTID": "1188",   "Shape": "Polygon",   "featurecla": "Reservoir",   "scalerank": "9",   "name": "Mitchell Lake",   "name_abb": "Mitchell L.",   "name_alt": " ",   "note": " ",   "delta": " ",   "dam_name": " ",   "year": "-99",   "admin": " ",   "DontShow": "0"   },   "geometryType": "esriGeometryPolygon",   "geometry": {   "rings": [      ],   "spatialReference": {   "wkid": 102139,   "latestWkid": 3067   }   }   } ] } From the above you can see, that with an explicit contains=true a partial "hel" string is correctly matched to full strings in underlying data: "L. Chelan", "Mitchell L." According to documentation, the same URL with no contains parameter specified at all should produce the same results (since contains=true is assumed by default). However, the following URL (same one as above, but with contains parameter omitted) returns no results whatsoever. Request URL: http://[Map service REST URL]/MapServer/find?searchText=hel&searchFields=&sr=&layers=2&layerDefs=&returnGeometry=true&maxAllowableOffset=&geometryPrecision=&dynamicLayers=&returnZ=false&returnM=false&gdbVersion=&f=pjson Response JSON: { "results": [   ] } So, I'm really lost here. It seems, that when contains parameter is omitted from the REST's Find request URL => the value of false is actually assumed by default instead of true, and, consequently, only exact matches are performed. Please, advise. Alexander. ... View more