Replies: 1 comment 1 reply
|
Yes - the less external dependencies, the better. |
1 reply
|
I’m actively developing both projects, but I haven’t seen much community feedback yet. That feedback would be very helpful to validate and stabilize the APIs and communication patterns. The goal is to keep them simple, but also move toward a standard that feels natural and comfortable for Ruby developers. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
For years Ruby lost something fundamental:
the ability to generate raster images, charts and map tiles natively.
Most projects depend on external tools (ImageMagick, Mapnik, etc), which makes
dashboards, reports and GIS pipelines fragile and slow.
I built a native GD-based raster engine for Ruby (ruby-libgd) and a GIS layer
on top of it (libgd-gis) that can already render:
• charts and plots
• filters and shapes
• map tiles with projections, icons and labels
This makes it possible to generate dashboards, reports and maps directly from
Ruby processes again.
I would love feedback from people building:
• reporting systems
• map-based products
• data visualization pipelines
Do you think native raster + GIS belongs in the Ruby ecosystem again?
ruby-libgd
libgd-gis
All reactions