====== Publish > Mobile Mapping ======
This page describes the EOS Console tab "Publish" > "Mobile Mapping". \\
The homepage for all documentation about the Publisher can be reviewed here : [[110:mobile_mapping:publishing:index|]].
{{ publish_moma.png?900&nolink |}}
===== Publication =====
**Publication List** \\
At the left side all publications are listed. \\
* Add, Remove or Copy a publication using the appropriated buttons at the bottom of the list.
* Set the Data and Viewer configurations for the the selected publication.
**Server URL** \\
Each publication must have a server url. The url is based on the following parameters:
* Server ID : The server's computer name, internal or external IP address as known by the connecting clients.
* Port : The port used by the Orbit Http Service . The Orbit Http Service operates by default on port 1111 but redirecting via port 80 is advised for online use.
Read more about the IT and Server configurations here : [[110:technologies:platforms:specs_publisher|]].
**Publish** \\
With a single click on the "Publish" button the selected publication will be accessible via a set of predefined html pages.
* default url syntax : http://:/publications//.html
* New html templates can be added via the publisher service folder : /server/program/services/publisher/publication_template
* Note, a url may not contain two consecutive spaces as most browser will reformat this syntax automatically to single spaces.
===== Data Setup =====
**Publication Title** \\
What's is a name. Give a clear name to your publication. \\
Since this name will be part of the URL, it is not advised to use spaces. Be careful with foreign characters as well. \\
If you change the name/title of the publication it is required re-publish this publication.
=== Mobile Mapping Projects ===
**Add or Remove** \\
Add or remove mobile mapping projects to the selected publication using the according buttons at the bottom of the table. \\
A user (login or preset login) requires permission to at least one of the mobile mapping projects to be able to open the publication.
**Labels** \\
Enter a label (user display name). All added projects with the same label will be grouped and used as one project label. \\
The user will see only one project record, or in other words it will appear to the user as one project. \\
The EOS console will sync or force all projects grouped by a label to have the same start-up visibility and color.
**Visibility** \\
Define the start-up visibility of a project (label). The EOS console will sync all projects grouped by a label having the same visibility. \\ A publication user can change the project visibility using the according panorama component sidebar function.
**Color** \\
Set the project color of a project (label). This color will be used for all image related presentations (photo positions, simplified trajectory, field of view overlay). The EOS console will sync all projects grouped by a label having the same color. \\ A publication user cannot change the project color.
=== Vector Overlay Datasets ===
Optionally one or more EOS vector datasets can be configured as vector overlay on map and panorama. Resources need to be organized as Workspaces and Dataset lists to be used as vector overlays.
**Select Worksapce Dataset List** \\
Select one dataset list from a workspace. All listed datasets will be available as vector overlay. \\
Only vector resources should be used as vector overlay. It isn't a good idea to over image or raster resources to be overlayed.
**Dataset legend** \\
The Orbit legend will be used to display the vector overlays on map and panoramas. \\
There are no Orbit legend limitations on the map component, on the panorama component only following basic legend parameters will be taken into account (no classifications) :
* Areas : fill color, fill transparency, outline color, outline with, outline transparency
* Lines : color, width (points on screen), transparency
* Symbols : name, size (points on screen), transparency, fill color, outline color
* Labels : size, hotspot, type (text, box, box rounded, callout, callout rounded), text color, box fill color, box outline color
Remarks :
* Yellow is the Orbit selection highlight color. Take care using yellow as line or fill color.
* The point legend [[110:orbitgis:datasets:legend:parameters:all_point|symbol parameter "Draw icons 1:1"]] is not used by the panorama component. If this parameter is used for map presentation, set a reasonable symbol size value. It will be used by the panorama component. Next update of the panorama component will take care of the Draw incons 1:1 setting.
**No username** \\
The dataset username is not displayed in the publication's vector overlay window if :
* no [[110:technologies:crs:crs_orbit|dataset crs]] has not been defined
* the resources is not a [[110:technologies:resources:supported_formats|supported vector resource]] (e.g. image or raster resources)
=== Blur and Erase ===
Enable detected blur and/or erase areas to be applied on the fly. The erase above horizon (1) and below horizon (2) colors can be adjusted to your preference.
=== Publication CRS ===
The Publication CRS is used to display the map and as default CRS to show the measurement results.\\
Enter the EPSG code in the appropriated CRS field.
* If this field remains empty the CRS of the overlayed Workspace DataSet List will be used
* To use a combined coordinate system (horizontal + vertical crs) enter + (e.g. 28992+5709).
More information about coordinate systems : [[110:technologies:crs:crs_orbit|]].
===== Viewer Setup =====
=== Login Settings ===
To open a publication a user must have permission to access at least one mobile mapping project of the requested publication. \\
Permissions on mobile mapping projects are set via the EOS Console extension's tab Mobile Mapping : [[110:eos:console:extensions:mobile_mapping|]]
Even if a user is able to open the publication, he (or she of course) is only able to view and open panoramas from projects for which permissions are granted. Similar for basemaps and vector overlays. More about permissions can be reviewed here : [[110:eos:concepts:roles_permissions|dataset permissions]].
**Ask for Login** \\
Protect your publication with a password. When loading the publication the user will be required to enter login and password to open the publciation.
**Preset Login** \\
As administrator you are able to preset a login and password for a publication. This preset will be used to auto login when a user is accessing the publication. The preset credentials still require access to at least one listed mobile mapping projects to open the publication.
If you switch between "Ask for Login" and "Preset Login" it is required re-publish the publication to take advantage of the new login settings. \\
Depending the browser settings it will be required to remove browsing data (cached images and files) to force the viewing client to request the updated html page.
**Force unique logins** \\
Restrict publication access to unique users to protect a publication to be used on multiple hardware (client computers) using the same publication login (username). Or in other words, when using "force unique logins" one login (username) cannot be used simultaneously by multiple users (persons) on different computers. \\
The first user gets in, the second user using the same login gets "Failed to login due to license constraints on the server."
=== Viewer Basemaps ===
Any combination of [[110:technologies:resources:supported_formats|supported resources]] can be used as map component basemap \\
The resources must be defined as EOS resources and need need to be organized as dataset lists in workspaces to be used as basemap.
Add and remove basemaps using the according buttons at the bottom of the table, rename the basemap by clicking the label field and select a dataset list using the "Select" button :
* Up to 6 basemaps can be configured
* The first listed basemap will be the default on start-up
* All datasets as available within the selected the dataset list will be used : visibility, order, legend, scale limits.
=== Startup Parameters ===
This set of parameters defines the start-up view on loading the publication.
**Heading, Tilt, FOV** \\
Fall back panorama view orientation and field of view (fov) setting on start-up, used if a publication is opened without specifying the image orientation. \\
This information is optionally displayed in the lower-right corner of the webclient panorama component.
\\ \\
**X,Y** \\
Fall back coordinates on start-up, used if a publication is opened without specifying a location or photo id.
\\ \\
**CRS** \\
Coordinate systems of entered X,Y start-up coordinates. For map and measure crs review the publication crs. \\
The coordinate system's EPSG code must be used. If empty the publication crs will be assumed.
**Scale** \\
The map scale will be applied when loading the publication (on start-up) and after a successful search result using the map component search box. \\
The scale units are defined by the publication coordinate system. Geocentric or geographic coordinate systems are using degrees, all projected coordinate systems use metric scale units. When using geographical map coordinates (publication crs WGS84, ESPG 4326) the scale can be defined as decimal value to zoom in more and get the start-up view you want.
=== Geocoding plugin ===
Add a geocoding plugin to the publication. This plugin will be available via the map component search box. Only one geocoding plugin can be added.
Geocoding services are varied, and implementation cannot be standardized. Therefore Orbit delegate the implementation of a geocoding service to JavaScript, which can be added on the fly and edited, adapted, debugged by you.
Geocoding plugins are stored on the server : /server/program/services/ext_publisher/publication_geocode_plugins \\
For more information review our developer's documentation : [[110:developer:index|Developer Zone]] > [[110:developer:webclient:geocoding_plugin|Geocoding Plugin]]
=== Point Cloud Overlay ===
Enable the possibility to overlay the point cloud on panoramas. \\
The point cloud will be displayed with a fix system legend based on distance to the panorama view location. \\
If required this legend can be adjusted via the point cloud legend system configuration file : /server/program/wwwroot/publications/point_cloud_panorama_legend.ini
The publication point cloud display requires extra server processing power. Keep an eye on the server's memory and CPU consumption.