Latest Contributions by MattWilkie3

Thanks for taking the time to respond Amnoy. Re #1, tying to a single network isn't a problem here, probably even an advantage and not a limitation, but I'm glad to have this aspect drawn out of the background detail. Re #2, could you expand on what this means please? What 3 applications? ... View more

Yes, I should have said I've gone through those pages. Thanks.  I didn't notice anything that looked like "with concurrent you won't be able to ..." but I wanted to give people a chance to point something out in case I've overlooked something. ... View more

In past we've had some workstations not able to find a given license manager because of IPv4 and v6 issues, with v4 always working and v6 only for some machines. I didn't to get to the bottom of it. My hunch is a general network config issue and not specifically Esri's. ... View more

@chris_fox-esristaff the first part of the idea is display only the selected records, but the second part is the ability to later inspect that selection and possibly alter it, as well save and share it. Copying the selection into a definition query would allow that, while creating a layer from selection does not. Also in my experience the redraw performance of def-query layers is markedly faster than selection-set layers, especially for image services. ... View more

There is an Idea asking Esri to add a LAZ driver, please go vote it up: Support LAZ format  ... View more

https://community.esri.com/ideas/13916  ... View more

This would be possible via https://community.esri.com/ideas/13916 , if implemented ... View more

Now an Idea, https://community.esri.com/ideas/13916  ... View more

Addition to the list: arcplus/uninstall-ALL-ArcGIS-products.md at master · envygeo/arcplus · GitHub  (up to date for 10.6 though some products could be missing; contributions welcome. Better yet, Esri distribute their own tool that does same.) ... View more

Thanks Laurene. It's the first link from Curtis's opening post above too. ... View more

This is useful Shaun, thanks. Do you have or are you aware of a location where useful arcpy patterns like this are collected? (hopefully curated?) ... View more

This presentation from Software Carpentry on Data Management is excellent even if it is for a different field: http://v4.software-carpentry.org/data/mgmt.html  It exposes a way of thinking about the problem that I'm finding useful, if not quite yet fruitful (for us).  ... View more

That's nearly identical to our current best layout! 😉 It is reassuring to see your project folder structure match ours so closely. It helps validate the thinking that got us this far. The pain points we have with it: Doesn't address shared data among related projects (e.g. "ProjectBBB\maps\composition.mxd" using a feature class from "ProjectDDD\data\Results.gdb\trails_2015") New versions/Archiving: It's 2017 and we need to run new series of maps first created in 2015. "2015\ProjectAAA" and "2017\ProjectAAA" - mega data duplication. Definitely easiest to see what is most current though, and is highly portable. "ProjectAAA\maps\2015\" and "ProjectAAA\maps\2017\" - Pretty clear for maps, but gets internally complicated for data layers (are you sure you remembered to change source from "base_2015.gdb\trails" to "base_2017.gdb\trails"?), and very difficult to share. Having mxd's in a subfolder became a real pain after the introduction of the 'Home Folder' concept, wherein you can't just click your way to the parent folder to get at Scratch and Source, but putting them all at the top quickly gets out of hand too. I could never figure out the best place for SomeCustom.tbx. (tried "Tools" and "Tools\scripts" subfolders for awhile, but is a navigation pain and leads to much extra typing) There are 500+ and growing top level "ProjectXXX" folders in my work unit alone. It's hard to track what's in what. (We're using a spreadsheet as index, which was great for a few years, but it's collapsing under it's own weight, and won't survive merging with other work units.) I like the concept of Map and Layer Packages combined with a Check-out and Check-in to storage central workflow, but it doesn't work well when there are numerous data layers which shouldn't be wrapped up that aren't stored in an SDE. (Sure would nice if one could say "Exclude all layers in folder or drive X".). I've considered spawning one or more pre-corporately-managed GDB instances to address this, but the internal flat nature of GDB (all feature classes and tables stored at same level) means we'd need a dozen or more, which makes me leery. Thank you for your contribution to this exploration. ... View more