Latest Contributions by KristianEkenes

Ervy, The intersect method is designed to return the geometry of the intersection in the lowest dimension of the two input geometries. Since this case uses two lines (which are one dimensional) the output must also be a line. Because this seems counterintuitive, we're looking at the possibility of adding GeometryEngine support for returning a lower dimension than the inputs for this very reason. With two lines you expect to get a point (or several points) back, not necessarily a line. Just know that this is the current expected behavior, it's on our radar, and we're looking at improving it. Also note that this isn't a simple problem to solve. Because lines can be complex, containing many segments and vertices, processing this on the client can potentially be heavy. ... View more

Thanks, David. It looks like you're still able to get a route. It's just the text that isn't displaying the way you want it to. I tried testing with 3.16 and it looks like it has same behavior as well (for Search widget only). I didn't test with directions widget. Can you use 3.16, so I can take a look at it? ... View more

Hmm...Interesting. Could you provide a link to a small sample reproducing this issue so we can take a look at it some more? ... View more

I'm having a hard time picturing this. Are the buffers moving, or are they in fixed locations? I presume the GPS locations will be updating at a set interval. Once a GPS point intersects a buffer, you want to send an alert that indicates the GPS point ID and the buffer ID. Is that correct? ... View more

This is by design. Does your app have a requirement for displaying the suggestion in the text input? ... View more

It's a matter of preference. I feel adding the layers in the constructor is more convenient if you want them added to the map when the view is ready. However, there is an advantage to loading a WebMap with predefined layers, versus doing everything programmatically with the Map class. All you have to do is pass the item id of the webmap to the WebMap constructor. This loads all the layers, their renderers, and popups as defined and configured in the WebMap in ArcGIS Online, Portal for ArcGIS, or ArcGIS Desktop. You can save yourself time from writing many extra lines of code doing this. ... View more

Benjamin, Could you clarify which geometryEngine method(s) you were using? Was it the distance() method? If so, then I would suspect it's the issue Robert pointed out - That you are calculating web mercator coordinates with planar measurements (distance() is a planar measuring tool, not geodesic). Therefore the calculation itself was likely correct, but the WebMercator projection was distorting the true measurement. Rather than using distance or planarLength(), I would suggest you use geodesicLength() instead if you are working in WebMercator. This allows you to get more correct measurements in a distorted projection with the benefit of keeping all calculations on the client and not having to make extra network requests. I encourage you to read this blog post that discusses this in more detail here - GeometryEngine part 2: Measurement | ArcGIS Blog Be sure to note the differences between distance() and geodesicLength() - distance takes in two input points, whereas geodesicLength() takes in a polyline. So if measuring the distance between two points, you will first need to create a polyline with those two points as beginning and ending vertices on the path. Let me know if you're still stuck with this. ... View more

This hasn't been fixed because there hasn't been a bug report logged for it. Once somebody logs as a bug it will be looked at and fixed. ... View more

These appear to be API bugs. We're taking a look at them. ... View more

Are you able to share the url to the service/layer so I can take a look at this specific case? ... View more

Mark, Did you compare the network requests that fetch the images between the apps? Are they any different? There shouldn't be a difference in 4.0 final. If I were you I would compare the requests to make sure some parameter isn't missing. Then I would submit a bug report so we can look at it more closely. ... View more

Thanks for pointing out this issue. We'll fix the sample. Another option is to display a table of fields using fieldInfos  like this: var pTemplate = {     title: "{title}",     content: [{       type: "fields",       fieldInfos: [{         fieldName: "place",         label: "Location",         visible: true       }, {         fieldName: "time",         label: "Date and time",         visible: true       }, {         fieldName: "mag",         label: "Magnitude",         visible: true       }, {         fieldName: "mmi",         label: "Intensity",         visible: true       }, {         fieldName: "depth",         label: "Depth",         visible: true       }, {         fieldName: "felt",         label: "Number who felt the quake",         visible: true,         format: {           digitSeparator: true,          places: 0         }       }, {         fieldName: "sig",         label: "Significance",         visible: true       }, {         fieldName: "url",         label: "More info",         visible: true       }]     }],     fieldInfos: [{       fieldName: "time",       format: {         dateFormat: "short-date-short-time"       }     }]   }; Then the link will be clickable in the table: ... View more

Can you also describe the service some more? Is this points, lines, or polygons? ... View more

Hi Justin, In 3.x you should call the redraw() method on the featureLayer after the values have updated. function updateValues(){   // values are updated in the layer   featureLayer.redraw(); } In 4.0 the redraw capability in the FeatureLayer is built-in. To ensure the layer's renderer updates, you will need to clone the renderer and reset it on the FeatureLayer. function updateValues(){   // values are updated in the layer   featureLayer.renderer = featureLayer.renderer.clone(); } The latter example is a bit contrived, but works. Do you have a sample you could share that shows what you're trying to do? ... View more

Thanks for the feedback Charlie. I think it is apparent that our Geoprocessing documentation isn't complete at the moment. We will make sure to revisit it, including with more snippets so it is more clear. ... View more