Latest Contributions by Joshua-Young

I think it would be useful to have an option to integrate ArcGIS Monitor with ArcGIS Portal and replace the Organization->Status page with a more detailed status page. What I am thinking of is having an entry under Organization->Settings->Servers to specify a connection to ArcGIS Monitor. That federates ArcGIS Monitor with ArcGIS Portal and spins up a new site in ArcGIS Monitor that is automatically configured based on the configuration and content of ArcGIS Portal. Finally replace the standard Organization->Status page with one based on the ArcGIS Monitor data. The new status page could have the user-friendly UI similar to the current status page, but with more details, and a link to the ArcGIS Monitor Server application URL to view all the details. ... View more

After selecting the Sync button on the Layers page of a Data Store, I think it would be particularly useful to have a page show a preview of everything that will change when the sync occurs. At a minimum, I think the preview page should list: layers that will be added layers that will be removed layers that have metadata changes layers that have schema changes layers that have editor tracking enabled in database time and need a time zone set It has not been a great experience to just select the sync button and find out what happened (or broke) after the fact. Once, I added a field to feature class that was already bulk published and, after syncing, every single web map using the feature class had the symbology reverted to a default symbol. A warning that would happen would have been appreaciated. ... View more

ArcGIS Portal really needs the capability to create and manage relationship classes in the web interface of ArcGIS Portal. One option is to have a way to create or manage related features or tables in the Settings tab on a feature, or map, service Item Details page. Another option that comes to mind is a new Relationship Class item type that allows you to define the relationship settings in the Settings tab on the Item Details page. I think the solution should work for both hosted and traditional services. We currently use Relationship Classes in an Enterprise Geodatabase. However, those do not seem to be recognized when using bulk publishing, or if related features are published as two different services and added to a web map or ArcGIS Pro.  ... View more

It would be extremely useful and conserve storage space to have what I would call an attachment repository. The idea being a file is uploaded once and then multiple features in multiple feature classes can be pointed to the same file. The way ArcGIS currently works if for all those features to have that file attached, I must upload the same file for every feature, which causes unnecessary growth of disk storage. For example, say I have a parcel GIS layer and I want to attach a PDF of the plat so my users can quickly review the plat when researching a property. If I have a plat with fifty lots, I must upload fifty copies of the PDF to my geodatabase as attachments. Then let's say the subdivision is re-platted. I now must upload another fifty copies of the replat PDF to the geodatabase. That is one hundred PDFs being stored in the geodatabase when only two PDFs are needed. My concept of an attachment repository is a new item type, like a feature class, mosaic dataset, etc. A geodatabase (or whatever method would be appropriate to store this new item type) could have multiple repositories. The repository should have privileges like any other GIS item. That way you could have curators that manage the repository and users who can only view the files. When a user goes to attach a file to a feature there is an option to upload a new file or add from a repository. Another benefit is if the attachment is updated in the repository then all the features referencing the attachment get the update automatically. Some other ideas are: give users the ability to define metadata fields or tags when creating the attachment repository to help find the correct file make attachment repositories special items in ArcGIS Online/Enterprise to allow for searching and management directly in ArcGIS Online/Enterprise ability to get URLs to files in the repository to embed the URLs in things like web map pop-ups ability to have attachment repositories store login credentials to popular cloud storage solutions so the "attachment" is just a pointer to the file in cloud storage but the ArcGIS user is not prompted to sign in to the cloud storage provided since the repository is handling that. Then if the credentials are changed for the cloud storage provider the credentials only must be updated once per repository instead of for each file. This way organizations have more choices of where to store their files and not be forced to move their files into ArcGIS. I do not want or expect this to be a replacement for a full featured document management solution. However, it could provide the foundation for third party document management solutions to integrate better with ArcGIS, or at least allow small organizations that are already invested in Esri to create a simple document management solution inside their GIS. ... View more

It would be extremely useful and conserve storage space to have what I would call an attachment repository. The idea being a file is uploaded once and then multiple features in multiple feature classes can be pointed to the same file. The way ArcGIS currently works if for all those features to have that file attached, I must upload the same file for every feature, which causes unnecessary growth of disk storage. For example, say I have a parcel GIS layer and I want to attach a PDF of the plat so my users can quickly review the plat when researching a property. If I have a plat with fifty lots, I must upload fifty copies of the PDF to my geodatabase as attachments. Then let's say the subdivision is re-platted. I now must upload another fifty copies of the replat PDF to the geodatabase. That is one hundred PDFs being stored in the geodatabase when only two PDFs are needed. My concept of an attachment repository is a new item type, like a feature class, mosaic dataset, etc. A geodatabase (or whatever method would be appropriate to store this new item type) could have multiple repositories. The repository should have privileges like any other GIS item. That way you could have curators that manage the repository and users who can only view the files. When a user goes to attach a file to a feature there is an option to upload a new file or add from a repository. Another benefit is if the attachment is updated in the repository then all the features referencing the attachment get the update automatically. Some other ideas are: give users the ability to define metadata fields or tags when creating the attachment repository to help find the correct file make attachment repositories special items in ArcGIS Online/Enterprise to allow for searching and management directly in ArcGIS Online/Enterprise ability to get URLs to files in the repository to embed the URLs in things like web map pop-ups ability to have attachment repositories store login credentials to popular cloud storage solutions so the "attachment" is just a pointer to the file in cloud storage but the ArcGIS user is not prompted to sign in to the cloud storage provided since the repository is handling that. Then if the credentials are changed for the cloud storage provider the credentials only must be updated once per repository instead of for each file. This way organizations have more choices of where to store their files and not be forced to move their files into ArcGIS. I do not want or expect this to be a replacement for a full featured document management solution. However, it could provide the foundation for third party document management solutions to integrate better with ArcGIS, or at least allow small organizations that are already invested in Esri to create a simple document management solution inside their GIS. ... View more

I think it would be very useful to have a map property that lets you set a specific map rotation. Then have a second map property to prevent a user changing the rotation by interacting with the map, but still let the rotation be set or changed using the map rotation property. This would be helpful for maps that need a specific rotation that should not change. For example the roads in my town generally run NE/SW and NW/SE so there are times I get requests for maps that are rotated exactly 45° to have the roads run up and down and side to side. ... View more