昨年11月にリリースされた ArcGIS Pro 2.9 に含まれていたアイデアを投稿してからしばらく経ちました。実際には32週間、または224日、あるいは5,376時間…ですが、誰が数えているでしょうか？多分私だけかもしれませんが、リリースの時期は本当に好きです。なぜなら、その時に ArcGIS Pro チームが行った作業を共有できるからです。皆さんの作業をより良くするために継続的に改善を重ねています…！
ArcGIS Pro 3.0 はメジャーリリースなので、アップグレードを決定する前にいくつか追加で考慮すべき点があります。Get Ready for ArcGIS Pro 3.0 とそのブログで参照されているドキュメントを必ず確認して、情報を得て、アップグレードの最適なタイミングについて正しい判断ができるようにしてください。
ArcGIS Pro 3.0 には ArcGIS Ideas を通じて提出された50以上のアイデアが含まれています。ビデオでクイックデモをご覧ください。すべてのアイデアがビデオに含まれているわけではありません。ビデオ内で紹介されているものにはブックマークされた時間が記載されているので、直接その部分にジャンプできます。お楽しみください！
最もリクエストされたもの
新しいフィーチャクラスを作成せずに空間結合 (8:26)
Change Domain Owner ツールの追加 (8:15)
ユーザーが SQL Server geodatabase の名前を変更できるようにする (8:06)
アプリケーション
プロジェクト終了時に表示キャッシュを自動クリア (7:27)
タブハイライト (1:18)
解析 & ジオプロセシング
エクスポート時にフィールド名エイリアスを保持するオプション (2:40)
レイヤーエクスポート時にフィールドの並び替えを許可する (2:47)
ArcGIS Pro 更新中にクローンされた Python 環境を更新する (7:16)
ジオプロセシングウィンドウで以前の属性による選択を保持する (7:00)
ジオプロセシングツール - 選択されたフィーチャの注記 (3:09)
ArcGIS Pro 2.6：テーブルの値を連結するジオプロセシングツール (6:04)
出力フィールドと場所の一貫性 (2:30)
排他的ポリゴン内の空白グリッド／ラスター (5:50)
すべての結合をプログラムで削除する機能
Pro で Python を使って COGO を更新する機能 (4:51)
フィールドマッピング：GP ツールで新しい出力フィールドをより簡単に追加する機能 (3:46)
ユーティリティネットワークのステージング時にデフォルトでBranch Versioningをオンにする<\/A><\/U> (3:38<\/A>)<\/P>ArcGIS ProからのWebレイヤー共有・上書き時に欠落しているWebレイヤー編集設定をダイアログに追加する<\/A><\/U> (3:57<\/A>)<\/P>Pro - すべての既存ファイルを表示する「出力場所」を復活させる<\/A><\/U> (2:22<\/A>)<\/P>テーブルフィールド選択<\/A><\/U> (2:16<\/A>)<\/P>お気に入りにサーバー接続プロパティを表示する<\/A><\/U> (1:23<\/A>)<\/P>モバイルジオデータベースをデフォルトにする<\/A> (1:30<\/A>)<\/P>Merge Parcel Pointsの「結合するポイント」リストのサイズ変更を許可する<\/A><\/U> (1:51<\/A>)<\/P>.rbjファイル（DataReviewerバッチジョブ）をジオデータベースの属性ルールに変換するコンバーター<\/A><\/U>ArcGIS Pro - webSceneの更新<\ / A ><\ / U > (< A href = " https : \/ \/ mediaspace . esri . com \/ media \/ t \/ 1 _ hc4hj4l6 ? st = 65 " target = " _ blank " rel = " noopener nofollow noreferrer " > 1 : 05 <\ / A > ) <\ / P > < P >< U >< A href = " https : \/ \/ community . esri . com \/ t5 \/ arcgis-pro-ideas \/ set-defaults-in-move-to-tool \/ idi-p \/ 1097987 " target = " _ blank " > 「移動先」ツールでのデフォルト設定を行う <\ / A ><\ / U > <\ / P > < P >< U >< A href = " https : \/ \/ community . esri . com \/ t5 \/ arcgis-pro-ideas \/ add-zoom-to-select-to-the-selection-group-in-edit \/ idi-p \/ 1011245 " target = " _ blank " > 編集タブの選択グループにズームして選択を追加する <\ / A ><\ / U > (< A href = " https : \/ \/ mediaspace . esri . com \/ media \/ t \/ 1 _ hc4hj4l6 ? st = 30 " target = " _ blank " rel = " noopener nofollow noreferrer " > 0 : 30 <\ / A > ) <\ / P > < P >< U >< A href = " https : \/ \/ community . esri . com \/ t5 \/ arcgis-parcel-fabric-ideas \/ merge-parcel-points-should-filter-selection \/ idi-p \/ 1107088 " target = " _ blank " > Merge Parcel Pointsは選択をフィルターすべきである <\ / A ><\ / U > <\ / P > < P >< U >< A href = " https : \/ \/ community . esri . com \/ t5 \/ arcgis-parcel-fabric-ideas \/ warn-user-if-currently-selected-record-does-not \/ idi-p \/ 1129502 " target = " _ blank " > 現在選択されているレコードが編集中の区画と一致しない場合、区画への誤ったレコード割り当てを避けるためにユーザーに警告する <\ / A ><\ / U > (< A href = " https : \/ \/ mediaspace . esri . com \/ media \/ t \/ 1 _ hc4hj4l6 ? st = 35 " target = " _ blank " rel = " noopener nofollow noreferrer " > 0 : 35 <\ / A > ) <\ / P > < P > <\ / P > < P >< STRONG > マッピング＆ビジュアライゼーション <\ / STRONG > <\ / P > < P >< U >< A href = " https : \/ \/ community . esri . com \/ t5 \/ arcgis-pro-ideas \/ colorblind-mode-in-arcgis-for-cartographic-design \/ idi-p \/ 940504 " target = " _ blank " > 図式設計用ArcGISの色覚異常モード <\ / A ><\ / U > (< A href = " https : \/ \/ mediaspace . esri . com \/ media \/ t \/ 1 _ hc4hj4l6 ? st = 458 " target = " _ blank " rel = " noopener nofollow noreferrer " > 7 : 38 <\ / A > ) <\ / P > < P >< U >< A href = " https : \ / \ / community . esri . com \ / t5 \ / arcgis-pro-ideas \ / arcgis-pro-apply-color-scheme-on-selected-symbols \ / idi-p \ / 939589 " target = " _ blank " > ArcGIS Pro：選択したシンボルにカラースキームを適用する <\ / A ><\ / U > (< A href =
@giancarlociotoli This is a very good question that the Geostatistical Analyst team spent quite a lot of time thinking about and debating. We came to the conclusion that this tool should only be used for predictive purposes, and it was not suitable for explanatory purposes. This is why explanatory variable coefficients and PCA loadings are not provided by the tool.
Without going into too much detail, problems arise with EBKRP's subset mixing methodology. Different subsets will perform PCA independently, and their loadings are often wildly different, even for the same explanatory variables. Within a single subset, this is not a problem, but there is no clear way to meaningfully aggregate different loadings in areas of transition between different subsets.
EBKRP mixes only the final predictive distributions across subsets produces, and this produces stable predictions. However, that does not imply that mixing individual components of the models produces stable estimates of a mixed component. In our experimentation, we found that attempting to mix components produced unstable coefficients and uninterpretable loadings, while still leaving stable predictions. Because of this, we only recommend it for predictive purposes, not explanatory purposes (this is also why the word "Prediction" is explicitly in the name of the tool).
- Eric Krause
Regarding the Empirical Bayesian Kriging Regression, ArcGis Pro help reports that this algorithm for estimating a response variable needs a set of rasters as predictors. Furthermore, help reports that before building the regression kriging model, the explanatory variable rasters are transformed into their principal components, and these principal components are used as the explanatory variables in the regression model. However, there is no possibility to see in the output the results of the PCA, in terms of how many factors were extracted and what are the loadings of the original variables within the factors. Can you please tell me if there is a way to display these results, and if not, are you going to implement a function that can return the number of factors extracted and the loadings of the factors?
Thanks
Best regards
Giancarlo
giancarlo.ciotoli@igag.cnr.it
@KoryKramer done!
https://community.esri.com/t5/arcgis-pro-ideas/make-quot-keep-previous-selection-and-or-field/idi-p/1205625/jump-to/first-unread-message
Hi @KoryKramer - Sorry for the delayed response. Below is an example of starting a field calculation for the street name, but the previous calculation was for the street type - obviously not useful. In general I find it takes a little longer for the dialog box to come up and then I have to delete it before beginning what I need to do. In Pro I find it really helpful to use the history tab or just leave the dialog box open if I want to repeat a query or field calculation. I realize keeping the previous query/calculation could be helpful - but I would much prefer the option to start with a clean slate each time.
I will submit a suggestion to disable this option and see what sort of traction we can get!
Hi @JohannaKraus2 You're right, that we brought this in because of the ArcMap equivalency aspect, and that it can be quite handy in iterative selection processes. Since you say that it is driving you crazy, can you share an example of what kinds of queries you typically set up, say in Select by Attributes (or wherever you see this that annoys you)? Is it that you are setting up multi-clause queries, or it is annoying even if you have a single clause that is persisted when the tool is re-opened?
It would be good for us to understand your situation, but to answer your question, no, there is not an option to disable this behavior (you could submit that as an idea though to help us gauge what other users are in your situation where they don't want this behavior...)
Looking forward to any additional details - those actually would be good fodder for a new idea if you submit one. Thanks!
@KoryKramer thank you have for having all the 3.0 updates all in one place, I really appreciate it.
The keep previous selection and calculations is driving me a bit crazy. I do realize this is a request based on arcmap functionality (and I can definitely appreciate that), but I found the history tab pretty useful if I need to repeat previous geoprocessing tasks. Is it possible to turn this option off? I looked under project - options - geoprocessing but I didn't see anything obvious. Thanks.
I'll be sure to pass on your thanks to the team @BranislavBlagojevic
Great Work, Kory!
Thank you!
Glad to hear that, Robert! Thank you for your continued contributions - they keep us improving 🙂
Thanks Kory. I've been working with it for less than a day but the enhancements in functionality and especially speed in 3.0 are much appreciated.
サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
