Opened 10 years ago
Closed 10 years ago
#24673 closed Bug (duplicate)
Extend GeoDjango docs with info about pros and cons
| Reported by: | Serhiy | Owned by: | nobody |
|---|---|---|---|
| Component: | Documentation | Version: | 1.8 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Installing PostGIS and all these libraries is really time-consuming and I'm not even sure what are the benefits in case I just want a simple lat/lon fields.
- S. IMHO all GeoDjango docs could use some improvement or review with some newcomers. It looks like it was written without trying to understand what reader really wants and without considering all possible use cases. It's not even clear that it's safe to replace django.db.backends.postgresql_psycopg2 for existing project.
Note:
See TracTickets
for help on using tickets.
Duplicate of #22274