Skip to content

Commit

Permalink
Add resolution note; small change in order of things
Browse files Browse the repository at this point in the history
  • Loading branch information
smknaake committed Dec 4, 2024
1 parent 28b9985 commit 76f8352
Showing 1 changed file with 24 additions and 23 deletions.
47 changes: 24 additions & 23 deletions docs/user_guide/bro_geotop.ipynb
Original file line number Diff line number Diff line change
Expand Up @@ -73,7 +73,7 @@
"cell_type": "markdown",
"metadata": {},
"source": [
"As you can see, a selection returns a new [`GeoTop`](../api_reference/bro_geotop.rst) instance for the desired coordinates.\n",
"As you can see, a selection returns a new [`GeoTop`](../api_reference/bro_geotop.rst) instance for the desired coordinates. Note that the x-resolution has also been changed because the coordinates in the last selection are approximately 300 meters apart.\n",
"\n",
"### Selections\n",
"\n",
Expand Down Expand Up @@ -114,7 +114,7 @@
"cell_type": "markdown",
"metadata": {},
"source": [
"We can see that the first number (at index 0) is \"B31H0541\". Notice in the \"surface\" and \"end\" columns that the borehole is between +1.2 m NAP and -9.9 m NAP. Let's select this borehole from the [`BoreholeCollection`](../api_reference/borehole_collection.rst) and then compare lithology and stratigraphy information in the borehole data with the voxel column. We can select the first index from `geotop_at_locations`, select the depths between 1.2 and -9.9 m NAP and create a DataFrame to compare the data. In similar way, selection method for other use cases are available when working with [`GeoTop`](../api_reference/bro_geotop.rst). See the [API reference](../api_reference/bro_geotop.rst) for available methods."
"We can see that the first number (at index 0) is \"B31H0541\". Notice in the \"surface\" and \"end\" columns that the borehole is between +1.2 m NAP and -9.9 m NAP. We can select the first index from `geotop_at_locations`, select the depths between 1.2 and -9.9 m NAP and create a DataFrame to compare the data. In similar way, selection method for other use cases are available when working with [`GeoTop`](../api_reference/bro_geotop.rst). See the [API reference](../api_reference/bro_geotop.rst) for available methods."
]
},
{
Expand All @@ -123,29 +123,10 @@
"metadata": {},
"outputs": [],
"source": [
"borehole = boreholes.get(\"B31H0541\")\n",
"\n",
"# Increase zmin and zmax by a little to make sure the complete depth of the borehole is covered\n",
"voxel_column = geotop_at_locations.sel(idx=0, z=slice(-10.5, 1.5))\n",
"voxel_column = voxel_column.to_dataframe().sort_index(ascending=False) # Make depth increase from top to bottom\n",
"\n",
"borehole.data.df # Check out the borehole data"
]
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"Let's check `voxel_column` for the comparison:"
]
},
{
"cell_type": "code",
"execution_count": null,
"metadata": {},
"outputs": [],
"source": [
"voxel_column"
"voxel_column # Check out the result"
]
},
{
Expand All @@ -154,7 +135,9 @@
"source": [
"### Relabelling GeoTOP information\n",
"\n",
"Notice that in the `voxel_column` result, the columns \"strat\" (i.e. stratigraphy) and \"lithok\" (i.e. lithology) contain numbers, instead of names which makes it difficult to understand what the unit and lithology at specific depths are. GeoST provides the [`StratGeotop`](../api_reference/geotop_selection.rst) class and [`Lithology`](../api_reference/geotop_selection.rst) class which make it easy to translate these numbers into more meaningful names. Let's import them and check which stratigraphic unit belongs to the number 2010 in the \"strat\" column and what the number 6 in the \"lithok\" means:"
"Notice that in the `voxel_column` result, the columns \"strat\" (i.e. stratigraphy) and \"lithok\" (i.e. lithology) contain numbers, instead of names which makes it difficult to understand what the unit and lithology at specific depths are. This makes a comparison with the borehole data difficult.\n",
"\n",
"GeoST provides the [`StratGeotop`](../api_reference/geotop_selection.rst) class and [`Lithology`](../api_reference/geotop_selection.rst) class which make it easy to translate these numbers into more meaningful names. Let's import them and check which stratigraphic unit belongs to the number 2010 in the \"strat\" column and what the number 6 in the \"lithok\" means:"
]
},
{
Expand Down Expand Up @@ -197,6 +180,24 @@
"voxel_column # See the result"
]
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"Now, let's select borehole \"B31H0541\" from the [`BoreholeCollection`](../api_reference/borehole_collection.rst) (this was the borehole at the first index in `geotop_at_locations`) and then compare lithology and stratigraphy information in the borehole data with the voxel column."
]
},
{
"cell_type": "code",
"execution_count": null,
"metadata": {},
"outputs": [],
"source": [
"borehole = boreholes.get(\"B31H0541\")\n",
"# Check out relevant information in the borehole data\n",
"borehole.data[['nr', 'surface', 'end', 'top', 'bottom', 'lith', 'strat_2003']]"
]
},
{
"cell_type": "markdown",
"metadata": {},
Expand Down

0 comments on commit 76f8352

Please sign in to comment.