Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Whilst you might be happy to simply view integrated meshes within ArcGIS Pro, it’s more likely that you’ll want to add additional contextual data, either from standard mapping products or your own project-specific resources. ArcGIS Pro is well-equipped to support this.
Before getting started, should you be new to using the 3D ‘Scene’ mode, it’s important to understand the differences between the ‘2D Layers’ and ‘3D Layers’ sections that are found within the Contents pane of Scene projects. Although their titles initially appear obvious, their actual function isn’t quite what you might expect.
All spatial data used with ArcGIS Pro will have a dimensionality – either 2D or 3D. This is exclusively defined by format of geometry column. As such:
If a feature has only ‘X’ and ‘Y’ ordinates within its geometry, but has a ‘Z’ ordinate included as a separate attribute, then this is still considered to be a ‘2D layer’ by ArcGIS Pro.
In contrast, if a geometry includes ‘X’, ‘Y’ and ‘Z’ ordinates, but ‘Z’ values are all set to zero, then ArcGIS Pro still treats this as being a 3D layer.
The ‘2D Layers’ section of the contents pane is used when you wish to drape vector data over a surface (which may be an integrated mesh). This is something that you’d typically wish to accomplish when working with 2D data. However, 3D data dragged into ‘2D Layers’ will be treated as if it were 2D and will thus be draped in the same way.
The ‘3D Layers’ section of the Contents pane is used when you want to render data in 3D space in accordance with its 3D geometry. In fact, both 3D and 2D layers are accepted here, with 2D layers assigned zero-value ‘Z’ ordinates.
Once the integrated mesh has been added to the scene, you’ll want to navigate in 3D space to view your content from all angles. The controls for accomplishing this are common to all Scene projects, so experienced 3D users should already be ‘good to go’.
For users not already familiar with Scene projects, there are two primary navigation modes – 'Planar' (the default mode) or 'First Person' navigation. The first of these works well if you're going to be primarily using mouse input to explore the 3D environment. The latter, meanwhile, has similarities to the control systems used in some genres of video game. Which mode you choose is likely going to be down to personal preference rather than functional differences.
To configure the navigation options, a ‘Navigator’ user interface will appear at the bottom-left of the main scene window. This can be toggled on/off, from the view menu, if required. This has two basic states, named ‘Show Heading’ and ‘Show Full Control’, with the latter offering a complete set of on-screen controls and the former being smaller and more limited. Dedicated buttons, at the top of this, facilitate the selection of the ‘Planar’ and ‘First Person’ modes.
The default Planar navigation mode is primarily intended to offer intuitive mouse-orientated control. The core mouse options are shown in the table below.
Rotate/Tilt
Press down mouse wheel and move mouse.
Pan
Press left mouse button and move mouse.
Zoom
Turn mouse wheel or press right mouse button and move.
Beyond this, additional keyboard controls can be used alongside, with both the arrow keys and ‘W’,’A’,’S’,’D’ also enabled as available alternatives.
‘First Person’ navigation offers a somewhat similar experience to the controls found in many video games. Here, navigation is primarily achieved using the ‘W’,’A’,’S’,’D’ and arrow keys, combined with additional mouse movement to pan left/right and up/down.
Perhaps the most straightforward and effective way of enhancing and individualising a 3D integrated mesh is to drape a 2D polygon layer over it.
This is achieved by simply dragging an appropriate polygon layer into the ‘2D Layers’ section of a project that already contains a 3D mesh object. ArcGIS Pro will automatically handle the draping and will also enable its interactivity, upon clicking individual features, by default. You can still style the draped polygons using the standard Symbology interface. When combining polygon layers with an integrated mesh, you’ll likely also want to adjust the layer transparency, so that both sources remain sufficiently visible.
A thinly populated (or heavily filtered) polygon layer can be used to achieve an effect that’s analogous to drawing on the mesh with a highlighter pen. This just requires an adjustment to the polygon layer’s symbology (maybe choose a neon-type colour…), along with a suitable layer transparency (try 50%). An example of this is shown below:
Rather than highlighting only selected areas of the mesh, another approach is to highlight individual feature classifications using colour/style variations. In the example below, 2D polygons from the OS NGD Land Use Theme have been added to the scene. Using the Symbology tools, these polygons have been styled according to the unique values found with the ‘oslandusetiera’ attribute. A transparency of 50% has also been applied to the entire layer.
Even though draped, these features can still be clicked upon, allowing their individual attributes to be interrogated via a pop-up window.
It’s possible to individually insert custom 3D models into a scene. This is a technique that can potentially combine well with integrated mesh content. One example of this could show a visualisation of a planned building or structure at its intended location. A new ‘3D object’ feature class has been introduced to support this flowline (see ), although the long-established ‘multipatch’ format also works. Various standard 3D file formats are supported (.dae, .fbx, .glb, .obj, etc) – any of these can be exported from Blender or other similar modelling tools.
It’s outside the scope of this document to go into detail about this process. However, if you want to explore this further, we recommend this ESRI tutorial on how to .
Line feature layers can be useful if you want to represent network data on top of your integrated mesh. Transport data is an obvious candidate for this, but other linear features, such as power lines, could also work well. Using line feature layers can be a little more challenging than working with polygons, as they’re prone to unwanted interactions with the base mesh. Both 2D and 3D line feature data can be used for this, albeit via differing methods and results.
Line features can be dragged into the ‘2D Layers’ section of the Contents pane, where they’ll be styled using current Symbology settings and draped over the mesh.
The advantage of draping line features concerns their visibility – they’ll never ‘disappear’ under the mesh. Unfortunately, the downside of this is that the lines may be rendered on top of obstructing features such as trees or bridges. This can look very strange and may not be what you really want. Also, the geometry can become jagged and is prone to looking untidy.
In the example below, 2D road features, from OS Open Zoomstack, have been draped onto an integrated mesh.
In the following example, using the same OS Open Zoomstack data, it can be seen how the line features have been draped across overhanging treetops, which probably isn’t the desired outcome. Also, when viewed from the side, the lines no longer appear to be straight. Obviously, the severity of these problems depends very much on the content represented within the mesh itself.
In contrast to the above, dragging road data into the ‘3D Layers’ section will plot line features in 3D space, using their full 3D geometries. Ideally, you’ll want to use true 3D data layer for this, as 2D layers will likely find themselves hidden beneath the mesh.
OS NGD Road Link features are an example of an OS vector product that contains Z values by default and is thus a good candidate for this type of project. Nevertheless, when visualised over an integrated mesh, it may be observed that the lines are prone to cutting through and under the mesh. The extent to which this is desirable will be dependent on individual use cases.
To avoid issues where the line features appear to be passing under the roads, a good solution is simply to move the line features upwards. ArcGIS Pro offers at least two methods to accomplish this.
The simplest solution is to use the ‘Cartographic Offset’ parameter, found in the Elevation pane, to apply a visual z-axis adjustment. Alternatively, should you want to make the transformation permanent, the ‘Adjust 3D Z’ geoprocessing tool can be used. Of course, it’s best to make a copy of your source data before attempting this.
Should you wish to improve the general visibility of the line features, you can use the ‘Buffer 3D’ geoprocessing tool (included in the 3D Analyst extension) to convert the basic line features into something akin to 3D pipes.
Should you not want to drape your 2D data over your mesh, you can avoid this by generating an additional 3D version. There are two primary methods for achieving this.
Firstly, if the layer contains height information within a separate column, you can use this to create true 3D data using the ‘Feature To 3D By Attribute’ geoprocessing tool.
Alternatively, as shown below, height values can be extracted from a separate elevation model, using the ‘Interpolate Shape’ geoprocessing tool (requires the 3D Analyst extension).
Unfortunately, it isn’t currently possible to use an integrated mesh as an input into the Interpolate Shape tool. Instead, you’re limited to just using a standard surface object, which isn’t necessarily what you’re going to want in this context. Hopefully, this is something that will be addressed in a future update.
A basic way to improve the overall look of your integrated mesh is to apply scene lighting. This can be enabled using the 'Enable Lighting' button on the ‘Integrated Mesh Layer’ menu. Further lighting variations can be chosen from the Lighting dropdown menu (a full description of these can be found at ).
In ArcGIS Pro version 3.3, specifically, we’ve experienced issues with the lighting options than weren’t present when using previous versions. We assume that this will be addressed in a future update.
The content of this document has been created with ArcGIS Pro version 3.3. Some aspects covered won’t be supported in earlier versions. If you’re using a more recent version of ArcGIS Pro then it is of course possible that some aspects have since been revised.
Ordnance survey mesh data is currently available in three streaming formats – ESRI (.SLPK), Cesium 3D Tiles and Skyline (.3DML). ArcGIS Pro supports the first two of these, although the ESRI option is more established and is likely going to be the obvious choice in this context.
The OS 3D Mesh getting started guide is broken down into the following topics:
As was the case with polygon and line data, stylised vector point features can be draped on an integrated mesh. An example of this is shown in the image below:
The result of this may or may not be what you intended. As such, it’s often better to use the ‘3D Layers’ section when working with 3D symbols.
If you wish to render 3D point data in 3D space, you’re typically going to want to avoid just depicting it as a small dot. Instead, you’ll likely wish to represent it either as a ‘3D symbol’, or as a 2D ‘billboard’ symbol that will automatically rotate to face the scene camera.
A ‘3D symbol’ is a small, usually simple, 3D model that can be rendered at the position of a 3D point. Within its Symbology toolset, ArcGIS Pro has a separate section dedicated to supporting such symbols. However, this is only available when using layers present in the ‘3D Layers’ section of the Contents pane.
By default, ESRI provide a selection of basic 3D symbol primitives that includes cubes, spheres and diamonds, along with some more map-centric objects like push-pins and flags. However, if you can use a 3D modelling tool, such as Blender, it’s possible to design and use your own custom models for this purpose (for further details, see our tutorial on creating 3D symbols for GIS applications on More than Maps. Alternatively, you may be able to source pre-made 3D models (with a suitable level of detail…) from an online library.
As mentioned previously, it’s not currently possible to use the integrated mesh as a source of heights. In the example above, the points were heighted from the ArcGIS Pro default surface, which was far from ideal, as this placed the points below the integrated mesh. To get around this, points were moved upward by 20meters, using the Cartographic Offset property.
Regular 2D images can still be used as symbols within a 3D scene. The typical way to achieve this is via the ‘billboard’ function, which, when enabled, will ensure that the symbols rotate to always face the scene camera. ArcGIS Pro offers two modes for this – ‘full’ and ‘signpost’ rotation, with the latter locking the rotation to just the Z (upward) axis. Alternatively, ‘billboard’ mode can be turned off entirely, leaving the symbols facing in just one constant direction.
You may wish to include text labels within a scene that also contains an integrated mesh. This behaves as just another form of billboard. The challenge, when setting this up, is to choose a label symbology that sufficiently stands out against the background. In this example, the ‘halo’ option, which adds a white rim to the text, greatly helps in keeping the text legible.
Once your data layers have been uploaded and are ready for use, you’ll then need to commence with the creation of your project. ESRI offers some interesting options (for example, Story Maps), but the simplest choice will be to create a 3D scene that will be accessed from with the Scene Viewer tool.
There are several ways to achieve this, but the most obvious is to navigate to the Scene page (via the top menu), then press the [+] button that’s found on the top menu. Here, you’ll be asked to choose between creating a ‘Global’ or ‘Local’ scene. Global scenes are based around a full globe model, whilst a Local scene will offer a more typical 3D environment. By default, ESRI provides a default background map layer for both options. If you’re going to be working with OS mesh data, the ‘Local’ scene option is likely going to be more appropriate.
Within its 3D Analyst extension, ArcGIS Pro includes a ‘Line of Sight’ geoprocessing tool for calculating visibility between a given viewpoint and target. This tool can treat integrated mesh models as a core source of obstruction objects. As such, this provides a strong use case for working with mesh data.
To use this tool, you will need to create or obtain one, or more, line features. The beginning of each line will represent the viewpoint, with the end point representing the target. These line features, along with all potential obstruction objects, are provided as tool input. Upon completion, new line features will be created. These will be shaded green where the line is visible and red where it is not. An illustration of this is shown below, with icons added to indicate the viewpoint and target vertices of the supplied line feature.
The official documentation for this tool can be found at:
ArcGIS Pro provides a suite of animation tools, some of which support the creation of 3D fly-throughs. Of course, an integrated mesh has the potential to serve as an engaging backdrop for such projects.
The authoring of animations is an extensive subject that can’t be adequately addressed in this document. As such, we recommend checking out .
AGOL scenes default to using the Web Mercator spatial reference system, with all default background map content also conforming to that. Unfortunately, the subsequent mixing of layers with differing spatial reference configurations is not supported. As such, any default background maps will be removed if, say, a mesh in EPSG:27700 (British National Grid) is introduced alongside. This behaviour contrasts to what can be expected when working inside ArcGIS Pro.
It is possible to re-project an EPSG:27700 integrated mesh into Web Mercator, using the ‘Project’ geoprocessing tool found in ArcGIS Pro. Although this might take a notable amount of processing time to accomplish, the output will potentially be able to sit alongside any ArcGIS Online background content. If taking this route, you’ll obviously need to re-project any other data layer that you’re planning to use before introducing them into the AGOL environment. In most situations, it's going to be impractical and ineffective to apply the default background mapping within your project.
Scene navigation, within the Scene Viewer, is standard regardless of content. The middle mouse button controls the zoom extent, whilst the left and right mouse buttons, in conjunction with mouse movement, control panning and rotation. When applicable, clicking a distinct feature, within the current view, will open a pop-up menu showing relevant attribution.
On the top-right of the UI, buttons enabling several further tools can be found. These include options for further adjusting the scene’s appearance, via the use of real-time daylight and weather data.
While your users may be happy just to view a raw OS 3D mesh, it’s more probable that you’ll want to combine this with other data sources to create your own unique narrative. Geospatial vector layers are an obvious source of additional detail, so we’ll cover this in detail in the following pages.
The method for adding vector layers is no different from how you would add a mesh – you just choose what you need from your Content repository. Assuming everything is working correctly, these layers will then be added into your scene in the same manner.
This getting started guide provides instructions for using OS 3D Mesh in different software applications. Users with limited technical knowledge will be able to follow this guide.
This document attempts to describe some of the core options when working with an OS integrated mesh within ESRI's ArcGIS Pro application. If you’re using data that has been supplied in the ESRI-orientated Scene Package File (.slpk) format, you should find that it’s very straightforward to import it into your ‘Scene’ projects. However, learning how to integrate such meshes with other datasets is slightly more challenging, so this aspect will be covered in detail in the following pages.
The software applications covered in this getting started guide include:
It’s normal for analytical tasks, such as line-of-sight calculations, to be undertaken in a desktop GIS environment, rather than a web environment like AGOL. However, AGOL is certainly a platform that can be effective at sharing the results of such analysis, particularly in the context of an ESRI Story Map.
ESRI Story Maps, along with the other AGOL tools, allow the inclusion of 3D Scene components…which therefore supports interactive usage of OS 3D Mesh data. There’s clearly a lot of creative potential present here. How you choose to utilise this is up to you!
With a 3D scene successfully created, you’ll want to add your own content. For the purposes of this guide, we’ll assume that you’ll first want to add an OS 3D mesh.
To do this, choose the Browse Layers option, via the ‘+’ button on the side menu, to open the Browse Layers window. This will list your current repository of online content. From here, find the entry for your mesh and press the associated ‘Add +’ button.
The mesh will be now added into the 3D scene.
This page details some of the core options when working with OS 3D Mesh Data within ESRI’s ArcGIS Online (AGOL) web application.
OS meshes can be incorporated in AGOL and used within the various tools and templates that are offered. Further to this, additional data layers can be incorporated alongside, enabling the creation of unique and engaging content. It’s a great way of sharing mesh data to a wider audience.
Whilst AGOL contains a lot of functionality, it probably shouldn’t be viewed as a stand-alone solution. Instead, it’s typically used in conjunction with a separate desktop GIS application (ArcGIS Pro, etc.), with such tools typically being used for data preparation. This aspect isn’t covered in this document, as it’s assumed that you’ll already have your own methods and preferences for such activities.
The output from AGOL projects can be a basic view of the data using the Scene Viewer tool. However, more specialist options, such as ESRI Story Maps or Experience Builder, can also be configured to use mesh-orientated scenes.
AGOL is accessed by visiting Account Login - ArcGIS Online and following the sign-on process that’s relevant to your specific account. Once successfully logged in, you’ll see the AGOL homepage, which will include a top menu bar that looks something like this:
The options listed on this menu link to the most commonly used AGOL tools. However, an additional ‘waffle’ menu (i.e. nine dots in a square) grants access to an extended set of options. For the purposes of these instructions, where an integrated mesh is the primary subject of interest, we’ll primarily work within the Scene Viewer, additionally using the Content page to manage our resources.
The topics covered in this guide are listed below:
The general functionality of point layers largely mirrors that of polygons and lines, detailed on the previous two pages. For points, the primary rendering options are ‘2D Marker’ or ‘3D Object’. Details of these options are included below.
This mode displays each point as a 2D ‘billboard’ object. That is, the point representations will always rotate to face the user.
To select a shape, users can choose from a small selection of ‘Basic Shapes’ or a much larger selection of ‘Icon’ images. There’s also an option where a custom image can be uploaded. In addition, further styling options are available. If using such icons over a detailed mesh, care needs to be taken to ensure that they remain sufficiently visible.
Rather than use a 2D billboard, ‘3D Object’ mode allows a full 3D model to be used to represent each point. Many candidate objects are available, which have been classified across several different screens. A selection of these is shown below:
Unfortunately, there doesn’t seem to be an option to upload your own custom 3D models for use with this feature.
When using this option alongside a mesh, it’s very easy for the models to either get lost, or to dominate the scene out of all proportion. As such, a degree of caution is advised!
The AGOL ‘Content’ page is the primary means for building and viewing the collection of resources that you are going to be using in your project. This includes any OS 3D mesh objects you might be wishing to work with. Data layers can be added in to your Content page in a few distinct ways. If you already have data within ArcGIS Pro, you can copy that into AGOL. Alternatively, data can be uploaded from your local machine, or from cloud services like Dropbox or OneDrive. Web service links are also supported. The ‘New Item’ button, found in the Content page, is used to access most of these options.
If data is already present in an ArcGIS Pro project, you can push this into your AGOL environment from within ArcGIS Pro itself. To achieve this, open your ArcGIS Pro project and select the layer you wish to use within the Contents pane. Then, right-click the layer and select Sharing -> Share As Web Layer, as shown below:
Upon doing this, a ‘Share as Web Layer’ window should become visible. Here, descriptive details about the layer can be entered. These will then be made present in the online content.
This tool also includes an ‘Analyze’ function, which checks that the layer is suitable for inclusion within the Online space. A common reason for this to fail is when ‘Unique numeric IDs are not defined’. To solve this, right-click the error message and select ‘Auto-Assign IDs Sequentially’.
To continue with the upload, use the ‘Publish’ button.
On completion of the upload, the layer should then be listed within AGOL’s Content page. That screen should then look something like this:
Polygon vector layers are typically easy to integrate, alongside a mesh. When working with such data, the main choices are ‘2D polygon’ and ‘3D Extrusion’. In addition to these, a third option, ‘Water’, enables animated water effects.
Alongside the ‘Layer style’ panel, the ‘Layer properties’ panel, selectable from the same pop-up list, is also available. This includes parameters for things like ‘transparency’, ‘elevation’ and ‘visibility range’.
Upon adding a polygon layer into a scene, it may initially be visualised using just some simple black outlines. If you’re working with a mesh, this can be a problem, as these lines can become hidden, making it appear that your layer has failed. Fortunately, this issue will resolve itself upon the selection of one of the ‘Layer style’ options. Alternatively, you can temporarily hide the mesh layer, using the eyeball icon, to obtain an unobstructed view.
A simple, unclassified, polygon layer can be effectively used to draw attention to significant areas within a mesh. The ‘2D Polygon’ option, from within the ‘Layer style’ panel, should be sufficient to achieve this. As can be seen in the following figure, adding a degree of transparency to that layer will likely prove effective.
If you’re working with a set of categorised polygons, extending the previous method to make use of the ‘Choose the main attribute to visualise’ option can achieve worthwhile results. Choosing a suitable attribute from this drop-down list will automatically assign categorised colours to each polygon. However, these colour choices, along with other attributes, can be subsequently edited for each individual category from within the Options screen.
Again, in the following example, transparency has been adjusted to ensure that mesh detail is still easily visible.
As with all such vector layers, individual features can be selected by left-clicking on them. Any associated attribution is then displayed within a pop-up menu.
Finally, it should be noted that, upon selecting a categorisation attribute, AGOL removes the option to render the polygons as animated water.
If the ‘3D Extrusion’ option is chosen from the ‘Layer style’ panel, the selected polygon layer will still be draped over your mesh. However, it will also be vertically extruded to form solid objects. Due to the erratic nature of mesh geometries, the result of this can often be unappealing, as is evident in the example below:
It seems probable that the ‘3D Extrusion’ option wasn’t created with mesh-based applications in mind. Instead, this is something that’s going to be more useful when directly working with building footprint data, perhaps in a more standard mapping environment.
The third of the polygon-orientated ‘Layer style’ options is specific to the representation of water extents. When used alongside a mesh, this works in much the same way as the ‘2D Polygon’ option, in so far as it drapes the nominated polygon layer over the mesh surface. However, as the name implies, this option renders the polygons as an animated water surface. In an appropriate environment, this will include reflections of the surrounding scene. It’s a very nice effect.
To set up an effective water scene, you will likely need to adjust settings in both the ‘Layer style’ and ‘Layer properties’ panes. Specifically, if you should notice that the water polygon is not visible and that the layer name is ‘greyed out’, the Visibility Range parameter may need adjusting. Also, if you’re depicting rivers or lakes, it’s also likely that you’ll need to change the water’s colour to something more appropriate than the default bright blue!
An additional, more advanced, AGOL feature involves placing custom 3D models within a 3D scene. Incorporating such models alongside an OS mesh offers a lot of scope for creativity and interest. This could be particularly effective, should you wish to demonstrate how a new building or structure might fit in, visually, with existing surroundings.
Many tools are available that allow you to create whatever 3D model you need. Blender, for example, is a popular open-source choice that can work well for this. Alternatively, repositories of pre-made models are available online, should a stock model be sufficient for your requirements.
Unfortunately, it’s not currently possible to add a 3D model directly into the AGOL Content area. Instead, an ESRI-specific ‘3D Object’ feature type needs to be prepared, within ArcGIS Pro, as a preliminary step. This ESRI tutorial - Import and incorporate 3D models in a scene | Documentation - covers this well. Once the model has been prepared and exists as an ArcGIS Pro layer, it can then be ‘shared to web’ (left-click the layer and select ‘Share As Web Layer’…), thus copying it directly into your AGOL Content store.
We’ve found that, after a 3D model is shared into AGOL, error messages may appear if you try to use that model immediately (even though everything appears to be complete). If this happens, wait for a few minutes and try again! This seems to resolve the issue.
When creating a 3D asset, it’s usually good practice to locate each object’s origin towards the bottom of the model. If using Blender, it’s also advisable to apply any rotation and scaling, along with any active modifiers, before export. Also, if you’ve used any advanced procedural shading tools, you’ll need to bake those into a texture.
Finally, upon export, the suggested 3D file format is .glTF/.glb. This is a good option, as it’s able to pack textures within the file, making it straightforward to manage.
In ArcGIS Pro, any layer dragged into the ‘2D Layers’ section in a Scene will automatically be draped across a suitable ‘surface’. Meanwhile, layers within the ‘3D Layers’ section will be rendered according to their full 3D geometry.
In AGOL, however, things are handled slightly differently. Here, there is no need to place the layer under a particular heading. Instead, styling/rendering behaviour will be defined by choices made within the ‘Layer style’ and ‘Layer properties’ panels. Of these, ‘Layer style’ defines the core rendering options.
To access the ‘Layer style’ panel, the Layer Manager panel first needs to be selected from the side bar, as shown:
Each listed layer will have further options that will be exposed via the ellipsis ( ‘…’) icon. ‘Layer style’ can be found at the top of this list.
Selecting ‘Layer style’ should then open this interface:
The ‘Layer style’ panel will typically include an option relating to attribute-based classification, along with several ‘drawing style’ choices. Each of these choices, once selected, will then reveal a further set of options and settings.
An option to include text labels, that relate to a given layer, can be found in the ‘Layer type’ options of polygon and point features. If this is enabled, a set of additional parameters is exposed. These allow you to specify which attribute you wish to base the labels on, as well as choose from some simple label styling options.
Line feature layers can be added into an AGOL scene by, again, first adding them into your Content area, then selecting them from within the Scene Viewer interface using the ‘+’ button.
Line feature layers have their own unique options within the ‘Layer types’ pane. The options offered will be dependent upon whether the line feature layer, itself, has been supplied with a 2D or 3D geometry.
If you’re using 3D data, but are also using an attribute for feature classification, the ‘Layer type’ display may revert to apparently offering the ‘2D Types’ and ‘3D Types’ options. We assume that this is an error with the user interface only, as the functionality does not appear to be affected.
If you’re working with 2D data, the available ‘Layer type’ options should look like this:
Alternatively, if you’re working with a 3D line layer, you should instead see these options:
Examples of each option are thus described below.
The ‘2D Types’ option renders the line features as 2D draped lines. When used alongside a mesh, it can be an effective solution when viewed from afar. However, as the following figures show, it can look rather odd when viewed close-up.
If using this mode, it’s certainly worth experimenting with different line widths, as it’s often easy for detail to be lost amongst the complexity of a 3D mesh.
The ‘3D Types’ option will render line features as a solid geometry. By default, this will be realised as a set of ‘tubes’, but different shapes are available, should you prefer a rectangular or square profile. As with ‘2D Types’, there is also the option to specify different line widths.
The ‘3D Types’ option also undergoes a degree of mesh draping. However, for this option, the result seems to be much generalised in comparison. Thus, if viewed close-up, the ‘tubes’ may be seen to pass directly through a tree canopy, rather than conform to its outer edges:
In this option, line features will be rendered very simply, as if they were lines on a page, albeit in 3D space. As the supplied line layer will already contain its own height data, no attempt to drape the features will be made. As such, there will no direct dependency on the mesh, assuming one is present. This, of course, will eliminate the potentially unwanted behaviours discussed in the previous sections. However, there may, instead, be occasions where the line features dip below the mesh’s surface in ways that are not wanted.
Like the ‘3D Type’ option covered previously, this option will render lines as solid objects, using the shape profile of your choice. Again, because full 3D geometry is present, no draping is undertaken, with the vertical position relying entirely on the layer’s own geometry. This option can potentially solve the ‘below the surface’ issue mentioned above, with the line thickness making it more likely that the layer will remain fully visible.