Latest Contributions by RupertEssinger

Yes, see: https://community.esri.com/community/gis/web-gis/storymaps/blog/2017/03/19/arcgis-blog-how-to-launch-a-story-map-series-at-a-specific-entry  And here's a blog post that reviews all the supported URL parameters: https://community.esri.com/community/gis/web-gis/storymaps/blog/2017/07/27/story-maps-developers-corner-using-story-map-url-parameters  Rupert ... View more

Hi The embed bar is something we added to Story Maps this year. There were many cases where authors were embedding story maps in web pages in fairly small frames without providing a way to maximize that story for better/easier viewing, especially on mobile devices. So the embed bar provides that capability automatically. It can also appear when you embed Story Maps in other Story Maps, as you point out. When you embed a story inside another story , the embed bar get automatically suppressed if the ArcGIS domain (i.e. myorg.maps.arcgis.com) of the story you are embedding is the same as the ArcGIS domain of the story you are embedding it into. To see whether the embed bar will appear for stories embedded in your story map,  be sure to preview your story, because that rule doesn't kick-in inside the builder. So for example if you embed a story map that is on  www.arcgis.com into a story map that is on a different domain, like myorg.maps.arcgis.com, it will have that embed bar.   To suppress the embed bar when you embed stories created by other authors in your story map, access those stories using the same domain as your story map. So if your story is on myorg.maps.arcgis.com you can access any publicly shared story via that URL, and the embed bar won't appear. Alternatively, you can add the &classicEmbedMode parameter to the end of the URLs of the stories you embed, i.e. https://cityofcambridge.maps.arcgis.com/apps/Cascade/index.html?appid=dc50eccdc77d4ec7ab2e9de89630e5c0&classicEmbedMode   To suppress the embed bar when you embed stories in web pages, you can add the &classicEmbedMode parameter to the end of the URLs of the stories you embed.   Hope that helps   Rupert ... View more

Hi Adrian Officially, our support for photos in Flickr and Google+/Picasa has always been intended as a way for people and organizations who are already using those photo sharing systems to easily integrate them into Story Maps, and also provide a way for Story Map authors to access photos that other folks are already sharing publicly using those systems. For example when you access Flickr images from the Story Map builders you can enter the name of any author in order to find albums they are sharing publicly (so if you enter 'Rupert Essinger' you can access my public albums). In addition, in Story Map Cascade you can search Flickr publicly shared photos by keyword to add into your story, the same way you can search and access Unsplash images.  We've never intended Story Map authors to use Flickr or Google+ solely as a way to get photos into Story Maps, Flickr is a really nice place to host and share your photos, and being able to add public photos from Flickr into Story Maps easily is an added benefit of doing that. For example if you add Flickr images into Story Map Tour or Story Map Shortlist we pick up the geolocation, name and caption that is stored in Flicker for each pic. So if you work for , say, a non-profit that maintains a public Flickr album of pics, you can use them directly in your stories, or if you use Flickr already for sharing your own pics it is great. But we don't recommend getting a Flickr account solely as a way to get your pictures into Story Maps.  To add images into a Story Map our recommendation is always to upload your images directly into the Story Map builder. That's the easiest and most secure way to add images into Story Maps: your photos are stored in the story (or, in the case of Story Map Tour, as a layer in an associated web map) and are given the same sharing status as your story (so if your photos are confidential to your organization no one outside your organization will be able to access them if you only share your story within your Org, which is obviously not the case with Flickr/Google+), You also don't have to worry about photos being deleted or unshared in Flickr or Google+, especially if you are not the author, or worry about someone else on the web using one of your publicly shared pics in a way you might not expect or intend. (For example I mark my Flickr pics as public domain which is the most liberal sharing status, but it still felt a bit weird when one of my Hiking Trip to Mammoth Mountain pics was used in an online feature in Elle Decor magazine: they did credit me as the photographer but for public domain pics they don't need to notify you). If you have a large number of images you'd like to use, such as 50+ pics for the places in a Story Map Tour or Shortlist, I'd recommend putting those on your own web server, such as your agency or business's own web server or website, and simply referencing them via URLs. In this way you can manage your pics as a set of files and do things like include their URLs as attributes in map layers or spreadsheets and build your Tour or Shortlist in batch from those instead of one-by-one. That workflow isn't possible with image uploads or Flickr/Google+ images. You could reference images that are already on the web using URLs but the big issues with doing that are that their file size is often way too large for good draw performance, and images that you don't manage yourself have a tendency to be deleted or renamed without you knowing about it. Referencing images via URLs in Story Maps does not optimize the images automatically, like uploading them or pointing at them in a system like Flickr does, so you will want to be able to manage their file size yourself if you have a big database of images. For example for my Tours and Shortlists about San Diego I pick from a set of 200+ of image files I have put onto an Esri web server and that I have resized for good draw performance. So if you go this route you should definitely check the Story Map FAQs to find out the recommended image size for the Story Map app template(s) you want to use. Rupert ... View more

There's no longer a limit in Shortlist. Our original, download only version had a limit of 99 per tab because at that point we ran out of numbered marker icons . In the current version of Shortlist we generate the markers on the fly, so there's no limit. However for best performance and the comfort of your readers, we'd still recommend not exceeding 100 or so places per tab in a Shortlist. For really huge numbers of places (i.e. thousands), a web map containing clickable points, perhaps with photos in their popups, will be faster and easier to author with your GIS than a Shortlist.  Rupert ... View more