Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
The discussion here suggests it might be super-easy, but it would be nice to have a solution that didn't involve renaming files. Thanks!
The JPEG2000 reader does not seem to read at the full resolution possible; opening my files in other viewers results in much better quality. Quality seems to deteriorate the lower you look in the image.
It would be nice to have a toggle for invalidating the entire dataset if any record failed an attribute validation rule. An all or nothing option. Otherwise if I want to kick the data back to the original requestor, I have to do record count and tester and it's rather cumbersome. Thanks!
I was looking around for a way to identify aggregates in order to deaggregate them.I hoped for GeometryFilter but couldn't find it. So I ended up with a Tester for fme_geometry = fme_aggregate.Would be nice to have an option for Aggregates in GeometryFilter though.
FME needs an out-of-the box AGOL Feature Collection Writer. If you want high-available data on AGOL, Feature Collections are the way to go.
Currently, if you specify the folder path to filecopy_source_dataset, the contents of the entire folder will be copied, but many times I just want to copy some subfolders or files. I hope to provide include and Exclude filter for FileCopy Similar to Fastcopy (free file copy software from Japan).This will make FileCopy more powerful.eg.Include:2017*.shp ?Just copy the shape at the beginning of 2017?Include:2017* ?Just copy the folder at the beginning of 2017?Exclude:2017*.shp ?Copy all subfolders and files except the shape file at the beginning of 2017?Exclude:2017* ?Copy all subfolders and files except the folder that begins in 2017?
Add a handshake to TCP transformers to allow a credentialed login to the host
The ability to create a SSL connection to a Google Cloud SQL database. Currently this not an option, you are not able to add/associate the three required files. Of course once we can do this on the desktop it would be great to be able to use this connection information on FME Cloud.A non-ssl connection works.Client KeyClient CertificateAuthority Certificate
It might be useful if FME could upload, list, download and delete files with Azure Blob Storage.Note: there are custom transformers for this available in the FME Hub.It might be good if this support was offered natively in FME, like other remote file systems - i.e Connector transformers and select file from web for readers.
The PhotoCoordinateExtractor on the FME hub works well, but wouldn't it be better if:The JPEG reader automatically converted and exposed the lat/long to decimal degreesYou could expose an optional feature type containing point features for the photo locationsFormats other than JPEG (i.e. TIFF) were also supportedFor the second one, I'm thinking it would maybe work as an option on the initial reader setup, where you could choose whether to bring in the photo, the points, or both. I guess they would have to carry a common identifier so you could join them back together if you needed to...
The CommonSegmentFinder would benefit from the following improvements:Candidates Only Mode (like the neighborFinder)Attributes that Must Differ parameter (matcher, spatialRelator)List of features that share a common segment(neighborFinder, matcher, spatialRelator)CommonID (matcher match_id)
***Note from Migration:*** Original Title was: @round() expression evaluator function should have an argument to round to a specific number of decimals Currently the @round function takes one argument, the value to round, and rounds it to the nearest integer. It would be nice is there was an optional second argument to specify the number of decimal places to round to (like AttributeRounder transformer), if the second argument is not supplied, then it should round to the nearest integer.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.