nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

バグ：ArcGIS Onlineでフィーチャのポップアップのアウトラインが歪む

Anonymous User

バグ：ArcGISでポップアップのアウトラインが歪むが、3.25のサンドボックスでは正常に動作する

上記の元のスレッドは、このバグを最初に経験した際に、まずJS APIのカテゴリに投稿したものです。そのため、最初の投稿は削除していただいて構いません。ただし、これはArcGIS Server 10.6.1、またはAGOLを実行している環境の不具合によるもののようです。

バグの内容： Webマップにポリゴンレイヤーを追加します。ポップアップを有効にしてクリックすると、以下に示すようにアウトラインが大きくずれ、位置が合わず、形状も歪みます。 Esriのテクニカルサポートでも再現され、割り当てられたバグIDは # BUG-000115968 です。

3.25のサンドボックスでは正常に動作します（この例のとおり）。そのため、2018年7月のAGOLアップデートで、何らかのジオメトリの簡略化や投影に関する問題が導入されたようです。

Esriがこの問題を解決する方法の一つとして、'zoom-in'イベント時にフィーチャのハローを再描画する方法があります。そうすれば、小縮尺ではジオメトリを簡略化し、ズームインした際には頂点を増やして再描画できます。疑似コード：ズームインイベントが発生したら、JSON経由でフィーチャのジオメトリを再取得し、詳細度と頂点数を段階的に増やしてリクエストする。上限値も設けるとよいでしょう。頂点が十数個から二十数個程度の単純なポリゴンなら、簡略化せず、一度ですべて取得すればよいだけです。

これは単純なWebマップで発生し、Web Mercatorのレイヤーでも同様に発生します。 10.51と10.61のサーバーのサービスでもこの現象を確認しました。それぞれ、ステートプレーン座標系のSDEとWeb MercatorのGDBを使用し、Webマップのポリゴンレイヤーで発生しました。この問題は、プラットフォーム全体の空間精度に対するエンドユーザーの信頼を損なう可能性があります。ビューアーでユーザーが区画をクリックしたときに線が歪んだら、問い合わせが殺到するでしょう。幸い、現在使用しているビューアーではRobert's eSearchを使っており、フィーチャのジオメトリをハイライト表示する際にこの問題は発生しません。

テクニカルサポートからは、報告済みでこれ以上は言えないとの回答しかありませんでした。担当者によると、10.6.2まで対応が見送られる可能性があるそうです。開発チームの超一流エンジニアにこの問題が届くことを願っています。テクニカルサポートに問い合わせたところ、My Esriの「Elevate」を使うよう案内されましたが、皮肉なことに、そのボタン自体が見当たりません。

注：これは、ダイナミックマップサーバーとして追加した場合のことです。

Kelly Gerrow‌ ご参考まで

タグ付きの投稿をもっと見る

Accepted answers

Anonymous User

Chris Whitmore‌ & Robert - perfect. That fixes it. Thank you. 3.26 example - ArcGIS Web Application

Before 3.26 was out they had had me test 3.24 so I had already had that example (as posted in EAC forum) but had not tested 3.26 yet, and was thinking it was Server. It is curious it never impacted the Sandbox. Must be some interaction between the API and WAB versions. Thanks both. Have a great day!

All comments

KellyGerrow

Hi Kevin,

Thanks for the FYI. Here is some information about escalating bugs through My Esri:

https://community.esri.com/groups/technical-support/blog/2016/03/28/how-to-escalate-a-defect

Esri Technical Support

Please go ahead and follow the steps for an official escalation as this can be tracked and followed up on. I'll update this post when I have more information.

-Kelly

Anonymous User

Hi Kelly, thank you for your reply as always!

I noted above the button is ironically missing. It only says Subscribe. Support was not sure why it was not present.

The problem with having inaccurate geometry displayed back to a user... For a property mapping site, it's an issue. It will lead to users questioning accuracy. We were hoping this would be fixed a few weeks given the severity. I proposed a solution in terms of business logic for how to handle returning geometry at a progressively higher detail above; although with a popup one would think it should never be an issue since it is only one feature except in certain circumstances like multi-part features or large detailed polygons like an entire state. Nevertheless, rendering progressively more detail as a user zooms would seem a good solution.

KellyGerrow

Hey Kevin,

Thanks for the feedback,

This bug was marked as a duplicate of another existing bug. This is planned to be addressed in the Javacript API (and Map Viewer) in the upcoming September release of ArcGIS Online. Katie Cullen

-Kelly

Anonymous User

Hello Kelly,

We're experiencing the same bug in our ArcGIS Enterprise deployment (10.6.1). Though we already have an incident running with our local esri reseller, we're currently down one of the core features of the platform because of this (as an Electricity & Gas DSO with many assets close to eachother "selecting" a feature is something our users do a lot). For now we're hosting feature layers (which won't group nicely in default apps) but it's a huge huge huge issue at the moment.

Do you have any insight in a patch for Enterprise users? An in-place downgrade is simply not possible due to how the platform built-in back-up tooling works...

Anonymous User

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?

Kelly Gerrow‌ Katie Cullen‌

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)

Anonymous User

:::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.

KellyGerrow

Hello,

There are two issues mentioned in this blog that result in similar issues but are resolved indifferent ways.

1. There was a bug in the Java script API, which was fixed in ArcGIS Online last release (September 2019) and can be fixed through a patch to Enterprise 10.6.1

Esri Support Portal for ArcGIS 10.6 (10.6.1) This isn't an issue that was identified with ArcGIs Enterprise 10.5.1, so if you are running into this issue please check out the second issue or get in contact with Technical Support for more information.

2. Google Chrome V. 70, introduced an issue where features shift. This has been fixed in Chrome V 71 and 72. Chrome 71 should be released soon. For updates, check out this status page:Chrome Platform Status

As this fix needs to be implemented in the browser, we suggest using a different browser or waiting for the new version. If you are experiencing the issue in a different browser, please get in touch with technical support to narrow down what is causing the issue.

Here is a link to the bug logged from the chrome issue:

BUG-000117959: In a Google Chrome web browser, an individual map se..

Please let us know if you have questions,

-Kelly

Anonymous User

Kelly Gerrow‌ yay!! you did it! I think that has fixed it. I updated and haven't seen it all day. I'll post back if I do. Thank you again.

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.