Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Cancel
- Home
- :
- About JoelBennett
JoelBennett
MVP Regular Contributor
since
07-04-2014
659
Posts created
85
Kudos given
161
Solutions
290
Kudos received
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
My Ideas
(2 Idea Submissions)Latest Contributions by JoelBennett
|
POST
|
If you don't want a given layer to appear in the Legend, you can set its legendEnabled property to false.
... View more
08-12-2024
11:10 AM
|
0
|
0
|
688
|
|
POST
|
As of now, yes, but that could change at any time. See this message.
... View more
08-12-2024
10:34 AM
|
0
|
1
|
3571
|
|
POST
|
There doesn't appear to be a simple way to do this, but the following function would do the job in theory. Note, due to the nature of hitTest, it can't just return a Boolean, but instead has to return a Promise. function checkCluster(view, graphic) {
return new Promise(function(resolve, reject) {
view.hitTest(view.toScreen(graphic.geometry), {include:[graphic.layer]}).then(function(hitTestResult) {
var result = ((hitTestResult.results.length === 0) || (hitTestResult.results[0].isAggregate === true));
resolve({graphic:graphic, isCluster:result});
}, reject);
});
} However, it doesn't work as expected in practice. The reason is because in cases where a graphic that is part of a cluster doesn't intersect the cluster graphic, hitTest will still return the graphic from the layer, even though it's not visible in the view. I don't think hitTest is supposed to work this way. The documentation is somewhat ambiguous, but my expectation is that it's supposed to only return objects that are visible in the view. After all, why would a hit test return something that's not rendered in the view? It doesn't seem like you should be able to"hit" something that's not there. @UndralBatsukh could you please weigh in here? Here is the adjusted code for testing that you can paste into the Sandbox for the "Intro to clustering" sample. If you click somewhere on the map, the dev tools console will output results, indicating if the features whose coordinates (but not symbology!) intersecting the view are part of a cluster or not. I highly recommend panning to a region where there's only a few, for clarity of results. <html lang="en">
<head>
<meta charset="utf-8" />
<meta
name="viewport"
content="initial-scale=1,maximum-scale=1,user-scalable=no"
/>
<title>Intro to clustering | Sample | ArcGIS Maps SDK for JavaScript 4.30</title>
<style>
html,
body,
#viewDiv {
padding: 0;
margin: 0;
height: 100%;
width: 100%;
background: rgba(50,50,50);
}
#infoDiv {
padding: 10px;
}
</style>
<link rel="stylesheet" href="https://js.arcgis.com/4.30/esri/themes/dark/main.css" />
<script src="https://js.arcgis.com/4.30/"></script>
<script>
require([
"esri/Map",
"esri/layers/FeatureLayer",
"esri/layers/GeoJSONLayer",
"esri/views/MapView",
"esri/widgets/Legend",
"esri/widgets/Expand",
"esri/widgets/Home"
], (Map, FeatureLayer, GeoJSONLayer, MapView, Legend, Expand, Home) => {
// Configures clustering on the layer. A cluster radius
// of 100px indicates an area comprising screen space 100px
// in length from the center of the cluster
const clusterConfig = {
type: "cluster",
clusterRadius: "100px",
// {cluster_count} is an aggregate field containing
// the number of features comprised by the cluster
popupTemplate: {
title: "Cluster summary",
content: "This cluster represents {cluster_count} earthquakes.",
fieldInfos: [{
fieldName: "cluster_count",
format: {
places: 0,
digitSeparator: true
}
}]
},
clusterMinSize: "24px",
clusterMaxSize: "60px",
labelingInfo: [{
deconflictionStrategy: "none",
labelExpressionInfo: {
expression: "Text($feature.cluster_count, '#,###')"
},
symbol: {
type: "text",
color: "#004a5d",
font: {
weight: "bold",
family: "Noto Sans",
size: "12px"
}
},
labelPlacement: "center-center",
}]
};
const layer = new GeoJSONLayer({
title: "Earthquakes from the last month",
url: "https://earthquake.usgs.gov/earthquakes/feed/v1.0/summary/all_month.geojson",
copyright: "USGS Earthquakes",
featureReduction: clusterConfig,
// popupTemplates can still be viewed on
// individual features
popupTemplate: {
title: "Magnitude {mag} {type}",
content: "Magnitude {mag} {type} hit {place} on {time}",
fieldInfos: [
{
fieldName: "time",
format: {
dateFormat: "short-date-short-time"
}
}
]
},
renderer: {
type: "simple",
field: "mag",
symbol: {
type: "simple-marker",
size: 4,
color: "#69dcff",
outline: {
color: "rgba(0, 139, 174, 0.5)",
width: 5
}
}
}
});
// background layer for geographic context
// projected to Alaska Polar Stereographic
const baseLayer = new FeatureLayer({
portalItem: {
id: "2b93b06dc0dc4e809d3c8db5cb96ba69"
},
legendEnabled: false,
popupEnabled: false,
renderer: {
type: "simple",
symbol: {
type: "simple-fill",
color: [65, 65, 65, 1],
outline: {
color: [50, 50, 50, 0.75],
width: 0.5
}
}
},
spatialReference: {
wkid: 5936
}
});
const map = new Map({
layers: [baseLayer, layer]
});
const view = new MapView({
container: "viewDiv",
extent: {
spatialReference: {
wkid: 5936
},
xmin: 1270382,
ymin: -1729511,
xmax: 2461436,
ymax: -953893
},
spatialReference: {
// WGS_1984_EPSG_Alaska_Polar_Stereographic
wkid: 5936
},
constraints: {
minScale: 15469455
},
map: map
});
view.ui.add(new Home({
view: view
}), "top-left");
const legend = new Legend({
view: view,
container: "legendDiv"
});
const infoDiv = document.getElementById("infoDiv");
view.ui.add(new Expand({
view: view,
content: infoDiv,
expandIcon: "list-bullet",
expanded: false
}), "top-left");
const toggleButton = document.getElementById("cluster");
// To turn off clustering on a layer, set the
// featureReduction property to null
toggleButton.addEventListener("click", () => {
let fr = layer.featureReduction;
layer.featureReduction = fr && fr.type === "cluster" ? null : clusterConfig;
toggleButton.innerText = toggleButton.innerText === "Enable Clustering" ? "Disable Clustering" : "Enable Clustering";
});
function checkCluster(view, graphic) {
return new Promise(function(resolve, reject) {
view.hitTest(view.toScreen(graphic.geometry), {include:[graphic.layer]}).then(function(hitTestResult) {
var result = ((hitTestResult.results.length === 0) || (hitTestResult.results[0].isAggregate === true));
resolve({graphic:graphic, isCluster:result});
}, reject);
});
}
view.on("click", function(evt) {
view.whenLayerView(layer).then(function(layerView) {
var query = layerView.createQuery();
query.geometry = view.extent;
layerView.queryFeatures(query).then(function(featureSet) {
featureSet.features.forEach(function(feature, index) {
checkCluster(view, feature).then(function(result) {
console.info(result.graphic.getObjectId().toString() + ": " + result.isCluster.toString());
});
});
});
});
});
});
</script>
</head>
<body>
<div id="viewDiv"></div>
<div id="infoDiv" class="esri-widget">
<button id="cluster" class="esri-button">Disable Clustering</button>
<div id="legendDiv"></div>
</div>
</body>
</html> In this example below, we see there's a cluster of 10 features, and a standalone feature: Here's what it looks like with clustering disabled: Before running the test, I would expect one unclustered feature, and as many as 10 features that have been clustered. (I say "as many as" because some could be off-screen.) However, running the test indicates 5 unclustered features, and 5 clustered features. Four of those features said to be unclustered are such because their shapes don't intersect the cluster graphic, and therefore are invisible, but returned by hitTest nonetheless. This kind of workflow is the only way I can think of to determine if a feature is clustered or not. But with hitTest implemented the way it is, the results here are unreliable.
... View more
08-09-2024
05:16 PM
|
1
|
0
|
1910
|
|
POST
|
This thread shows how to get a reference to features after the user has confirmed to delete them, but prior to them actually being deleted.
... View more
08-07-2024
02:21 PM
|
1
|
0
|
1133
|
|
POST
|
If I'm understanding this correctly, I think the problem is that FeatureLayer ignores the symbol property of its graphics. If you want each graphic to be rendered uniquely, I think your best bet is to create and populate a UniqueValueRenderer object, and set it to the layer's renderer property. You could add the url to the graphic's attributes, and use that as the field for your renderer. Also, if you've created a code block in one of your posts, you can double-click it to re-open and edit.
... View more
08-07-2024
09:37 AM
|
1
|
3
|
2083
|
|
POST
|
Nice, good to hear you got it working. The description of the arguments object here is definitely better than what I would come up with. By calling apply with the arguments object, it ensures the function being called is executed with the same arguments (if any) that were passed to the current function.
... View more
08-07-2024
09:24 AM
|
1
|
1
|
1637
|
|
POST
|
It looks like they've taken down the 3.x links. The direct URLs still work though...for now. Go here, copy the URL from the JSON text it outputs, and paste back into your browser.
... View more
08-06-2024
03:04 PM
|
1
|
0
|
6533
|
|
POST
|
Do you have a constraint preventing you from hosting the API locally? I would definitely recommend hosting it to anybody that can, since it gives more control and less dependencies on third parties.
... View more
08-06-2024
01:35 PM
|
0
|
2
|
6542
|
|
POST
|
There doesn't seem to be a "natural" way to do this since by the time "edits" has been fired, the feature has been deleted, with no way to get its info from the layer anymore. The widget otherwise provides nothing like a "before-edits" event, which would be helpful in this regard. I see a couple options here though. First, you could put logic between the "edits" event and your changes getting pushed to the server. In this intermediate step, you could get the feature's data from the server before sending the information to the server about the feature being deleted. This kind of workflow would require an extra server request being added to your overall workflow, and so would be somewhat inefficient, since you'd be sending a network request to get information that existed on your client less than a second ago. The other option is to add a hack that gets you a reference to the feature before it gets deleted. The best way appears to be by overriding the deleteFeatureFromWorkflow method of the Editor widget, because this method gets called immediately after the final "Delete" button on the widget is clicked, but before the delete operation actually takes place. Therefore, this would be the ideal place to examine the attributes of any features being deleted: var editor = new Editor({view:view});
var deleteFeatureFromWorkflow = editor.deleteFeatureFromWorkflow;
editor.deleteFeatureFromWorkflow = function() {
//This is the array of graphics being deleted
var graphics = editor.activeWorkflow.data.candidates;
graphics.forEach(function(graphic) {
//Do something with the graphic reference here
console.log("identifiedMarkerID: " + graphic.attributes.identifiedMarkerID;
});
return deleteFeatureFromWorkflow.apply(this, arguments);
};
... View more
08-06-2024
11:05 AM
|
1
|
3
|
1659
|
|
POST
|
Yes, the PrintingTools service is a built-in service that comes with ArcGIS Server, so if you want to host it, you would need to install and license ArcGIS Server on your own server. More information is available here.
... View more
08-06-2024
10:29 AM
|
0
|
0
|
754
|
|
POST
|
I see...one of the main problems here is you won't be able to use "declare" anymore. After migration, my modules use one of two interchangeable approaches: a vanilla implementation, or extending Accessor: Vanilla: define(["esri/Color", "esri/rest/geoprocessor/execute"], function(Color, Geoprocessor) {
var a = function() {
function b(options) {
//this is the constructor
}
b.prototype.isAvailable = function(installation) {
//this is an example member function
};
b.prototype.activate = function(toolParams) {
//this is another example member function
};
return b;
}();
a.prototype.declaredClass = "myPackage.myFolder.myModule"; //optional
return a;
}); Extending Accessor (note, uses undocumented "Evented" class to add support for emitting and handling events with "emit" and "on" like in 3.x): define(["esri/Color", "esri/core/Accessor", "esri/core/Evented", "esri/rest/geoprocessor/execute"], function (Color, Accessor, Evented, Geoprocessor) {
return Evented.EventedMixin(Accessor).createSubclass({
declaredClass: "myPackage.myFolder.myModule", //optional
constructor: function(options) {
//this is the constructor
},
isAvailable: function(installation) {
//this is an example member function
},
activate: function(toolParams) {
//this is another example member function
}
});
}); The error message in your console also indicates it's looking for dojo modules in the ESRI JSAPI, but that was removed in 4.20 (which was what my first post was about). It also shows you're using the API from ESRI's server, but my discussion from the previous post assumes an environment where the API has been downloaded and installed on the local server.
... View more
08-05-2024
12:20 PM
|
1
|
0
|
6595
|
|
POST
|
Yes, it's still valid, but getting everything set up is slightly more complicated than previously. Migrating from 3.x would've been a bit easier prior to 4.20, because dojo was still packaged with the API in those days. When I migrated our platform in the days of 4.16 - 4.18, I was able to eliminate about 94% of the references to dojo, but some of those remaining references still exist to this day (although with charting components hopefully coming out of beta in the near future, we might be ready for the final push to remove dojo entirely). When the dojo-less 4.20 came along, I thought "oh, I'll just load dojo from the 3.x install instead", but it didn't work out that way, because the 3.x loader and the 4.x loader didn't play nice together. To make this work, I ended up copying the dojo, dijit, and dojox folders from the 3.x install into the 4.x install like so: The screenshot below shows the code for loading dojo separately from the Maps SDK for Javascript: For good measure, the screenshot below shows the value of the "baseURL" setting in the dojo.js file which matches the environment displayed above: Hope that helps...
... View more
08-05-2024
11:19 AM
|
0
|
0
|
6603
|
|
POST
|
The root cause of why event handlers within your HTML tags are ignored is discussed in this thread, along with some suggested workarounds.
... View more
07-26-2024
12:44 PM
|
0
|
1
|
2137
|
|
POST
|
For the very few people interested (if any at all), this occurs in 3.x as well. The following hack to the _onExtentChangeHandler function of DynamicMapServiceLayer appears to do the job: var _onExtentChangeHandler = DynamicMapServiceLayer.prototype._onExtentChangeHandler;
DynamicMapServiceLayer.prototype._onExtentChangeHandler = function(a, b, c) {
if ((a) && (a.declaredClass == "esri.geometry.Extent")) {
var extents = a.normalize();
if (extents.length == 2) {
var ext1 = extents[0];
var ext2 = new Extent(ext1.xmin, ext1.ymin, ext1.xmax + extents[1].getWidth(), ext1.ymax, ext1.spatialReference);
ext2._normalize = function() { return this; };
_onExtentChangeHandler.call(this, ext2, b, c);
return;
}
}
_onExtentChangeHandler.apply(this, arguments);
}; Note, only tested with 3.46...
... View more
07-22-2024
02:21 PM
|
0
|
0
|
787
|
|
POST
|
The lengths of each segment aren't included in the event object, but if you have a reference to the polyline object, you can calculate them without much trouble. You would just need to (1) step through the polyline's points 2 at a time (perhaps using getPoint), (2) create a new Polyline object from those two points, and then (3) get the distance for the new 2-point polyline from geometryEngine.geodesicLength.
... View more
07-16-2024
10:09 AM
|
1
|
0
|
1401
|
My kudoed posts
| Title | Kudos | Posted |
|---|---|---|
| 1 | a week ago | |
| 1 | 03-19-2024 10:37 AM | |
| 1 | 03-31-2026 02:34 PM | |
| 1 | 12-09-2025 09:35 AM | |
| 2 | 12-09-2025 09:06 AM |
Activity Feed
- Got a Kudo for Re: 4.19 Legend widget bug - duplicated requests. a week ago
- Posted Re: 4.19 Legend widget bug - duplicated requests on ArcGIS JavaScript Maps SDK Questions. a week ago
- Got a Kudo for Re: Go to specific index in popup. 06-05-2026 07:57 AM
- Kudoed Re: ArcGIS Maps SDK for JavaScript – Version 5.0 Release for Noah-Sager. 04-21-2026 10:02 AM
- Got a Kudo for Re: ArcGIS Maps SDK for JavaScript – Version 5.0 Release. 04-10-2026 09:11 AM
- Posted Re: ArcGIS Maps SDK for JavaScript – Version 5.0 Release on ArcGIS JavaScript Maps SDK Blog. 03-31-2026 02:34 PM
- Kudoed ArcGIS Maps SDK for JavaScript – Version 5.0 Release for Noah-Sager. 02-25-2026 08:30 AM
- Kudoed Re: Use Fonts locally or from portal (CORS error) for SebastianKrings. 01-20-2026 10:31 AM
- Posted Re: Use Fonts locally or from portal (CORS error) on ArcGIS JavaScript Maps SDK Questions. 01-20-2026 10:26 AM
- Posted Re: Use Fonts locally or from portal (CORS error) on ArcGIS JavaScript Maps SDK Questions. 01-15-2026 04:03 PM
- Got a Kudo for Re: Timeslider web component ShadowDom not fully rendered even though component is "ready". 12-18-2025 12:11 AM
- Got a Kudo for Re: Adding a row to a table using JS 4.x. 12-09-2025 09:39 AM
- Posted Re: Adding a row to a table using JS 4.x on ArcGIS JavaScript Maps SDK Questions. 12-09-2025 09:35 AM
- Got a Kudo for Re: Timeslider web component ShadowDom not fully rendered even though component is "ready". 12-09-2025 09:11 AM
- Posted Re: Timeslider web component ShadowDom not fully rendered even though component is "ready" on ArcGIS JavaScript Maps SDK Questions. 12-09-2025 09:06 AM
- Posted Re: Adding a row to a table using JS 4.x on ArcGIS JavaScript Maps SDK Questions. 12-05-2025 08:39 AM
- Posted Re: How to show/hide spinner feature programmatically? on ArcGIS JavaScript Maps SDK Questions. 12-04-2025 03:10 PM
- Posted Missing new fonts in 4.34 on ArcGIS JavaScript Maps SDK Questions. 12-04-2025 09:16 AM
- Got a Kudo for Re: Disabling the Esri JavaScript API v4.x IdentityManager login prompt?. 12-03-2025 12:43 PM
- Got a Kudo for Re: dojoConfig (loader) replacement strategy for large JavaScript app with many files?. 12-01-2025 11:46 AM