Latest Contributions by BrianCrist

I'm experiencing a situation where identifyGraphicsOverlay calls are never indicating they've finished to the application.  I've got an application with several layers of GraphicsOverlays, and when an end-user clicks on the mapView, I need to identify what items in which layer may have been clicked. What I'm observing is that if I get "click happy" the identifyGraphicsOverlay calls will stack (I am keeping a list of taskWatchers) and nothing happens... eventually the mapView will lock up until I move the mouse off the application; at which point all of the tasks seem to execute and the mapView "frees up" as if nothing ever happened. I've put in a monitor function to gain information about the taskWatchers, and they are valid and remain so.  Here's a little bit of that monitor's output: Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Other task count: 22 -- tasks started: 60 ; tasks finished: 38 "Hung states = [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid] [valid]" Again, as soon as I move the mouse off of the application, I am seeing this: Other task count: 0 -- tasks started: 60 ; tasks finished: 60 Other task count: 0 -- tasks started: 60 ; tasks finished: 60 Other task count: 0 -- tasks started: 60 ; tasks finished: 60   Here is the relevant code:   connect(m_mapView, &MapGraphicsView::identifyGraphicsOverlayCompleted, this, &App::identify_overlay_completed); ... void App::build_taskwatchers(const QList<our_layer_enum> layers_to_watch, const int x, const int y) { constexpr double tolerance = 5; constexpr bool returnPopupsOnly = false; constexpr int maximumResults = 10; // Set up a bunch of identifyGraphics threads to see which (if any) overlay items // were clicked. for (our_layer_enum layer : layers_to_watch) { Esri::ArcGISRuntime::TaskWatcher tw = m_mapView->identifyGraphicsOverlay(m_overlays[layer].data(), x, y, tolerance, returnPopupsOnly, maximumResults); } } ... void App::identify_overlay_completed(const QUuid id, Esri::ArcGISRuntime::IdentifyGraphicsOverlayResult * raw_result) {   ... do stuff   Again, if you click like a sane human, this all works fine.  But our users tend to get click happy; and when they do so "identify_overlay_completed" is never called. I have tried to do the  identifyGraphicsOverlays / identifyGraphicsOverlaysCompleted pairing instead, and it did the same thing; that is, it never finished tasks if someone was click happy.   I guess what I'm looking for is a way to actually have TaskWatcher::cancel work.  I have tried cancelling the tasks in my little monitor function if they are aged out, and it does absolutely nothing.   The only (seemingly magical) way to get these stuck identifications unstuck is to move the mouse off of the application.   Note:  I did build the "IdentifyGraphics" tutorial, and while it never freezes up, if you get click-happy with it, it will intermittently not pop up the "Tapped on Graphic" message.  It never seems to lock up though.   ... View more

Hi Y'all,   This is an embarrassing question to ask, because it will expose my ignorance to GIS topics.  But I can't figure out how to do this operation and I'm wondering if someone could throw me a bone.   So I have an image that I need to scale based on the zoom level of the map and place in a PictureMarkerSymbol.  (Operating in Map / MapGraphicsView).  When I place the image at location 0,0 (WGS84), the UnitsPerDIP call returns a value that scales the image appropriately.  But (perhaps obviously), when I place the image at a location away from (0,0), the image's size is different.   So is the solution to use the GeometryEngine to MoveGeodetic to the location in question?  If so, I don't really understand how to "move" a PictureMarkerSymbol (which is referenced by a single point) instead of something like the 4 corners of an envelope... but an envelope isn't the geometry I need.   Another way to put it:  I have an icon that is a 10x10 meter square.  When I scale my original graphic's PNG using UnitsPerDIP at location 0,0 it scales properly.  When I scale it at WGS84 lon,lat (-70.6, 41.9) the graphic renders to somewhere in the mid 7 meters per side.  How do I make it 10x10 meters at (-70.6, 41.9)?  Thank you,   Brian Crist ... View more

Hi,     I've been trying to implement solution for displaying a sonar fan in a map for about 6 months now with little to no success due to various issues with PictureMarkerSymbols and KML Icons as they behave in the 2-d (map/mapview) environment.    So I'm wondering if it's possible to implement my own Animated symbol derived from the MarkerSymbol class?  I'm guessing it's not, but I felt like it was worth asking.   If it is possible, is there a guide or sample code anywhere? Regards,   Brian Crist ... View more

I have a graphic that is being updated at a regular interval (15-20hz) that I would really like to use a KML overlay for, but cannot since updating KML Overlays doesn't work in 2d maps.  (Prior Conversation on GeoNet) So I've been using a PictureMarkerSymbol with some success, but I am now observing some weirdness with it.  I'm wondering if it's something I am doing wrong or if I've stumbled on another bug. The basic workflow is the sensor (a sonar) that we're tracking feeds us a stream of QImages.  I scale the QImage to the appropriate size according to our current zoom level and map scaling and create a PictureMarkerSymbol using this code block: Esri::ArcGISRuntime::Graphic m_graphic;          // declared elsewhere Esri::ArcGISRuntime::GraphicsOverlay m_overlay;  // Set up elsewhere Esri::ArcGISRuntime::Point point;                // Set up elsewhere Esri::ArcGISRuntime::PictureMarkerSymbol pms(scaled_image,this); pms.setAngle(m_heading); pms.setWidth(scaled_image.width()); pms.setHeight(scaled_image.height()); if (m_graphic.isNull()) {   m_graphic = new Esri::ArcGISRuntime::Graphic(point, &pms);   m_overlay->graphics()->append(m_graphic); } else {   m_graphic.data()->setSymbol(&pms);   m_graphic.data()->setGeometry(point); } The functionality is great to an extent.  But when the image exceeds a certain size (in this case, 20 meters), the PictureMarkerSymbol seems to unexpectedly change its shape as demonstrated in the 3 images I have attached.  The first image shows a sonar at range of 16 meters, the second a range of 19 meters; you can see the aspect ratio of the image/PictureMarkerSymbol (dim red rectangle with the sonar fan in the front of it) is a distinct rectangle. When the range reaches 20 meters, the aspect ratio of the image / PictureMarkerSymbol changes into a square!!  I know this is not in the QImage scaling code, as I've stepped through and observed the QImage itself scaling properly.  The "change" happens within the PictureMarkerSymbol. Please advise. Regards,   Brian ... View more