Shape the future of FME with your ideas
Open ideas have been reviewed by our Product Management and are open for commenting and voting.
It would be very helpfull to have support voor the QUERY method in the HTTPCallerhttps://horovits.medium.com/http-s-new-method-for-data-apis-http-query-1ff71e6f73f3I'm specifically working with a Linked Data Apache Jena Fuseki triple store with a REST API and it would be nice to be able use the s-query method (and not escape all special characters for URL encoding).
In the counter, you can set the "Counter Name" to a attribute value, but can not set up multiple attribute values, if can be allowed to do so, will be more convenient to generate the "Group ID" such values.
FME Server prodive a filter function in the Jobs menu. It's possible to filter by the Job Status. In a normal situation I expect that if a workspace run until end I've a SUCCESS status.For some reasons is usefull to add LogMessage transformer for logging information during the execution of the job as warnings and error. It could be interesting to filter jobs by LogMessage type as warnings and errors even their status is SUCCESS.Thanks
Allowing the app to store the forms and request data on the devices for asynchronous demands would open usage to zones with poor network and new use cases. Here are some ideas but I am sure there are many more scenarios :The requests could be pushed when network is back and/or when the user wants.The requests could be accessible in a list and updated multiple times before being sent to the server. The requests could be moved out of the devices and treated by FME Desktop or closed network FME server when users come back at the office if the formats are open (SQlite /zip).
The CSV reader supports selecting a Date Input Format from a pulldown or custom format you enter. Frequently multiple date formats are within one CSV file or even within one attribute column, please support allowing a set of formats, say pipe delimited, and to retain bulk mode processing when multiple date formats are specified. How about pipe delimited like: %m/%d/%Y %H:%M:%S %p|%m/%d/%Y
A feature similar to the HTTPCaller's 'rate limiting' options may be very useful for reading features from feature services. We very often get failures when reading feature services, when the feature service throws an error about 'Too many requests, API calls quota exceeded'. I've had to work around this by stringing together multiple FeatureReaders with Decelerators between them. These read 6000 features, then a Decelerator has the workspace pause for 65 seconds, then read the next 6000, so on and so forth. It'd be awesome if instead of this clunky workaround, we'd be able to just configure the FeatureReader/reader to only read a maximum of 6000 features per minute, or something along those lines.
With the release of FME 2022 the 3DTiles writer contains the option to generate a texture atlas for each model. This is really great functionality and something I've been wanting to see for a while.It would be great to see this functionally extended to all 3D Formats - Alternatively a transformer such and an "AppearenceMerger" or "TextureAtlasGenerator" would be really helpful.
GeometryReplacer has an option for "EncodedPolyline". This supports polylines encoded to Google's documented 5 decimal places. But I have a polyline encoded to 6 decimal places, and so had to use PythonCaller and some ugly hacks to get a WKT formatted polyline.Why am I using 6 decimal places? I'm using the Valhalla open-source routing engine for OpenStreetMap (https://valhalla.github.io/valhalla/).Valhalla's reasoning for using 6 decimal places is documented at https://valhalla.github.io/valhalla/decoding/I used the Python script in FME to get my decoded polylines, but would prefer an option in the GeometryReplacer for "Encoded Polyline 6dp" below "Encoded Polyline"Their demo tool at https://valhalla.github.io/demos/polyline/ is useful in debugging.Here's a random 6dp encoded polyline:zsyo}@{cobaH??_KtDiHn@{HjHaMtDyOlHmI_AyL}HbGyt@jDwTHsc@tCsBw^pMgl@dFi_@j@}UlDw_@rCaKrQy[PmFdU{p@fZqx@pFuOfCiIVeCBkBAyBOkA{AcB}CyB}AaAgEyAqr@a]wdAmf@aJcCoHa@oIrAqIzDkGpDiF~DuB`B{B`As@~A CJnDDhDKxFN|EBfHeRjyCeIhjAiCfWmCdNk`mA}Jfa@cFrb@sHniA_EhU}EzReMre@}Lhe@kDpRmAbPmC`i@q@jO{IhqBaAlU_ClWkKvs@qAxOWdO`@`K`D|[hHzn@rO||AxHzx@tDlb@hX`nDbAhKnAfLzQhnAtEb]RrRFbF_A|Nc@`HGj@cCpW_AtIoFfh@mHtr@mCrLaD|JuFvIkHhImMnO_LrLiAlAw]|Z{FbF}}@|t@qwCr~BeGvEwSjPkRhOob@x^qm@fl@wObL_JtCqHpAuGZmQqAsDj@}Bf@gDpAEj@FzEXvFbClNrX~|@zDxVzA`N`BdTp@jWg@|kA~SgBbUwErr@kDld@cD~b@e@nFsEzp@sOlsAQbH~BvQNj@Hn@Bn@?n@Cl@In@Oj@Qh@Wf@[`@c@b@N`DmBpK]hEa@nH{DrdAg@bUcAh}@t]eDl}@}@~WqBxh@yJnwDF~Lh@tOf@~S|Af KhrAnGjw@hNnzA~Axa@d@xq@Anh@A`T`A|tCFlTlBb|DXryDr@viBHly@tBd`CX|[`AndAa@~f@]tTYpOy@z]wEz{@iIbaAoJbfAkh@rcGi^l{DeCpNcEdYgGpd@wD`r@sBjq@o`@|lEqNtaBe@xXf@`V~Eb]zGnUvGrPbVvZ|NtLtStKdm@xMd_BdXlr@zLv^dIpOxFfUlO|TdWlJfQfJ|UhPfcArFz_@nJfc@bKvWhNrWvQdV`UdTh|A|sAtk@re@jhYhZ`XfMfLjWp[`Wbc@t`~@bGtdFrYnK`v@tl@zyGhGpr@vDnd@rJ~iAbMjkAbK`y@fe@ntDtPdrAhGnc@zQrfAny@xfD~Rvq@xObl@n[nmA`Orq@hLtn@jPtkAbKf}@~Fdv@xTdsDhInn@jFfZ~Mli@jzAf{Djd@|gCfh@diC|Utq@~b@fz@jh@xz@|h@zz@zWvd@vV|r@zIda@rH|i@zOvmDvAr]xG`aBh[~oGpMncD^pS_AvUuAbTgEbXcGlVoJ~VuLxSwNvQoSnTap@nn@{d@`d@cMvLmm@`m@y[p]eOlTuTx_@av@ttAqX|f@{HnQsGrR{ClO}CtTaCrUaKrfAaLnjA}JxbAe@|EiK`jAsGzw@iDhj@wIvwAiAdW[hPp@fTtCvXnE~TzJzZrLbT`KzMtJzJbWpPzs@~YnP|GxKlHtJjInLdMpLhQhH~MzGzPfUhw@lPdk@hGbV`DlTtAjQZ|ToAv^g_@|uDcIt}@qBdVcAdJ}AnJ}@xH_AtDYxAMpBQfLJXPt@Fx@?x@Iv@Qt@Yn@GLyEhh@_NrdBmErj@mBpVo@be@M~JUvO{@bp@Zld@jBr`@zB|WdEtYjFtZz@|Cn@fBdA~A~GzGn@ @f@h@l@x@fA|@jBn@jBfBRbBFlAAxBOxA]nAe@dAq@~@q@n@s@`@_Ak@JaAFe@?}EzEaCpBiBtBiCxDsE|Dia@xt@qu@vtAax@lwAiMxUeLxVuJnWmI`X_eFn}Ps~DbsLuKz[ge@~yAeUvs@{x@j`C_]zaA_kEpfMyc@xaBoNf`BeC~xBu@`oBdAx]RlEl@jFzAjIt@vAb@`BPfB?hBQfBc@~As@tAaAfAWRmGxr@_BvxByAnkCj_Itj@eVtr@ulAluBq]pu@wN|c@qTvzAgHzsAmZnbGmPj`Cmf@j~Ic@|j@VxbIoYvuMcU~yFgEffAeFtfDs@jmAc@fw@lAx^dHlg@bZthAnY~eBlHdaAv@l[Kb_AuAr|Al@fs@dC`s@xe@~vHlG|p@lJjj@|Mjf@pPhc@di@reAni@vfAxHhS|BdJ~AxJnBrSVpUkAjSmCvSiOlq@kGxVsN`e@iIzPwI`MgL|K}OjJuPrFmSnCcRCwPgBaZmGyYuHkTuEgTiDiQiBsQ}@oS[{SNgOr@oOtAqOpBaOpCcQbE_QrF{MbFuMbG}w@he@ew@pe@koBplAeQjLeOnMaIlIsGdJaP`YaMpoI~^iDvYwEfk@wHlfAycA`uLoHzu@cAjK{g@xbGeAfLoJ|eAQtQKpE@vCBfIBLLr@Dr@At@Ir@Op@Wj@]f@c@^IFYrB]nBiA|Eo@nFgB~Re@fDw@`FUzAG|AFbBd@pCCnDHLbDPdC`ArDnAvDbArEd@zTvB|h@zFlf@rHfrBne@hf@`Mvf@jInsBtX|j@nGpGv@fgExr@rgClp@dd@nRjc@tTvb@xUd`Alq@h{@zw@zt@`x@rs@ro@r`BzfBj`An}Ari@|iAhi@dbB~P~p@zFfX~FnXjDxQtHhc@nLrt@tJvi@~Ido@rM|w@dArFxO`z@x@vD|o@`~CjQpz@z@xFfJtm@|@~H|C|XnBjQb@`E~@nIrGhDpCtE`AbENpGo@|E}DpHwHjDiI]yDsB}CiEaAwCk@mGLkD_BuR_BeScAoGsUesA{Nw{@ke@cwDigoBG[
I wanted to throw around the idea of adding a job board on this site. With knowledge.safe.com being the premier location for FME analysts, developers, and decision makers to find anything related to questions why not add a help wanted/help needed page. The quality of people here is one of the highest pedigree and most active of many technical forums I've been a part of in my career. I have found myself recently on both sides of the fence... needing to find work, short-term/long-term consulting and at times needing to hire a short-term expert to compliment or supplement my own abilities. I've used sites like Hired, Upwork, elance, etc... to find work, but by having an FME centric job board, both contractors and employers would know exactly what they are getting. Maybe include something like a "Twitter Verified Account" checkbox next to their name for FME Certified Professionals and Trainers. With the 'tag' system in place, I would be able to find a specific type of FME person I need to contract. For example, I need and FME Certified Professional with SQL and DBA experience. With other sites I've had various success, but the FME community is quite tight-knit. The trust-factor is already built in through interactions with the community and I propose and opportunity to take it one step further. Safe would act as the broker with no liability, essentially it is just making the connection with FME being the common factor. How the deal occurs offline is up to the two parties communicating. @daleatsafe @donatsafe
The LRS functionality in FME need something in the lines of the Calibrate Routes toolbox in ArcGIS.It should have two input ports:POINTSLINESTransformer parameters should include:Group ByTolerance in ground unitsAttribute name containing measure/calibration valueInterpolate between missing calibration points?Extrapolate before calibration points?Extrapolate after calibration points?Output should be line features with measures applied from the point dataset.
Create a Reader and Writer for QGIS Metadata file (QMD) which is a form of XML. We would use this to insert/update our spatial catalogue without scraping data from the QMD files created by our QGIS users.
I would like to see the omf included as a reader/writer - most mining applications now support this format so it could be a quickwin for FME.https://www.linkedin.com/pulse/open-mining-format-more-important-than-you-think-industry-large/ Myself (and most mining houses) would also like to see FME native support for:Micromine - https://www.micromine.com/micromine-mining-software/ - .dat files, simple text files but be good to native supportLeapfrog - https://www.seequent.com/products-solutions/leapfrog-geo/ Datamine - https://www.dataminesoftware.com/solutions/studio-rm-resource-modelling/ - .dm filesDeswick - https://www.deswik.com/software/IOgas - https://reflexnow.com/product/iogas/Surpac - https://www.3ds.com/products-services/geovia/products/surpac/ - again simple text files but be good to native supportBeing able to reproject to and from custom mine grids to UTM etc would be great as well as filtering transformation as a start.
Add an option to the BulkAttributeRenamer which replaces non-ASCII characters in AttributeNames with ASCII in a standardized way.e.g. Ö->O, Ø->O, ø->o, æ->aeUTF-8 code c380 to caafWould be useful e.g. with PostgreSQL writer etc.
There seems to be a notable hole in the geometry handling of FME.There's no easy way to split a polygon by a line. This is something even kindergarten kids can do ("if you cut the pie here, how many pieces do you have?"), but FME can't.So can we please have a transformer that splits a polygon by a line. If you search these boards you'll see it's a commonly requested question (how to).
Source data for buildings and other BIM related objects often comes as wireframes with 3D vertices. For example Microstation Smart solids are read by FME as wireframe data. We often need to recreate true solids or faces in FME for these features to write to BIM formats such as IFC or Sketchup etc.Safe PR#39030
PythonCaller has no attributes to set apart from grouping and output parameters, and of course the code.Any input parameters to be set outside the code, needs to be set in another transformer like AttributeCreator.It would be nice to have a small list of input parameters, so one can easily change input parameters without changing the code. Just a simple name/value list, just like other transformers. The values could then in turn be tied to user parameters in the workspace/custom transformer if need be.
It would be helpful if you could save an empty workspace. I would like to start my workflow by selecting 'Blank Workspace' and then being able to save it. At present you must begin editing your workspace before you can save it. This means you often forget to save the workspace and if FME crashes you loose what you are working on.I find adding any old transformer to a workspace in order to save it discrupts your thought process. Not a ground breaking idea but would be a tiny improvement
Could it be possible to add a new transformer with Moral global & local autocorrelation indexes?
When a distribution is not normal you need addittional measures to shape the distribution: Skewness and Kurtosis.If they can be added to the StatisticsCalculator transformer would be perfect.
The geometry picker should have an easier interface for setting basemaps and it could also support other formats than WMTS and also other CRS. If one could put vector layers on top of the basemaps to indicate where is data, it would be nice too. These updates could provide very powerful and easy way to e.g. let citizens or other organizations to download data from the provider organization. For example: administrator sets up a FME data streaming server app with geometry picker that has a basemap with polygon(s). The polygons tells the boundary/boundaries of any spatial dataset. Everyone with access to the app could easily see where they could get data, then just simply draw an area of interest that overlaps the polygons, and get their requested data through web browser download.
As an FME Admin I would like to have an FME server rest api call that can help me determine if users are creating/ using notification topics to let them know that the workbench failed.Enhanced workspace rest api call that automatically associates the email of the workbench author so that I can easily on notify them when something fails.
It looks like FME is very flexible in reading JSON files containing smaller errors. In our case we detected an extra "," at the end of an array. The JSONValidator detects this error clearly with the following error message: 'A trailing comma was found after the last value in an object or array'. But the JSON-Reader never validates JSON files and seems to be flexible and okay with minor issues like the one occured here. Please improve the JSON reader to validate the content of a file by option.
It would be useful if FME Server could be configured to have a maximum file size in the DataDownload service before splitting/spanning the archive into multiple files.
I would like to be able to pan beyond the extent of the workflow, which I believe is currently not possible. This would make it easier to create room for additional workspace items, which I would currently do by zooming out.
When a workspace app features a streaming service and is configured to run immediately, the URL is automatically extended by "/streaming/fmedatastreaming/[repository name]/[workspace name].fmw" after workspace app was triggered.Any user who likes to bookmark this page receives a 404 error code when trying access the page because the bookmarked URL including that annex is not working. For the sake of a better accessibility especially for non-professional users, I suggest to either hide/suppress the URL annex or let a workspace app also work when directly addressing the entire URL.
In-depth courses for all FME skill levels.
Explore our extensive collection of how-to guides and tutorials.
Log an issue with us. Our support team is ready to help.
