bug: feature popup outline is mis-shapen in ArcGIS Online
bug: popup outline is mis-shapen in ArcGIS but works fine in 3.25 sandbox
The original thread above I put in JS API initially based on my first experiences with this bug. So it is ok to delete the first one. However, it appears to be more a function of a bug with ArcGIS Server 10.6.1 or what runs AGOL.
The bug: Add a polygon layer to ArcGIS in a web map. Enable its popup, and click it. The outline is way off and misaligned and warped in shape, as shown below. Esri TS has reproduced this, and assigned bug ID is # BUG-000115968.
Although it works fine in the 3.25 sandbox (as in this example). Thus it would seem AGOL introduced some sort of geometry simplification and/or projection issue with the July 2018 AGOL update.
One solution Esri could use to fix this, would be to simply re-draw the feature halo on a 'zoom-in' event, so that the geometry could be simplified at small scale and re-drawn with more vertices if zoomed in to. pseudo-code: IF zoom-in event THEN re-request feature geometry via json and progressively request more detail and vertices. And perhaps with a minimum cap. If it's a simple property with a dozen or two vertices, no need to ever simplify, just request them all once.
This happens with a simple web map and even with a layer in web mercator. I also saw the effect on services from our 10.51 and 10.61 servers, both from SDE in state plane and a GDB in web mercator respectively, in poly layers in web maps. This would cause an end user to not trust the spatial accuracy of the entire platform. If someone clicks a property in a viewer and the lines get warped, I will be getting calls. Fortunately our current viewer uses Robert's eSearch which does not have this problem when highlighting a feature(s) geometry.
Tech Support has simply said it is submitted and can't say more; our rep said it may wait on 10.6.2. I hope this can be elevated to the uber ninjas in dev team. I asked Tech Support and they said to use Elevate in My Esri but that button is ironically literally missing.
note: this was when adding it as dynamic mapserver.
Kelly Gerrow fyi
This bug still is present in part. On further testing for a release candidate for my site, I noticed it still happens about 1 of every 5 to 10 clicks. (the 'warping' as per the original post, was on every click, for reference, before it was partially fixed in API 3.26)
I noticed it on the parcel layer which is on by default. I called Tech Support, they could not repro, but I repro'd on several machines here on Chrome on Win 10. So, there are 3 things this bug causes. I hypothesize these are related to the data geometry generalization bug in my first post above. For the original quantization/generalization bug TS said it was resolved by switching WAB to use API 3.26. But I still see the issues below. Also note, I bumped the API to version 3.27 in env.js and it still happened.
- When you click a parcel, occasionally it will highlight only part of the parcel.
- If this happens, it also often is warped or shifted. Especially if you move the map or popup, it will ‘snap’ away and shift away as shown below.
- Lastly, a third bug was noticed. Sometimes when you click a parcel, it simply doesn’t highlight, at all, such as shown below.
Interestingly I don't see this happen in MS Edge. Just Chrome. And, it happens on my screen with no zoom and 100% page size. (I have some monitors zoomed with Windows zoom but I have a reference monitor to test and it still happens on it in Chrome)
Also, this happens to viewers in WAB 2.5 with services from our internal server on 10.5.1 so it's not necessarily just 10.6.x causing this. It appears to be more of a JS API 3.2x bug.
The Support analyst said this bug is “fixed”. We have to upgrade to ArcGIS Server 10.7. He could not say when 10.7 is coming out. That is untenable. Will a fix from API 3.28 be able to address this issue?
Chris Whitmore I understand the Server/Enterprise aspect to generating the new geometry generalization property but upgrading a production server may not be possible for some time. Do you think a fix solely from the API can address it?
If I may recommend - I believe I have a way to fix this from a design view:
First - do not trigger the generalization until you hit a certain number of vertices on a feature or on all features in the extent, perhaps 500 or 1,000. Modern devices including mobile could handle that; perhaps the number could be based on some cross-platform testing. And let this be a programmable parameter, whether to trigger generalization after certain number of vertices and/or draw scale; with developers deciding that number or scale.
Second, let programmers simply have the option to turn this off. (that could be the 'hot fix' for API 3.28 at least, so we can turn this off until it's truly fixed and implemented)
:::update 12/4/18::::
I also see this bug where the parcel doesn't highlight cyan, in a plain old web map from a 10.6.1 service and 10.5.1 service. It takes a few clicks clicking around but it happens after about 10. I am thinking this is all related, given that all of it is regarding the popup cyan highlight.
10.61
10.51:
I don't know if this is caused only by a bug in Server 10.51 / 10.61 or if it is caused by or amplified by the JS API.
But I hope a fix from the JS API end can resolve this. That would be better than having to install a server patch on production machines.
I have been in touch with our Solution Engineer and TS and they've been great working with me diligently. They found this patch but since it is for Portal I don't know if it would help. Esri Support Portal for ArcGIS 10.6 (10.6.1) (Should I install it?) And we will not be able to upgrade our internal 10.5.1 machine for a while so hopefully an API update can resolve it. It is looking like we'll need the API Engineering team to weigh in here.
