Latest Contributions by StephanieSmith

I have been working with the elevation profile widget for a hiking website. For us, this is a replacement to the WebAppBuilder version we had fully customized through CSS styling. I am finding the Experience Builder option to be too limiting. Below are some enhancements that would really help make this tool more versatile. Allow a way to choose how you want users to create a profile. Either select a line, draw a polygon, or both. Right now select a line and draw a polygon are always on. This is confusing for use cases where you don’t want users drawing their own or you might not have lines and only want them to draw. These should be options instead of always on.  Allow text customization to fit users needs for all the text within the widget. For instance changing "Select a line to view the elevation" to "Select a trail to generate a hike profile.” This will make the widget more accessible for diverse users and increase clarity on how to use the application for specific industries. The reset option combined with the “New Profile” button in user testing has been confusing. Please allow a way to turn off one and customize the text to give users better instructions. Like remove reset and change the button text to “Generate New Profile.” Ability to not have (Reference) added to the elevation reference layer legend detail. Most people have no idea what this means unless they are GIS professionals, they just want to know what the line and shaded area means (or not have it at all). This will make the widget more accessible for diverse users and increase clarity. Allow full css options to change colors of the lines, placement of icons, and overall customize the layout in a more dynamic way. There can be reasons why you might want the colors to be different from the general theme options in the overall Experience.  The following suggestion likely goes beyond just the profile widget, but there needs to be a way to customize how the “View Elevation Profile” appears in the pop-up. There seems to be no way to customize this or even limit it from showing up. But it would be helpful to allow a way to customize how the generated profile appears. Right now, it is nested under an icon with no clear indication what the icon is for. User testing has shown that this is confusing, hard to find, with too many clicks to get to what they need. It would be great if it could appear similar to how it appears in the Instant App Basic Version with just simple text beside “Zoom to”.     ... View more

It would be great if the pdf export from Insights maintained the vectors of the visualizations. This is necessary if you are doing any professional printing or work with graphic designers. The quality of the image exports does not work for all publishable material, but a vector based export would allow for the visualizations to be used in any size or media without having to completely recreate it in a vector based software. ... View more

The already configured dynamic charts would be very useful to share with a broader group besides the data curators with logins. I can share the analysis url with those with account logins or make everything public, however, I would like to share the already configured charts and graphs in a public way with the possibility of hiding some fields. This way public contributors or others that are interested in these data can see the patterns and trends, but keep unnecessary or sensitive fields hidden. Rebuilding them in dashboard has been problematic with multiple choice questions, and a pdf is only a static glance and not helpful for a survey that is continually being added to overtime. If sharing only the analysis page in this way is not possible, has there been considerations from the Survey123 development team in making sharing results easier for public data or better integration of the Survey123 data in Dashboards? ... View more

The newest or newer update to the basemap topographic option "world topographic map (v2)" in the basemap selection overrides the previous basemaps also titled topographic or "world topographic map". For maps and apps that relied on the original topographic map, the new version is completely different and does not serve the same purpose causing problems with already created products. Besides making a whole new color palette that may not match already created product styles, there are no topo lines in v2. This not only contradicts the name of this basemap but for products that needed the topo lines like in the original product, this override is a big problem. Why not name the new version something different that more closely reflects what it is displaying (i.e. hillshade with some administrative boundaries) and give both options in the basemap selector instead of replacing the actual topographic map with the new one? This way already created products won't be obsolete but instead expanded on.  Also, when something is named topographic, you expect it to actually be a topographic map. This is confusing not only to web map developers but for the end user as well. For us building the web map, we can, of course, search for the old version and still use it, but in web applications that only have the basemap selector, this replacement is a big problem. Here is an example in an elevation profile map that we use. To the left is the original version with topo lines and detailed labels and the replacement to the right of the same location without topo lines and far fewer labels. If you want to try it yourself to see the difference here is the East Rim Trail example used above. The initial load will be the original topo map, but if you switch the basemap to topographic in the basemap selector it will change to the new one. After the switch the only way to get the original back is to reload the page. ... View more

I have a public survey created on Survey123 online. I need users to submit images but the results (data/mapped features) need to be private, so personal information is not shared. I have followed directions via several blogs and other threads to set my editing as follows in the image below. When I test the survey I get an error message that it can not include attachments (images). Is this a limitation when limiting what features editors can see, or did I set something up incorrectly? View of my permissions on my Feature layer (hosted, view). ... View more