|
POST
|
In testing out the 4.9 API, I'm running into and issue around CORS with demographics8.arcgis.com. We're pulling a MapImageLayer from this domain and it's throwing a CORS error in the console. I've tried esriConfig.request.trustedServers.push('https://demographics8.arcgis.com'); but that didn't help. Is there something else I need to do on my end? I'd really rather not setup a proxy since it was working in 4.8 but if that's what's required, then I'll do it. I'm wondering (hoping) if there's some issue on the Esri side for this? And for what it's worth, the legend for the layer does work--just the actual map part of the service is throwing this error. Here's the two errors it's throwing: Access to Image at 'https://demographics8.arcgis.com/arcgis/rest/directories/arcgisoutput/USA_Demographics_and_Boundaries_2018_MapServer/x_____x8rpmfxe7ycCrgTOULj6txw..x_____x_ags_map00d241a884ec469dafb1aeebc2cb111d.png?token=<redacted>' from origin 'http://localhost:3000' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access.
and
{"error":{"name":"request:server","message":"Unable to load the resource","details":{"url":"https://demographics8.arcgis.com/arcgis/rest/directories/arcgisoutput/USA_Demographics_and_Boundaries_2018_MapServer/x_____x8rpmfxe7ycCrgTOULj6txw..x_____x_ags_map00d241a884ec469dafb1aeebc2cb111d.png?token=<redacted>","requestOptions":{"responseType":"image"},"ssl":false}}}
... View more
09-28-2018
03:46 PM
|
0
|
4
|
3968
|
|
POST
|
For anybody following this, Esri has filed two bugs related to this: #BUG-000115988 Picture Marker Symbols in Feature Layer are unable to display with WebGL enabled when imageData of the symbol stored at REST Endpoint is lengthy. #BUG-000115991 Picture marker symbols in FeatureLayer with WebGL enabled display as jumbled when using more than 10 unique value categories to symbolize points.
... View more
08-23-2018
06:35 AM
|
1
|
1
|
2695
|
|
POST
|
I have only been able to get halos working on FeatureLayer and MapImageLayer sublayer labels. Halos don't seem to work if adding a TextSymbol to the map as a Graphic. Not sure if this is working as intended or not, but it may be worth filing a bug report.
... View more
08-23-2018
06:31 AM
|
1
|
0
|
1575
|
|
POST
|
Just adding a "me too" here as well. I have seen this across a couple different apps we've moved over to 4.8.
... View more
07-17-2018
12:10 PM
|
0
|
0
|
2422
|
|
POST
|
And here's a public layer that demonstrates the issue. There's a single point east of I-35 near the OK/KS line. const lyr = new FeatureLayer({
url: 'https://services1.arcgis.com/aUqH6d4IMis39TBB/arcgis/rest/services/test_webgl_issues/FeatureServer/0',
outFields: ['*'],
opacity: 1.0,
visible: true
}); The image file I used is this one: Logo Thanks for having a look at this. I'm also using the js cli if that matters at all.
... View more
07-09-2018
02:47 PM
|
0
|
1
|
2695
|
|
POST
|
Rene, there's no cors warnings in the dev console and I wouldn't expect that since the feature layer is coming directly from AGOL. Here's a link to a couple images that exhibit the issue: Image the First Image the Second All we're doing is setting the symbology for the layer in AGOL and saving the layer there. The images are all originally from our dropbox folder. The layer isn't public but let me see if I can setup a test case with a public layer.
... View more
07-09-2018
02:32 PM
|
0
|
2
|
2695
|
|
POST
|
I've got a feature layer on AGOL that users picture marker symbols for its symbology. If I enable webgl feature layer using "esri-featurelayer-webgl": 1 then the symbols do not all render correctly though they are correct in the legend: Disabling esri-featurelayer-webgl solves the issue but then breaks the labeling and feature highlights for popups which are required for the app I'm building here. The incorrect symbols appear as a mishmash of other symbols squished together. This is observed in both Chrome and Firefox on OS X. Using JS API 4.8. Any ideas here? Is this a bug in the API or something I'm doing wrong on the coding side?
... View more
07-09-2018
12:52 PM
|
0
|
6
|
3325
|
|
POST
|
Yes it is using the default print service. Unfortunately there is no ArcGIS Server instance available that we could use for a custom print service. I was under the impression that if the various secured Esri premium layers worked with the widget then our own layers would work as well. In fact, I can setup an app using the web app builder in AGOL and the print widget works as expected with our secured layers so it seems like I'm missing something here in the config.
... View more
07-05-2018
06:27 PM
|
0
|
0
|
1393
|
|
POST
|
Hello, I'm attempting to get the Print Widget functioning with some secured layers hosted on AGOL but am running into some difficulty getting this to work. We have several feature layers that we've created (a mix of both points and polygons) and if any of them are turned on, the print widget fails: {
"error": {
"code": 400,
"extendedCode": -2147467261,
"message": "Unable to complete operation.",
"details": ["Error executing tool. Export Web Map Task : Failed to create layer from service at https://services8.arcgis.com/redacted/arcgis/rest/services/redacted/FeatureServer/0.\nFailed to execute (Export Web Map).\nFailed to execute (Export Web Map Task)."]
}
} The strange this is that the print widget DOES work as expected with various Esri provided "premium" layers such as Tapestry Segmentation, Population Density, etc. It seems like it should be possible to get this print service to work with AGOL secured services, since it works withe the Esri premium layers but this one has me baffled. If anybody has any insight into this, it'd be appreciated. Thanks. Relavent code snippets: Print Widget const print = new Print({ view: this.view, printServiceUrl: 'https://utility.arcgisonline.com/arcgis/rest/services/Utilities/PrintingTools/GPServer/Export Web Map Task', }); this.view.ui.add(print, 'top-right'); Feature Layer import FeatureLayer from 'esri/layers/FeatureLayer'; import popupTemplate from '../../helpers/redacted'; const fLayer = new FeatureLayer({ url: 'https://services8.arcgis.com/redacted/arcgis/rest/services/redacted/FeatureServer/0', outFields: ['*'], title: 'redacted', opacity: 1.0, visible: false, popupTemplate: popupTemplate }); export default fLayer; This is observed in MacOS, Chrome 67. I'm using the Esri js cli version 4.7 and Typescript.
... View more
07-05-2018
03:07 PM
|
0
|
2
|
1905
|
|
POST
|
Mark thanks for the follow up. Unfortunately we cannot create a feature view for this layer since it is a Dynamic Map service and one of the Esri Premium Living Atlas layers. To work around the issue for now, we've created a service in our own AGOL with the geometry and fields we're trying to use. It works, however it isn't ideal since it's disconnected from Esri's authoritative data thus updates require a manual process on our end. It's also a Feature Service where we'd ideally like to use a Dynamic Map service for the sake of speed. Plus, we'd obviously prefer not to spend credits on essentially duplicating an ready-to-go layer. Looking forward to trying it out in the next release though and seeing how it goes. -Todd
... View more
05-22-2018
09:38 AM
|
0
|
0
|
1147
|
|
POST
|
I've run into this problem as well after updating to 4.7. In prior versions of 4.x, native promises worked as expected for popup templates but at 4.7 they do not. The solution is to NOT use native promises and instead use Dojo's version of promises: dojo/Deferred The issue is that there is no .isFulfilled() method on native promises, however that method is is present on dojo/Deferred. I meant to file a bug report with Esri for this the other day when I found it but have not yet done so.
... View more
04-30-2018
06:53 PM
|
2
|
1
|
1788
|
|
POST
|
Mark, thank you very much for your time and help. I'm going to fiddle around with some ideas for a workaround on our end as well.
... View more
04-16-2018
02:31 PM
|
0
|
2
|
1147
|
|
POST
|
Thanks for your help, Mark. I set a breakpoint for All C++ Exceptions and it's not giving me any additional info than what I posted earlier--it's breaking at the same spot with the same exception.
... View more
04-16-2018
01:32 PM
|
0
|
4
|
1147
|
|
POST
|
Some further findings: I swapped out the service for the USA Flood Risk Layer (arcgis.com/home/item.html?id=6b09b1c163c740559dc31cce9144222e) and it's returning all the attributes and everything seems to be in order. (I'll track down some more map image services to test and see how they fare.) Going back to the Demographics (arcgis.com/home/item.html?id=eda0f20edc8448adaa3373cce237a57f) results in only the same 8 attributes being returned. I noticed, however, that this only worked once. Any subsequent attempts to do an identify on the layer results in an application crash at ags_sqlite3_clear_bindings. Makes me wonder if the sheer number of fields in the demographics service is making the API choke? I'll be the first to admit I'm way out of my league when it comes to looking at this particular error.
... View more
04-16-2018
12:16 PM
|
0
|
6
|
2914
|
|
POST
|
It's an AGSGeoElement which I'm getting via identifyLayers(atScreenPoint:, tolerance:, returnPopupsOnly:, maximumResultsPerLayer:) Relevant code where I tested the .load method: for subLayerResult in result.sublayerResults {
for subElement in subLayerResult.geoElements {
guard let f = subElement as? AGSArcGISFeature else {
return
}
f.load(completion: { (error) in
guard error == nil else {
print("Error")
return
}
print("f", f.attributes)
})
print(subElement.attributes)
}
}
... View more
04-16-2018
11:30 AM
|
0
|
1
|
2914
|
| 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 |
04-07-2026
11:00 AM
|