Latest Contributions by K_Rocks

‎01-14-2021

Thanks for the reply. Neither the admin or dataset owner can add a field. The dataset has been in use for data collection by multiple organisation members since last summer and there has been no problem adding features or correcting entries, so it doesn't seem to be a permissions issue.

‎01-13-2021

Hi all, We have a wish to add a field to a hosted feature layer, but the option does not appear in an ArcGIS Online web map or the item's Data or Field pages for this item. When attempting to add the field in ArcGIS Pro, it also fails, with error 000852 given. The hosted feature service was created from publishing a Survey123 form. In order to handle repeats, it contains a 'parent' feature layer, several 'repeat' feature layers and a 'repeat' table. There have been a number of views created from this feature service for web map and ops dashboard purposes, but it is a layer in the original hosted feature service that the additional field is required for, i.e. not a copy or view. Given all of these existing views and the established link to a Survey123 form, I would be reluctant to create and publish a new feature service. Can anyone suggest what the problem might be? As I say, it is not a copy and nor does it have related tile layers, both of which are listed here as being restrictions to adding or deleting a field. I came across this post with a similar problem, but our situation is not connected to the Election Management solution mentioned. Thanks for any insight.

‎05-14-2020

We have a Enterprise login problem for ArcGIS Online accounts on Collector (v20.1) and now Explorer (also 20.1) on Android 9 devices. It is throwing up the "The server you are trying to connect to (https://www.arcgis.com) cannot be verified" error after entering the url and selecting the organization's Enterprise login name. It also gives a similar error on Survey123 v3.9.148, but this asks if you wish to continue, whereas Explorer and Collector do not. I am aware that there have been similar certificate issues flagged previously for more recent versions of Collector - see posts here and here - but we have tried installing certs locally on the device, as suggested, to no effect. These posts also refer to Portal, whereas we are only trying to access ArcGIS Online at this time. It is possible to login to ArcGIS Online within the device's internet browser with no such issue. As you would expect, there is a reluctance to upgrade the Survey123 version further in case it ends up with the same problem. Thanks for any insight.

‎02-26-2020

So as the form opens. Great - many thanks for clearing that up for me James.

‎02-24-2020

Hi, This is a simple query that I can't seem to find an answer to by searching. Is there any problem with publishing a Survey123 form that does not have a geopoint question on the form, but one which should record coordinates to a feature service? If so, when are these coordinates recorded: at the location that the form is opened or at the location that it is submitted? Thanks for any insight.

‎02-24-2020

Hi Peter, Yes, I ran through my scenario with the local Esri guys and making GlobalID = Guid type is the way to do it. In order not to be tampering with live feature services, I downloaded all 3 feature services to file geodatabases, appended the relevant tables one by one (as you suggest above), and then uploaded this as a new feature service to AGOL. All worked out fine. Thanks.

‎11-21-2019

I haven't heard anything yet on this, Leigh, but did come across this blog thread which suggests specifying the Type of the resulting GlobalID and ParentGlobalID fields as "Guid" rather than "GlobalID" when setting up the Append tool. Doing this appears to allow the old IDs to be maintained with an Append process in a file geodatabase at least (I had made a copy to try it rather than work with a live feature layer). As there happens to be no additional data coming in for that particular project over the next few months, I might try this Append procedure directly on the layers in the AGOL feature service after I've backed them up. However, it would be of some comfort if it could be confirmed that this is the correct approach.

‎11-18-2019

Thanks Curtis. I never thought the feature dataset might be the problem but it appears that it is, just as you thought. I've been using ArcMap 10.5.1 and tested things by copying a few of the feature classes to another geodatabase that doesn't have a feature dataset enclosing them. The model works fine then.

‎11-15-2019

I had hoped to create a DTM raster using a series of point feature classes in a file geodatabase. Each feature class covers a grid with its points all lying 10m apart (all in a feature dataset with projected coordinate system). As there are almost 300 of them, I planned to use a ModelBuilder iteration to run through all the feature classes with the Point To Raster tool converting them. There is no problem inserting the Feature Classes iterator and the output shown in the ModelBuilder window appears to to pick up the feature classes fine. However, when I try to link this to a Point To Raster tool, I run into a problem. Similar to this question and others I've found on StackExchange, I get an "Error 000918 - Cannot retrieve feature class" for the Input Features once I specify the desired output raster cellsize to be 10 in the Point To Raster tool set-up. This only arises using the iterator, though. I can run Point To Raster directly or in ModelBuilder for individual feature classes, setting the output cellsize as 10, without the error appearing. The input and output geodatabases are in different locations, so copying the features before Point To Raster, as suggested by some, doesn't make a difference. Is there something obvious I'm missing here? Thanks for any help.

‎09-30-2019

Hi, I'm hoping for some advice on the best procedure for appending related feature layers in a AGOL feature service. We have a hosted feature service on AGOL updating from a Survey123 form. It includes a Survey point feature layer and several repeats, 4 of which are point feature layers with potential attachments and related to that parent Survey layer (through parentGlobalID). There is also a table, again with repeats related to the Survey point. This feature service is currently live. There are two older iterations of the feature service, each with the same basic structure of the Survey layer and the several repeats layers with attachments. The parent Survey feature layers in these have slightly different schemas from the current one, with a small number of fields having being added/removed/renamed in the iterations. These feature services are no longer live. We wish to append the two older feature services to the current feature service, maintaining the relationships for each repeat and attachments to the parent survey. Bearing in mind the Append tool only allows one target dataset at a time, and therefore feature service-to-feature service is not possible, what is the best procedure to carry this out? If I append the Survey layers first, will the repeats then relate as expected? I tried to test this with local file geodatabase copies but found that ticking "Preserve Global IDs" in the Append tool resulted in a 999999 error. With this unticked the append did work, but surely that would result in the relationships being broken as the GlobalID-parentGlobalID relationships need to be maintained? I'm wary of testing it on the current live layer. Thanks for any help.

‎09-06-2019

The join works fine now, Peter, and updates as required, so it was indeed the reserved words. Thanks for your help in pointing us in the right direction.

‎09-05-2019

Thanks Peter. The BUG-000117882 that you've linked to refers to the error being thrown when 'Use current map extent' is selected. I had actually unselected that option and chose 'Create results as hosted feature layer view' (as the alternative solution suggests) in the attempted joins, so I can't blame that bug. My understanding was that creating a view was required anyway in order to have a live/dynamic join layer that updates as the Survey123 form adds to the underlying feature service. We are going republish the form (and therefore create a new feature layer) with the start and end field names replaced in order to see if it will allow a join now. I'd rather not waste someone's time raising a support case if that solves the issue for us anyway. However, if it doesn't, might there be another general reason that feature layers deriving directly from Survey123 forms fail to join?

‎09-04-2019

Thanks Peter. Yes, Layer 2 is a view based on a layer generated from a Survey123 form published through Connect. There are several select_one questions and repeats. Would that prevent a join working? I downloaded the hosted feature layer view as a geodatabase, replaced the start and end fields, uploaded the altered geodatabase, published a feature service and was able to join it to Layer 1 without a problem. Given that there are repeats, and therefore related layers/tables within the feature service, there is a reluctance to change the survey form too much to the extent that it would create a new feature layer, as we would then have to merge the data already collected.

‎09-03-2019

Hi all, I'm trying to make a (dynamic) feature layer from join analysis in AGOL. I own both feature layers and the join is based on attributes. However, I keep getting an ""Unable to add feature service definition" error, with a corrupted layer being created as a result. One of the feature layers is a view. Is that a problem? I have attempted the join using the original feature layer that the view is based on and still get the error. Layer 1 has the following fields: Username, Port, County, Email, Vessel, SurveyYear, Initials. Layer 2 (the view) has a lot more fields, which include: start, end, username, email, deviceid, version, datesSurveyStart, datesSurveyEnd, surveyID, datesTrip, datesTripDay, dateTrip. The other field names are specific to the project and are clearly not reserved words. Are there any reserved words that jump out from those lists as causing the problem? The intention is for the one-to-many join to be based on Layer 1's 'Username' and Layer 2's hidden 'Creator' attributes. Thanks for any help.

‎09-02-2019

Is there a way that this scenario - allowing the user to move on to a new repeat without filling in a required question - can be allowed but with the restriction enforced when the user tries to submit the form? Therefore the idea would be to prevent them from doing this and remind that there are required questions in some repeats to be completed before submission is allowed. Thanks.

Online Status	Offline
Date Last Visited	‎02-09-2021 07:27 AM

My Ideas

Latest Contributions by K_Rocks

Re: Add Field not available for feature layer

Add Field not available for feature layer

Apps-AGOL login error: server cannot be verified

Re: Survey123 without geopoint

Survey123 without geopoint

Re: Appending hosted feature layers with repeats

Re: Appending hosted feature layers with repeats

Re: Why would a ModelBuilder iteration throw Error 000918?

Why would a ModelBuilder iteration throw Error 000918?

Appending hosted feature layers with repeats

Re: Join failure - unable to add feature service definition

Re: Join failure - unable to add feature service definition

Re: Join failure - unable to add feature service definition

Join failure - unable to add feature service definition

Re: Required message not working in all Repeats

Add Field not available for feature layer

Re: Appending hosted feature layers with repeats

Re: Why would a ModelBuilder iteration throw Error...

Re: Data formats on Drone2Map (import and export)