POST
|
@DavidVanValkenburgh Sure, one of us will get in touch with you via direct message
... View more
03-08-2021
01:30 PM
|
0
|
0
|
829
|
POST
|
Of course! We'll contact you via direct message on the upcoming API.
... View more
02-04-2021
04:01 PM
|
0
|
0
|
913
|
POST
|
While we don't do device management per se, the next release includes API that enables you to easily connect to an EAAccessory with the protocol strings. We manage the streams and push NMEA messages internally. I'm happy to provide more info on that if you are interested in trying it out. We also don't certify devices or specific models and that's part of why we do not provide protocol identifiers for each. Our fields apps like Collector do have a list of receivers that they support but again they also don't share identifiers for those.
... View more
02-04-2021
03:46 PM
|
0
|
2
|
920
|
POST
|
Hello Michael, Our SDK is GNSS hardware agnostic, as long as the receiver is able to provide NMEA messages. With 100.10 version, you'll have to establish connection, create session, extract the NMEA messages appropriately and push to our NMEALocationDataSource. Runtime will then extract the location information for that and propogate it through our API. We are currently working on some coarse grained APIs that would simplify reading NMEA data from the device. We are hoping these would be device agnostic as well. If you are interested in trying them out with your devices and give us feedback, I can reach out to you over email. Regarding GNSS hardware IDs, we don't work with those. You can get the protocol strings of a connected bluetooth accessory like so: for accessory in EAAccessoryManager.shared().connectedAccessories {
print("accessory: \(accessory)")
print("protocol: \(accessory.protocolStrings)")
} Thanks, Suganya
... View more
02-03-2021
07:56 AM
|
0
|
0
|
930
|
POST
|
Hello Todd, `table` is declared as a local variable in the method and therefore goes out of scope by the time the query is complete and the call back can be fired. That's probably why you don't see anything. You can declare the table as a property on your class so it's retained. A second option is you can access the table/its properties within the query call back, so it's held on to without being released. You may not have a reason to do this in which case the first option is recommended where the table is defined at a broader scope so it can be retained Option 1: class VC {
let table = AGSServiceFeatureTable(url: URL(string: PGRLAYERURL)!)
func getCountsInGeometry(creds: AGSCredential?, polygon: AGSGeometry?, bufferPoint: AGSPoint, query: String) {
...
}
} Option 2: table.populateFromService(with: queryParams, clearCache: true, outFields: ["*"]) { (results, error) in
// Access table or its properties here, so it can be retained.
...
} When you create a layer from a table, and add the layer to a map, the map holds on its layers (and the layer to its backing table), and that's why you don't see the issue in that case. Hope that helps! Suganya
... View more
11-19-2019
11:29 AM
|
1
|
1
|
379
|
POST
|
Thanks for the clarification. Unfortunately, we do not offer the capability right now for the rectangular envelope to be always upright. We can consider that feature for a future release.
... View more
07-29-2019
01:21 PM
|
0
|
0
|
547
|
POST
|
Can you please clarify your question? I don't understand if your question is about the rectangular envelope or just sketch moving along with the map? SketchEditor is added to the map view, so it sticks to the map while the map rotates. This is intentional since the sketch is usually drawn based on the contents of the map, and we want to maintain that relationship when the map is rotated. However, the sketch alone can be rotated, irrespective of the map's rotation. The rectangular envelope around the sketch is responsible for it. You can disable that by setting `sketchEditor.editConfiguration.allowRotate = false`. If you can provide further details, I'd be happy to help you.
... View more
07-29-2019
12:29 PM
|
0
|
2
|
547
|
POST
|
You can consume and render heat maps in Runtime starting with version 100.1, provided the renderer is authored in your existing map from Pro or Online. See ArcGIS Runtime SDK for iOS: AGSHeatmapRenderer Class Reference We do not support authoring heat map renderer in Runtime at the moment. Hope that helps!
... View more
05-20-2019
01:07 PM
|
0
|
0
|
340
|
POST
|
This has been fixed in the upcoming 100.5 release. Thanks, Suganya
... View more
03-29-2019
11:06 AM
|
2
|
0
|
1083
|
POST
|
Greg, I tested the service in the sample in a stand alone application using the same identify method as you did, and I get correct results. Since this is a map image layer, I wonder if you are checking the sublayers for the results? I've attached the code I used in its entirety (as a text doc). Let me know how it works against your service Suganya
... View more
01-25-2019
03:31 PM
|
0
|
1
|
374
|
POST
|
Hello Arthur, Unfortunately that's still the case. We do not have support for it yet or a workaround, I've raised the issue with the team. Thanks, Suganya
... View more
01-25-2019
01:00 PM
|
1
|
0
|
273
|
POST
|
Hello, it's hard to say what's wrong without having tried your service, but can you provide some additional information? - Are there overlapping features where you tap on your map? - Which device are you using? - Is it possible to share your service, if not, can you see if you can reproduce the problem with the service in the samples app? If I understand the problem correctly, you get incorrect results on identify, is that correct? Thanks, Suganya
... View more
01-25-2019
12:38 PM
|
0
|
3
|
374
|
POST
|
Hello, Which version of the SDK are you using, and what level license did you set?
... View more
01-25-2019
12:34 PM
|
0
|
9
|
1045
|
POST
|
Yes, it would. A feature created just exists in memory whereas an update operation is done on the table. canUpdateFeature would return true after you've added the feature to the table using add method.
... View more
01-08-2019
04:23 PM
|
0
|
0
|
298
|
POST
|
That is correct. For new features, you would first create a feature using one of the create methods on AGSGeodatabaseFeatureTable. Once created, you can add the feature to the table using the add method. For existing features, you typically get a reference to the feature first (query, identify etc), edit and call the update method. Hope that helps.
... View more
01-08-2019
03:59 PM
|
1
|
2
|
298
|
Title | Kudos | Posted |
---|---|---|
1 | 08-04-2015 12:58 PM | |
1 | 01-08-2019 03:59 PM | |
1 | 05-16-2016 11:22 AM | |
1 | 11-19-2019 11:29 AM | |
1 | 11-28-2016 10:01 AM |
Online Status |
Offline
|
Date Last Visited |
06-05-2023
05:23 PM
|