Overview
The Oracle Network Management System Operations Mobile App GeoJSON Offline Landbase Maps. When OMA is not connected to the Internet, the offline landbase will give the user some geographic context in the OMA map.
To minimize storage of the offline maps on the device and to optimize performance when rendering them in the map, OMA recommends utilizing street centerline data and other simple landbase features (such as railroad centerlines, water body outlines, and so on).
To configure the build process for the offline maps, you will need to configure two items for your project:
1. A [project]-build-landbase-mobile-maps script that knows what maps comprise the landbase maps to be processed and will generate the landbase .geojson maps and a map index mobile_geojson_landbase_maps.json file in a landbase subdirectory ($OPERATIONS_MAPS/data/export/landbase). These files are zipped into offline_landbase_maps.zip. In addition to this zip file, an offline_landbase_maps.json file is also created containing version information. These two files will need to be placed in your OMA2 project directory and they will be consumed in the OMA2 build process.The OPAL model has an example [project]-build-landbase-mobile-maps script file in the $NMS_BASE/OPAL/bin directory named OPAL-build-landbase-mobile-maps.
2. A [project]_landbase_geojson_export.dat containing the definitions of the objects to transform from the landbase centerline .mb file to the resulting geojson files. OPAL has an example of this in the $NMS_BASE/OPAL/sql directory named OPAL_landbase_geojson_export.dat. It utilizes the NMS standard street centerline model plus a few OPAL specific modeling objects (railroads and waterways). Do not import any text objects or street intersection points.
The OMA product template has a set of offline landbase maps prepackaged in it covering the OPAL model area as an example in the OMA2 directory.