Latest Contributions by PeterKnoop

@JasonHrubizna1 If you set the Parallel Processing Factor to a number of processes greater than or equal to the number of system cores on your machine, then it will result in worse performance. Under those circumstances, your are forcing the swapping of a greater number of process across a lesser number of cores, so the overhead slows things done. Hence, when you choose 100% (and greater), you were slowing things down with that overhead (assuming other factors, such as I/O or memory, were not bottlenecks.) To achieve the maximum performance boost from parallel processing, you should choose a number (or percentage) that results in at least one core being left available for running processes other than the tiling job. Depending on what else you are doing on the computer while the tile job is running, you may even need to leave additional cores available to get maximum performance out of the cores being used for the tiling job. ... View more

Would really like to see support for links added to the Information Banner and Access Notice options. We often want to keep the message short and simple, so that people pay attention to it, while still wanting to include a link to more, extended information for people who need more details. ... View more

Would really like to see support for links added to the Information Banner and Access Notice options. We often want to keep the message short and simple, so that people pay attention to it, while still wanting to include a link to more, extended information for people who need more details. ... View more

Hi Kevin, I think there are a wide variety of successful ArcGIS Pro version management strategies. I believe which one might work best for a particular institution depends on what their user community looks like. So hopefully more folks will chime in with what their community looks like and what works best for them. For our community of over 10,000 GIS users, we typically have 150-250 daily users of ArcGIS Pro, and more than 400 over the course of a typical semester. The frequent users represent a mix of students, staff, and faculty using Pro for classes, research, and administrative tasks. The other users are a similar mix using Pro for a class project or two during the term, or using Pro for a particular phase of their research or administrative work. The users are from a number of different campus units, or students from a variety of degree programs, so there is a broadly-based community that needs to be served. With the differences between Pro 2.9 and 3.x, which version was used where, represented a major concern in terms of keeping what people wanted and what was available to them coordinated. In recent years, for the various versions of 3.x, this has not been an issue. Our users access Pro in managed computer labs, managed virtual environments, faculty/staff labs and offices, and on a wide-variety of personally-owned machines (particularly students). In general, the managed labs and VMs are kept at a specific version of Pro during a semester to avoid changes in UX, functionality, capabilities, etc. being a source of confusion. Those environments are controlled by different IT groups across the institution; however, they strive to kept their versions synchronized each semester. The version used in such environments is usually the latest version from about 2-3 months prior to a semester beginning. For labs and offices, people can choose whether to have their version managed or not. If they choose managed, then the version is generally the same as in the managed labs, or one of several previous versions (the use can choose the version they run.) If they choose to take care of it entirely themselves, then they can run any version they want. Similarly, when it comes to personal machines people can choose to run what ever version of Pro they want. For those managing their own ArcGIS Pro installations, they can access instructions and installers via the same, familiar institutional workflow they use for other such software available for personal use. The installers and instructions are typically customized for our environment. For example, they are set to use Named User licensing and our main ArcGIS Online organization as the Portal and Licensing servers. The customized instructions also are designed to help clarify some of the common pain-points found in Esri's documentation for installing Pro. For example, directing them to the specific .NET package (i.e., .NET Desktop Runtime) they need to select from all the versions Microsoft provides on the same download page. We do not use MyEsri for distributing ArcGIS Pro to end-users, as the overhead of managing access to MyEsri for such a large, broad user community is unrealistic. That means our ArcGIS administrators take on the task of downloading the installers from MyEsri. Whenever there is a new version they redistribute/repackage it for access via those familiar institutional sites. Such sites are fronted by the same single-sign-on resource that determines if a user is authorized to use ArcGIS, so only those users who are authorized to use ArcGIS can get to the installation resources.   ... View more

You can use the ArcGIS API for Python to access the _gnss_metadata.json attachments via the AttachmentManager class in the arcgis.features.managers module. For example, if you are interested in the gnss metadata for a single feature in your line or polygon layer, then determine the object ID of that feature and pass it to the download method. You will end up with a local copy of the JSON file which you can then parse to pull out the data of interest to you. Note that the json file will be stored locally under the specified "save_path" in a directory structure where the first level is the object ID and the second level is the attachment ID (e.g., <save_path>/1/1/_gnss_metadata.json.)  You can also pass download a list of OIDs, if you want to download the _gnss_metadata.json file for a bunch of features at once, and they will be placed into the same directory structure under your save_path.   ... View more

When working with Hosted Feature Layers, we've found that using the ArcGIS API for Python usually yields significantly better performance than ArcPy, especially if you apply your updates (or edits) in batches. What takes minutes with ArcPy might only take seconds with the ArcGIS API for Python. ... View more

As the warning message indicates, you are trying to create a layer that exceeds the USGS 3DEP service's limitations. You cannot use Make Image Server Layer for the whole USGS 3DEP data set, as it covers an area that exceeds the service's 8000x8000 pixel limit. To solve this, you will want to limit the area the tool is processing to an area of interest that is smaller than the limit.  You can do so by specifying a "Processing Extent" in the tool's Environments tab. (You can also directly specify a "Processing Extent" in the Environments tab in the Extract Multi Values to Points tool to avoid the same error there, if that approach fits your needs.) Since you are interested in a 24x24 mile area, however, the 1-m cell size resolution of the 3DEP data will likely result in an extent that is still greater than the 8000x8000 pixel limit. So you will need to breakup your area of interest into batches or chunks whose extents are less than the limit, or downgrade the elevation data to a lower resolution. ... View more

@StaceMaples wondering if you were deleting whole items (i.e., hosted feature layers), or if you were deleting features from a hosted feature layer on ArcGIS Online, but not the layer itself? If the latter, then according to BUG-000135310 (closed with "as designed") deleting features will not free up the ArcGIS Online storage used by those features, "Due to the nature of storage management by the data store engine, space is not necessary reclaimed after a feature is deleted."  In order to reclaim the storage used by deleted features, you need to compress the hosted feature layer's feature service after deleting features: Open the Item Details view of your hosted feature layer in ArcGIS Online. Scroll down and look for URL on the far right, and click to open the layer's ArcGIS REST Services Directory view. Click on "Admin" near the top-right. Scroll down to the "Supported Operations" at the bottom of the page, and click on "Compress". On the page that opens, click the "Compress Data" button. It may take some time to complete the operation, particular if you deleted a lot of features, so you may need to continue to check the status of the job. AND, if you have deleted all of the features in a table or layer -- perhaps by using Truncate  -- then there is the additional step of having to create a new feature (and deleting it, if you don't need it), which will finally trigger freeing up the space. The reported feature storage usage should update within a few minutes to show the reclaimed space. ... View more

For those able to follow it, BUG-000164474 (In-Review currently) is tracking the issue of Pro's incompatibility with high-precision date fields for tracking creation and last edit. ... View more

Removing the license duplicates is a good use case to support the existing Idea, Ability to display and select all members when managing settings for existing users on the Members tab.  ... View more

A try/catch capability would potentially help with the goal of capturing whether the current user has access to a data source, and if not, then return a message in a List widget, rather than popping up the login dialog. For example, one could wrap FeatureSetByPortalItem with a try/catch to handle the error returned when a user does not have access to a portal item. ... View more

@OwenGeo thanks for the detailed explanations! I think the documentation would be improved by adding such a level of information (e.g., Collaborate on a story, collection, or a theme.) ... View more