Latest Contributions by JohnDye

I'm not the original down-voter but I did just down-vote this idea since I think the realities of implementing something like this would fundamentally change the nature of Workforce for the worse. The workflow described where the customer has additional items that need to be tracked which in turn requires a more complex data schema is best served by Collector where you can set up and customize the schema any way you want. Even better, the customer could pretty easily implement an App Integration between Collector and Workforce to facilitate opening Collector from Workforce to track those additional metrics. They could even track everything within the same dataset/feature layer if they liked by creating the Workforce project manually and extending the Workforce schema with additional fields as needed. However, asking Workforce to support completely custom fields throws is a pretty big ask in terms of extending the UI of the dashboard and mobile apps to handle this and would likely only serve to confuse the product's purpose and mission. Customizing some of the existing workforce domain values I could understand - for example extending the priority domain or changing the coded value descriptions to something more meaningful to your organization. Custom schemas though - Collector is your friend. Sorry. Just my 2 cents. ... View more

Thanks folks. I put in an ArcGIS Idea to try and get vector basemaps added to the Pro basemap gallery. Vote it up. https://community.esri.com/ideas/14030  ... View more

Nice! ... View more

Great thought. Never going to happen. All new development is going to Pro. ArcMap is dying on the vine. ... View more

Your addresses might be standardized with this kind of functionality, but accurate, I'm not so sure. Latitude and Longitude are still your most accurate indicator of location. Geocoding is an imperfect science. Esri does a great job, but man it is really hard and never 100%. If you're really after this kind of functionality, you could write an SOI to automatically geocode a feature when it is created and write the address values into some fields in your service. Therein lies another problem with your request, Esri would need to make a lot of assumptions about your data schema in order to facilitate this. What fields do you want them to write the address into? I'd bet the way you organize your address fields is slightly different from the way the next customer organizes theirs. Also, where would you want to configure kind of capability? On the layer? Which Geocoding Service would you want to use? Esri's World Geocoding Service? Do you want to use your own Geocoding Service? It's not possible to add new fields to an existing service, your fields have to already exist. So which fields do you want the addresses written into? How do you want the address components parsed? Do you want them parsed at all? So many big challenges with this. It's not as simple as you think. ... View more

The inverse of this would also be useful for when you have lots of points that are geographically coincident. ... View more

GIS Mountains, What exactly are you trying to accomplish by direct-connecting to the Datastore? There are likely much better alternatives to do whatever it is that you want which would not put the integrity of the Datastore at risk. Direct Connecting to and tinkering with the Datastore is almost always a very bad idea. ... View more

A significant effort would be an understatement. TD13 houses our entire data warehouse. We currently have no plans to go to 14, for some reason that no one will tell me. ... View more

Try putting all of your files into into a File Geodatabase and then using the License Geodatabase tool to restrict access to it with a license file. This will give you a way to issue a license file for that Geodatabase and also set an expiration. Once you've done that, create your package from that Geodatabase.  When someone tries to open the package, I'd bet they'd need that license file. ... View more