This is an automated email from the ASF dual-hosted git repository.
joshfischer pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-baremaps-site.git
The following commit(s) were added to refs/heads/main by this push:
new abfdc18 Modify language of example (#14)
abfdc18 is described below
commit abfdc18e19662ee1338ba04e0cda8a2664884e4f
Author: Marc Brooks <[email protected]>
AuthorDate: Mon Mar 6 13:56:14 2023 -0600
Modify language of example (#14)
Swapped `roughly` in for `rawly`
---
pages/documentation/examples/extrusion.mdx | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/pages/documentation/examples/extrusion.mdx
b/pages/documentation/examples/extrusion.mdx
index 55991d0..e217b9a 100644
--- a/pages/documentation/examples/extrusion.mdx
+++ b/pages/documentation/examples/extrusion.mdx
@@ -17,7 +17,7 @@ baremaps workflow execute --file
examples/extrusion/workflow.json
In the
[tileset.json](https://raw.githubusercontent.com/apache/incubator-baremaps/main/examples/extrusion/tileset.json)
file, notice the SQL query associated with the building layer. Here, the
number of levels stored in OSM is multiplied by
-3, which rawly corresponds to the height of a level in meters.
+3, which roughly corresponds to the height of a level in meters.
```sql
SELECT id,
@@ -76,4 +76,4 @@ Well done, a map of London with extruded buildings should now
appear in your [br
## Conclusion
-In this tutorial, we learnt how to import OSM data in PostGIS with a workflow
and then use the MVT specification to extrude the vector tiles into a 3d object.
\ No newline at end of file
+In this tutorial, we learnt how to import OSM data in PostGIS with a workflow
and then use the MVT specification to extrude the vector tiles into a 3d object.
