Hacker News Reader

I haven’t done a ton with Rails professionally - but in my mind, if I was doing customer facing CRUD I would reach for rails, I think the deployment ecosystem and development experience is a bit better.

Django, however, is wonderful for internal tooling, or anything where you need to plug in Python libraries. GIS is a clear win for Django, as well as custom BI work or data analytics

View on HN

Django, however, is wonderful for internal tooling, or anything where you need to plug in Python libraries. GIS is a clear win for Django, as well as custom BI work or data analytics

Can you share more here? Would you go the route of django templates for internal tooling?

How is GIS a clear win for Django, when the largest gis project on earth (OpenStreetMap) runs on rails?

How is the largest GIS project, or OpenStreetMap, relevant example for most projects?

But, to help those wondering about RnR vs Django for dealing with GIS data, the answer is the python ecosystem is just larger for dealing with GIS data. There are more libraries like fiona, shapely, gdal examples, etc. Django ORM supports all of the PostGIS functions, geos and ogr object helpers.

Rails does not have an alternative for PolygonField, Raster support, or geometry field queries like filter(geom__intersects=area)

Reply on news.ycombinator.com