A web-based framework for editing GTFS (General Transit Feed Specification) data, now deprecated.
gtfs-editor is a web-based framework for editing GTFS (General Transit Feed Specification) data, which is the standard format used worldwide for public transportation schedules and geographic information. It provides a browser-based interface to modify transit routes, stops, and schedules, solving the problem of managing complex transit data without specialized desktop tools. The project is now deprecated, with development continuing in a newer repository.
Transit agency staff, transportation planners, and developers working with public transportation data who need to create or modify GTFS feeds for scheduling and mapping applications.
Developers chose gtfs-editor because it offered a dedicated web-based solution for GTFS editing, eliminating the need for desktop GIS software and making transit data management more collaborative and accessible through a browser interface.
A web-based GTFS editing framework. THIS PROJECT IS DEPRECATED. See https://github.com/ibi-group/datatools-ui for current version.
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Allows editing GTFS feeds directly in a browser, eliminating the need for desktop GIS software and enabling collaborative transit data management, as highlighted in the project's philosophy.
Provides a dedicated framework for manipulating GTFS formats, which simplifies development for transit-specific applications like route and schedule editing.
Leverages PostGIS for geographic data storage and queries, essential for handling transit routes and stops spatially, as noted in the key features.
Offers tools for managing routes, stops, and schedules, tailored to public transportation needs, making it a specialized solution for GTFS data manipulation.
The project is no longer actively maintained, with development shifted to a newer repository, leading to potential compatibility issues and lack of future updates.
Requires Play Framework 1.2.x, which is incompatible with modern versions, and specific old versions of PostgreSQL and PostGIS, making integration difficult.
Installation involves following a separate INSTALL.md with dependencies on legacy systems, which can be cumbersome and error-prone for new users.