|
IDEA
|
Another scenario in which this functionality would be helpful is when a group of users have shared editing access to a StoryMap, and the last user to have it open for editing doesn't close it. Perhaps they simply forget or they become otherwise engaged, and it sits open unnecessarily, and their collaborators who try to edit it are presented with the warning about someone else is already editing the story. Perhaps the trigger would be 8 hours of inactivity?
... View more
12-17-2024
12:06 PM
|
0
|
0
|
2022
|
|
POST
|
@EmmaTeuten1 as you noted you don't have complete control over the report date ranges. You can produce multiple reports and aggregate the CSV files and/or filter the CSV file using your favourite tool to the desired date range. Besides exploring the report CSV files in a Notebook, by downloading them directly into a notebook, the ArcGIS REST API also provides access to the data from which reports are derived, and with more granular control, see Portal History
... View more
12-10-2024
08:15 AM
|
0
|
0
|
1770
|
|
POST
|
While there is not a direct download option from that part of the interface, the same data is available from ArcGIS Online Administrative Reports, Organization > Status > Reports. You can find documentation on this capability at Create and schedule reports, and a nice overview in Supercharge your ArcGIS Online Organization Management with Reports. For example, if you want to generate a list of users who have used ArcGIS Pro in the last four months, you could generate an Activity report for that time period. You could then filter the report for the "login" action for the "arcgisprodesktop" clientid, and eliminate duplicate "actor" values (i.e., usernames) for users who logged in more than once during the time period, to get your list of recent ArcGIS Pro users.
... View more
12-10-2024
05:39 AM
|
2
|
2
|
1804
|
|
POST
|
This is a open bug with Enable Editor tracking in ArcGIS Pro. You can ask Esri Support to attach you to BUG-000164474 to track progress on resolving the issue. Another workaround, though also time consuming, is to add two new fields that are low-precision date fields, calculate their values from the corresponding high-precision fields, delete the high-precision fields, rename the new fields to the original names, and then turn on editor tracking. You can implement that workflow in a Notebook for convenience and speed, if you find yourself doing it regularly.
... View more
12-05-2024
11:33 AM
|
3
|
0
|
4516
|
|
POST
|
ArcGIS Pro does not work well when used directly with cloud storage sync technologies, such as for Dropbox, OneDrive, Google Drive, etc. It can result in unexpected data loss and should be avoided. Read more in ArcGIS Pro and Cloud Storage Services.
... View more
12-05-2024
11:23 AM
|
1
|
0
|
685
|
|
BLOG
|
It looks like their is a typo above, and the correct option for signIn is "require", not "required", when you want to force users to sign in to access a publicly shared survey.
... View more
11-26-2024
08:33 AM
|
0
|
0
|
1989
|
|
IDEA
|
I'll add the terminology of polar plot or polar chart for this idea as well.
... View more
11-19-2024
05:47 AM
|
0
|
0
|
1484
|
|
IDEA
|
@achapapkowski The warning recently added right at the top of the page for Install and set up --> ArcGIS Pro is perfect! I think that will be very helpful in preventing users from wasting time going down a path that will fail.
... View more
11-14-2024
05:44 AM
|
0
|
0
|
1671
|
|
IDEA
|
There are great instructions to get one started with HOW TO: Download a large hosted feature service with attachments from a REST endpoint. It stops, however, at the point where you have downloaded a bunch of separate database replicas. It would be nice improvement if the document also included the steps for how to recombine the separate replicas back into a single geodatabase.
... View more
11-07-2024
06:52 AM
|
2
|
0
|
416
|
|
POST
|
Unfortunately there isn't a direct method for this yet in the ArcGIS Python API. Would be a good enhancement idea to submit though (via ArcGIS API for Python Ideas or github.) The workaround we use is to directly edit the JSON in the form package, manually changing the status from open to closed, or closed to open. Below is simplified code that makes that simple change. (If your survey status is set to scheduled, then the code won't work as-is, however you could add code to handle scheduling as well.) Make sure to put the item ID for your survey in the code below. from arcgis import GIS
from zipfile import ZipFile
import os
# Connect to GIS
gis = GIS("home")
# Get Survey123 Form as item.
item = gis.content.get('provide_item_ID_of_survey_form_here')
# Download the data package for the form (its a zip file in this case.)
item.download(
save_path=".",
file_name="survey_data.zip"
)
# Extract all the files in the form package
with ZipFile("survey_data.zip") as zObject:
zObject.extractall('survey_data')
###
# Choose one of the following to uncomment and run: open to closed, or closed to open
###
# Set an Open survey to Closed.
with open(r'survey_data/esriinfo/form.json', 'r') as f:
x = f.read()
if( '"status":"open"' in x ):
print("Changing status from open to closed")
x = x.replace('"status":"open"', '"status":"closed"')
with open(r'survey_data/esriinfo/form.json', 'w') as f:
f.write(x)
with open(r'survey_data/esriinfo/form.info', 'r') as f:
x = f.read()
if( '"status":"open"' in x ):
print("Changing status from open to closed")
x = x.replace('"status":"open"', '"status":"closed"')
with open(r'survey_data/esriinfo/form.info', 'w') as f:
f.write(x)
# # Set a Closed survey to Open.
# with open(r'survey_data/esriinfo/form.json', 'r') as f:
# x = f.read()
# if( '"status":"closed"' in x ):
# print("Changing status from closed to open")
# x = x.replace('"status":"closed"', '"status":"open"')
# with open(r'survey_data/esriinfo/form.json', 'w') as f:
# f.write(x)
# with open(r'survey_data/esriinfo/form.info', 'r') as f:
# x = f.read()
# if( '"status":"closed"' in x ):
# print("Changing status from closed to open")
# x = x.replace('"status":"closed"', '"status":"open"')
# with open(r'survey_data/esriinfo/form.info', 'w') as f:
# f.write(x)
# Compress all of the files in the form package directory to a zip file.
with ZipFile('new_survey_data.zip','w') as zip_ref:
for root, dirs, files in os.walk('survey_data'):
for file in files:
zip_ref.write(os.path.join(root, file), os.path.relpath(os.path.join(root, file), 'survey_data'))
# Upload updated form package back to item on ArcGIS Online.
item.update(
item_properties=None,
data = r'new_survey_data.zip'
)
... View more
10-31-2024
12:54 PM
|
1
|
1
|
3529
|
|
POST
|
@ZacharyHart this unfortunately sounds like it is probably an issue specific to your environment, so I'm not sure I can help further. My best guess is that your fresh environment does not meet one or more of the system requirements of 2.4.0. Perhaps it was not an empty environment, and you've installed other packages in it that are the source of the incompatibility?
... View more
10-31-2024
06:24 AM
|
0
|
0
|
3228
|
|
IDEA
|
When a new major/minor version of the arcgis package is first released, it often is not compatible with the default python environment available in the latest release of ArcGIS Pro. Since much of the documentation talks about first cloning the default Pro python environment, and then upgrading/installing arcgis into the cloned environment, the documentation should discuss this. Many users are not knowledgeable enough about arcgis and conda/python to understand that at times there are incompatibilities between the latest release of arcgis' requirements and the default python environment they have in Pro. For example, the current arcgis release, 2.4.0, is not compatible with the default python environment in the currently released version of Pro, 3.3. Once Pro 3.4 is released, then it will compatible, however, in the meantime, many users are being set up for failure.
... View more
10-31-2024
06:12 AM
|
3
|
4
|
1775
|
|
POST
|
@ZacharyHart, is it the case that you are trying to install arcgis 2.4.0 into a conda environment that you cloned from the default arcgispro-py3 environment that comes with ArcGIS Pro? arcgis-2.4.0 is not compatible with some of the packages (e.g., arcpy) in the default environment created by currently available versions of ArcGIS Pro (i.e., 3.3). It will be compatible with the default environment shipping with Pro 3.4. It will also be the arcgis version included in ArcGIS Notebook Runtime 11. For the time being, if you want to use arcgis 2.4.0, then you have to create a new, empty conda environment, and install it there. (It is often the case that there is a short window during which the latest version of the arcgis package is not compatible with the default Pro environment, until the next major/minor version of Pro is released.) In that new, empty conda environment, the command conda install -c esri arcgis=2.4.0 arcgis-mapping will install arcgis 2.4.0 specificially, and arcgis-mapping and their related dependencies. (arcpy is not one of the dependencies, and the currently available versions of arcpy on the esri channel do not include one that is compatible with arcgis 2.4.0)
... View more
10-31-2024
05:52 AM
|
2
|
2
|
3245
|
| Title | Kudos | Posted |
|---|---|---|
| 1 | a week ago | |
| 4 | a month ago | |
| 1 | 06-18-2026 06:19 AM | |
| 3 | 06-05-2026 02:45 PM | |
| 4 | 06-02-2026 06:04 AM |
| Online Status |
Offline
|
| Date Last Visited |
3 hours ago
|