Latest Contributions by NaicongLi

Hello @wayfaringrob , Thank you for your feedback.  ArcGIS Pro is already behaving as you suggested - when you create a new file geodatabase or mobile geodatabase in the project home folder, the newly created geodatabase will be automatically added to the project, appearing under the Databases container.  Could you please describe your workflow in more details where you did not see this happening?  Thank you. ... View more

Hello @MicheleH1_DNReply, @DavidDurst, @LynnCarlson__GISP, @JamalNUMAN, and everyone, (This is a response to this idea thread and to https://community.esri.com/t5/arcgis-pro-ideas/stop-recreating-missing-geodatabases/idi-p/1010302 and https://community.esri.com/t5/arcgis-pro-ideas/add-options-on-create-new-project-dialog/idi-p/928765.) We have been listening to your suggestions and comments, and we understand that you have workflow disruptions connected to this aspect of the architecture of ArcGIS Pro. We have in fact been exploring solutions for this for some time, but unfortunately haven't yet found one that would not have a negative impact on functionality, without fundamental changes of ArcGIS Pro’s architecture. From its initial design, an ArcGIS Pro project has three fundamental properties that must be specified – project home folder, project default geodatabase, and project default toolbox. They are there to ensure that when you perform an operation, the output always has some place to go, even if you did not specify the location. These requirements have been there since day one as a built-in assumption for many operations. Their absence could cause unexpected and bad behaviors in ArcGIS Pro. This is the reason why ArcGIS Pro requires their presence during the creation of a new project, and auto-regenerates them when they are lost. We agree with you all that we need to provide more flexibility in how the default geodatabase and toolbox are handled. Some of you have proposed alternative ways to handle this, for example: ArcGIS Pro does not generate a default geodatabase and toolbox when creating a new project. For the reasons above, this is unlikely to happen, at least not in the near future. At the project creation time, allow users to specify an existing geodatabase and toolbox to be used as the project default geodatabase and toolbox. This is indeed a direction that we are considering. When the default geodatabase or toolbox is missing or broken (which could be made to happen when the project is closed, or while it is open, if you manipulate the default geodatabase or toolbox in File Explorer instead of in ArcGIS Pro), have ArcGIS Pro prompt the user to create or select one. It’s been suggested to have this happen on project reopening, or when a Geoprocessing tool is about to run, or when the project is being saved. In all cases, this would require blocking all the operations in the UI until the default geodatabase or toolbox is restored, a state that many users would not want. We agree with you that it is annoying to see default geodatabases and toolboxes regenerated after you deliberately deleted them in the File Explorer. We will continue to look for a good solution that would not cause major impacts on ArcGIS Pro’s operations, and we are keeping this idea thread open. In the meantime, however, given the current constraints we have, the best thing to do is to NOT manipulate default geodatabases and toolboxes in File Explorer. In fact, managing your items inside ArcGIS Pro instead of File Explorer has always been the recommended practice, even for nondefault geodatabases and toolboxes. If you want to use a different geodatabase as the project default geodatabase, please use the following workflow: Add to the project the geodatabase that you want to be the default one (or create a new one). Rename it as needed. Right-click it and click Make Default. Delete, or remove the original default geodatabase in ArcGIS Pro if you do not want to use it in the project. Use the same workflow to change the default toolbox. One side point, in case some people are not aware of this option when creating new projects: instead of letting ArcGIS Pro create a default geodatabase and toolbox, you can designate a pre-existing geodatabase and toolbox for all new projects that you create from here on, by using the settings in the Options dialog (General tab, Create projects section). Note that you can change these settings any time and as often as needed. Again, we are keeping this idea thread open and will continue to look for a good solution, while balancing it with our other priorities. Thank you all for contributing your comments and suggestions. ... View more

Hello @MicheleH1_DNReply, @DavidDurst, @LynnCarlson__GISP, @JamalNUMAN, and everyone, (This is a response to this idea thread and to https://community.esri.com/t5/arcgis-pro-ideas/stop-recreating-missing-geodatabases/idi-p/1010302 and https://community.esri.com/t5/arcgis-pro-ideas/arcgis-pro-2-4-2-why-the-arcgis-pro-creates-gdb/idi-p....) We have been listening to your suggestions and comments, and we understand that you have workflow disruptions connected to this aspect of the architecture of ArcGIS Pro. We have in fact been exploring solutions for this for some time, but unfortunately haven't yet found one that would not have a negative impact on functionality, without fundamental changes of ArcGIS Pro’s architecture. From its initial design, an ArcGIS Pro project has three fundamental properties that must be specified – project home folder, project default geodatabase, and project default toolbox. They are there to ensure that when you perform an operation, the output always has some place to go, even if you did not specify the location. These requirements have been there since day one as a built-in assumption for many operations. Their absence could cause unexpected and bad behaviors in ArcGIS Pro. This is the reason why ArcGIS Pro requires their presence during the creation of a new project, and auto-regenerates them when they are lost. We agree with you all that we need to provide more flexibility in how the default geodatabase and toolbox are handled. Some of you have proposed alternative ways to handle this, for example: ArcGIS Pro does not generate a default geodatabase and toolbox when creating a new project. For the reasons above, this is unlikely to happen, at least not in the near future. At the project creation time, allow users to specify an existing geodatabase and toolbox to be used as the project default geodatabase and toolbox. This is indeed a direction that we are considering. When the default geodatabase or toolbox is missing or broken (which could be made to happen when the project is closed, or while it is open, if you manipulate the default geodatabase or toolbox in File Explorer instead of in ArcGIS Pro), have ArcGIS Pro prompt the user to create or select one. It’s been suggested to have this happen on project reopening, or when a Geoprocessing tool is about to run, or when the project is being saved. In all cases, this would require blocking all the operations in the UI until the default geodatabase or toolbox is restored, a state that many users would not want. We agree with you that it is annoying to see default geodatabases and toolboxes regenerated after you deliberately deleted them in the File Explorer. We will continue to look for a good solution that would not cause major impacts on ArcGIS Pro’s operations, and we are keeping this idea thread open. In the meantime, however, given the current constraints we have, the best thing to do is to NOT manipulate default geodatabases and toolboxes in File Explorer. In fact, managing your items inside ArcGIS Pro instead of File Explorer has always been the recommended practice, even for nondefault geodatabases and toolboxes. If you want to use a different geodatabase as the project default geodatabase, please use the following workflow: Add to the project the geodatabase that you want to be the default one (or create a new one). Rename it as needed. Right-click it and click Make Default. Delete, or remove the original default geodatabase in ArcGIS Pro if you do not want to use it in the project. Use the same workflow to change the default toolbox. One side point, in case some people are not aware of this option when creating new projects: instead of letting ArcGIS Pro create a default geodatabase and toolbox, you can designate a pre-existing geodatabase and toolbox for all new projects that you create from here on, by using the settings in the Options dialog (General tab, Create projects section). Note that you can change these settings any time and as often as needed. Again, we are keeping this idea thread open and will continue to look for a good solution, while balancing it with our other priorities. Thank you all for contributing your comments and suggestions.   ... View more

Hello @MicheleH1_DNReply, @DavidDurst, @LynnCarlson__GISP, @JamalNUMAN, and everyone, (This is a response to this idea thread and to  https://community.esri.com/t5/arcgis-pro-ideas/add-options-on-create-new-project-dialog/idi-p/928765 and https://community.esri.com/t5/arcgis-pro-ideas/arcgis-pro-2-4-2-why-the-arcgis-pro-creates-gdb/idi-p/931850.) We have been listening to your suggestions and comments, and we understand that you have workflow disruptions connected to this aspect of the architecture of ArcGIS Pro. We have in fact been exploring solutions for this for some time, but unfortunately haven't yet found one that would not have a negative impact on functionality, without fundamental changes of ArcGIS Pro’s architecture. From its initial design, an ArcGIS Pro project has three fundamental properties that must be specified – project home folder, project default geodatabase, and project default toolbox. They are there to ensure that when you perform an operation, the output always has some place to go, even if you did not specify the location. These requirements have been there since day one as a built-in assumption for many operations. Their absence could cause unexpected and bad behaviors in ArcGIS Pro. This is the reason why ArcGIS Pro requires their presence during the creation of a new project, and auto-regenerates them when they are lost. We agree with you all that we need to provide more flexibility in how the default geodatabase and toolbox are handled. Some of you have proposed alternative ways to handle this, for example: ArcGIS Pro does not generate a default geodatabase and toolbox when creating a new project. For the reasons above, this is unlikely to happen, at least not in the near future. At the project creation time, allow users to specify an existing geodatabase and toolbox to be used as the project default geodatabase and toolbox. This is indeed a direction that we are considering. When the default geodatabase or toolbox is missing or broken (which could be made to happen when the project is closed, or while it is open, if you manipulate the default geodatabase or toolbox in File Explorer instead of in ArcGIS Pro), have ArcGIS Pro prompt the user to create or select one. It’s been suggested to have this happen on project reopening, or when a Geoprocessing tool is about to run, or when the project is being saved. In all cases, this would require blocking all the operations in the UI until the default geodatabase or toolbox is restored, a state that many users would not want. We agree with you that it is annoying to see default geodatabases and toolboxes regenerated after you deliberately deleted them in the File Explorer. We will continue to look for a good solution that would not cause major impacts on ArcGIS Pro’s operations, and we are keeping this idea thread open. In the meantime, however, given the current constraints we have, the best thing to do is to NOT manipulate default geodatabases and toolboxes in File Explorer. In fact, managing your items inside ArcGIS Pro instead of File Explorer has always been the recommended practice, even for nondefault geodatabases and toolboxes. If you want to use a different geodatabase as the project default geodatabase, please use the following workflow: Add to the project the geodatabase that you want to be the default one (or create a new one). Rename it as needed. Right-click it and click Make Default. Delete, or remove the original default geodatabase in ArcGIS Pro if you do not want to use it in the project. Use the same workflow to change the default toolbox. One side point, in case some people are not aware of this option when creating new projects: instead of letting ArcGIS Pro create a default geodatabase and toolbox, you can designate a pre-existing geodatabase and toolbox for all new projects that you create from here on, by using the settings in the Options dialog (General tab, Create projects section). Note that you can change these settings any time and as often as needed. Again, we are keeping this idea thread open and will continue to look for a good solution, while balancing it with our other priorities. Thank you all for contributing your comments and suggestions. ... View more

Hi @AlfredBaldenweck , I changed the status of your idea back to Open, as you requested. ... View more

Hello @wayfaringrob, The functionalities that you mentioned above on the Living Atlas site already exist in ArcGIS Pro, through the filters in both Catalog views and the Add Data browse dialog box: You can also view the basic metadata for the selected item in the Add Data browse dialog, and its full metadata in a Catalog view. In a Catalog view, you can also switch to the tiles view: Please let us know whether these functionalities in ArcGIS Pro are meeting your needs. Thank you for your feedback. ... View more

@Bud - status changed back to Open. ... View more