Latest Contributions by DavidColey

An update - this is also an issue in Pro.  Public basemaps in our custom basemap agol group won't load to Pro if those webmaps are Collaborated.  I think that because we do not allow anonymous access to our Portal, that this is what is causing the hiccup for both the WAB and PRO. If I save a copy of one of my collaborated webmaps, that removes the Collaborated tag (status, icon, whatever).  Then that webmap WILL load to Pro from the basemap ribbon tool.  I'm wondering if Kelly Gerrow‌ has come across this yet?   ... View more

Well, in that case look at the constructor details for the basemaps gallery BasemapGallery | API Reference | ArcGIS API for JavaScript 3.30  and populate your gallery using either the basemapsGroup parameter or construct an array of basemapLayers to populate the basemap object with the .add method, then add the basemap object as an array to the basemapGallery object. You can use the 'community map' v2 tile layer as part of the basemaps layer. ... View more

So this isn't working for you because the 'Community' layer you are pointing to isn't a webmap, it is a vector tile layer, and as far as I know you can't set a vector tile layer as a basemap.  Instead, look for the 'Community Map' webmap from living atlas, add that webmap to your org, and then do something like this: const imgBasemap = new Basemap({ portalItem: { id: "4509cfefb72e4c5b977f6ee568116a6b" }, thumbnailUrl: "css/Aerial2013r2.png" }); const localBasemap = new Basemap({ portalItem: { id: "7a474639e9204183a96063e3ab34bea7" }, thumbnailUrl: "css/LocalMap_r1.png" }); const topoBasemap = new Basemap({ portalItem: { id: "a0cdf807f11f4a1db617aef111760c8a" }, thumbnailUrl: "css/WorldTopo.jpg" }); const basemapGallery = new BasemapGallery({ view: app.mapView, source: [imgBasemap,localBasemap,topoBasemap], container: "collapseBasemap" });‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍ where you are adding the webmaps you want to use by pulling them in by portalItem id and then adding them to the basemap gallery ... View more

After contacting support, there has been a bug logged about this issue. There is a size threshold dictated by the combination of number of nodes (complex 3d multipatch shapes) and attributes to cache.  In my case for detailed building footprints with roofforms, that appears to be around 10mb.  For another case, the size limitation appears to be around 35mb.  According to support this is scheduled for fix at the 10.8 release, and so I will mark this as 'Assumed answered'. ... View more

Not really, what I've ended up doing is just continuing to use these scales/resolutions in my state plane vector tiles as kind of a work around. ... View more

Still unresolved.  I am able to publish a scene layer package to ArcGIS Online and then access the 3D Scene layer (hosted) layer in portal by collaboration ... View more

This never did get fixed.  The solution is to delete the feature classes first. ... View more

Hi again -  has anyone seen a resolution to this?  Because we have living atlas basemaps configured as part of our basemap gallery.  This has become an even greater issue when using the 3D Wab because there is no configuration for the 3D basemap gallery widget.  In 2D, I can at least configure and hard code in our Enterprises' basemaps from our basemap gallery, but cannot do so in 3D.   ... View more

Hi again -  has anyone seen a resolution to this?  Because we have living atlas basemaps configured as part of our basemap gallery.  This has become an even greater issue when using the 3D Wab because there is no configuration for the 3D basemap gallery widget.  In 2D, I can at least configure and hard code in our Enterprises' basemaps from our basemap gallery, but cannot do so in 3D.   ... View more

ok thanks Robert - if I find anything I'll post ... View more

Hi all - has anyone yet to discover any issues the 2.14 web dev release and this current 2.13 eSearch release?  I have not, just trying to be proactive . . .  ... View more

Hi Mike - some of our sections have to have data explorer and lookup maps with lots of layers.  Think utilities.  Most of staff uses the online web app builder and other online templates so that's not really an option for them.  The WebGL usually behaves in the developer edition of the web app builder (in that you can see all your layers and not lose them during a basemap switch in the app) and in any online webmaps that use a raster base. A workaround may be that staff has to save a map with a raster base in order to have 16+ visible (but scale-dependent) layers, or that more layers have to be set not visible.  Either seems to work for the most part.  Awaiting the 4x map viewer. Thanks, David ... View more

Hi Kelly - I haven't communicated with you in some time, but as you know we have really embraced collaborations as our tool for managing hosted layers, webmaps and apps in our 10.7.1 Enterprise and send them to our various workspaces in our AGOL org.  It's been working really well after we ( well, you all   ) got us past the size limitations and the earlier issue with layers-by-reference behaving as copies - and we all thank you for that.   However, a couple things have cropped up: Our Custom Basemap collaboration sends a few of our basemap-webmaps and some of the esri basemap-webmaps to our org's custom basemap gallery.   But these maps will not load in Pro at 2.4.2 when selecting a basemap from the ribbon tool.  For example, I have found that the esri basemaps containing vector tiles will not load, such as World Streets, Human Geography, World Topo (Vector).  For World Topo Vector, the 'World_Hillshade' layer will load, but the vector tile will not. The maps do load from Portal's custom gallery (the collaboration source workspace) , but the Collaborated maps won't load from our org's custom basemap gallery. I have also made a copy and customized the Light Gray Reference layer from living atlas for use in our localized custom hybrid basemap.  This layer will not load into Pro 2.4.2 no matter where it's coming from.  If you have any insight on this that would be great- Thanks, David ... View more

Hi Mike - so is there a work around on this?  For us this happens alot when we use the human geography basemap, and a recently created local base map that uses the Light gray base, a local base vector tile, a local detail vector tile as a reference, and a copy of the light gray reference vector tile as a reference. How do I stop or otherwise disallow my hosted feature layers in the agol or portal map viewer to not utilize webgl?  Is that possible? ... View more

Hello - we use Enterprise at 10.7.1.  I have created a custom basemap gallery for Enterprise with 2 webmaps customized with our own vector tile reference layers, one for our image basemap and another for our local basemap.  The gallery also contains a subset of default esri basemaps. At any rate, I then send this collection to our AOGL via a collaboration.  However, in ArcGIS Pro at 2.4.2, once connected to our AGOL org, none of the vector tile style basemaps will display in the Pro map pane. Feels like a CORS issue? ... View more