POST
|
Yes, we are observing this behavior on a service hosted on a 10.5.1 server that doesn't support pbf format.
... View more
10-19-2020
12:58 PM
|
0
|
0
|
1679
|
POST
|
Exact same here. We also saw that eventually the browser (Chrome) would crash with an "Oh snap" error on the page.
... View more
10-19-2020
12:34 PM
|
0
|
0
|
1679
|
POST
|
Ah, I didn't know that about the ES classes and the Esri API. I'm having a look at the Accessor stuff in there but haven't had a lot of success yet. Maybe because I'm using esri-loader in this project (it's a create-react-app project). I'll fiddle with it some more and see if I can get it to work this way, otherwise I can refactor the code and workaround it. Thanks again for your help.
... View more
07-29-2020
01:37 PM
|
0
|
0
|
1245
|
POST
|
At 4.16, extending the FeatureLayer no longer works. We have a feature layer where we set the source property in the constructor to generate some graphics on the client side. For this layer in particular, we extended FeatureLayer to add a few helper methods that lets us talk to our internal API. At 4.15, this worked as expected, however at 4.16, we now get an error: "Feature layer must be created with either a url or a source". Inspecting the output, the source property is undefined so at some point along the line the constructor is failing if the class extended. Codepen Example: https://codepen.io/tatkins/pen/JjGQYqp Just swap from 4.16 to 4.15 in the api url and the layer will work. For example: class ExtendedLayer extends FeatureLayer {
constructor(props) {
super(props);
}
}
const layer = new ExtendedLayer({...})
At 4.16 this will fail but will work correctly at 4.15. Any insight is appreciated.
... View more
07-29-2020
11:28 AM
|
0
|
3
|
1319
|
POST
|
Yeah, that's what I'm doing. It's not a showstopper but using Typescript on all our projects does make it more of a hassle to workaround.
... View more
07-22-2020
10:43 AM
|
0
|
0
|
442
|
POST
|
With 4.16, the properties of DrawPointAction changed, however the documentation and the Typescript typings do not reflect this change. In 4.15, one could get the coordinates of the DrawPointAction using the coordinates property. At 4.16, this property is now called vertices, however neither the documentation nor the Typescript typings reflect this change. I have not investigated other draw action events so not sure if they are similarly affected or not, but just wanted to give a heads up so the docs and typings can be updated.
... View more
07-21-2020
05:38 PM
|
0
|
2
|
486
|
POST
|
Yeah I think you're on the right track and to me (as a non vue guy, lol) it looks like your solution is a good one. Glad you got it working.
... View more
02-06-2020
04:26 AM
|
1
|
0
|
1543
|
POST
|
I will preface that I'm not familiar with vue but I do something similar to what you're doing in React... Are you instantiating your map and map components with esri-loader? Or are you doing it the "regular" way outside of vue? If using esri-loader could you use the bullt-in methods in vue to observe your store updates change then update the def query? In React, I use the Context API that stores the various bits of data that go into the def query and the user can manipulate this data via some UI. On UI input, it updates the def query and my map component (technically a layer component) sees that update through the native React Context API and and updates the layer's def query as needed.
... View more
02-05-2020
09:59 AM
|
0
|
0
|
1543
|
POST
|
Robert, yeah, I saw that, unfortunately `actionsMenuEnabled` doesn't exist on `view.popup` at least at 4.13 and 4.14. Neither in the type definitions nor if I just inspect it in the console.
... View more
01-20-2020
04:19 PM
|
0
|
2
|
749
|
POST
|
Using 4.14 (and it did it at 4.13 too), the popup actions seem to be maxed out a 2 before it starts hiding them behind a .... button. Is there a way to override this? We only use icons for our actions thus I have plenty of room to show the buttons before they're hidden. I've seen previous threads that say to use view.popup.actionsMenuEnabled, however this property does not appear to exist anymore. Is there a workaround for this or am I barking up the wrong tree? Thanks all.
... View more
01-16-2020
03:27 PM
|
0
|
4
|
873
|
POST
|
Wow thanks for the code! It works very nicely for what I'm trying to do. I'll buy you a beer in Palm Springs, haha. I would also posit that this may be worth putting in the examples section for those trying to use the Living Atlas demographic layer.
... View more
11-22-2019
07:06 AM
|
1
|
1
|
786
|
POST
|
No problem, thanks for the input. I think what I'll try next is just craft a query and hit the rest endpoint directly with URLSession.
... View more
11-21-2019
06:01 PM
|
0
|
4
|
786
|
POST
|
So I gave this a try but I'm getting an error: "Cannot call this method in this context". Here's an example of what I'm doing. Watching the requests in Charles I see it requesting the layer's info (http://demographics9.arcgis.com/arcgis/rest/services/USA_Demographics_and_Boundaries_2019/MapServer/3?f=json&returnAdvan… ) which includes a listing of all 2,075 fields in that layer. Is this issue possibly why the request is failing or am I making some other sort of rookie mistake here? func doQuery(mapPoint: AGSPoint, mapScale: Double) {
var layerId: Int?
self.layer.subLayerContents.forEach { subLayer in
guard let sl = subLayer as? AGSArcGISMapImageSublayer else {
return
}
if sl.isVisible(atScale: mapScale) && sl.sublayerID > 2 {
layerId = sl.sublayerID
}
}
guard layerId != nil else {
return
}
let queryParams = AGSQueryParameters()
queryParams.geometry = mapPoint
queryParams.spatialRelationship = .intersects
queryParams.returnGeometry = false
// queryParams.whereClause = "OBJECTID = 1000"
guard let url = URL(string: "\(DEMOGRAPHICSURL)/\(String(describing: layerId!))") else {
return
}
print("\(DEMOGRAPHICSURL)/\(String(describing: layerId!))")
let table = AGSServiceFeatureTable(url: url)
table.featureRequestMode = .manualCache
table.credential = self.loginState.agolCreds
table.populateFromService(with: queryParams, clearCache: true, outFields: ["OBJECTID"]) {(results, error) in
let strongTable = table
guard error == nil else {
print("Error doing demographic identify. \(error?.localizedDescription ?? "N/A")")
return
}
guard let features = results?.featureEnumerator().allObjects else {
return
}
features.forEach { feature in
print(feature.attributes)
}
}
}
... View more
11-21-2019
02:40 PM
|
0
|
6
|
786
|
POST
|
So I've created an AGSServiceFeatureTable and trying to populate it with features based on a query, however it doesn't seem to be completing. I don't get an error or anything and watching the url requests in Charles show's no network requests being made. The endpoint url and whereClause query I'm using is the same as a separate table i've used as a source for a Feature Layer on the map and it draws correctly. Am I missing something here (likely! haha) or is something else wrong here? func getCountsInGeometry(creds: AGSCredential?, polygon: AGSGeometry?, bufferPoint: AGSPoint, query: String) {
print("getting counts")
guard let polygon = polygon as? AGSPolygon else {
return
}
let table = AGSServiceFeatureTable(url: URL(string: PGRLAYERURL)!)
table.featureRequestMode = .manualCache
table.credential = creds
let queryParams = AGSQueryParameters()
queryParams.geometry = polygon
queryParams.spatialRelationship = .intersects
queryParams.returnGeometry = true
queryParams.whereClause = query
table.populateFromService(with: queryParams, clearCache: true, outFields: ["*"]) { (results, error) in
print("done populateFromService")
guard error == nil else {
print("Error \(error?.localizedDescription)")
return
}
print(results?.featureEnumerator().allObjects.count)
}
}
... View more
11-19-2019
10:11 AM
|
0
|
2
|
581
|
Title | Kudos | Posted |
---|---|---|
1 | 08-23-2018 06:35 AM | |
1 | 08-23-2018 06:31 AM | |
1 | 09-24-2019 01:11 PM | |
1 | 10-25-2018 06:01 PM | |
1 | 10-23-2017 12:51 PM |
Online Status |
Offline
|
Date Last Visited |
06-13-2024
02:30 PM
|