Latest Contributions by ShawnCastrianni

I can easily do this in a web browser by accessing the web interface to Query for that feature layer and specifying the OutField AND specifying DISTINCT as shown in this attachment: ... View more

That works!  I will go with this, but I should still write a test program since the other way did not work. ... View more

What is an example public feature service I can use in the test program? ... View more

I tried again, and I remembered CORRECTLY.  If I use Identify on a featurelayer and select that identified feature, selection works.  If I use Query on a featurelayer's servicefeaturetable, I can get back the correct feature, but when I try to select that feature, nothing happens.         public async override Task<bool> ShowWellInLayer(string uwi,string layerName,DataTypes dataType)         {             FeatureLayer featureLayer = GetMapLayerWithName(layerName) as FeatureLayer;             if (featureLayer == null)                 return(false);             QueryParameters parms = new QueryParameters {                 WhereClause = dataType.UWIESRIFieldName() + " = '" + uwi + "'"             };             FeatureQueryResult result = await ((ServiceFeatureTable)featureLayer.FeatureTable).QueryFeaturesAsync(parms, QueryFeatureFields.LoadAll);             Feature feature = result.FirstOrDefault();             if(feature != null) {                 //if (_mapCallback != null)                     //_mapCallback.MapCallout(feature);                 //if (_calloutCallback != null) {                     featureLayer.SelectFeature(feature);                     //_calloutCallback.ShowMapCalloutView();                 //}                 return (true);             }             return(false);         } ... View more

That is what I said near the beginning of this thread:  "I tried running a query to get the feature and then select that feature.  Nothing happened on the select."  Let me try again as maybe I am remembering wrong. ... View more

Thanks.  I may look into manual caching. It sounds like my guess of the two managed instances being different causing the select to not work was correct?  If the new feature layer design is to keep a low memory footprint, then I think it would be very important for the feature instances to not matter.  If I say select a feature with a different instance, it should use the OBJECTID of my instance and select the feature instance that IS loaded in the map with that same OBJECTID.  But I am just getting used to the new 100.X design so this may not make sense. I don't use the identify operation because I don't have any coordinates.  In addition to our map services, we also have data services from a different data source.  I have a non-map page that lists wells.  This list contains a UWI (Unique Well Identifier) property.  When the user clicks a row in this list, I want the corresponding well feature to be selected and called out in the map view.  So the only information I have is the UWI which is also one of the attributes on the feature graphic.  So I need to programmatically select a feature graphic on the map that is already loaded and visible with a query definition of "'UWI = 'ABCDEF"". Based on the information you are providing, it sounds like, I have 2 choices: Use manual caching where I control the ServiceFeatureTable and when items are loaded into cache using PopulateFromService.  I assume then that I can loop through the features in the ServiceFeatureTable since I am in manual cache mode and look for a feature with a specific UWI and then select it?  Or maybe I have to use FeatureCollectionTable?  Not sure, I haven't looked into manual caching yet. Keep everything the way it is, but when I want to select a feature based on UWI, I must first make a server query with that UWI to get back the lat,lon of that feature, then do an Identify using that lat,lon, then loop through all the features that came back from the identify since more than 1 can be in the same spot on the map and select the one with the correct UWI and open its callout? ... View more

Maybe if I try to explain what I am trying to do.  I want to programmatically select a feature and open its callout based on attribute values of that feature, not an x,y.  I tried running a query to get the feature (which I didn't want to do because if it goes to the server and back, it is a waste of time since the feature is already loaded and on the map) and then select that feature.  Nothing happened on the select.  My guess is because the feature I get back from the query is a different instance from the feature that was loaded on the map.  So I was looking for a way to find the feature that is already loaded on the map. One way to do that is IdentifyFeature, but that requires an x,y as if the user touched it.  I need QueryParameters to locate my feature using attributes already loaded on the map.  In the old days, I just manually looped through the Graphics collection available on all layers (including feature layers). ... View more

I will see if I can create a test program.  I do not have my hopes up as I have done a lot of experimentation here to try and narrow down what the problem is.  If my build machine creates the build, it runs fine.  it is only my dev machine that produces an app that crashes on startup.  If my other developer produces a build on his dev machine, it used to crash a few days ago but now it doesn't.  He did make a change to his machine within those few days which was to install the Xcode command line tools.  His machine now has the same version of xcode 4 and the command lines tools as the build machine and both produce good binaries.  My dev machine has xcode 5 with both ios 6 and 7 and a later version of command line tools.  If I build the app against ios 6, it crashes.  If I build the app against ios 7, it runs but then suffers from ios7 look and feel issues which I do not have time to address.  this symbol comes from Standard C++ and is the out_of_range exception class.  If you edit the file: /usr/include/c++/4.2.1/stdexcept you will see the out_of_range class which I believe is this undefined symbol.  So I cannot figure out what is the cause of the problem as it could be any one of the following variables: OSX Mountain Lion vs. Lion xcode 4 vs. 5 Xamarin vs. Objective C ios 6 vs. ios 7 While I try to create a test program, maybe all of this information about the Standard C++ stdexcept file might help you to figure something out on your end.  I do know that if I remove ArcGIS from my app, it starts up just fine. ... View more

I am the same guy that posted over on Xamarin as well.  I wonder if you guys are actually reading what I am typing as the name on this post matches the name on the post over in Xamarin so it was obvious it is the same post to two different user forums. Look, this is very simple.  If you run nm on the ArcGIS library, you will see several references to a symbol:          U __ZTISt12out_of_range That proves that the ArcGIS references this out_of_range symbol that is coming from an external source.  If you then run nm on CoreTelephony from iOS6, you get: 00059d94 D __ZTISt12out_of_range 00059d94 D __ZTISt12out_of_range This proves, along with the error message in my original post, that this symbol comes from CoreTelephony in iOS6.  However, if you run the same nm command on CoreTelephony from iOS7, you get NOTHING!  This proves that Apple either removed this symbol or moved it somewhere else. I just ran nm on all the frameworks from iOS7 and I think I found it in AudioToolbox.  So I thought maybe I could solve this problem by adding AudioToolbox as an additional framework.  I tried that but I get the same error.  The error seems to imply that it needs to be in CoreTelephony?  I am not sure. As far as providing an example, why do you think that is necessary if you can run these nm commands yourself and verify what I am saying is true?  The error in my original post clearly states that this symbol is expected to be in CoreTelephony but the nm command shows that it is not there for iOS7. ... View more