Latest Contributions by TracyThorleifson

In the current ArcGIS Explorer release (20.0.1, build 2647), raster layers can be included in a mobile map package (mmpk) authored in ArcGIS Pro, but the symbology of the raster layers in the source ArcGIS Pro project is not honored. Instead, they revert to what appears to be a default grayscale stretch symbology. The source map in ArcGIS Pro looks like this: Here's what the same area looks like in Explorer: Not bad, but not nearly as nice as the original. It would be really nice if Explorer could be enhanced to honor the original ArcGIS Pro symbology. The desired functionality would be especially useful with digital elevation rasters and the like, where the important information is encoded in the pixel values. For those who would like to play with this data: Turkey Mountain Ranch ArcGIS Pro map package Turkey Mountain Ranch mobile map package ... View more

While you can use pip to install a package in a conda Python environment, such packages do not appear in the ArcGIS Pro Python Package Manager, leaving an un-savvy user with a misleading understanding of which Python modules are actually installed in a given environment. However, the 'conda list' command will display all installed modules in a conda environment, including those installed using pip. It would be very nice if the Python Package Manager would at least display packages installed with pip, like the 'conda list' command. (With the understanding that package metadata other than version would be unavailable for the pip-installed packages, since pip packages do no include conda metadata.) For extra credit, it would be really great if the Python Module Manager were able to search for and install pip packages. Justification: Many Python modules are available for installation via pip rather than conda. In many cases where both conda and pip packages are available for a given Python module, the conda package will be several versions behind the pip version. If you need the latest and greatest for a given Python module, often only a pip package will be available. The reason for this is that pip is the primary installation tool for pure Python modules in the larger Python community. (Conda, on the other hand, offers built-in environment management, and can handle distribution of non-Python dependencies, which pip cannot. So while it's not as ubiquitous as pip, conda is a technically superior tool for managing Python installations, and a good choice for Python module/environment management in ArcGIS Pro.)  ... View more

I need access to Azure 4.0.0. There is (of course) a pip install available, but no conda install (highest version for conda install is 1.0.2). Accordingly, I created a cloned environment, and installed from the command line via conda and pip: activate arcgispro-py3-azure-crypto (my cloned environment; pip is already in this environment, however, I did upgrade pip to 19.1.1.) pip install azure When I list packages in conda, everything looks fine: However, when I look at the environment in Pro, nothing is there: Everything is working, which means the conda listing is correct (and the packages are installed in the appropriate envs directory, but not in the pkgs directory of <localappdata>\ESRI\conda), but it’s just not showing up in the Pro Python Package Manager. I did a little digging around, and it looks like the Python Package Manager is actually reading the above contents from C:\Program Files\ArcGIS\Pro\bin\Python\pkg-metadata\metadata.json. Question 1: How do I get these pip-installed packages to show up in the Python Package Manager? Question 2: Is the Python Package Manager reading from the metadata.json file, and if so, how do we update it? Question 3 (and this is a larger question): What is the best practice for installing our stuff in conda world? Are we OK to install our own packages directly to the arcgispro-py3 environment, or should we be creating a new environment (or selecting another existing environment) and installing to that? Thanks in advance! Tracy ... View more

I'd like to provide a bit of feedback on Event Editor configuration documentation, in particular documentation relative to modifying the config.json file for actual use. While I was able to get the Event Editor up and running without too much pain, that's only because I'm already reasonably versant in the operation and administration of ArcGIS Server and Portal. Without that prior experience, I don't believe I'd have been able to successfully configure Event Editor using the documentation provided. The documentation for modifying the config.json file (Configuring the Event Editor web application) is particularly deficient in providing useful detail and examples for Portal implementations. I humbly offer the following specific suggestions: Property: webmap - The example rwc.json webmap configuration file is almost useless. Documentation for this file should explain, in detail, each element of the .json webmap file. Documentation should explain to the user how to obtain webmap URLs and other relevant properties on ArcGIS Server, as well has how to do the same for basemap layer elements in ArcGIS Online. Screenshots should be provided. Property: geometryServiceUrl - Documentation should tell the user how to locate the URL for the geometry service on ArcGIS Server, with appropriate screenshots. Property: proxyUrl - The provided link takes the user to the generic ArcGIS Serve JavaScript API 3.x documentation home page - it doesn't take you to any topic pertinent to the subject property. Property: security: portalAppId - A link to the topic for obtaining the Portal App ID for the registered web app (Configuring Portal for ArcGIS or ArcGIS Online for Event Editor) should be provided, as well as a discussion of why this is important from a security standpoint. The above suggestions should be considered minimal enhancements; they'll help the user get Event Editor up and running in a reasonably secure fashion in a Portal implementation, but not much more. It would be very helpful to provide the user with step by step configuration overview of some sort; perhaps a flow diagram with embedded links would be appropriate. A tutorial video of some sort might also prove very useful. In general, the documentation appears to targeted towards someone who already knows how to do the configuration, and just needs a reference document. It does not appear to be targeted towards first time APR users, much less users who are novices in Portal and ArcGIS Server administration. If the intent is to help promote widespread adoption of APR, the existing documentation is not doing a lot to help. ... View more