diff --git a/docs/ref/contrib/gis/geos.txt b/docs/ref/contrib/gis/geos.txt
index a82ac87..6969048 100644
a
|
b
|
return a :class:`GEOSGeometry` object from an input string or a file::
|
75 | 75 | >>> pnt = fromfile('/path/to/pnt.wkt') |
76 | 76 | >>> pnt = fromfile(open('/path/to/pnt.wkt')) |
77 | 77 | |
| 78 | .. _geos-exceptions-in-logfile: |
| 79 | |
| 80 | .. admonition:: My logs are filled with GEOS-related errors |
| 81 | |
| 82 | It may happen that you find many TypeError or AttributeError exceptions |
| 83 | filling your Web server's log files. It generally means that you are |
| 84 | creating GEOS objects at the top level of some of your Python modules. |
| 85 | Then due to a race condition in the garbage collector, your module is |
| 86 | garbage collected before the GEOS object. To prevent this, try to create |
| 87 | GEOSGeometry objects inside the local scope of your functions/methods. |
| 88 | |
78 | 89 | Geometries are Pythonic |
79 | 90 | ----------------------- |
80 | 91 | :class:`GEOSGeometry` objects are 'Pythonic', in other words components may |
diff --git a/docs/ref/contrib/gis/install.txt b/docs/ref/contrib/gis/install.txt
index dcc343f..78d37b5 100644
a
|
b
|
GEOS C library. For example:
|
191 | 191 | The setting must be the *full* path to the **C** shared library; in |
192 | 192 | other words you want to use ``libgeos_c.so``, not ``libgeos.so``. |
193 | 193 | |
| 194 | See also :ref:`My logs are filled with GEOS-related errors <geos-exceptions-in-logfile>`. |
| 195 | |
194 | 196 | .. _proj4: |
195 | 197 | |
196 | 198 | PROJ.4 |