Ça fait un moment que je n'ai pas publié les idées qui accompagnaient la sortie d'ArcGIS Pro 2.9 en novembre dernier. En fait, cela fait 32 semaines. Ou 224 jours. Ou 5 376 heures... mais qui compte ? Peut-être que c'est juste moi, mais j'aime vraiment le temps de sortie car c'est à ce moment-là que je peux partager le travail que l'ArcGIS Proéquipe a accompli, en améliorant continuellement pour vous aider faire votre travail... mieux !
ArcGIS Pro 3.0 est une version majeure, donc il y a quelques considrations supplmentaires faire avant de dcider de mettre jour. Assurez-vous de consulter Prparez-vous pour ArcGIS Pro 3.0 et la documentation rf9frence9e dans ce blog afin d'tre inform et pouvoir prendre la bonne dcision sur le meilleur moment pour effectuer la mise jour.
ArcGIS Pro 3.0 comprend plus de 50 ides soumises via ArcGIS Ideas. Regardez les dmos rapides dans la vido. Toutes les ides ne sont pas incluses dans la vido ; celles qui le sont indiquent le temps signet pour que vous puissiez y accder directement. Profitez-en !
Les plus demands
Jointure spatiale sans cration d'une nouvelle classe d'entit9 (8:26)
Ajouter l'outil Changer le propri9taire du domaine (8:15)
Permettre aux utilisateurs de renommer leur g9odatabase SQL Server (8:06)
Application
Effacer automatiquement le cache d'affichage 9 la fermeture du projet (7:27)
Surlignage des onglets (1:18)
Analyse & G9otraitement
Option pour conserver l'alias du nom de champ lors de l'exportation (2:40)
Permettre de r9organiser les champs lors de l'exportation d'une couche (2:47)
Mettre 9 jour les environnements Python clon9s lors de la mise 9 jour d'ArcGIS Pro (7:16)
Conserver la s9lection pr9c9dente par attributs dans la fen8atre de g9otraitement (7:00)
Outils de g9otraitement - noter les entit s s lectionn es (3:09)
ArcGIS Pro 2.6 : Un outil de g otraitement pour concatener les valeurs d'une table (6:04)
Coh rence dans le champ et l'emplacement de sortie (2:30)
9Grille/Raster vide l'int rieur des polygones exclusifs ( ) < P > < U > < A href = " https : // community . esri . com / t5 / arcgis - pro - ideas / remove - all - joins - programatically / idi - p / 974557 " target = " _ blank " > Supprimer toutes les jointures programmatiquement </ A > </ U > < / P > < P > < U > < A href = " https : // community . esri . com / t5 / arcgis - parcel - fabric - ideas / update - cogo - with - python - in - pro / idi - p / 930624 " target = " _ blank " > Mettre jour COGO avec Python dans Pro </ A > </ U > ( < A href = " https : // mediaspace . esri . com / media / t / 1 _ hc4hj4l6 ? st = 291 " target = " _ blank " rel = " noopener nofollow noreferrer " > 4 : 51 </ A > ) < / P > < P > < U > < A href = " https : // community . esri . com / t5 / arcgis - pro - ideas / field - mapping - add - new - output - field - more - easily - in / idi - p / 1146281 " target = " _ blank " > Cartographie des champs : Ajouter un nouveau champ de sortie plus facilement dans les outils GP </ A > </ U > ( < A href = " https : // mediaspace . esri . com / media / t / 1 _ hc4hj4l6 ? st = 226 " target = " _ blank " rel = " noopener nofollow noreferrer " > 3 : 46 </ A > ) < / P > < P > < U > < A href = " https : // community . esri . com / t5 / arcgis - pro - ideas / enable - metadata - support - for - the - new - atbx - toolbox / idi - p / 1119208 " target = " _ blank " > Activer la prise en charge des m tadonn es pour le nouveau format de fichier atbx toolbox </ A > </ U > ( < A href = " https : // mediaspace . esri . com / media / t / 1 _ hc4hj4l6 ? st = 209 " target = " _ blank " rel = " noopener nofollow noreferrer " > 3 : 29 </ A > ) < / P > < P > < U > < A href = " https : // community . esri . com / t5 / arcgis - pro - ideas / support - python - toolbox - as - the - project - standard / idi - p / 1038015 " target = " _ blank " > Supporter Python toolbox comme la toolbox standard du projet </ A > </ U > ( < A href = " https : // mediaspace . esri . com / media / t / 1 _ hc4hj4l6 ? st = 101 " target = " _ blank " rel = " noopener nofollow noreferrer " > 1 : 41 </ A > ) < / P > < P > < U > < A href = " https : // community . esri . com / t5 / arcgis - pro - ideas / update - python - version / idi - p / 1133932 " target = " _ blank " > Mettre jour la version Python </ A > </ U > < / P > < P > < U > < A href = " https : // community . esri . com / t5 / arcgis - pro - ideas / rename - tool - option - to - rename - alias / idi - p / 1030482 " target = " _ blank " > Renommer l'option d'outil pour renommer l'alias </ A > </ U > < / P > < P > < U > < A href = " https : // community . esri . com / t5 / arcgis - pro - ideas / add-fields-multiple-could-import-from-existing / idi-p /1106026" target = "_blank">Ajouter des champs (multiples) pourrait importer depuis un modl e existant ou une classe d'entit template </ A ></ U >( < A href = href="https:\/\/community.esri.com\/t5\/data-management-ideas\/turn-on-branch-versioning-by-default-when-staging\/idi-p\/933796" target="_blank">Activer la versionnage de branche par défaut lors de la mise en scène d'un Utility Network<\/A><\/U> (3:38<\/A>)<\/P>Ajouter les paramètres manquants d'édition de couche web au dialogue lors du partage\/écrasement d'une couche web depuis ArcGIS Pro<\/A><\/U> (3:57<\/A>)<\/P>Pro 93 ramener 93 Emplacement de sortie 94 qui affiche TOUS les fichiers existants<\/A><\/U> (2:22<\/A>)<\/P>Sélection de champ de table<\/A><\/U> (2:16<\/A>)<\/P>Afficher les propriétés de connexion serveur dans Favoris<\/A><\/U> (1:23<\/A>)<\/P>Géodatabase mobile par défaut<\/A> (1:30<\/A>)<\/P>Permettre le redimensionnement de la liste 93 Points à fusionner 94 dans Fusionner les points de parcelle<\/A><\/U> (1:51<\.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\/.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\.\\."/>
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.
Glad to hear that, Robert! Thank you for your continued contributions - they keep us improving 🙂
Great Work, Kory!
Thank you!
I'll be sure to pass on your thanks to the team @BranislavBlagojevic
@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.
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!
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!
@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
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
@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
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
