|
POST
|
Thank you for the clarification. I'm going to pull in a colleague familiar with the intricacies of Authentication to help out. One of us will reply with feedback. -Mark
... View more
11-02-2022
02:30 PM
|
1
|
0
|
2046
|
|
POST
|
Hello, sorry to hear you are having issues. Which method(s) are you using to create the AGSFeatureLayer? If you're using an `AGSServiceFeatureTable` to create the layer, you can simply set a credential on it, so you don't have to mess with tokens or anything else. If the service can be authenticated on different environments, then you should be all set. `AGSServiceFeatureTable` inherits from `AGSRemoteResource`. That protocol has a `credential` property that you can use to prevent authentication challenges from being displayed to the user (provided the credential is valid for the resource you're trying to access). All classes that inherit from `AGSRemoteResource` operate that way. Give that a try and if it doesn't work I'll be more than happy to dig into it further with you. -Mark
... View more
11-02-2022
08:59 AM
|
0
|
2
|
2056
|
|
POST
|
I created a similar scenario, based on your information. It seems to be working for me, but let me know if this mimic's your situation. The items in the list view are `AGSPopup`s. They don't have a title, so I'm simply using the "popup.geoElement.geometry.description" as the text in the table view cell. Tapping on a row creates a new "AGSPopupsViewController" with a single Popup and then pushes it onto the navigation stack: "navigationController?.pushViewController(popupsViewController, animated: true)" I'm using Xcode 14 and the iPad Pro (9.7-inch) iOS 16 simulator. Let me know how well this matches your code; if you are able provide some code that reproduces the issue in a simple project, that would help. Mark
... View more
09-16-2022
02:27 PM
|
0
|
1
|
1022
|
|
POST
|
Sorry to hear you are having problems. I have tested the basic scenario with the "AGSPopupsViewController" and did not see any issues with iOS 16 (or iOS 15.5) in the simulator. If you could provide a bit more information about what context you're displaying the popups from I can help you resolve your issue. You said you're using iOS 16. Are you running on a device or simulator (or doesn't it matter)? If you could provide some screen shots of what you're seeing that would be great. Also, some more information on what the view controller hierarchy is, either through some sample code/pseudo code/screen shots, that would help. -Mark
... View more
09-15-2022
09:57 AM
|
0
|
3
|
1032
|
|
BLOG
|
This release includes: - Augmented reality (AR) - Remove use of the deprecated `ARSCNView.hitTest` method. See this issue. - Augmented reality (AR) - Fix crash in AR Example. See this issue. - The minimum supported iOS version is now 14.0, to match the Runtime SDK. You can find the Toolkit here. See this blog post for information on the SDK release. We hope you enjoy the new release! Let us know what you're building with it.
... View more
08-17-2022
12:11 PM
|
1
|
0
|
487
|
|
POST
|
Thank you for the code, it helped reproduce things here. After speaking with a member of our 3D team, I found a solution to your problem. The LocationToScreen method takes an input MapPoint but its not aware of SurfacePlacement modes unlike Graphics in a Layer. The MapPoint will be treated as absolute. To work around this, you will need to retrieve the elevation value for the X,Y of the point and add it to the Z value of the graphic/geometry you want to input into the LocationToScreen method. sceneView.scene?.baseSurface?.elevation(for:, completion:) will retrieve the elevation, which you would then add to the Z value of your point. I realize you mentioned that method earlier, and that it is asynchronous, but hopefully it won't be too difficult to incorporate it into your code. Let me know if I can be of further assistance, Mark
... View more
07-21-2022
03:12 PM
|
0
|
0
|
1091
|
|
POST
|
I've tried a few things out on my end, but to make sure I'm understanding things correctly, can you send me the coordinates and SR of the `AGSPoint` used to draw the graphic? Also, the `SceneView`s `currentViewpointCamera`? I can then replicate what you're seeing. For example: print("currentViewpointCamera: \(sceneView.currentViewpointCamera())") print("geometry = \(g.geometry)") Which gives this output: currentViewpointCamera: AGSCamera: heading: 330.00, pitch: 97.00, roll: 0.00, location: AGSPoint: (-4.459500, 48.388900, 80.000000, nan), sr: 4326 geometry = Optional(AGSPoint: (-4.460926, 48.390397, 71.284401, nan), sr: 4326) If you could also provide the elevation source you are using (if it's OK to share), that would be great. That way I can recreate the issue here and delve into it some more. Thank you for your patience! Mark
... View more
07-20-2022
02:55 PM
|
0
|
0
|
1100
|
|
POST
|
Sorry, I think I misunderstood your initial question, which was to get a screen location. So, obviously, screenToBaseSurface won't work. What do you want to do with the screen point once you have it? The screen location of a particular map point/graphic/feature will change as the map is panned/zoomed. What kind of issues are you seeing with AGSSceneView.locationToScreen? A screen shot would be helpful, if possible. Thanks, Mark
... View more
07-18-2022
12:14 PM
|
0
|
0
|
1112
|
|
POST
|
Thank you for your question! There are a couple of things you can try. - You can try using the - (AGSPoint *)screenToBaseSurface:(CGPoint)screenPoint; method instead. That method Converts the specified screen point to a location on the base surface i.e. ignoring any 3D features/graphics on or above the surface that may be intersecting the screen point. The location returned will have a z-value corresponding to the elevation at the intersecting surface. - Depending on if your features/graphics are in a layer or in a graphics overlay, look at the AGSSurfacePlacement and AGSLayerSceneProperties classes. AGSLayerSceneProperties has a AGSSurfacePlacement property, which specifies how data belonging to the layer should be placed in relation to the scene's surface. Both AGSGraphicsOverlay and AGSFeatureLayer have a AGSLayerSceneProperties property which you can use to specify how the data is placed. If that doesn't solve your issue, or if you have more questions, please reach out! Mark
... View more
07-18-2022
08:17 AM
|
0
|
0
|
1121
|
|
POST
|
Hello! Thank you for your question. You are correct, the "AGSArcGISMapImageLayer" does not have an option to change the symbology, but the sublayers of that layer do have that option. They have a renderer property which allows you to set symbology that will be used to render that layer. You need to find the sublayer you want to change, create a renderer, and assign that renderer to the "renderer" property. let mapImageSublayer = mapImageLayer.mapImageSublayers[index] as! AGSArcGISMapImageSublayer let simpleRenderer = AGSSimpleRenderer(symbol: AGSSimpleMarkerSymbol(style: .cross, color: .red, size: 12)) mapImageSublayer.renderer = simpleRenderer You need to make sure your layers support dynamic layers ("Supports Dynamic Layers: true"). See this blog post for more information. If you have more questions, let us know! Mark
... View more
07-06-2022
02:18 PM
|
1
|
1
|
1500
|
|
BLOG
|
This release includes: - FloorFilter - a new component which simplifies visualization of GIS data for a specific floor of a building in your application. See the documentation here. - The "basemap type" and "static basemap" initializers have been deprecated in the SDK at 100.14. They have been replaced by the "basemap style" initializers/methods. See this issue. - Fix new linter warnings resulting from "SwiftLint 0.47.1". - Replace the deprecated AGSLocationDataSource.stop() method with stopWithCompletion:. You can find the Toolkit here. See this blog post for information on the SDK release. We hope you enjoy the new release! Let us know what you're building with it.
... View more
04-27-2022
12:57 PM
|
0
|
0
|
439
|
|
POST
|
Excellent, I'm glad you found the issue! If you have any more questions, please let us know! Mark
... View more
04-06-2022
12:07 PM
|
0
|
0
|
1689
|
|
POST
|
Ok, great, I'm glad you resolved the issue. If you have any other questions, please let us know. Mark
... View more
04-06-2022
09:37 AM
|
0
|
0
|
799
|
|
POST
|
Also, what version of the Runtime SDK for iOS are you using?
... View more
04-06-2022
09:20 AM
|
0
|
2
|
1692
|
|
POST
|
Sorry to hear that didn't resolve your problem. Can you send some sample lat/long values that you are using as inputs when initializing the "AGSPoint" and also any specifics of the basemap in your map (Are you using an AGOL basemap? What's the basemap's Spatial Reference?). Thanks, Mark
... View more
04-06-2022
09:19 AM
|
0
|
0
|
1692
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | 07-30-2025 09:41 AM | |
| 2 | 11-25-2024 01:58 PM | |
| 2 | 08-19-2024 02:33 PM | |
| 1 | 05-31-2023 09:26 AM | |
| 1 | 04-19-2023 08:58 AM |
| Online Status |
Offline
|
| Date Last Visited |
08-18-2025
09:06 AM
|