Hypertegrity Node-RED Transportation Nodes

A collection of Node-RED nodes for shared mobility and electric vehicle charging infrastructure.

📝 Introduction

This package provides nodes for integrating transportation data into your flows, focusing on electric vehicle charging (OpenChargeMap) and shared mobility (GBFS).

Included Nodes

| Node | Description | |------|-------------| | openchargemap | Queries the OpenChargeMap API for EV charging station locations and details | | gbfs | Retrieves bike and scooter sharing data from any GBFS (General Bikeshare Feed Specification 1.x–3.x) compliant feed (palette module gbfs-data) |

Configuration by message

Every node accepts an optional msg.config object on its input. Its properties use the same names as the node settings in the editor and override them for this message only; the stored configuration stays unchanged. Existing message properties of earlier versions (msg.systemIds, msg.manualUrls of gbfs) keep working, msg.config takes precedence. Invalid values raise an error that can be handled with a Catch node. The help text of each node lists the supported properties.

msg.config = { locations: [{ type: "circle", value: { lat: 50.94, lon: 6.96, radius: 2000 } }] };

Security notes

The editor helper endpoints require the <node type>.read permission when adminAuth is enabled. The Open Charge Map API key is sent in the X-API-Key header instead of the URL, and only to the origin of the API base URL of the node (default https://api.openchargemap.io); a message that points msg.config.baseUrl to another origin must carry its own msg.config.key. A contact address for the User-Agent sent to Nominatim can be configured in settings.js:

hypertegrity: { contact: "mailto:[email protected]" }

Notes on upgrading to 0.3.2

• gbfs: stations are now output even if no vehicle is available (earlier versions dropped them). GBFS 3.x feeds now deliver vehicles and stations. Credentials entered for authenticated feeds were not stored in earlier versions; please enter them again. Open and save the node once so that the system details are stored in the flow and fetching no longer depends on systems.csv. Stored credentials are only sent to the origin configured in the editor: an entry in msg.config.manualUrls or in the legacy msg.manualUrls that reuses the ID of a configured source (or its position manual_<i>) with another protocol/host/port needs its credentials in msg.config.auth, otherwise the message fails with an error and nothing is fetched. msg.config.onlyAvailable/respectTtl/unknownAsNull only accept true/false (also as text), and msg.config.locations with invalid coordinates or a polygon given as text raise an error instead of silently filtering out all objects. Failed feeds are reported as warnings with a yellow status (also if a source delivers stations while its vehicle feed fails); only if all sources fail and no data at all is output, the status turns red and the error is passed to the Catch node (earlier versions always showed a green status). Manual discovery URLs entered as plain text or without a name work again; earlier versions stopped with "node._ is not a function" on Node-RED 4 and 5.
• openchargemap: areas whose answer reaches the result limit are now split automatically, so more stations than before may be returned. Several areas can be configured in the dialog. An answer that is not a list of stations (e.g. an HTML page or broken JSON) now counts as a failed area instead of "0 stations"; stations with coordinates outside ±90°/±180° are skipped like stations without coordinates; msg.config.rawText only accepts true/false (also as text). The new setting API base URL (default: the public API) points the node to a proxy or a test mock; msg.config.baseUrl changes it for one message (another origin than the configured one requires msg.config.key).

Installation

Install via the Node-RED Palette Manager or using npm:

npm install @htag/node-red-contrib-hypertegrity-transportation

🌍 About the Project / Über das Projekt

📍 Über dieses Projekt / About this Project

DE: Dieses Open Source Projekt ist im Rahmen der Förderung Modellprojekte Smart Cities entstanden und wurde durch die Initiative des Projekts Südwestcluster ermöglicht.

EN: This open source project was created as part of the Smart City Pilot Projects (Modellprojekte Smart Cities) funding and was made possible by the initiative of the Südwestcluster project.

💡 Hintergrund / Background

DE: Die Entwicklung wurde durch öffentliche Gelder im Kontext der Förderung Modellprojekte Smart Cities unterstützt. Dadurch können wir diese Lösung der gesamten Community als Open Source zur Verfügung stellen.

EN: The development was supported by public funds in the context of the Smart City Pilot Projects (Modellprojekte Smart Cities) funding. This allows us to make this solution available to the entire community as open source.

🌐 Open Source Philosophie / Open Source Philosophy

DE: Wir unterstützen aktiv die OSS-Community und fördern kollaborative Entwicklung. Durch die Veröffentlichung als Open Source profitieren alle Beteiligten:

• Community: Freier Zugang zu moderner Smart City Technologie
• Transparenz: Nachvollziehbare und überprüfbare Lösungen
• Innovation: Gemeinsame Weiterentwicklung durch verschiedene Akteure
• Nachhaltigkeit: Langfristige Verfügbarkeit und Wartbarkeit

EN: We actively support the OSS community and promote collaborative development. Releasing it as open source benefits everyone involved:

• Community: Free access to modern Smart City technology
• Transparency: Traceable and verifiable solutions
• Innovation: Collaborative development by various actors
• Sustainability: Long-term availability and maintainability

🙏 Danksagung / Acknowledgements

DE: Ein besonderer Dank gilt der Förderung Modellprojekte Smart Cities für die finanzielle Unterstützung sowie dem Projekt Südwestcluster für die Initiative und Koordination:

• Eifelkreis Bitburg-Prüm
• Stadt Kaiserslautern
• Landkreis Kusel
• Stadt und Verbandsgemeinde Linz am Rhein
• Landkreis Mayen-Koblenz
• Landkreis St. Wendel

EN: Special thanks goes to the Smart City Pilot Projects (Modellprojekte Smart Cities) funding for financial support and the Südwestcluster project for the initiative and coordination:

• Eifelkreis Bitburg-Prüm
• City of Kaiserslautern
• District of Kusel
• City and Collective Municipality of Linz am Rhein
• District of Mayen-Koblenz
• District of St. Wendel

📜 License & Contact / Lizenz & Kontakt

© 2026 HYPERTEGRITY AG. Alle Rechte vorbehalten. / All rights reserved.

⚖️ License Compatibility / Lizenz-Kompatibilität

DE: Details zur Lizenzierung und zu den Nutzungsrechten finden Sie in der beigefügten LICENSE Datei.

EN: Details on licensing and usage rights can be found in the attached LICENSE file.

📧 Contact / Kontakt: [email protected] 🌐 Website: www.hypertegrity.de