Opened 9 years ago
Closed 9 years ago
#25923 closed Cleanup/optimization (wontfix)
remove django.contrib.gis.utils.ogrinfo
| Reported by: | Sergey Fedoseev | Owned by: | Sergey Fedoseev |
|---|---|---|---|
| Component: | GIS | Version: | dev |
| 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
I propose to remove undocumented and untested django.contrib.gis.utils.ogrinfo, as it says docstrings:
This module includes some utility functions for inspecting the layout of a GDAL data source -- the functionality is analogous to the output produced by the
ogrinfoutility.
This functionality seems to be useless because this module depends on GDAL and if user has GDAL I don't see a reason to not use ogrinfo shipped with GDAL.
Change History (2)
comment:1 by , 9 years ago
| Owner: | changed from to |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | assigned → closed |
Note:
See TracTickets
for help on using tickets.
The difference is that the
ogrinfoutility is accepting aDataSourceinput to inspect, which is still adding some value over the command line utility. I don't see the gain dropping it.