Latest Contributions by DataOfficer

How do we make sure community sign in settings for hub premium are honoured? I have logged in to our hub site, gone to >Settings in order to edit the Sign In Options. I have disabled social logins and enabled 'Allow members to auto join with email'. These changes display correctly in the preview pane, but are not transferred over to the actual hub site. See screenshots below. 1. Settings showing social logins disabled and auto join with email enabled. Note preview pane displays correct settings. 2. Sign in screen showing social logins still enabled and no option to create a community user account Many thanks, Rob ... View more

We have a webpage (www.arc-trust.org/garden-dragon-watch), within which we have embedded a survey123 form, built using Connect. The embedded form contains a geopoint question. This displays correctly when the webpage is accessed from a PC or laptop, but not when accessed from some mobile devices / via some mobile browers. When a user clicks on the geopoint question to add their location, the map screen goes black (though the address entry still seems accessible). If the form is opened as a standalone item in a web browser (https://arcg.is/1XieXr0) it performs as expected. Are there any known limitations of browser types supported / unsupported?  I am using the following iframe html code: <div class="embed-container" style="height: 1500px;"><iframe width="680" height="2200" name="survey123webform" frameborder="0" marginheight="0" marginwidth="0" title="Amphibians and reptiles in your garden" src="//survey123.arcgis.com/share/046b1389d4884f659e06baafba1119eb" allow="geolocation https://survey123.arcgis.com; camera https://survey123.arcgis.com"></iframe></div> Screenshots of the issue Accessing via the embedded form on our website from a mobile device: Accessing via the direct link to the Survey123 webform on a mobile device:   As an example, on my own phone (Samsung Galaxy S5 Neo, Android) it does not work in the following browsers: - Google Chrome version 81.0.4044.138 (address entry displays, but map is black) - Samsung Internet version 11.2.1.3 (address entry displays, but map is black) - Microsoft Edge version 45.03.2.4958 (address entry displays, but map is black) Functions correctly in: - Mozilla Firefox 68.8.1 The issue has also been reported by iPhone 6 users (presumably running Safari), but as it is a public survey, it has been difficult to get feedback and device / browser specifications when issues are occurring outside of internal testing. Many thanks, Rob ... View more

Hi, I work at Amphibian and Reptile Conservation - a charity NGO in the UK. Our offices are based in Bournemouth, England, but we manage a number of reserves and have projects across Britain and further afield. My role is Data and GIS officer, which entails managing the organisations data and data flows, carrying out data analyses, supporting other staff as needed and various other bits and pieces. I am a zoologist and conservation biologist by training with a specialism in herpetology (reptiles and amphibians), and have picked up GIS and other skills along the way which I now use day to day.  Traditionally my spatial work has used ArcMap / ArcGIS Pro, but this year we have been working to integrate ArcGIS Online, Hub and a number of other products (e.g. Survey123, Explorer, Dashboard) in to our workflows and projects. We have made some good progress with this, and I am looking forward to further developments with these systems. Much of my work in GIS is related to species distribution mapping and modelling, and species monitoring.  ... View more

Make it possible to apply visibility range controls to selections and popups. We have visibility range controls in place to prevent the public viewing data at a high resolution (i.e. to obscure the exact location of a point or feature). If a feature is selectable, e.g. in a dashboard or webmap with popups, the selection remains beyond the set visibility range and the user can zoom to the exact point. This appears to be an oversight. The only workaround so far has been to disable popups and make features non-selectable, which is far from ideal as it limits the information that can be conveyed to users. Example: Figure 1 - Feature (right hand side) selected within set visibility range (popups are enabled for demonstration purposes) Figure 2 - Zooming beyond the visibility range removes the feature, but the selection (blue square) and popup remain. Figure 3 - zoomed in to pinpoint accuracy, with selection still showing. ... View more

Make it possible to apply visibility range controls to selections and popups. We have visibility range controls in place to prevent the public viewing data at a high resolution (i.e. to obscure the exact location of a point or feature). If a feature is selectable, e.g. in a dashboard or webmap with popups, the selection remains beyond the set visibility range and the user can zoom to the exact point. This appears to be an oversight. The only workaround so far has been to disable popups and make features non-selectable, which is far from ideal as it limits the information that can be conveyed to users. Example: Figure 1 - Feature (right hand side) selected within set visibility range (popups are enabled for demonstration purposes) Figure 2 - Zooming beyond the visibility range removes the feature, but the selection (blue square) and popup remain. Figure 3 - zoomed in to pinpoint accuracy, with selection still showing. ... View more

Make it possible to apply visibility range controls to selections and popups. We have visibility range controls in place to prevent the public viewing data at a high resolution (i.e. to obscure the exact location of a point or feature). If a feature is selectable, e.g. in a dashboard or webmap with popups, the selection remains beyond the set visibility range and the user can zoom to the exact point. This appears to be an oversight. The only workaround so far has been to disable popups and make features non-selectable, which is far from ideal as it limits the information that can be conveyed to users. Example: Figure 1 - Feature (right hand side) selected within set visibility range (popups are enabled for demonstration purposes) Figure 2 - Zooming beyond the visibility range removes the feature, but the selection (blue square) and popup remain. Figure 3 - zoomed in to pinpoint accuracy, with selection still showing. ... View more

I would like to coalesce date fields in Survey123. Is this possible? Explanation and use case described below. Note: This was raised as a support case but I was referred here to suggest it as an idea (if coalescing of dates is not already supported). I've produced a survey form using Connect, published publicly and accessed solely via the web form for submissions. The user is given three options of date entry (reason for this is given below): Date (d/m/y), Month (m/y), Year (y) Background calculations are then used to feed those results in to a single RecordDate field using coalesce functions (see below). These are all outside of a repeat (note we have had issues with coalesce functions within a repeat in recent support cases). The bind::esri:fieldType is set to esriFieldTypeDate. The feature is storing the individual date value (date_day, month_year or date_year) but not performing the coalescing function - leaving RecordDate blank. Testing without setting the bind::esri:fieldType to esriFieldTypeDate results in successful coalescing, but stores the output as a string rather than a date. As another workaround, is there a way we could convert this coalesced string to an appropriate date format? The use case for this is we want a strong understanding of the accuracy of dates submitted with wildlife records. This is important for analysing phenology.  Summary of XLSForm design of what we have tried so far: type name label calculation date date_day Date date monthyear Month & Year date date_year Year hidden coalescedate1 Date (coalesced 1) coalesce(${date_day},${monthyear}) hidden coalescedate2 Date (coalesced 2) coalesce(${date_day},${date_year}) hidden coalescedate3 Date (coalesced 3) coalesce(${coalescedate1},${coalescedate2}) hidden RecordDate Record date format-date(${coalescedate3},'%m/%d/%Y')   ... View more

I have a public webmap containing a single hosted view layer which holds wildlife records from a public survey. This webmap / single layer feeds in to a public dashboard. The layer visibility range is set so that the public can only see (in the dashboard) where wildlife records have been submitted up to a certain visibility range. This helps protect the location of those completing the survey, whilst still displaying the results on a map. The problem, is that if a public user manages to find the public webmap or view layer in ArcGIS Online, they can change the visibility range to any level, undermining the entire point of limiting the visibility range to the public. I have tried setting the visibility range of the non-public layers which the public view layer is derived from but this seems to have no effect. ... View more