Latest Contributions by MattWilkie3

Yes it's available in My Esri downloads now. Thanks for the follow up. Pro won't let me update in place, which is inconvenient for me but that's okay because I'd rather download once and have our users install from a local server. (We're bandwidth constrained.) ... View more

A further limitation of Selections that Def Queries don't have is that many operations ignore the features/rows in "Selection from layer xxxxx" and read straight from the source table anyway.  ... View more

I didn't find an accessible solution for v10 arcpy, however in Pro it's available out of the box as arcpy.mp.ArcGISProject().defaultGeodatabase. See ArcGISProject—ArcPy | ArcGIS Desktop  and  file geodatabase - Setting default gdb from ArcPy? - Geographic Information Systems Stack Exchange  for more ... View more

A thousand times YES! (and please also make sure to include a keyboard shortcut to get to it. Office uses [Alt-Q].) ... View more

See arcgis desktop - Exporting ESRI image Tiles designed for Export? - Geographic Information Systems Stack Exchange  Nutshell summary: by exploring the REST API service page and it's sub-pages, especially Export Tiles Estimate, you can test and refine input parameters until you get usable results. ... View more

Personal Geodatabase a.k.a. Esri specific tables inside an Access MDB container is clearly a dead end road, or a cul-de-sac at the very least. There are reasons both inside and outside the Arcgis ecosystem for this. External factors include: MS has deprecated .mdb in favour of .accdb; the 2GB file size limit; mdb requires distinct SQL syntax and reserved keywords. I'll leave it to someone else to enumerate the Esri reasons.  I submit that a fruitful path forward would be to embrace SQLite as the future Personal Geodatabase format: SQLite db are single files that can be moved and hosted anywhere. There's no chance of breakage because of forgetting a side car file somewhere along the way. ArcGIS already has baseline support for the format via Support for OGC GeoPackage specification in ArcGIS.  SQLite is used under the hood by ArcGIS Collector already anyway - How To: Access offline edits from Collector for ArcGIS directly from an Android or iOS device  The SQL Features That SQLite Does Not Implement list is mercifully short There are ODBC drivers which would allow clients to continue to use MS Access as a front end. In the event there are limitations of this route: There is an actively maintained on all major platforms full featured client in DB Browser for SQLite (there are other clients also) SQLite is as about as future proofed as one can get. It has official authors' commitment through to year 2050 and is recommended by US Library of Congress for digital preservation. See Long Term Support. SQLite is the most rigorously tested application/library/format I've ever read up on, with 711 times as much test code and scripts as feature code. See How SQLite Is Tested. Note: this suggestion is different from Add support for SQLite/SpatiaLite and PostGIS geodatabases  (which I encourage people to vote for and comment on). What I'm proposing here is "make SQLite-gdb a first class citizen on par with File-GDB", which is more than just "supports", which Esri can argue it does already. (For me 'no editing' means 'not supported'). ... View more

Still present in 10.6, though it's fixed in ArcPro. I've summarized your and Tim Haverland‌ diagnosis and solution at arcmap - Make Query Layer - where are the results? - Geographic Information Systems Stack Exchange . Thank you for getting me on the right track! ... View more

Thank you for the rownum work-around Ryan. I've added it to the conversation at arcgis desktop - Converting double field to integer in database view so ArcMap query layer can use field as unique ident…  ... View more

Excellent description Erik. Thank you. My wish for Esri: recognize that you are masters in the GIS domain, and you have nothing to fear and a lot to gain to by increasing the number of inter-operable and exchange surfaces with other knowledge domains. The recent improved integration with AutoCAD is a step in the right direction. Let's do this with other areas too: not just personal geodabases but any standard database, round trip GPX files, read and write LAZ files natively, .. the list is long and your customers will thank you for it. (Instead of always wondering if the next X is something that makes breaking the Esri confinement worthwhile.) -- Says the guy who has just spent well over 20 hours trying and failing to build a simple read only view of a non-gdb database table in ArcGIS that can be accomplished in few minutes with any SQL workbench tool. ... View more

This sounds relevant: bug NIM003653, dating back to v9.2 (2006), citing upstream limitation of Microsoft GDI sub-system. The recommended response is to a) increase default printer page size or b) print from ArcGIS Pro instead which doesn't rely on the same export mechanism. Be aware that font substitution fall back does not happen (boxes may show for unsupported characters). More details in knowledge base article Bug: Picture symbol legend patches, inserted images, and objects fail to draw when exported to PDF, EPS, AI, and SVG  When images or objects (such as JPEGs, BMP files, or Excel spreadsheets) are inserted in an ArcMap layout with a page size that is larger than the default printer's default page size, they fail to draw or draw incorrectly when exported. Picture marker symbols, or areas with a picture fill, may also fail to render properly on export. Legend patches of web map service layers may become pixelated or fail to draw on export, as well. Note: At ArcGIS version 9.2 and later, picture marker symbols that are converted to vector with the 'Vectorize layers with bitmap markers/fills' option may also fail to render properly outside of the default printer's default page size. Additionally, certain cartographic representations that draw as an inserted EMF can also be affected by this issue. Cause If the inserted object, image, or legend patch falls outside the default page size of the Windows default printer, Windows GDI drawing calls used by ArcMap may not properly draw the object or image on output. ... View more

What we've done in this situation is compose and export the map at 50% of final print size, output at 600dpi, and then double the scale in Adobe reader/acrobat when printing. It took some careful calculating to get the font, graphic sizes, etc. correct but worked. ... View more

Thanks Micheal. That's the first thing I've read that has the smell of something on track. I will definitely follow up. ... View more

For us: yes it stops work often. A full close and restart of ArcMap is needed. Moving to Pro is not a solution. We use Pro, but ArcMap is still the primary and will be for at least a few more years. ... View more