Latest Contributions by AnneFitz

We've installed a fix for the blurriness that will be released at version 4.28. You can test it out on our development version of the API, https://js.arcgis.com/next. Please let us know if you are still running into issues! ... View more

Thanks for the additional info @AndrewTaylor0942 ! I can see there is some blurriness -- we will take a look!  In the meantime, you can try converting your complex SVGs to CIM symbols using the CIM Symbol Builder. Here's a blog that walks you through how to do this: https://www.esri.com/arcgis-blog/products/js-api-arcgis/developers/upload-symbols-from-svg-in-the-updated-cim-symbol-builder/ Let me know if that works for you or if you have any questions! 🙂 ... View more

Hi @AndrewTaylor0942 - can you share a codepen or something reproducing the issue? I tested out your SVG using a SimpleMarkerSymbol and do not notice any blurriness.  Here's an example: https://codepen.io/annefitz/pen/poQYvwJ?editors=1000 ... View more

Hi @PrashantR - this is currently a limitation with our current FeatureLayer implementation, the symbol text will always render on top. GraphicsLayer is a great alternative, especially if you are only rendering a few manually defined graphics, like in your code example above.  ... View more

This is not currently supported. I'd suggest submitting this as an enhancement request through Esri support or posting to ArcGIS Ideas. Thanks! ... View more

Sorry to hear that! I would recommend reaching out to Esri support for assistance with why that option is not appearing.  Another route you could take is to define the symbology manually on your layer. You create a multi-layer symbol in the JavaScript SDK using the CIMSymbol class. Here's an example: https://developers.arcgis.com/javascript/latest/sample-code/cim-lines-and-polygons/ ... View more

Thank you to everyone who joined us live!! In case you missed it, the recording is available here: https://www.youtube.com/live/bMP0mhF4KKI?feature=share Stay tuned for the next one! 🙌 ... View more

This might just be a layer publishing issue. If using ArcGIS Pro 3.1, make sure that "Use symbol types compatible with all clients" is not checked when publishing your layer. This will allow for multi-layer symbology. If that checkbox is checked, then the symbology gets downgraded, which could potentially be why you are just seeing the hatch fill and not the solid fill behind it. If this doesn't solve it, then I'd take Kristian's advice and reach out support. Thanks!   ... View more

Hi @BryanMc - thanks for pointing this out! It does seem like a bug - we'll take a look for the upcoming release. ... View more

This has been implemented for the upcoming June 2023 release of ArcGIS Online. Thanks for your feedback! ... View more

We've installed a fix for the upcoming 4.27 release (expected to go out in June). You can test out this fix in the development version of the API at https://js.arcgis.com/next Let us know if you are still running into any issues @LeoDeng ! ... View more

You can use the filterFunction on PortalBasemapsSource to filter basemaps in the BasemapGallery. Starting at version 4.27 (planned release in June), you will be able to pass in an asynchronous filter function, allowing you to load the basemap before filtering, like this:  const basemapGallery = new BasemapGallery({ view: view, source: { portal: "https://arcgis.com", // async filterFunction supported starting at v4.27 filterFunction: async (item, index, basemaps) => { let bool = true; await item.load().then((loadedBasemap) => { // filter out the Oceans basemap if (loadedBasemap.title == "Oceans") { bool = false; } }) return bool; } } }); Here's an example using the development (/next) version of the API: https://codepen.io/annefitz/pen/VwEZNEP ... View more