Latest Contributions by DiveshGoyal

Hi, Tariq - A couple of suggestions : 1) Do you have the returnDirections property on AGSRouteTaskParameters set to YES? If so, you can try setting the returnRouteGraphics property to NO. This is because, you're essentially getting the entire route geometry twice if both these properties are enabled. The only difference is that the entire route is broken into smaller units as part of the directions. 2) You can try generalizing the route geometry through the outputGeometryPrecision property on AGSRouteTaskParameters. By default, it is set to generalize using a distance of 5 meters, but you can increase this depending on how accurate you want the route geometry to be. The less accurate it is, the lesser vertices it will have and thus the size of the geometry will decrease. You may need to experiment to see what value works best for you without sacrificing too much accuracy and still keeping the size reasonable. ... View more

There are a couple of ways. 1. You can tweak the feature layer such that it only brings down OBJECTID & STATUS fields. Then, when a popup is created for a  graphic in this layer, it will only display information for these fields. featureLayer.outFields = [NSArray arrayWithObjects:@"OBJECTID", @"STATUS", @"Shape" nil]; 2. The feature layer can continue to bring down all the fields from the server, but you will need to dig into the AGSPopupInfo that is created for a graphic of this layer, and remove the metadata related to fields you don't want to display. AGSPopupInfo* info = [AGSPopupInfo popupInfoForGraphic:graphic];         //Filter the fields we want to display to the user     NSMutableArray* fieldInfos = [info.fieldInfos mutableCopy];     NSMutableArray* displayWorthyFields = [[[NSMutableArray alloc] init] autorelease];         for (AGSPopupFieldInfo* fieldInfo in fieldInfos) {         if([fieldInfo.fieldName isEqualToString:@"STATUS"] ){             [displayWorthyFields addObject:fieldInfo];         }     }         info.fieldInfos = displayWorthyFields; Note, we explicitly filter out the OBJECTID field in a popup because we don't recommend displaying that to an end user. ... View more

Thank you for your feedback. Map rotation is currently not supported (v2.0). We hope to support it in an upcoming version. ... View more

This will be fixed in the next release. ... View more

Rick, you are not missing anything. The API primarily works in connected mode - most of the heavy lifting is done on a remote server. The tasks take in a URL because they are just proxies to the capabilities on the server. They don't provide any functionality when the device is offline. ... View more

This should help you get started with the query task : http://help.arcgis.com/en/arcgismobile/10.0/apis/iOS/1.8/concepts/index.html#/Query_Task/00pw00000016000000/ ... View more

The behavior you described is not expected. Can you please share your code? ... View more

You're absolutely right. Thanks for reporting this. ... View more

I spoke too soon. I was able to get it to work. Are you sure you have initialized your error variable to nil? NSError* error = nil; ... View more

This doc contains instructions on how to set up your Xcode project : http://help.arcgis.com/en/arcgismobile/10.0/apis/iOS/1.8/concepts/index.html#/Creating_a_New_Xcode_Project/00pw00000044000000/ ... View more

This appears to be a bug. Thanks for reporting it. ... View more

Have you looked at Simple KML ? https://github.com/incanus/Simple-KML/ ... View more

When using the initWithLayerDefinitionJSON method (what we refer to as feature collections), definition expressions are not honoured. ... View more

That is one way. Another way is to use the AGSQueryTask and execute a SQL query (such as "1=1") to get all the features from a particular layer. You'd have to do this for every layer in the service whose features you want. Note, the number of features returned by query and identify task are limited by the 'max record count' setting on the service. At version 10, it defaults to 1000 features. You may need to bump it up if you want to retrieve more features in a single request. ... View more

The setting affects any query performed against the service. If you set the initial extent of the map such that it contains only 500 features, you'll get to see all of them. But if you zoom out later to an extent that, say, contains 3000 features, you will only see the *first* n features (where n is the 'max record count' property of the service) ... View more