|
IDEA
|
When designing a survey in Survey123 Connect, it would be helpful to be able to comment out rows in the XLSForm so that they are not processed. Sometimes I want to comment one or more rows because something is wrong in those rows, which is preventing the survey from rendering in Connect. So I want to hide those rows from being processed, so that I can see how everything else in the XLSForm is looking. Another use case is to paste in some rows from another XLSForm that I want to use as models for building new rows in the current XLSForm. I don't want those pasted rows processed, however, I want them there as a reference adjancent to the rows I am working on.
... View more
04-24-2025
11:34 AM
|
7
|
2
|
581
|
|
BLOG
|
If one intends to run this Notebook in ArcGIS Online, then make sure to change the runtime from ArcGIS Notebook Python 3 Standard - 7.0, which is missing some of the required libraries, to ArcGIS Notebook Python 3 Standard - 10.0. (Do not go to 11.0 or above, as the API changes beyond 10.0 are not compatible with this Notebooks' code.)
... View more
04-22-2025
12:43 PM
|
1
|
0
|
2776
|
|
POST
|
The workaround we have been using to do something like a Map Tour with multipoint "points" is to use a Sidecar with an Express Map: Insert a Sidecar into your story. Add an Express Map to the first slide's main media area, and add all of your points to the Express Map. You may find it helpful to use the group function to put all of the points for one project in the same group, as it makes it easier to style them all in one go in later steps. If you don't want popups on mouse-over for each point, then leave the fields empty for each point. Otherwise, if you do want popups, then you probably want to paste the same information into each point that is part of the same project. Duplicate the first slide, and edit the express map to change the color of all the points associated with your first project to make them stand out from the rest. (If you grouped the points in step #2, then you can do this all in one go, rather than idividually.) Enter information about the project in the slide's text and extra media area. Repeat Step #3 for each project you have. Hide (or delete) the first slide with all the points, if you don't need an overview slide with all the project points, and none of them highlighted. One of the shortcomings of this approach is if you need to add more points after you've made your initial Express Map. You would need to add the new points to original and each duplicate of the Express Map. Hope that helps!
... View more
04-17-2025
02:45 PM
|
1
|
0
|
873
|
|
IDEA
|
See also Set coordinate system when creating New Feature layer in ArcGIS Online.
... View more
04-16-2025
06:47 AM
|
0
|
0
|
397
|
|
POST
|
You might find this resource on self-check quizzes to be helpful: How to add a self-check quiz into ArcGIS StoryMaps using Survey123
... View more
04-01-2025
09:00 AM
|
1
|
0
|
1067
|
|
POST
|
In my experience, StoryMaps does not correctly enforce the 10MB limit. Instead, it appears to checking to see if the bytes value is greater than 10,000,000. (10MB does not equal 10,000,000 bytes, but rather is equivalent to 10MB x 1024 kB/MB x 1024 bytes/kB or 10,485,760 bytes.)
... View more
04-01-2025
06:13 AM
|
0
|
0
|
1138
|
|
POST
|
There are a number of solutions that would work here. Many of which folks have already suggested. If you are using Survey123 Connect to design your survey, are comfortable with Survey123 JavaScript functions, and your sites are far enough apart for the user's GPS to clearly distinguish one location from another, then I would suggest a variation on @ClayDonaldsonSWCA's use of the geospatial aspect, which would calculate your Site ID in real-time. You can use a custom JavaScript function to populate the site ID in your survey form based on where the person filling out the survey is standing. The script would use the geopoint question's location to identify the closest site from a feature class that contained the site locations and site IDs. This has worked well for us in similar situations, where we are trying to keep things as simple as possible for the data collectors, who are typically not GIS folks. Typically we hide the GeoPoint question in the survey, so that the user has a nice, clean, simple form. If we foresee the use case where a user might need to enter data while standing elsewhere, however, then we do present the GeoPoint question, so that they can move their position close to the desired site, so that the correct site ID is calculated. An example of such a script is provided by @IsmaelChivite on github, getNearsestRecord. It returns the whole record for the nearest site, however, you can modify it to return just your Site ID attribute, so that it can populate your survey question with that value.
... View more
03-31-2025
09:35 AM
|
0
|
0
|
919
|
|
IDEA
|
Be nice if one could choose to delete the SD file from such as warning as well.
... View more
03-28-2025
08:06 AM
|
0
|
0
|
276
|
|
IDEA
|
When exporting data to a particular format, provide methods that enable users to check what potential limitations may be imposed by that format, in order to identify and address potential data loss. This would be for classes like, arcgis.features.GeoSeriesAccessor.to_featureclass(), arcgis.gis.Item.export, arcgis.features.FeatureSet.to_geojson, etc. This will assist users – both new and experienced – with quality assurance when managing the export of data to a more limited format, such as from a feature set or hosted feature layer to a shapefile. Issues can arise later on, particular with automations, where changes in the data may trigger unexpected results not caught during initial testing. To enable users to produce more robust code for dealing with such circumstances, provide methods for evaluating limitations imposed by an export format on the original data source. Some quality assurance testing for these situations is already provided by methods like arcgis.features.GeoAccessor.sanitize_column_names. I’m sure many folks regularly find themselves writing code to check original data sources against potential limitations of an export format, with logic to decide on a predictable way to address those shortcomings, or to log a helpful error message for manual intervention. It would be helpful to have standardized methods in the API for the former part, identifying those export limitations in the context of a specific data source and the chosen format (e.g., shapefile, csv, kml, geojson.) For example, if exporting from a hosted feature layer to a shapefile, then warn a user about field names that will get truncated (and what the autogenerated new field names will be in a shapefile, in case they want to capture a field mapping to metadata), datetime fields (which will have their time component truncated, which they may want to address before the export by splitting into two fields), attachments that will not be included (which they may decide to export separately to a zip file with a link table), etc.
... View more
03-28-2025
06:41 AM
|
1
|
2
|
582
|
|
POST
|
The Pro patch release versions generally do not include updates to the Python package versions. So all of the 3.4.x versions, including the just released 3.4.3, come with the ArcGIS API for Python version 2.4.0. While you cannot update to 2.4.0.1 via the Package Manager within Pro -- even in your cloned environments (hasn't worked for me at least) -- you should be able to update it via conda without forcing it. You do need to do so in an environment cloned from arcgispro-py3. In such a cloned environment you can use: conda update arcgis -c esri And that environment should end up with 2.4.0.1.
... View more
03-20-2025
08:08 AM
|
3
|
1
|
1195
|
|
POST
|
I've had a similar experience with size and credit charges not going down as expected when features are deleted. See this thread about needing to use Compress and then adding a dummy feature to actually free up the storage: https://community.esri.com/t5/arcgis-online-questions/reduction-of-space-and-credit-consumption/m-p/1392911/highlight/true#M57968 You might give the Compress and edit route a try on your feature layer to see if that reconciles things with what your are expecting.
... View more
03-14-2025
09:01 AM
|
0
|
1
|
868
|
|
IDEA
|
@OwenGeo the Filter functionality achieves the goal! I think I would still want to keep this Idea alive as a suggestion for enabling the same thing through searching, should the limitations you mention go away (or as a reason for a new design without those limitations.) Searching is often a natural starting point for a question like this, particularly for people new to a product, while Filtering is typically something reserved more for those knowledgable about a product, who know more about what they are after. I did not notice that I could do this via Filtering. I think there are two things that obscure this functionality, which perhaps could be addressed. It isn't obvious that there is a filter functionality, as it is not present by default, as it is in other areas of ArcGIS Online. It is only accessible after one locates and clicks on the Filter toggle near the top-right. For example, if I am in My Content view in ArcGIS Online, the filter options are present by default in the same size browser window. Likewise, in the "my projects" view on the StoryMap website, the "filtering" options are already there on the left. I would suggest starting with the Filtering options displayed for the Gallery, when the screen width is sufficient to show the filtering options in those other areas. It isn't obvious that there is a level of filtering for specific features. When you first toggle open the Filter view, it shows one thing, Category, however, there is the greater-than sign as a visual queue to expand it. After expanding it, one sees a list of categories, like Features, however, there is no visual queue that it too can be expanded. It is only if one takes the time to click on Features that the additional options are presented. I would suggest adding a visual queue to indicate that the categories can also be expanded.
... View more
03-04-2025
10:38 AM
|
0
|
0
|
593
|
|
POST
|
When you are sharing from Pro to ArcGIS Online, there is an option to "Preserve editor tracking info." It sounds like you may not have enabled that when sharing? If you had editor tracking enabled for the data in Pro, then to carry that through to Online, you must check the box for "Preserve editor tracking info" when you are sharing your data. For example, see Configure a web feature layer for how to enable the option in that workflow.
... View more
02-27-2025
09:54 AM
|
1
|
1
|
620
|
| Title | Kudos | Posted |
|---|---|---|
| 3 | Friday | |
| 6 | Thursday | |
| 5 | 2 weeks ago | |
| 1 | 10-23-2025 06:38 AM | |
| 2 | 11-03-2025 08:52 AM |
| Online Status |
Offline
|
| Date Last Visited |
yesterday
|