Latest Contributions by DamianSmith

‎01-25-2021

Yes, we do. I find myself contstantly frustrated by web feature layers. I would love to be be able to remove or add specific layer items as well from/to a web feature layer. Just like I can and or delete specific. Feature classes from a geodatabase

‎01-06-2021

I understand the security concerns. At least for my organization and the group I created, I’m the group owner and setup the group roles as need. But because I work for large institution, I won’t be given admin privileges beyond the publisher role for AGOL. I’m not a fan of shared accounts, but we have been forced to set one up, as we have help come in in the spring and summer. I also work in an interagency environment, which adds additional challenges They often have little GIS experience and going through the process of getting them an account doesn’t make sense. We need to be able to hand them an iPad with Collector and show them how to get the information we need. Those user only have the access to data I want them to. I’m trying to help teach my less experienced coworkers the basic ins & outs of managing geospatial data, setting up new features, geodatabase, making and editing high quality map, etc. Plus getting them to understand the changes I’m making and why for long term improvements in continuity and quality of the data collected and updated. And finally getting myself more comfortable AGOL itself, it’s limitations, etc. I don’t do GIS work full time, it just one my additional duties. I only suggested dual ownership for when it is absolutely critical. In my case having dual ownership is particularly beneficial to me when it comes to manipulating some their data sets

‎12-31-2020

I have and I did. If I could give a thousand votes and have it implemented today in ArcPro and AGOL. I’d be stoked.

‎12-31-2020

The ability to add multiple owners for a web feature layer would be useful. Particularly when like me, I share some responsibilities for maintaining, creating and editing these web feature layers. However, some coworkers don't have the experience with GIS or AGOL, and allowing an additional owner would allow me to make improvements to those web feature layers or vice versa. It would allow also for when I leave my current position and/or employer and a simpler way to transfer ownership of the data and ensure continuity.

‎12-31-2020

I should add that this should also be supported in AGOL. As I’m in the process of moving much of our data to it for sharing purposes with other colleagues.Also improved support for contingent values in AGOL would be helpful as well. We don’t have access to Enterprise server or necessarily need it.

‎12-29-2020

They are similar, but not exactly the same. What I'm thinking would be for a single feature class and its related attributes. For example, I deal with up to 20 properties, each of those installations have named management units and a numbered sub unit. The options presented for each of the attributes would be filtered based on the spatial domain/filter. So to the user at all three levels would be only presented one option or potentially two property names, and limits choices for next attribute(management unit), and filter the choice for numbered-sub unit Like a cascading select but the spatial Domain/Filter works as a choice filter in a cascading select.

‎12-29-2020

I could use this for several hosted features layers I have. It would save me time and complaints about some data entry choices I've made in the past. Please Please do this!

‎12-29-2020

So I have to deal with multiple locations for a single web feature layer that we use for tracking purposes. It would a nice and useful for our field workers to have their attribute value choices stored in a domain filtered using some sort of spatial filtering. The way I'm thinking about how this would work is like a cascading select in Survey123. I know I can set up contingent values and attributes rules to accomplish some of this, but being able to link the acceptable choices for workers would save time and make it easier for users to collect the data. While also potentially speeding up the data entry and improving data quality. The spatial filter/Domain could be created by adding a bounding box for coded domain value So the idea is this 1)Create Spatial filter/Domain 2) Attribute value choices present to the user are limited based on the location. 3) Spatial bounding could be used as the limiting feature for each value or create a link to a particular feature class in the layer. In my mind, it would work like this. When you have multiple properties, each with named management areas and preestablished compartments within those management areas. Property spatial attribute choice limits management area choice, and finally, the compartment potential compartments. But by using the location data, I prune the options presented to the user and potentially do it faster than have to setup new attribute rules, contingent values, etc

‎12-29-2020

Thank you for coming up with an answer, so quickly. This will save me quite a few headaches, especially when generating new maps on the fly, while in the field. I'm just curious as to what the cause was?

‎12-29-2020

Hi Aubri, When I export from Arcpro, either a map or layout, the tool behaves normally. However, when I bring those maps/layouts into Avenza; it tells me the map isn't referenced and no coordinates are detected. The particular files that have this problem were all updated and exported from 2.6-2.7 and under 3 megabytes on export. The imported files into Avenza are also no not too large. Same size files, I've been exporting and importing into Avenza for years. The coordinate systems haven't changed. Attached is an image of the Avenza Error message (Nothing you can do about that) and my tool setting, which are the same settings I used before 2.6/2.7 without issue for 2.5 years.

‎12-29-2020

@_____ I've seen others posting about issues with exporting georeferenced maps since ArcPro 2.6. Earlier solutions posted from a couple of years ago don't apply to our situation. We use both Collector and Avenza Maps for different solutions. Avenza is mainly for static reference maps that don't change and during particular projects, where data collection isn't needed or we lack reliable internet connections. Has anyone found a workaround for the problem? We're entering a busy period for us and it critical that I'm able to be able to produce georeferenced pdf maps or layouts

‎10-06-2020

It was created using Survey123 Connect (3.9.120) and published through AGOL. We selected the publish in the current version option on AGOL. As for the iOS app version, I'm waiting to get that information from them, as we aren't using an enterprise setup to manage the ipads being used. Once I know I'll let you know. A copy of the original form is attached

‎10-06-2020

One of the field workers is getting a Send Error when attempting to submit survey results. The Error states "Incorrect Syntax near '.' must declare the scalar variable "@positionSourceInfo". Must Declare scalar variable "@_NewFeatureID_". We didn't run across this error while testing before deployment. I'm going to speak with the person who submitted the error to see what they are doing. We are using the current version of Survey123 and Survey123Connect. Any help would be appreciated.

‎06-01-2020

This a function that a colleague would find extremely useful for adapting an old data collection protocol. It would make some data entry significantly faster and allow them to use survey123 for critical monitoring functions.

‎05-07-2020

I get the following error message when attempting to update my survey. The Alt(altitude) field was published in the original survey without issue for a geopoint. Not sure how to fix the issue. As I am collecting this for a series of photo repeats as well. Only the geopoint related field is causing this issue. I have found a solution.

Online Status	Offline
Date Last Visited	‎06-16-2023 08:03 PM

My Ideas

Latest Contributions by DamianSmith

Re: Support for Contingent Values in ArcGIS Online

Re: Ability to add an additional owner to web feature layer

Re: Spatial Filter for Attribute Choices

Ability to add an additional owner to web feature layer

Re: Spatial Filter for Attribute Choices

Re: Spatial Filter for Attribute Choices

Re: Support for Contingent Values in ArcGIS Online

Spatial Filter for Attribute Choices (Domain)

Re: ArcPro 2.6-2.7 Can't export working georeferenced pdf maps

Re: ArcPro 2.6-2.7 Can't export working georeferenced pdf maps

ArcPro 2.6-2.7 Can't export working georeferenced pdf maps

Re: Survey123 Send Error

Survey123 Send Error

Re: Creating Input Tables in Survey123

Survey123 Mismatch:esriFieldTypePointZ !=unknown

Re: Field Maps allowing multipart geometry?

Auto generated QR codes for map layouts

AGOL Assistant updates web map layer URL

Ability to add an additional owner to web feature ...

Spatial Filter for Attribute Choices (Domain)