IDEA
|
Adding the use case of grading student's StoryMaps in courses for accessibility. In order to include the presence/absence of alt text as part of grading a StoryMap, it would be helpful to have an easy way to determine for how many of the possible locations in their story a student has provided alt text.
... View more
a week ago
|
0
|
0
|
24
|
POST
|
As an Esri Education Institution Agreement holder, are members of our community eligible for a discount on the cost of Esri Technical Certification Exams? Thanks!
... View more
2 weeks ago
|
1
|
2
|
94
|
POST
|
I don't know of a way to do this in the StoryMaps app itself. So far the best way I've found to do this requires modifying the JSON of the StoryMap using something like the ArcGIS Assistant. Below are the steps we share with our users, if they are willing to take on the risk of working directly with a story's JSON. Not required, however, if you're not comfortable working with JSON, then I would recommend making duplicates of your Briefing and StoryMap. Follow the remaining steps below using those copies until you are comfortable. Edit your destination StoryMap and add an Express Map block as a placeholder. It is not required, however, I would recommend publishing your StoryMap at this point, so that you can work on the draft version, and revert to this published version if something goes wrong. In ArcGIS Assistant, go to your Briefing and View Item JSON. Switch to the Data tab, from the default Description tab. In the "nodes" section, identify the node that contains the Express Map in your Briefing that you want to copy, and note it's id (e.g, "n-f9qxjg".) Look for that node's id in the "resources" section (near the bottom of the JSON), and note the listed itemId (e.g., "expressmap_1711645656520.json".) Now switch to the Resources tab at the top. Identify the resource(s) that represent your Express Map block in your Briefing. There should be one json resource whose name begins with draft_expressmap, which represents the current version of your Express Map in the draft version of your Briefing. If you have published your Briefing, then there should be a second resource with the same id, but whose name begins with pub_expressmap. If you you have no unpublished changes in your Briefing, then the two are the same. Otherwise, decide which version of you Express Map you want to copy to your StoryMap, the draft or published version. Click on the name of the Express Map json file that you want to copy (either draft or published), and copy the entire content of the file. (If needed, save it somewhere temporarily, as there a number of steps before you need to paste it.) Now go to your StoryMap in ArcGIS Assistant and View Item JSON. Switch to the Data tab. In the "nodes" section, identify the placeholder Express Map block that you added, and note its id. Look for that node's id in the "resources" section, and note the listed itemId. Now switch to the Resources tab. Identify the resources that represent your placeholder Express Map in your StoryMap. As before, there should be two resources, a draft_expressmap and a pub_expressmap, assuming you followed the advice above and published your StoryMap. Click on the name of the draft_expressmap to open the JSON view of it. Click on the "Edit resources" button in the top-right to enable editing the JSON content. Replace all of the JSON with what you copied from the Briefing resource item, and hit "Save." (I would recommend replacing only the draft version at this time, then viewing your StoryMap in edit mode, and only then publishing your StoryMap if you happy with what you have done. If something has gone wrong, then you can discard unpublished changes to revert to your original version of the StoryMap.) Now open your StoryMap in edit mode and you should see the Express Map you copied from your Briefing has replaced your empty placeholder Express Map.
... View more
3 weeks ago
|
1
|
1
|
143
|
IDEA
|
With today's wide-format screens, some users would like to be able to move the Sidecar slide navigator from being a horizontal strip along the bottom of the screen, to being a vertical strip along the side of the screen. They would like a way to change the configuration, perhaps as a setting toggle or by dragging it from one location along an edge to another. Given the consolidation of the Slideshow block into the Sidecar block as a layout option, it could also be helpful to have the initial orientation of the slide navigator visually reflect the flow of the selected layout. The navigator would be presented vertically by default for the Docked and Floating layouts, and horizontally by default for the Slideshow layout. The orientation of navigator would thus match the vertical scrolling actions a reader performs in a Docked/Floating layout, and the horizontal paging actions a reader uses in a Slideshow layout.
... View more
03-08-2024
06:01 AM
|
0
|
0
|
153
|
IDEA
|
Sometimes the spatial content you want a reader to focus on in a image or map in a Swipe block would be better served by a vertical swipe, rather than a horizontal one. Also, on a mobile device, with its narrow viewport, the swipe experience may be better served with a vertical behavior. Perhaps an option could be added to the Swipe tool for the author to choose between horizontal and vertical behavior?
... View more
03-07-2024
02:59 PM
|
3
|
0
|
172
|
POST
|
We have run into this as well when clearing out a hosted feature layer by truncating it. (Get yourself attached to BUG-000135310 for more details, which is listed as fix, however, they seem to mean in this case that "it is working as expected.") The workaround to reset the size, so that you are not charged credits unexpectedly, is to compress the empty feature service. And, if that doesn't do it by itself, then make an edit in the feature service to trigger the reset (i.e., add a bogus new feature, then delete that feature.) After a few more hours the size should be zero. (Our experience has been that the second step is required most, but not all time.) One way to do all this is to go to your hosted feature layer's Item Details view, after you have deleted all the data, then: View the feature service URL in the lower-right of the page. Select the Admin interface in the top-right. Select Compress from the Supported operations at the bottom of the page. Click the "Compress data" button. Give it a few hours for the size to go to essentially zero. If it hasn't changed, then go on to second part: Create a new feature in the layer. Delete that feature. Wait a few more hours for the size to go to zero. You do not have to wait though, if you don't care about seeing the size go to zero. Once you have deleted all the features, you can compress it, and immediately start editing features again, and you should see the correct size of your new content reflected after several hours.
... View more
03-07-2024
02:40 PM
|
0
|
0
|
259
|
IDEA
|
Being at an education institution, we continually are introducing new users to the Map Viewer. While users get it after awhile, most find the current experience initially counter-intuitive, and, if they are not frequent users, they are generally confused whenever time they resume using Map Viewer. As @AlexAnder notes, users are expecting to see an indicator shown when a layer is visible, rather than an indicator shown when a layer is not visible. For our users, who often are not previous users of Map Viewer Classic or Pro, this expectation is being set through user experience with other applications they commonly use.
... View more
03-02-2024
06:01 PM
|
0
|
0
|
353
|
POST
|
As @ChristopherCounsell notes, what you are looking for is a group's capabilities. If you set the parameter users_update_items=True when you create a group, then 'updateitemcontrol' is added to the group's capabilities. There are other capabilities a group can have, such as "distributed", so you should not rely solely on testing that capabilities is not null. I would recommend explicitly testing that 'updateitemcontrol' is in the group's list of capabilities. You can specify a capability as part of your group search query, so one way to retrieve a list of shared update groups is: shared_udpate_groups = gis.groups.search(
# A shared update group has 'updateitemcontrol' as one of its capabilites.
query = 'capabilities:updateitemcontrol',
# 10,000 appears to be a hard limit.
# If more than 10,000 might be returned, then split up your query and aggregate the results.
max_groups = 10000
)
... View more
03-02-2024
05:49 PM
|
1
|
0
|
224
|
POST
|
I don't have a solution for you. Only an explanation. I've found that the StoryMap embed block strips fragments from your URL. So the content with the "#" in your Experience Builder URL is removed. Unfortunately, that fragment is what Experience Builder is using to indicate it should be opened with the specified feature selected (see the Select data section in Use URL parameters.)
... View more
02-29-2024
12:39 PM
|
0
|
0
|
238
|
POST
|
@ThePreatorian that is helpful advice to QA programmatically created content. Do you know where one can find a definition of the StoryMap model to check against, such as what keywords are required, optional, etc.?
... View more
02-28-2024
05:18 AM
|
0
|
1
|
242
|
IDEA
|
@OwenGeo definitely a complicated problem! Happy as always to share pain points and use cases. Perhaps it would help to consider some more complete use cases too, rather than focusing on only the portion that intersects with StoryMaps in its current form? (Even the organization of Ideas places in this community has the unfortunate side-effect of forcing things into specific silos, which makes it difficult to figure out where/how to discuss user scenarios that span multiple aspects of the system. @SaraJL's post getting moved around being an example.)
... View more
02-27-2024
05:20 PM
|
0
|
0
|
299
|
IDEA
|
I'm not sure I would agree user education is the answer. Why not redesign the system to match user expectations and be more intuitive? Other than users with public-only accounts, aren't users tied to an organization? Perhaps the user experience could treat organization-centric access as the primary mode of operation? Perhaps single-purpose sites, like storymaps.arcgis.com could also be eliminated in favour of users going to their ArcGIS Organization, and then choosing to work on StoryMaps? In addition to being problematic for the use case described here, the siloing of StoryMaps into its own site feels like it goes against the idea of StoryMaps being able to integrate other aspects of ArcGIS Online in stories, such as web maps, dashboards, insights, etc.
... View more
02-26-2024
09:52 AM
|
0
|
0
|
269
|
IDEA
|
Another potential use case for this kind of functionality, using a feature service for your Map Tour that has as its symbology "an arrow or cone that pointed in the direction that the photo was taken" (from Idea, Map Tours Points.)
... View more
02-25-2024
06:27 AM
|
0
|
0
|
110
|
IDEA
|
When creating a Map Tour from an existing data source (i.e., Start with a feature service), it would be nice to have the option for the tour's map to use the existing style of the hosted feature layer. For example, you might be building a Map Tour of points of interest of different types in a park or at a field site, and you've styled the layer to use different symbols for different types of POIs. You want to have those symbols used in the Map Tour, rather than the default pins, as they help easily convey information about the POI.
... View more
02-23-2024
01:37 PM
|
2
|
1
|
196
|
IDEA
|
I will add that we too are observing this kind of siloed user experience being detrimental to people understanding ArcGIS Online and StoryMaps. They may "get it", for StoryMaps, the day they go through a tutorial, however, they are often challenged on how to proceed again in the short term, and how to leverage other components of ArcGIS Online in the long run. The current user experience develops an unfortunate perception and disconnect among our users that all they can do is work inside StoryMaps. Once the learn they can also access their stories directly from their ArcGIS Online content -- just like other content they may be working on, such as web maps, scenes, dashboards, insights workbooks, etc. -- then they are much more comfortable doing things, and better understand that StoryMaps is just piece of an overall picture; and a piece that can bring together other types of content they can generate. A common observation is confusion around what the "filtered" view of their content -- showing just their stories -- is supposed to achieve. This is especially true when their story involves other types of ArcGIS Online content. And, a common question is, "why can't I start a new storymap or web map from 'New item' in My Content?" Often paired with observations like, "content is where all of my stuff is stored," or "content is where I create other kinds of ArcGIS Online content." If one ditched the current StoryMap landing page, then it seems like the functionality that would need to be moved -- perhaps under New item in their content, or by clicking on the ArcGIS StoryMap app in the picker -- would be to choose between creating a new story, briefing, collection, or theme, and then proceeding directly with such. This kind of user experience, shared by other tools too, enforces a siloed view of the system that might match development team structures, however, it appears to use to hinder usability.
... View more
02-22-2024
05:55 AM
|
0
|
0
|
361
|
Title | Kudos | Posted |
---|---|---|
1 | 2 weeks ago | |
1 | 3 weeks ago | |
3 | 03-07-2024 02:59 PM | |
1 | 03-02-2024 05:49 PM | |
2 | 02-23-2024 01:37 PM |
Online Status |
Offline
|
Date Last Visited |
7 hours ago
|