M.App Enterprise Tutorials

[#1]

This article describes how to get your 3D data into M.App Enterprise.

Note: This tutorial is only useful if you have a pro license for M.App Enterprise. 

Note: 3D data only usable in browser apps with 3D map.

Note: In order to get your data into Luciad Fusion / M.App Enterprise you need to crawl certain folders in Luciad Fusion Studio. One folder (_fusion / uploads) is created within the M.App Enterprise Warehouse location, which is crawled automatically.

If you need additional folders, you have to create jobs in Luciad Fusion Studio. Here you can find the tutorial how to get it done.

 

Digital Elevation model

To get a DEM into a browser app, you have to do the following steps:

1. Upload the GeoTIFF to the Warehouse of M.App Enterprise
2. Crawl the folder (either the one which is automatically there or your own defined one)
3. See the GeoTIFF in the data tab
4. Select it and click Create Service (at the top bar)
5. Select as a service type LTS
6. Wait until the service is started
7. Switch to M.App Enterprise studio and click 3D data
8. Select New -> Elevation
9. Select the service from step 6
10. Define a name (you have to click on the pencil to change it) and a scale (optional) and click Save
11. Add the DEM to the browser legend

OGC 3D Tiles

Prerequisite: To use 3D buildings in Luciad Fusion / M.App Enterprise your data must be either in:

• OSGB Format (Open Scene Graph Binary), which can be created with Bentley ContextCapture, Skyline PhotoMesh or Airbus Pixel Factory
• OGC 3D Tiles (Details about the standard can be found here), which can be created for example with FME.

To get 3D buildings (converted with FME into OGC 3D Tiles) into a browser app, you have to do the following steps:

1. Upload the data to the Warehouse of M.App Enterprise
2. Crawl the folder (either the one which is automatically there or your own defined one)
3. See the 3D Tiles in the data tab
4. Select it and click Create Service (at the top bar)
5. Select as a service type OGC3DTiles
6. Wait until the service is started
7. Switch to M.App Enterprise studio and click 3D data
8. Select New -> OGC 3D Tiles
9. Select the service from step 6
10. Define a name, a scale (optional), Quality factor (optional) and Terrain Offset (optional) and click Save
11. Add the OGC 3D Tiles to the browser legend

LAS / LAZ Files

Prerequisite: Coordinate Reference System information must be available in order to use .las / .laz files in Luciad Fusion for M.App Enterprise. There are two ways to achieve this. Either the information is in the header of the .las / .laz files OR you can define a .prj file (see detailed information further down).

1. Upload the data to the Warehouse of M.App Enterprise
2. Crawl the folder (either the one which is automatically there or your own defined one)
3. See the LAS / LAZ files in the data tab
4. Select it and click Create Service (at the top bar)
5. Select as a service type OGC3DTiles
6. Wait until the service is started
7. Switch to M.App Enterprise studio and click 3D data
8. Select New -> OGC 3D Tiles
9. Select the service from step 6
10. Define a name, a scale (optional), Quality factor (optional) and Terrain Offset (optional) and click Save
11. Add the OGC 3D Tiles to the browser legend

Defining a .prj file

Most important thing is that the .prj file has EXACTLY the same name as the .las / .laz file. Example of a .prj file for EPSG:3857:

PROJCS["WGS_1984_Web_Mercator_Auxiliary_Sphere",GEOGCS["GCS_WGS_1984",DATUM["D_WGS_1984",SPHEROID["WGS_1984",6378137.0,298.257223563]],PRIMEM["Greenwich",0.0],UNIT["Degree",0.0174532925199433]],PROJECTION["Mercator_Auxiliary_Sphere"],PARAMETER["False_Easting",0.0],PARAMETER["False_Northing",0.0],PARAMETER["Central_Meridian",0.0],PARAMETER["Standard_Parallel_1",0.0],PARAMETER["Auxiliary_Sphere_Type",0.0],UNIT["Meter",1.0]]

 As you can see it is nothing more than the WKT definition of the EPSG code within a file with the extension .prj

[#2]

Hi, is the format .e57 supported by Luciad Fusion for M.AE? What are the requirements?

[#3]

Thanks for the tutorial,

I created a first  3D application, using a point cloud. In my case the point cloud is floating in the sky, because of the value of the Z.  The globe what Z has? How can I manage this?

thanks

[#4]

Any news?

[#5]

Hi Giuseppe, 

maybe you can put this in the discussion board, because otherwise not many people getting notifications about the comments on a tutorial.

To answer the question. I guess you have to add an elevation model to this app as well, otherwise it will always float in the air. The "normal" 3D map (in this case OSM) doesn't contain any z- value.

Hope this helps and as I said, please write the next time into the discussion board.

Kind regards,

Stefan