FME Hub Alerts

FME Hub user dmitribagh just uploaded a new transformer to the FME Hub.The transformer reads FME Realize Augmented Reality files (*.fmear).The transformer needs Blender installation (https://blender.org) in order to run. InputAn FME Realize file (a file with an extension *.fmear).OutputThe content of the *.fmear file with all the features in their respective feature types and containing IDs, and summary annotations as attributesParametersSelect a FilePath to the .fmear file to read. Path to Blender ExecutableFull path to the Blender executable.Path examples:- macOS: /Applications/Blender.app/Contents/MacOS/Blender- Windows: C:\Program Files\Blender Foundation\Blender 3.6\blender.exeBlender is used to convert the model model into a Collada file (.dae) that FME can process. The conversion runs headless and deletes intermediate files afterward.Coordinate System (Optional)The coordinate system originally used in the dataset, from which the fmear file was created.FMEAR files store geometry

FME Hub user kevs-2021 just uploaded a new transformer to the FME Hub.# PythonLibCheckerThis script checks if one or a list of python librairies are installed and available. It is meant to check dependencies prior running a PythonCaller.Would you like to know more? Click here to find out more details!

FME Hub user clowncutie just uploaded a new transformer to the FME Hub.Uses GTFS data to create unique trip variants.Creates complete geometri and joins attributes.Trip variants means of a transport line have multiple destinations, one feature is created per trip variation and direction. So ex bus line 1 can have Start_Headsign A but different stop_headsignes, and will therefor be 2 attributes with different geometries. route_main_mode is added according to GTFS standard Extended GTFS Route Types | Static Transit | Google for DevelopersSee help if you want just one line per route, ex bus 1 as one line. Would you like to know more? Click here to find out more details!

FME Hub user kevs-2021 just uploaded a new transformer to the FME Hub.AttributeCleanerThis transformer replaces common encoded characters to human readable text. For exemple:before: FDV-Dokument%20for%20prosjekt%20Ã…sgard%20(finalâ„¢).pdfafter (if utf8=false):FDV-Dokument for prosjekt Asgard (final ).pdfafter (if utf8=true):FDV-Dokument for prosjekt Åsgard (final™).pdfSee the help for more information.Would you like to know more? Click here to find out more details!

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.BRGChartBar converts incoming FME features into a ready-to-embed HTML/CSS bar chart.It is designed to plug seamlessly into the BetterReportGenerator (or a BRGGroup) as a drop-in replacement for FME’s HTMLReportGenerator bar-chart output.ParametersParameterWhat it doesTitleSection header shown above the chart.DescriptionOptional descriptive text that appears under the title.Value Attribute NameRequired. Numeric or integer attribute to plot as the bar length/height.X Label AttributeAttribute whose value becomes each bar’s label on the X-axis.X LabelA static caption that appears under the X-axis.Card TypeDefines how (or if) the chart is wrapped in a Bootstrap-like card. • No Card – bare chart • Static Card – always open • Collapsable Card – user can collapse/expand, default open • Collapsed Card – user can collapse/expand, default closedOrderAn integer used by BetterReportGenerator to sort multiple BRGComponents in the fi

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.BRGTabs collects multiple BRGComponent features and renders them as a tabbed section within an HTML report produced by the BetterReportGenerator (BRG) framework. It allows end‑users to switch between different report components seamlessly.ParametersParameterTypeDefaultDescriptionTitleString / AttributeTabsHeading displayed above the tab set.OrderInteger / Attribute0Numeric value used by downstream generators to position this component among its siblings.Group ByAttribute Name(none)Name of an attribute whose distinct values will be used to group input features into separate tabs.Would you like to know more? Click here to find out more details!

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.BRGChartRadar converts the attributes of incoming FME features into a self-contained radar chart (sometimes called a spider or web chart).It emits a single BRGComponent feature whose attributes already contain the markup, styling, and JavaScript needed for display.Pass those BRGComponent features directly to a BetterReportGenerator or to any BRGGroup transformer to insert the chart section into your HTML report.ParametersParameterWhat it doesNotes / Allowed valuesTitleHeading displayed above the chart.Plain text (no HTML).DescriptionParagraph shown under the title.Accepts Markdown \.Label AttributeAttribute whose values become axis labels around the radar.One value per input feature.Data AttributeSingle numeric attribute plotted as the radius for each axis label.Must be numeric.Card TypeHow the chart is wrapped in a UI card.No Card = bare chart, Static Card = always open, Collapsable Card = starts open with a toggle, C

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.BRGChartLine converts incoming FME features into an HTML/CSS (and minimal JavaScript) component that renders the selected attribute values as one or more lines on a responsive chart. The component is intended to be forwarded to BetterReportGenerator (or to a BRGGroup) where it is assembled into the final HTML report.Typical use cases include visualising time‑series measurements, production statistics, or any ordered numeric data held in your workspace features.ParametersParameterDescriptionTitleText displayed as the heading of the chart section.DescriptionRich‑text block (HTML permitted) shown beneath the title. Use it to explain the data’s context.Value Attribute NameOne or more numeric attributes to plot. A separate line is drawn for each selected attribute.Sort AttributeAttribute used to order the features along the X‑axis before plotting. Must be sortable (e.g. date/time or number).X Label AttributeAttribute whose

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.BRGGroup is an FME custom transformer that collects multiple BRGComponent features and organises them into a single section of an HTML report generated by BetterReportGenerator (BRG). It allows you to:Define a title for the section.Control whether the section is rendered inside a card container and how that card behaves (static or collapsible).Sort incoming components to control their display order.Split incoming components into multiple subsections based on an attribute value.The transformer outputs one new BRGComponent feature for every unique group that is created. Each output component already contains the required HTML & CSS to be consumed directly by either another BRGGroup or the final BetterReportGenerator transformer.Typical Use CasesBuilding a multi‑section report where each section wraps one or more visual elements (e.g. maps, charts, tables).Collapsing large sections so that a reader can expand them on

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.The BRGKeyValuesIndicator transformer inserts a card‑style key–value indicator into a BetterReport. It highlights one or more attribute values from the incoming features, optionally grouped and sorted, and renders the indicators as ready‑to‑embed HTML/CSS that follows the BetterReport visual language.PortsPortDescriptionInputAccepts any geometry or null‑geometry feature that contains the attributes you wish to display.BRGComponentOutputs a single feature (per group) containing the indicator’s HTML/CSS. Route this to BetterReportGenerator or BRGGroup.ParametersParameterRequiredDescriptionKey Values Attributes✔︎Select one or more attributes to present. Each will be rendered as its own key–value tile.Order✔︎Integer or expression used to sort BRGComponents inside the report. Lower numbers appear first.Group ByAttribute used to partition the input. One BRGComponent is generated per distinct value. Leave blank to treat all i

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.The BRGButton transformer creates a styled HTML button component for use in BetterReportGenerator (BRG) workflows. For every incoming feature—or for each group of features when Group By is specified—it outputs a single BRGComponent feature that contains all the HTML markup and inline CSS required to render the button in the final report.Input PortsPortDescriptionAnyAccepts any feature type and schema.Output PortsPortDescriptionBRGComponentEmits one BRGComponent feature per input (or per group) representing the button.ParametersParameterTypeRequiredDefaultDescriptionButton LabelText✔—Text shown on the button.URLText✔—Destination URL opened when the button is clicked.OrderInteger✔0Determines display order inside a BRGGroup or BetterReportGenerator; lower numbers appear first.Group ByAttribute name✖(none)If set, features sharing the same value in this attribute are aggregated into a single button component.Would you like

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.BRGMap converts any incoming spatial features into an embeddable web map that uses an OpenStreetMap basemap. The resulting map is packaged as a BRGComponent feature containing all required HTML + CSS so it can be rendered by BetterReportGenerator (or another BRG-aware transformer such as BRGGroup). This gives you a lightweight alternative to FME’s native HTMLReportGenerator while keeping full control over look-and-feel and layout order.InputAny feature class that carries a valid FME geometry.OutputOutput Ports: 1BRGComponent – Pass this feature to BetterReportGenerator or BRGGroup to embed it in your final report.ParametersParameterType / Allowed ValuesDefaultDescriptionTitleStringMapHeading shown above the map (or in the card header).DescriptionMultiline String—Optional paragraph that introduces the map section. Markdown is supported.Map OverlayBoolean (checkbox)NoUnchecked – Description appears before the map.Checked

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.BRGImage converts any incoming FME feature into a BRGComponent that contains the HTML + CSS needed to add an image-centric section to a Better Report Generator (or a BRGGroup). It is designed as a lightweight, highly configurable alternative to FME’s built-in HTMLReportGenerator.2 Input & Output PortsPortCardinalityDescriptionIN0..∞Any geometry or non-geometry feature you want to document.OUT0..∞One feature per incoming record (or per group; see Group By). Each carries:• brg_html – the generated fragment• brg_css – styles scoped to the fragment• All original attributes (unchanged)Tip Connect the OUT port directly to a BetterReportGenerator or to a BRGGroup chain to build multi-section reports.3 ParametersParameterType / OptionsWhat it doesTitleStringHeading shown above (or beside) the image section.DescriptionStringFree-form text (Markdown is supported) that accompanies the image.Image SourceURL | FileTell the tran

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.BRGTable converts any incoming FME features into an HTML table that can be embedded in a BetterReportGenerator (or in a nested BRGGroup). It provides fine-grained control over how the table looks, how the data are grouped, and where the component appears in a multi-section report.Input & OutputPortDescriptionInput (IN)Accepts features of any geometry or schema. All features sent to this port are listed in the table.Output (OUT)Emits a single feature of type BRGComponent. The feature carries two attributes—brg_html and brg_css—containing the table’s markup and style rules, ready for consumption by BetterReportGenerator or BRGGroup.ParametersParameterTypeRequired?DescriptionTitleStringNoSection heading that appears above the table. If left blank, no heading is generated.DescriptionStringNoParagraph of explanatory text displayed between the heading (if any) and the table. Supports basic HTML tags (<b>, <i>

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.BRGText creates a text component that can be fed into BetterReportGenerator or BRGGroup to appear in an HTML report. It converts incoming features—regardless of geometry or schema—into BRGComponent features that encapsulate the HTML and CSS required to render a textual section.Typical uses include:Adding introductions, explanations, or narrative paragraphs.Inserting headings or sub‑headings between visual components such as maps, tables, or charts.Displaying dynamically grouped commentary (e.g. one description per city or per data category).Input PortsPortDescriptionInput (Any Feature)Accepts any feature type. .Output PortsPortDescriptionBRGComponentEmits one feature containing the text block plus styling information. The feature carries the attributes required by BetterReportGenerator.ParametersParameterPurposeNotesTitleHeading displayed above the text block.May include HTML entities; rendered inside an <h3> ele

FME Hub user alexbiz just uploaded a new transformer to the FME Hub.BetterReportGeneratorOverviewBetterReportGenerator assembles full HTML reports from BRGComponent features that you create with other BRG transformers (e.g. BRGText, BRGTable, BRGImage). It is designed as a drop‑in replacement for FME’s built‑in HTMLReportGenerator, adding modern themes, explicit ordering, and optional grouping support.Typical Use CasesProduce polished HTML dashboards directly in a workspace without external scripting.Generate one report per feature class, year, or any attribute using Group By.Input PortsAccepts BRGComponent features.ParametersParameterPurposePage NameSets the <title> element and appears in the browser tab and the title of the page.ThemeOptions: Light, Dark, Cream, Deep Purple.Output PortsEmits one feature per generated report.AttributeTypeDescriptionhtml_contentStringFully‑formed HTML document including consolidated <head> and <body>. Ready for an HTML Writer or to be

FME Hub user martin_ekstrand just uploaded a new transformer to the FME Hub.Creates an HTML report on all your triggers in all your automations and schedules, to be used as a dashboard in FME Flow.Takes a URL to an FME server and a web connection for authentication.It then connects to your server's REST API to get a list of all your automations.After that it gets each automation's configuration. It then parses all objects in the Automations canvas, checking for Triggers. For every trigger in every automation, it will check which workspaces are being triggered. Important note: You will need to install the Python library cron-descriptor before using this transformer. It's really easy, see the help for instructions.As of now it parses Schedule trigger (basic and cron), directory watch and ftp watch. The rest are output as other.This transformer replaces the FMEServerAutomationTriggersParserWould you like to know more? Click here to find out more details!

FME Hub user uvmsci just uploaded a new transformer to the FME Hub.This Transformer analyses CityGML (or any XML) file on text base.Can be used for manipulating CityGML (adding atts, removing features, etc...).Input:- text lines with atts: - text_line_data - text_line_number - fme_basename)Outputs:- TextLinesVertices: vertices with X=0, Y=text_line_number- XmlTags: represented by lines (use SpatialFilter to filter text lines)- GmlHeader: if present- Values/Coords: some text lines have no XML-tag, these are mostly coords or values- Errors: - Bracket count not even - Start tag without corresponding end tag - End tag without corresponding start tagWould you like to know more? Click here to find out more details!

FME Hub user conterra just uploaded a new fme_project to the FME Hub.OGC API Processes - Data Virtualization TemplateWould you like to know more? Click here to find out more details!

FME Hub user conterra just uploaded a new fme_project to the FME Hub.OGC API Features - Data Virtualization TemplateWould you like to know more? Click here to find out more details!

FME Hub user emma.at.safe just uploaded a new transformer to the FME Hub.The AsanaTaskQuerier custom transformer connects to the Asana API to retrieve all tasks for a specified project. It supports retrieving standard tasks, tasks with custom fields, or both, and automatically parses and restructures the JSON response into clean, attribute-friendly records. Use this transformer to integrate task-level data from Asana into your workflows with minimal setup.You will need to first establish an Asana connection using the Asana web connection: https://hub.safe.com/publishers/safe-sandbox/web-connections/asanaWould you like to know more? Click here to find out more details!

FME Hub user daveatsafe just uploaded a new format to the FME Hub.FME can read tiles from an ArcGIS Online Vector Tile dataset.Vector Tiles are often used a basemap to provide geographical context to a user's data. They have minimal attribution and often have smaller file sizes than the equivalent raster tiles.Tile sets often feature tiles of different sizes in order to equalize the amount of data in each tile. This reader can read the tile Index boundaries, the tile contents, or both.If the tile set is very large, we recommend using a search envelope.Would you like to know more? Click here to find out more details!

FME Hub user wghmapgear just uploaded a new transformer to the FME Hub.GeoApps Version ValidatorWith this transformer, you can easily validate if your GeoApps environment matches the minimum required version to use with FME. It also verifies if the required license is available on your GeoApps environment to use of this integration. At last, you can use this transformer to validate your setup: it is a simple request that verifies if you are able to connect to your GeoApps environment.PrerequisitesTo use this transformer, you need to have an active GeoApps subscription and a user account with enough permissions to run the jobs. In addition, you need to first set up a web connection to GeoApps from FME. You can find the web connection in the FME Hub at https://hub.safe.com/publishers/mapgear/web-connections/geoapps.How to use?Add the transformer in your workspace, and configure the parameters. You need to set up two parameters: the tenant name, and the web connection to GeoApps. After se

FME Hub user wghmapgear just uploaded a new transformer to the FME Hub.GeoApps Attribute Name VerifierEliminate data compatibility issues before they happen! With this transformer, you can easily verify that your feature attributes in FME are fully compatible with GeoApps, saving you time, preventing errors, and ensuring smooth data workflows.Perfect for data professionals who demand reliability and efficiency in their geospatial data preparation workflows. Whether you're working with complex enterprise datasets or simple feature collections, this transformer helps you in every way when transferring data to GeoApps.⚡ Key Features & BenefitsSImplify your data preparation workflow with these capabilities:🔍 Automated Compatibility Validation: Instantly verify that attribute names meet GeoApps standards - no more guesswork or trial-and-error uploads💡 Intelligent Error Diagnostics: Get clear, actionable error messages that tell you exactly what's wrong and why, eliminating confusion🛠

FME Hub user pierrekoelich just uploaded a new transformer to the FME Hub.DGN Linear Dimension DrawerThis custom transformer contains the framework to draw linear DGN dimensions when fed linear features(lines, polygons). This transformer will break the features into its constituent lines, and draw dimensions for each line. It has user parameters with presets to help make drawing the dimensions more visually appealing, these include: text alignment, text justification, arrow style, and offsetting the witness lines.Limitations:A major limitation of this custom transformer is that the user does not have control over where the dimension line gets drawn. It will be along the line that its measuring but which side the dimension line itself will be drawn on seems to be random.As the name suggests, this transformer cannot handle arc dimensions at all, a workflow to draw arc dimensions would be too different to incorporate into this one.Only 3 fonts are available, I recommend using the true typ