Be sure to review our Idea Submission Guidelines for more information!
Submission GuidelinesHello,
After used the new "Image Recognition Tool" a few days, I think you could improve it :
> by adding the dimensional constraints in front of each of the pre-trained models,
> by adding a true tool to divide the training data correctly (in order to have an equivalent number of images for each of the labels)
> at least, allow the tool to use black & white images (I wanted to test it on the MNIST, but the tool tells me that it necessarily needs RGB images) ?
Question : do you in the future allow the user to choose between CPU or GPU usage ?
In any case, thank you again for this new tool, it is certainly perfectible, but very simple to use, and I sincerely think that it will allow a greater number of people to understand the many use cases made possible thanks to image recognition.
Thank you again
Kévin VANCAPPEL (France ;-))
Thank you again.
Kévin VANCAPPEL
Parquet is a very fast, efficient and widely used data format, currently only below Parquet compression algorithms are supported and we cannot use Alteryx to read the parquet file that generated by other processes. This limits our usage in Alteryx.
Read support: Snappy and Gzip compression algorithms.
It would be great for Alteryx to support all types of Parquet format so we can maximize the use of Alteryx in data analysis.
You've built a workflow, but you want GIS to bring it into a systems-based report structure. Alteryx provides the blueprint, but GIS has to now take and translate each step into code.
Rather than have a developer spending valuable time interpreting and recoding the work you have already completed, what if Alteryx had a tool or ready-made output feature that translates your entire workflow into your code of choice (e.g. SQL, Python, VBA, other) that you could just send to GIS and they implement? Kind of like the Macro recording feature in Excel that translates steps into VBA. This would provide a near immediate solution, reducing the days, weeks or even months of additional development work and capacity for an already under pressure GIS.
Ah, but you say there's a catch to this idea. Let's say you need an enhancement to the workflow that has been hardcoded in system. You would need to now submit a ticket to GIS for them to develop and update the code, right?
No, just adjust and iterate in workflow, rerun and submit the updated code to GIS.
Create a connector for Azure Cosmos DB, integrate it directly into their Alteryx workflows
I think it would be very helpful (and very easy) to add metadata to a yxdb with the name and location of the workflow that created or most recently updated that file. Right now I have to add a column to the data frame with a formula tool with the location, which puts the filepath on every single line, and is not how I want to present a finished product dataset to a superior. Thank you!