Latest Contributions by SFM_TravisBott

‎05-12-2022

Ago-assistant works great. But not for Story Maps. Esri has documentation for a python script to clone content to another organization but it doesn't work yet.

‎05-10-2022

Is it possible to re-order domain options (by description) on a published layer? My layer has ~50 or so domain values that have been tacked on over time like a jalopy, and there are enough dependencies on it that I would rather not overwrite the layer with a new version from Pro. Is there any kind of back-door option? The GUI is beyond cumbersome. Thanks!

‎05-10-2022

Robert - please see my comment above. Item ownership can be changed, but not of a published story map. There also seems to be unique difficulties transferring a story map between orgs using AGO assist.

‎05-05-2022

@RobertBorchert I see what you're saying but you're updating the domain in the item description, which is an open text field. That's not really what that's for. It's a wide dataset with a whole host of fields, several of which have long domains. To put all of those in open text is impractical. Our org uses FGDC format. Each code/description combination for each item it domain has its own text box, making copy/paste all at once impossible. Each 'enumerated domain' is a single code/value description that needs to be added individually if they don't carry over automatically (which is in itself perplexing, since it's not consistent. See below. What there needs to be is a button to import a domain from a table or gdb into the metadata.

‎05-05-2022

Unfortunately you don't seem to be able to change ownership of a map that's been published, even within the org. You can change ownership of drafts, however, so if somebody else needs to edit it we will make a copy of the original, deprecate it, and then change ownership of the draft copy and re-publish. It's stupid but it's what they give us, so far as I can tell.

‎05-03-2022

Thanks, Robert. That would save literally typing each out, but there would still be a copy/paste for each code and then for each description. I have domains with dozens of options and that's still not practical.

‎05-02-2022

Is there a way to import domain code/description into a feature class's metadata? Once can import a domain to the geodatabase itself using Domain to Table/Table to Domain, but I can't find a way to import that same domain into the feature classes metadata. Some of those domains have dozens of options and it would be horrendous if Esri's designed/implied workflow was to type each of them manually....

‎05-02-2022

Why don't the same capabilities for managing value-based symbology exist for raster datasets the way they do for vector datasets? This is in 2.9 For instance, if you have a vector dataset symbolized on a field you can create headings and either right click and send a symbology value to an existing heading or drag it manually. Yet on a raster dataset you can symbolize on a value, specify headings, add values to new headings, but you can't add to existing headings or manually drag them (though the GUI suggests you can by displaying a line...it just doesn't actually work). This is what's available for vector data.... ...Where you can see it's possible to manipulate symbology categories. And here's what's available for a raster dataset... Which means that if one needs to add a new category you have to start over entirely? It seems the only option is to start with a blank slate and then grab the necessary categories and and 'add to new heading.' But if you miss one you have to start over. You also can't re-order headings on a raster dataset. Is there a way to achieve the same functionality for addressing symbology categories for a raster dataset as one has for vector?

‎04-19-2022

@ZhifangWang - Returning to this after a little bit: Is this workflow still valid? The documentation hasn't changed, but I've gone to implement this precisely as I had it before but to no avail. I am working with the first example... I am running a report from a 1:1 child record, and trying to reference an attribute in the parent. I cannot seem to access any record in the parent layer. ${City} is definitely a valid field in the parent layer.... Please let me know if anything has changed on Esri's end that would invalidate this workflow.

‎04-08-2022

I think this is fairly basic but I seem to lack the vocabulary to search for it. I have a raster dataset with values ranging from ~.35 - 3.75. I would like to symbolize with a divergent color ramp, but I'd like to manually place the midpoint at 1. The dataset is used in a calculation, so I want to symbolize areas where it will increase the value or decrease it, hence 1 being an important midpoint. How is this done?

‎03-29-2022

Found a quick answer by creating a secure item and limiting the URLs it could be accessed from. This process isn't entirely clean and clear in my mind, but that's a separate question.

‎03-29-2022

I to disable use of sensitive data in geoprocessing services. It's possible to disable editing and disable export for a feature layer, but is it possible to disable its use in geoprocessing services? If a layer can be used in a geoprocessing service it's possible to back-door export (e.g., using summarize within). I would like to be able to take advantage of the functionality of a feature layer (filtering and querying), but I do not want the users to be able to be able to use it in geoprocessing.

‎03-23-2022

I am getting errors on machine readable languages all of the sudden (thanks, update!). This is a carbon copy of a survey on a carbon copy of a table.... Naturally the text of the whole message can't be copied. It says: The following language declarations do not contain machine-readable codes: language (xx). Learn more at https://xlsform.org/#language The referenced website was no help.

‎03-22-2022

Except you can! Just not with a related table. And not easily with a view.

‎03-22-2022

I cannot seem to add a new field to a related table in a feature service. Is this expected behavior? Below is the GUI option for a regular service without related tables.... And below is in my service with related tables... I've checked a few other services and it seems this is consistent. So the question: is there a recommended workaround? I have already created several dependent products off this data and I would really like to avoid republishing. Can fields be added in Pro? Vis the JSON at the REST endpoint? There is currently a view created from a join, so that may complicate things, but I'm familiar with the workflow for adding a field to a parent service and editing the JSON to let it trickle through to the view.

Online Status	Offline
Date Last Visited	2 weeks ago

My Ideas

Latest Contributions by SFM_TravisBott

Re: Transferring items from one AGO organization to another?

Alphabetize domain by description in AGOL

Re: Story Map Permissions

Re: Import domain code/description to metadata

Re: Story Map Permissions

Re: Import domain code/description to metadata

Import domain code/description to metadata

"Move Value to Existing Heading" doesn't exist for raster datasets

Re: Include related records in Feature Report

Manually place midpoint of color ramp on stretched raster

Re: Can use in a geoprocessing tool be disabled for feature layer?

Can use in a geoprocessing tool be disabled for feature layer?

Re: Error converting XLSForm - Survey123 Connect 3.14 version

Re: Can't add fields to service with related table. Is this expected behavior? Workaround?

Can't add fields to service with related table. Is this expected behavior? Workaround?

Best practice for updating schema/domains for feat...

ArcGIS Notebook on AGOL: nvalid value for executio...

Re: Blank rows in 'hidden' repeat

Re: Blank rows in 'hidden' repeat

Re: Experience Builder Editor not honoring setting...

Wildfire Response GIS