MapInfo Pro

Happy #MapInfoMonday!

When working in the 3D map the layers can have many properties. This all depends on the type of layer. Out of the box, we have given you access to several of these properties. Besides these most used properties, we have also provided you the option to add additional properties.

Let's investigate how easy this is and the effects this can result in with an example.

The Elevation Source is rendered in the 3D map using a mesh method. This calculates triangles between the known elevations and uses these to drape an image over the elevation and render the result on the screen. As you probably can imagine, you can create many or fewer triangles for your Elevation Source. This is controlled by the Mesh Max Error property.

Here's the wireframe created by the default value of 4.0 for the Mesh Max Error property for my local neighborhood.

I'm certain, we can agree that there is a higher detail in the second wireframe, right?

So how would you put this in place? Let me walk you through the process.

First, you need to load your Elevation Source into a 3D map. Now unfold your Elevation Source layer, unfold the More Properties group, and click on the small pencil  Add/Edit/Remove Properties next to the group.

In the More Properties dialog, click on the Add button to insert a new property.

Now we need to specify this new property. Enter meshMaxErrror as the Key value. As Input Type select Float and as Output Type select number. You can also specify the Prompt as Mesh Max Error:. And set a Value for the property too. I set it to 1.0.

With this all set, click the OK button to add the new property to the 3D Layer List for the Elevation Layer.

This is how my Elevation Source looked with the default value of 4.0 for the meshMaxError property.

I now have the property in the 3D Layers List allowing me to control the details of my elevation source. If I change it to 1.0, the result will look like this.

It can be a bit hard to see the difference so let's try doing the same but with some additional vector layers in the 3D map.

Mesh Max Error of 4.0

Mesh Max Error of 1.0

Mesh Max Error of 0.1

I'm not sure how clear it is in these images. In the first image with a Mesh Max Error of 4.0 meters, some of the buildings seem to float above the elevation source and the orange dots which are points assigned the height from the elevation also seem to float in some areas and then go underground.

In the second image, the buildings sit nicely on the elevation source and the orange dots also follow the elevation nicely. here the Mesh Max Error was set to 1.0 meters

In the third and last image, the vector objects still follow the elevation source nicely but you can see some of the raster tiles are not that smooth. here the Mesh Max Error was set to 0.1 meters.

As you can see, you can change this value and get a far better result than with the default value. But you can also "overdo" it and end up with a result that isn't smooth.

I have only tried this with an elevation source built from a DTM with a resolution of 0.4 meters. I'm sure this initial resolution will affect which Mesh Max Error value would be best to use.

Changing the meshMaxError property can also affect how the underground will look. This is especially the case if you create tiled elevation sources. The vertical lines between the tiles will be smaller with a smaller Mesh Max Error.

This is a result of a Mesh Max Error of 1.0.

And here is the same area but with a Mesh Max Error of 4.0.

I showed you how to add a new property to the Elevation Source layer in the above. You can use the same method for adding properties to additional layer types. The properties depend on the layer type. You can find more details about the Terrain Layer Type in the Deck.gl documentation. Here is a list of the layer types Deck.gl support of which we currently support a handful.

Are there any specific layer properties you would like to see by default? Are there any layer types you'd like to see supported in MapInfo Pro 3D?

Thanks Peter

Much better result

------------------------------
John Ievers
CDR Group Limited
Hope Valley, United Kingdom

Original Message:
Sent: 05-13-2024 04:03
From: Peter Møller
Subject: MapInfo Monday: Improving Apparence of Elevation Source in the 3D Map

Happy #MapInfoMonday!

When working in the 3D map the layers can have many properties. This all depends on the type of layer. Out of the box, we have given you access to several of these properties. Besides these most used properties, we have also provided you the option to add additional properties.

Let's investigate how easy this is and the effects this can result in with an example.

The Elevation Source is rendered in the 3D map using a mesh method. This calculates triangles between the known elevations and uses these to drape an image over the elevation and render the result on the screen. As you probably can imagine, you can create many or fewer triangles for your Elevation Source. This is controlled by the Mesh Max Error property.

Here's the wireframe created by the default value of 4.0 for the Mesh Max Error property for my local neighborhood.

I'm certain, we can agree that there is a higher detail in the second wireframe, right?

So how would you put this in place? Let me walk you through the process.

First, you need to load your Elevation Source into a 3D map. Now unfold your Elevation Source layer, unfold the More Properties group, and click on the small pencil  Add/Edit/Remove Properties next to the group.

In the More Properties dialog, click on the Add button to insert a new property.

Now we need to specify this new property. Enter meshMaxErrror as the Key value. As Input Type select Float and as Output Type select number. You can also specify the Prompt as Mesh Max Error:. And set a Value for the property too. I set it to 1.0.

With this all set, click the OK button to add the new property to the 3D Layer List for the Elevation Layer.

This is how my Elevation Source looked with the default value of 4.0 for the meshMaxError property.

I now have the property in the 3D Layers List allowing me to control the details of my elevation source. If I change it to 1.0, the result will look like this.

It can be a bit hard to see the difference so let's try doing the same but with some additional vector layers in the 3D map.

Mesh Max Error of 4.0

Mesh Max Error of 1.0

Mesh Max Error of 0.1

I'm not sure how clear it is in these images. In the first image with a Mesh Max Error of 4.0 meters, some of the buildings seem to float above the elevation source and the orange dots which are points assigned the height from the elevation also seem to float in some areas and then go underground.

In the second image, the buildings sit nicely on the elevation source and the orange dots also follow the elevation nicely. here the Mesh Max Error was set to 1.0 meters

In the third and last image, the vector objects still follow the elevation source nicely but you can see some of the raster tiles are not that smooth. here the Mesh Max Error was set to 0.1 meters.

As you can see, you can change this value and get a far better result than with the default value. But you can also "overdo" it and end up with a result that isn't smooth.

I have only tried this with an elevation source built from a DTM with a resolution of 0.4 meters. I'm sure this initial resolution will affect which Mesh Max Error value would be best to use.

Changing the meshMaxError property can also affect how the underground will look. This is especially the case if you create tiled elevation sources. The vertical lines between the tiles will be smaller with a smaller Mesh Max Error.

This is a result of a Mesh Max Error of 1.0.

And here is the same area but with a Mesh Max Error of 4.0.

I showed you how to add a new property to the Elevation Source layer in the above. You can use the same method for adding properties to additional layer types. The properties depend on the layer type. You can find more details about the Terrain Layer Type in the Deck.gl documentation. Here is a list of the layer types Deck.gl support of which we currently support a handful.

Are there any specific layer properties you would like to see by default? Are there any layer types you'd like to see supported in MapInfo Pro 3D?

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data
------------------------------

How did it look before, John?

I am curious how it improves an area with "real" mountains compared to flat Denmark :-)

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data

Original Message:
Sent: 05-14-2024 06:03
From: John Ievers
Subject: MapInfo Monday: Improving Apparence of Elevation Source in the 3D Map

Thanks Peter

Much better result

------------------------------
John Ievers
CDR Group Limited
Hope Valley, United Kingdom

Original Message:
Sent: 05-13-2024 04:03
From: Peter Møller
Subject: MapInfo Monday: Improving Apparence of Elevation Source in the 3D Map

Happy #MapInfoMonday!

When working in the 3D map the layers can have many properties. This all depends on the type of layer. Out of the box, we have given you access to several of these properties. Besides these most used properties, we have also provided you the option to add additional properties.

Let's investigate how easy this is and the effects this can result in with an example.

The Elevation Source is rendered in the 3D map using a mesh method. This calculates triangles between the known elevations and uses these to drape an image over the elevation and render the result on the screen. As you probably can imagine, you can create many or fewer triangles for your Elevation Source. This is controlled by the Mesh Max Error property.

Here's the wireframe created by the default value of 4.0 for the Mesh Max Error property for my local neighborhood.

I'm certain, we can agree that there is a higher detail in the second wireframe, right?

So how would you put this in place? Let me walk you through the process.

First, you need to load your Elevation Source into a 3D map. Now unfold your Elevation Source layer, unfold the More Properties group, and click on the small pencil  Add/Edit/Remove Properties next to the group.

In the More Properties dialog, click on the Add button to insert a new property.

Now we need to specify this new property. Enter meshMaxErrror as the Key value. As Input Type select Float and as Output Type select number. You can also specify the Prompt as Mesh Max Error:. And set a Value for the property too. I set it to 1.0.

With this all set, click the OK button to add the new property to the 3D Layer List for the Elevation Layer.

This is how my Elevation Source looked with the default value of 4.0 for the meshMaxError property.

I now have the property in the 3D Layers List allowing me to control the details of my elevation source. If I change it to 1.0, the result will look like this.

It can be a bit hard to see the difference so let's try doing the same but with some additional vector layers in the 3D map.

Mesh Max Error of 4.0

Mesh Max Error of 1.0

Mesh Max Error of 0.1

I'm not sure how clear it is in these images. In the first image with a Mesh Max Error of 4.0 meters, some of the buildings seem to float above the elevation source and the orange dots which are points assigned the height from the elevation also seem to float in some areas and then go underground.

In the second image, the buildings sit nicely on the elevation source and the orange dots also follow the elevation nicely. here the Mesh Max Error was set to 1.0 meters

In the third and last image, the vector objects still follow the elevation source nicely but you can see some of the raster tiles are not that smooth. here the Mesh Max Error was set to 0.1 meters.

As you can see, you can change this value and get a far better result than with the default value. But you can also "overdo" it and end up with a result that isn't smooth.

I have only tried this with an elevation source built from a DTM with a resolution of 0.4 meters. I'm sure this initial resolution will affect which Mesh Max Error value would be best to use.

Changing the meshMaxError property can also affect how the underground will look. This is especially the case if you create tiled elevation sources. The vertical lines between the tiles will be smaller with a smaller Mesh Max Error.

This is a result of a Mesh Max Error of 1.0.

And here is the same area but with a Mesh Max Error of 4.0.

I showed you how to add a new property to the Elevation Source layer in the above. You can use the same method for adding properties to additional layer types. The properties depend on the layer type. You can find more details about the Terrain Layer Type in the Deck.gl documentation. Here is a list of the layer types Deck.gl support of which we currently support a handful.

Are there any specific layer properties you would like to see by default? Are there any layer types you'd like to see supported in MapInfo Pro 3D?

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data
------------------------------

This was the same data prior to this fine-tuning

How did it look before, John?

I am curious how it improves an area with "real" mountains compared to flat Denmark :-)

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data

Original Message:
Sent: 05-14-2024 06:03
From: John Ievers
Subject: MapInfo Monday: Improving Apparence of Elevation Source in the 3D Map

Thanks Peter

Much better result

------------------------------
John Ievers
CDR Group Limited
Hope Valley, United Kingdom

Original Message:
Sent: 05-13-2024 04:03
From: Peter Møller
Subject: MapInfo Monday: Improving Apparence of Elevation Source in the 3D Map

Happy #MapInfoMonday!

When working in the 3D map the layers can have many properties. This all depends on the type of layer. Out of the box, we have given you access to several of these properties. Besides these most used properties, we have also provided you the option to add additional properties.

Let's investigate how easy this is and the effects this can result in with an example.

The Elevation Source is rendered in the 3D map using a mesh method. This calculates triangles between the known elevations and uses these to drape an image over the elevation and render the result on the screen. As you probably can imagine, you can create many or fewer triangles for your Elevation Source. This is controlled by the Mesh Max Error property.

Here's the wireframe created by the default value of 4.0 for the Mesh Max Error property for my local neighborhood.

I'm certain, we can agree that there is a higher detail in the second wireframe, right?

So how would you put this in place? Let me walk you through the process.

First, you need to load your Elevation Source into a 3D map. Now unfold your Elevation Source layer, unfold the More Properties group, and click on the small pencil  Add/Edit/Remove Properties next to the group.

In the More Properties dialog, click on the Add button to insert a new property.

Now we need to specify this new property. Enter meshMaxErrror as the Key value. As Input Type select Float and as Output Type select number. You can also specify the Prompt as Mesh Max Error:. And set a Value for the property too. I set it to 1.0.

With this all set, click the OK button to add the new property to the 3D Layer List for the Elevation Layer.

This is how my Elevation Source looked with the default value of 4.0 for the meshMaxError property.

I now have the property in the 3D Layers List allowing me to control the details of my elevation source. If I change it to 1.0, the result will look like this.

It can be a bit hard to see the difference so let's try doing the same but with some additional vector layers in the 3D map.

Mesh Max Error of 4.0

Mesh Max Error of 1.0

Mesh Max Error of 0.1

I'm not sure how clear it is in these images. In the first image with a Mesh Max Error of 4.0 meters, some of the buildings seem to float above the elevation source and the orange dots which are points assigned the height from the elevation also seem to float in some areas and then go underground.

In the second image, the buildings sit nicely on the elevation source and the orange dots also follow the elevation nicely. here the Mesh Max Error was set to 1.0 meters

In the third and last image, the vector objects still follow the elevation source nicely but you can see some of the raster tiles are not that smooth. here the Mesh Max Error was set to 0.1 meters.

As you can see, you can change this value and get a far better result than with the default value. But you can also "overdo" it and end up with a result that isn't smooth.

I have only tried this with an elevation source built from a DTM with a resolution of 0.4 meters. I'm sure this initial resolution will affect which Mesh Max Error value would be best to use.

Changing the meshMaxError property can also affect how the underground will look. This is especially the case if you create tiled elevation sources. The vertical lines between the tiles will be smaller with a smaller Mesh Max Error.

This is a result of a Mesh Max Error of 1.0.

And here is the same area but with a Mesh Max Error of 4.0.

I showed you how to add a new property to the Elevation Source layer in the above. You can use the same method for adding properties to additional layer types. The properties depend on the layer type. You can find more details about the Terrain Layer Type in the Deck.gl documentation. Here is a list of the layer types Deck.gl support of which we currently support a handful.

Are there any specific layer properties you would like to see by default? Are there any layer types you'd like to see supported in MapInfo Pro 3D?

------------------------------
Peter Horsbøll Møller
Principal Presales Consultant | Distinguished Engineer
Precisely | Trust in Data
------------------------------