From 090b6a4f13687b4371f430a744278ce62447dae3 Mon Sep 17 00:00:00 2001 From: Mattijn van Hoek Date: Mon, 22 Jul 2024 11:54:24 +0200 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index d854809..4aaa90c 100755 --- a/README.md +++ b/README.md @@ -70,7 +70,7 @@ There you can find out that the `epsilon` value for `vw` is area-based and that Also, if your source projection is in meters, than it is very likely that your `epsilon` value should be magnitudes larger than the examples on this page where the source projection is in degrees. -There is a [section](https://py.geocompx.org/04-geometry-operations#sec-simplification) on simplification in the book-in-progress on '[Geocomputation with Python](https://py.geocompx.org/)' that describes it as follow: +There is a [section](https://py.geocompx.org/04-geometry-operations#sec-simplification) on simplification in the book-in-progress on '[Geocomputation with Python](https://py.geocompx.org/)' that describes toposimplification as follow: > _The main advanatage of `.toposimplify` is that it is topologically “aware”: it simplifies the combined borders of the polygons (rather than each polygon on its own), thus ensuring that the overlap is maintained._