Latest Contributions by Nicholas-Furness

‎09-14-2013

This link had me struggling for many hours (please avoid): https://developers.geoloqi.com/ios/maps Hi Carol. I'm intrigued to learn what you struggled with in that blog post. It seems to reflect exactly how we describe setting up projects in the main tutorial you reference elsewhere (and how I set up all my samples). I've not had any difficulty including AGSMapView in a view hierarchy, including as part of a Tab View Controller, so I'd be happy to look into it further with you since we're always keen to know if we can improve documentation. Please let me know. Cheers! Nick.

‎09-13-2013

Hi Hussein. Note that in your screenshot the drop-pin symbology is not blurry, it's just the map tiles. This is because the Geocode sample is using a basemap tile service (http://services.arcgisonline.com/ArcGIS/rest/services/ESRI_StreetMap_World_2D/MapServer) which is no longer updated and which doesn't have global coverage for all zoom levels. If you were to zoom in to that level in the US, you would not see the blurring. Really the sample (and you) should be using http://services.arcgisonline.com/ArcGIS/rest/services/World_Street_Map/MapServer. That tile service is the same as used by the basemap picker at ArcGIS Online and by the ArcGIS iOS App. Incidentally, in your screenshot of the app, it's using the Topographic Basemap, not the Streets Basemap. It's a multi-step process to look at an ArcGIS Online basemap and work out the URL to use, so I have created this reference page which may help: https://github.com/nixta/arcgis/wiki/Basemap-URLs Please let me know whether this resolves your issue. Nick. P.S. I have asked that the sample be updated to use the current tile sets.

‎08-06-2013

Could be. Depends on what the projection is of your map. I'm guessing it's not Web Mercator 😄 My solution will generate you a polygon that is pretty close to circular on the ground (i.e the edge is R miles north and R miles east of the center). If you are using a Web Mercator projection, it will appear circular on the map. If you are using WGS84 for example, it will indeed appear less tall as you move north or south from the equator, by virtue of the projection. If you want something that looks circular on a WGS84 map, and you know that your center point is WGS84, you can either use your & Technobrat's solution or something like this: -(AGSPolygon*) circleWithCenter:(AGSPoint*)point radius:(double)radiusInMiles { AGSGeometryEngine *ge = [AGSGeometryEngine defaultGeometryEngine]; // Get a "circle" around the point, using the 1 decimal degree ~= 69 miles. AGSPolygon *circle = [ge bufferGeometry:point byDistance:radiusInMiles/69]; return circle; } But remember that this is approximating the conversion between decimal degrees and meters, which is not constant for longitude as latitude varies. So, it really depends on what you are generating the 10 mile radius geometry for and (in short) how far north or south of the equator. Your solution may be good enough for what you want, but bear in mind that a degree of longitude will be very much less than 69 miles as you approach the poles. On the other hand, your application users may keep asking you why the "circle" is elliptical, and that might be a bigger headache than considering some things that might be more than 10 miles away.

‎08-06-2013

The units will be decimal degrees. What you might find useful is to buffer around your center-point. Try something like this: -(AGSPolygon*) circleWithCenter:(AGSPoint*)point radius:(double)radiusInMiles { AGSGeometryEngine *ge = [AGSGeometryEngine defaultGeometryEngine]; // Get a point in a spatial reference whose unit is Meters. AGSPoint *pointToBufferAround = (AGSPoint *)[ge projectGeometry:point toSpatialReference:[AGSSpatialReference webMercatorSpatialReference]]; // Get a "circle" around it, using the unit Meters (1 mile ~= 1609.344 meters). AGSPolygon *circle = [ge bufferGeometry:pointToBufferAround byDistance:radiusInMiles*1609.344]; // Project the output back to the projection of the input point (which is presumably what you're after). circle = (AGSPolygon *)[ge projectGeometry:circle toSpatialReference:point.spatialReference]; return circle; } That will use Meters (WebMercator's units). Note that your output may not be what you expect as the input or output approaches the poles. Also, there's no guarantee how many points the output polygon will have in its boundary.

‎06-03-2013

It's quite tricky to positioning the element on the User interface without adding them to the MapView-element. I succeed only positioning the element by the attributes. As I am new to all of this, i hope this helps you too. 😄 Hey Tom. Yep, this is pretty annoying Xcode behavior for me too. I've found the following have really helped me: Drop new UI components into the hierarchy on the left rather than directly into the WYSIWYG editor. Use the cursor keys to move the element. Hold SHIFT while using the cursor keys to move the component quicker. Hold OPTION while using the cursor keys to show position attributes. You can drag to resize a UI component without changing its position in the hierarchy (but drag to move will). COMMAND-Z is your best friend if you drop a control in the wrong spot 😄 Hope that helps too. Cheers, Nick.

‎01-10-2013

This has happened to me once but I couldn't reproduce it. I fixed it by uninstalling from wherever it got installed and running the installer package again. Then it was in the ~/Library... location. I can't quite recall but I may also have rebooted between uninstalling and reinstalling. I'm not happy with this answer, but it might get you going again until the real answer appears 🙂 Let me know whether it works? Cheers, Nick P.S. Caveat: I'm not on the iOS team - they might have a better idea of the problem. EDIT: Ah yes. Now I see your response below, I recall that I had to manually delete the /Library/SDKs directory (not ~/Library/SDKs, mind you!) and the /Library/Application Support/AGSiOSRuntimeSDK directory because, as Divesh mentions, the uninstall script doesn't touch those 🙂 Once I'd deleted those (and made sure I didn't have one under ~/Library), I just tried again and it worked. However, I'm not so confident that'll work for you given your other replies. Nick.

‎12-31-2012

You cannot just cast an AGSEnvelope to AGSMutableEnvelope (see here). Try something like this: AGSMutableEnvelope * env2 = nil; if([featureSet.features count]>0) { for (int i=0 ; i<[featureSet.features count]; i++ ) { graphic=[featureSet.features objectAtIndex:i]; if (env2 == nil) { // graphic.geometry.envelope is an AGSEnvelope // We need to derive a new AGSMutableEnvelope from it. env2=[graphic.geometry.envelope mutableCopy]; } else { // This is not the first graphic we've come across, so we'll // extend the working envelope (env2) to include it [env2 unionWithEnvelope:graphic.geometry.envelope]; } // Add the graphic to our graphics layer graphic.symbol=fillSymbol; [self.graphicsProjectQryLayer addGraphic:graphic]; } // env2 will now contain all the graphics we just looped over. // Refresh the graphics layer [self.graphicsProjectQryLayer dataChanged]; } This is typical with Cocoa development and Mutable versions of classes. You can generally cast a Mutable object to its non-mutable form (typically it's parent class, so an NSMutableArray is a NSArray), but the other way around requires a new object of some sort.

‎07-11-2012

Afraid not, so I wrote you one 🙂 For simplicity, I load up a few WebMaps ahead of time (you might want to do this on-the-fly in your app). I'll use these as basemap options. I'll also load up one WebMap with actual content. When the user picks a different basemap, I reference the content WebMap and the appropriate basemap WebMap. The only additional trick is to store and set the extent "around" the basemap change, otherwise each basemap change returns the map view to the content WebMap's default (saved) extent. I also don't initially set the basemap, but just rely on the "Content" basemap. You'd want to take care of that in a real app. Hope this helps, Nick.

‎07-11-2012

Hi John, Have you looked at AGSWebMap::openIntoMapView:withAlternateBaseMap: and AGSWebMap::openIntoMapView:withAlternateBaseMap:resetMapView:? If you have an AGSWebMap whose basemap layers you want to use, use the AGSWebMap::baseMap property to get an AGSWebMapBaseMap object, and pass that in to one of the above function on the AGSWebMap whose basemap you want to update. Note, you could just use the stock basemaps (although Bing and OSM may be special cases) rather than creating your own. Hope this helps, though I'm not 100% sure I understood your question. Nick.

‎03-16-2012

Hey Rob, I *think* I see what you're saying now, but if so I don't see what could be going wrong so it may be time to look at some code. Could you attach a project here for me to look at, PM me or send me an email (use my forum ID at esri.com)? Cheers, Nick.

‎03-16-2012

Hi Anoop, In short, since everything used by the web and mobile SDKs is being projected onto a flat (2D) surface, it will need to have a spatial reference (essentially a set of rules describing that projection). Many web/mobile maps use spatial reference 102100 (Web Mercator Auxiliary Sphere). This is good for display. It's what consumers have come to expect (hence why many of our basemaps use that spatial reference). But it's probably not best way to store geodata in most parts of the world, so you may encounter various spatial references across the data you use. In the documentation you quote, the gist is this: The first layer you add to the map will define the map's spatial reference. Once the map's spatial reference is set, all data will display in that spatial reference. Because Tiled Layers are cached in a predefined spatial reference, they cannot be re-projected on the fly (re-projecting takes effort, so it would defeat the purpose of caching them!). That is why the spatial reference of tiled layers must match the spatial reference of the map. Because Dynamic Layers are not cached, they may be projected on-the-fly. So while they must have a spatial reference describing the stored data, they can be re-projected to the map's spatial reference on request. Again, this can take effort on the server or client, so it's a balancing act, but in practice in most cases you'll be OK. See also here and here to learn more about Tiled and Dynamic layers. As for your example, the service is a GlobeServer service. You cannot use this with the mobile or web SDKs. Instead, here is the 2D equivalent. Note the type is Feature Layer. Because it's for use in 2D, it has a spatial reference. [Note also, it's in extended support and you should really use this.] Hope this clears things up a little. Cheers, Nick.

‎03-16-2012

Hi Robert, I'm not entirely sure I understand what you're asking, so please set me straight if I've got it wrong, but I think you want to have a UIView displayed above the AGSMapView and you want it active (i.e. the user can interact with it) only some of the time? Take a look at this post. You could set the userInteractionEnabled property of the UIView displayed above the map to control whether it traps UI events or not. Set it to NO and the events pass right on through to the map. Again, apologies if I've misunderstood. Let me know. Cheers, Nick.

‎03-06-2012

Hi Joshua, You need to set the map view's layer delegate. Add this line to your viewDidLoad method: self.mapView.layerDelegate = self; Edit: Also, see Nimesh's answer below. That should get you into the mapViewDidLoad: method. Cheers, Nick.

‎03-05-2012

For 10.0, the toolset is arranged differently but attacks the same problems. I should also point out that at ArcGIS for Server v10, you can use the maxAllowableOffset property of an AGSFeatureLayer to generalize on-the-fly. This blog post covers the topic. Nick.

‎03-02-2012

Hi Anoop, Good questions. Much of this is outside the scope of this thread and forum, but I'll try to give you some pointers. I didn't knew about generalization and our server version is 9.31. This is something we should implement on server side rite? Yes, server-side. And also how can we know if a layer is not generalized? Generalization is merely the process of reducing the "resolution" of your vector data to a level that suits your purposes (in this case, rendering at given zoom levels). For example, a polyline with thousands of points in it which is good for plotting a wall-sized map may only need one tenth the number of points to look exactly the same on a small screen. A better question might be: How do you know whether a feature class needs generalizing? Let's just consider viewing the data (editing is another issue, and the general rule is not to edit generalized data directly). And remember this discussion is for dynamic layers only (i.e. not tiled layers). [INDENT] Ex. 1: You could have a problem if you zoom in on a polyline or polygon layer much further than your app needs and can still see a lot of detail. That means that when you're zoomed at a working level, the data is too detailed for what you can see at that scale. Ex. 2: You could perhaps have a polygon that is the right level of detail, but that is much larger than your visible working area. The single polygon still needs to be pulled over in its entirety for rendering. Solving that can be a whole separate discussion. Ex. 3: You might find (as is possibly the case here) that the data is more detailed than your client specifications allow for, and so you'd want to create a generalized set of that data just for that client app. [/INDENT] There is a lot to consider. Client limitations, bandwidth, managing the data, data updates, editing. The 9.3 documentation has a short discussion on the topic and overview of the operations. You will need an ArcInfo license to use most of the tools (you'll probably need "Simplify Polygon"). For 10.0, the toolset is arranged differently but attacks the same problems. I do work with many complex layers with boundary of various states, municipalities etc. To be exact all the layers have some kind of complex irregular graphics in it 😞 If it were me, the first thing I would do is try to show that it is these complex layers that are causing your memory issue. Either use the profiler, or create a test set of generalized layers and use those. If so, try to categorize your feature classes: "Needs generalizing" (causes a memory warning), "could do with generalizing" (takes a while to load, but doesn't cause a memory warning), and "fine as it is". That should put you in a better position to work out your next steps (and longer term data management goals if necessary). Hope this helps a little, Nick.

My Ideas

Latest Contributions by Nicholas-Furness

Re: AGSMapView not working in Tab View Controller

Re: Retina Display Issue: Fuzzy Symbology and Tile Imagery

Re: Radius of a circle drawn as a polygon

Re: Radius of a circle drawn as a polygon

Re: Assertion Failure in AGSMapView layoutSublayersOfLayer

Re: Installation issues of the new ArcGIS Runtime SDK for iOS V10.1.1.142

Re: Unable to union two AGSEnvelope with unionWithEnvelope

Re: Changing Map type based on navigation toolbar button

Re: Changing Map type based on navigation toolbar button

Re: Capture touch events on UIView used as an overlay for a map view

Re: Is validation required before adding a Map Layer to MapView?

Re: Capture touch events on UIView used as an overlay for a map view

Re: Cannot initiate GPS/Location Services

Re: Memory Management tips when multiple layers are added to AGSMapView

Re: Memory Management tips when multiple layers are added to AGSMapView

200.8.2 LTS patch for ArcGIS Maps SDKs for Native ...

Re: Spatial Share Testers on Vision Pro

Introducing ArcGIS Maps SDKs for Native Apps 300.0

200.8.1 LTS patch for ArcGIS Maps SDKs for Native ...

Re: Distribution with Lite license