Alteryx Designer Desktop Ideas

When building an analytic app which uses a Map Input, please enable Interface tool functionality which would allow the app user to change the base map (roads, imagery, etc.) within the app map interface.  Currently I believe the only way to accommodate different base maps in an app is to configure multiple Map Inputs – one for each base map.  The resulting map interface duplication clutters up the app and opens the door for configuration errors.

Enable app user control of base map

Alteryx started as a geospatial application. The "y" and "x" in Alteryx stand for the geospatial origin of the application. So why doesn't every tool in the Spatial Category have a One Tool Example? As of version 2019.2.7, there is only one One Tool Example in the Spatial Category. It is for the Distance Tool.

Please make One Tool Examples for every Spatial tool. Thank you.

I think it would be really useful to add bearing in degrees to the Find Nearest Tool. While the cardinal direction is helpful for context, it would be great to have finer detail than just the 8 options.

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

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.

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

Thanks!

Currently I am unable to use Alteryx's spatial calculations in completing required reporting for CMS.  Its unfortunate, because in my mind Alteryx is a superior approach allowing for customization and seamless integration with varied data sources used within our company.

You might ask, why don't you just use actual driving distance?  The datasets that we are measuring are enormous. +60M member files are being compared to 70K providers.  Alteryx is missing a huge opportunity to get into this market.

Reference

https://www.cms.gov/Medicare/Prescription-Drug-Coverage/PrescriptionDrugCovContra/downloads/hsd_meth...

Travel Distance to Providers and Facilities

The second component of the review process tests the percentage of beneficiaries resident in a given county with access to a particular specialty type within the maximum travel distance. For a given county and specialty type, CMS uses the geographic coordinates for the associated providers or facilities and the geographic coordinates for the beneficiaries resident in the county and calculates the travel distance between them. The travel distance is calculated using a formula to determine the estimated driving distance (miles) between the latitude and longitude coordinates and provides an average for the total beneficiaries in the given county

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!

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?

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. 

An ability to modify the angle of the grids created. Degree Angle input would be real simple to use and would allow for creating more appropriate grids without making really small grids and re-merging them for similar result.  North South & East West grids are nice, however ability to change to NW by SE would be real nice.

North South & East West default

Alteryx's spatial tools are really powerful and offer a lot of value for analysis.  However, when rendering a map for output, there is currently no way to place an image inside of a polygon.  This feature would be very useful for customized layers on maps and other spatial-based processes.

My rough suggestion would be to scale a selected image to the size of the polygon's bounding rectangle, and then trim the edges of the image to fit inside the polygon itself.

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.

Please add the "Don't Output Input Objects" option. 

It would be nice to eliminate the input objects when the processed output object is all that is desired.  When processing spatial data, keeping the input objects can lead to massive amounts of unnecessary data in the output data stream.

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).

US and Canada datasets are underlined so far but,

Alteryx is expanding towards, Denmark, Germany, France and several other countries...

The question is; Why don't we have Eurostat data provided as well?

Bulk options for some datasets are available.

Even one can get a grasp on micro datasets and Alteryx may have a deal inf this micro dataset is anonymized...

A lot of popular machine learning systems use a computer's GPU to speed up some of the math to a huge degree. The header on this article on Medium shows a 15x difference from a high-end CPU vs a high-end GPU. It could also create an improvement in the spatial tools. Perhaps Alteryx should add this functionality in order to speed up these tools, which I can imagine are currently some of the slowest.

I have found a post where the grid size in the Grid Tool can be update using an interface tool -- which is really wonderful.

What I would love to see is the grid size text entry box being able to accept a field name/variable, so that this can be modified without needing the interface.

This would be useful because I have users uploading shapes to be analyzed -- they don't necessarily know the size of the shape so I would rather the grid size be automatically calculated based on the square mileage of the shape.

Please add support to read and write spatial data from a SpatiaLite database.  ESRI and QGIS have supported this format out of the box for quite a while.  We have a mixed use environment Alteryx, ESRI, Mapinfo and QGIS and would like a common file based spatial format.  You already support SQLite, its container, so expanding to the SpatialLite spec should be a no brainer.

https://en.wikipedia.org/wiki/SpatiaLite