Latest Contributions by Bud

Can anyone recommend a specific SQLite ODBC driver? For the purpose of connecting to a mobile geodatabase using non-ArcGIS programs like Excel. Use case: Store geoprocessing outputs in a format accessible to ArcGIS Pro and Excel ... View more

ArcGIS Pro 2.9.5; Oracle 18c 10.7.1 EGDB; ST_GEOMETRY Our master GIS data is stored in our enterprise geodatabase. The data can be easily accessed in Excel via ODBC for the purpose of tabular analysis and visualization by non-GIS people. That works well. However, when it comes to one-off geoprocessing outputs, I haven’t found a good place to store the resulting data. For example, I used the Spatial Join GP tool on EGDB data to bring the attributes of a polygon FC into a point FC (intersect). The question is: Where to store the output? The data needs to remain accessible in ArcGIS Pro. And it should also be accessible in Excel for the purpose of tabular analysis and visualization by non-GIS people. I don’t want to clutter the EGDB with a FC like PERMITS_spatial_join_SUBDIVISION_20240829. The data won’t be used regularly, but we do need to keep it for approximately one year. I could ask I.T. to create a data owner in the EGDB called GP_OUTPUTS and store this kind of data there. But it seems backwards to store ad hoc data in a production enterprise database. The source FCs have tens of thousands of features, so a ST_GEOMETRY spatial SQL query would be far too slow. Additionally, the query would be dynamic. In this case, a static, unchanging snapshot is preferred. A file geodatabase won’t work because it wouldn’t be accessible from Excel. Storing the data within an .XLSX file would strip out the spatial component. I’d prefer not to do that; I still want to access the data spatially in ArcGIS Pro. Although, in some cases, storing point coordinates in X & Y columns in the Excel data might be an acceptable workaround. Concurrent users aren’t a concern. And read-only access is fine. A file type that supports full-blown SQL queries would be preferred. Such as running a SQL GROUP BY query using Excel’s “Microsoft Query” window and ODBC. Excel Power Query would be an alternative option, but it is pretty clunky compared to SQL. Any ideas? ... View more

When exporting to Excel, I would like the option of automatically resizing all the columns to fit the existing values. Similar to selecting the entire sheet in Excel and auto fitting the column widths. There would be a max column width to keep the columns manageable.  ... View more

When using Table to Excel: I would like the option of exporting the data as a true table in the Excel sheet. The equivalent of hitting CTRL+T in Excel. ... View more

When using Table to Excel: I would like the option of defining the datatype/formatting of the fields. For example, lengthy ID numbers sometimes get formatted as scientific notation in Excel. I want to format those numbers as integers (numbers with zero decimal places) or as text. I want to define the formatting from within the GP tool or model, not after the fact in Excel. ... View more

When using the Table to Excel geoprocessing tool, the Output Excel File parameter is used as both the file name and the sheet name. I would like the option of defining a sheet name that is different from the file name. ... View more

In the Catalog pane > Export context menu, add an option to Export to Excel. Exporting to Excel is a common workflow. A Catalog option would be more convenient than searching for the Table To Excel tool.   ... View more