Latest Contributions by ColeAndrews

As mentioned here by Kory Kramer, ArcPy now has functions to calculate spatial objects as text, such as WKT and GeoJSON. Please add this to an out of the box GP tool-- I believe Calculate Geometry Attributes is the perfect place for it.  Purpose: populate a text field with the string representation of valid geometric objects, with options including WKT, WKB, and GeoJSON. Use case: Portability of GIS data. We need the ability to load a delimited csv of all tabular attributes of a feature class to data warehouses, including one text field containing the text representation of a spatial object. Once the csv is loaded to a data warehouse as a table, most of the database platforms can convert the geometry text to a spatial object using SQL functions like ST_FromText and TO_GEOGRAPHY. ... View more

As mentioned here by Kory Kramer, ArcPy now has functions to calculate spatial objects as text, such as WKT and GeoJSON. Please add this to an out of the box GP tool-- I believe Calculate Geometry Attributes is the perfect place for it.  Purpose: populate a text field with the string representation of valid geometric objects, with options including WKT, WKB, and GeoJSON. Use case: Portability of GIS data. We need the ability to load a delimited csv of all tabular attributes of a feature class to data warehouses, including one text field containing the text representation of a spatial object. Once the csv is loaded to a data warehouse as a table, most of the database platforms can convert the geometry text to a spatial object using SQL functions like ST_FromText and TO_GEOGRAPHY. ... View more

Requesting to add native support for reading in spatial data from Snowflake. We do "big data" analytics of data warehouses, which are within analytic databases like Vertica and Snowflake. With this being a growing market, it makes sense to add supported databases to the esri platform to support users like us.   Vertica idea was posted last year: Add Vertica as a Supported Database  ... View more

There is an either/or, catch-22 thing happening with the Join Field, Add Join, and Join Features tool. It creates inconsistencies between similar tools. Suggested enhancement(s) below. Use Case: The user wants to table join two feature classes based on a common field and only include the fields needed from the join table. The desired output is a new feature class. Join Field: With this tool, I can limit which fields are joined but it only updates the input table. There is no option to write a new output table, instead.  Enhancement: Add an optional 'new output table' option in this tool Join Features: With this tool, I can do the table join with a new output, but it copies every field from the join table and makes a mess of the output. There is no field mapping control nor a dropdown for which fields to join in from the join table. It requires subsequent, additional steps, to clean up the fields in the new output. Enhancement: Add a field map to the tool to allow output field configuration, or add a drop down to select which fields from the target table and/or input table should be joined. Add Join: This is temporary and not actually written to the GDB. I only mention this tool to address it as a third way to accomplish the use case, but you'd have to configure the fields in the layer after adding the join, or use the field mapper when exporting to a feature class. So, same problem of extra steps as noted above. ... View more