Alteryx Designer Ideas

When you use Create Points tool - you then almost always need to use a Select tool to rename that point.

Can we please add a single text field to the Create Points tool - which would then allow us to create and name a point in one step?

When calculating distance from a single point (or a list of points) to many other points, it can require a lot of processing time to append the single point into the same table as the multiple points (especially with very large datasets).  Seems it would be more efficient to allow the single point as in input to the distance tool and bypass the timely append step.

In GIS, spatial data is regularly stored/transmitted as text. With this comes metadata, including the projection used.

Example Issue: When extracting data from ESRI's ArcGIS REST Directories, the projection can be extracted from the information, but must be manually defined in the Make Points Tool. If you are trying to compile data from several different sources, all using different projections, you cannot automate the process. 

Suggested Solution: Add WKT to macro interface configuration options so that an Action Interface Tool can update the Create Points Tool.

Attachments:

JSON extract.png - This is a screenshot of the spatial reference metadata in a JSON formatted query from an ArcGIS REST Directory. 

action tool.png - Current configuration options for Create Points Tool in the Action Interface Tool.

Tableau v2018.3 introduced multiple table extracts. These are particularly useful for fact table to fact table joins and fact table to entitlement table joins for row-level security where the number of rows created by the join and/or size of join results would be prohibitively large. Also they are useful for fact table to spatial joins where we might have multiple spatial objects (for example custom province/district/health facility catchment) for each row of fact table data.

So in Alteryx I'd like to be able to specify 2+ tables & their join keys and then write out a .hyper multiple tables extract.

Jonathan

In Designer user settings, you have the option to set a default dataset for the reference base map. This is a fantastic feature when working with spatial objects. My suggestion is that this feature should persist when viewing .yxdb files outside of Designer workflows. 

When I'm browsing a folder of .yxdb files that contain spatial objects, clicking on those files opens a viewing/browse window outside of Designer. Unfortunately, the base reference map setting does not currently transfer and must be reelected each time a file is opened. I would like suggest that this setting persist in this situation. 

We now have the ability to output to an ESRI File Geodatabase, which is great, but it only allows you to output it to the WGS84 coordinate system.  I would like to have the same functionality to export it to other projections or coordinate systems similar to the ESRI Shapefile or ESRI Personal Geodatabase output tools (we specifically need NAD83 but I'm sure others would like other options as well).

Would be nice to have 3 outputs on Spatial Match, same as a standard Join.  Output unmatched objects from the Universe input.

Thanks!

First: Including mapbox in 2019.4 is GREAT!

That said, one of the great features of mapbox is the ability to customize your own map layers. 

It would be great if this was an option to use a custom map as the alteryx reference map similar to what is available within tableau. We in our organization have several custom map styles built with mapbox and I'd love to use them as a reference in the report map tool, or any other scenario where maps become useful.

Hey Alteryx Community,

I think Alteryx uses the Tableau SDK to create tableau data extracts, TDE's. Since Tableau 10.3, there is functionality to connect to spatial files in Tableau (.shp). These shapefiles can be converted to an tableau data extract within Tableau. The tableau SDK has this functionality as well, but Alteryx does not support it yet. The suggestion is to add this functionality. See https://onlinehelp.tableau.com/current/api/sdk/en-us/SDK/tableau_sdk_samples.htm for the SDK link. 

Spatial TDE's are way smaller (3gb .shp went to 140mb TDE) and way faster.

Thanks,

Marco 

We use Alteryx to extract the reports from 3D CAD system.

https://community.alteryx.com/t5/Alteryx-Use-Cases/Toyo-Engineering-Reduces-its-Workload-to-a-Fracti...

XYZ coordinate system is used in 3D CAD system but spatial function in Alteryx is applicable only for lat/long system.

Polygon generated by Alteryx can’t be imported into Tableau with proper scale and other useful spatial function can’t be used, neither.

It would be nice to have options to use XY coordinate system in addition to lat/long.

If XYZ, 3 dimensional coordinate system can be handled to calculate distance and overlap, that would be great.

In order to fully take advantage of Alteryx spatial features it would be great to have the ability of using Openstreetmap extract files natively.

While there are some sources available in SHP format they tend to be heavily cut down in detail, while the native OSM and PBF have the full feature set.

As it's an open format licensing shouldn't be an issue and it may pave the way to new features.

What do you think?

As mention on this post here I would love the ability to change the map provider to any other map service (Mapbox, google, some other paid option). This could be achieved by adding a "Map Severs" option in the default configuration and where you put in the map server details.

I am bringing this over from this post.

It would be really cool to have a workflow that you could configure to your server that we could schedule to pull down the new Cass updates and install them. Since they have to be reinstalled every two months, it would help to manage that.

I think that the data updates are set up with an FTP site, Cass could be done essentially the same way. Download it there and then use the command module to run the install? I may be over simplifying the process but it seems like this is something that Alteryx could tackle.

Currently, the distance tool provides an option to calculate mileage distance (as the crow flies) between a point and the edge of a polygon, but you can only calculate drivetime to the centroid.

I'd like to see an option to calculate drivetime based on the nearest edge rather than centroid, Thanks.

I would like the ability to take custom geographies and write them to a table in Exasol. We visualize our data with Tableau and rely on live connections to Exasol tables rather than Tableau extracts. One shortcoming with spatial is that we have to output our custom geographies as a .shp file then make a Tableau Extract.  This would save us a few steps in sharing this data with our users. 

Thanks!

Let's "Elevate" Alteryx to enter the Euclidean space and add the Z-Coordinates to our spatial tools!

We primarily work on tracking people through a store or any physical space and extract shopping trip information such as areas visited, dwell time, etc. This shopper track information consists of a series of X,Y coordinates which are also used to plot heat maps based on density of points in a given area.

I have been using a workaround due to the lack of cartesian coordinate support in spatial tools - involving converting cartesian values to Lat., Long. by dividing X,Y values by 10,000. This approach works fine for finding spatial matches between points and polygons. However, when using something like a heat map tool which requires Grid Size and Max Distance in Miles/Kilometers, since there is no support for smaller units of distance, you will not be able to generate a heatmap data file.

In addition to adding support for Cartesian coordinates, it would also be helpful to provide an option to load in a Floorplan/Image as Base Map when browsing Spatial tool results.

it would be nice Street Geocoding tool can be capable of accepting Latitude and Longitude and spit out the address like Reverse Geo Coding . The reverse Geo coding currently using TomTom is too slow to process hundred thousands records.. if the data is already local to our system in form of CASS or Street Geocoder that will be certainly faster.