myWorld

Release Notes
Version 2.7

Ubisense Limited, St Andrew's House, St Andrew's Road, Cambridge CB4 1DL, United Kingdom.

Telephone: +44 (0)1223 535170. Website: http://www.ubisense.net.

Contents
1: Introduction 4
1.1 Intended Audience 4
2: Installation 5
2.1 Supported Browsers 5
2.2 Alias File for Linux 5
2.3 Database Upgrade 5
3: Server 6
3.1 Feature Tables now Creatable via GUI 6
3.2 Feature Definition Validation Improved 6
3.3 Layer-Feature Association now via Geometry Field 6
3.4 New Option in Vector Layers Definition 6
3.5 New Options in LDAP Authentication 7
3.6 Other Changes 7
4: Client 8
4.1 Search GUI Enhanced 8
4.2 Toolbar Handles Overflow 8
4.3 Vector Rendering Performance Improved 8
5: Configuration Pages 10
5.1 Features Page Extended 10
5.2 Layers Page Enhanced 10
5.3 Replicas Page 10
5.4 Other Changes 11
6: Tools 12
6.1 Native App Tools Moved to Core 12
6.2 myw_db Command Enhanced 12
6.3 myw_tilestore Command Enhanced 12
7: Smallworld ETL 13
8: JavaScript API 14
8.1 Minification Process Changed 14
8.2 Event Feature Collection Modified Extended 14

Page ii
 8.3 Feature Retrieval Functions Modified 14
9: Documentation 15
10: Upgrading 16
10.1 Upgrading your myWorld Server 16
10.2 Upgrading your Smallworld ETL Configuration 16
10.3 Post-upgrade Activities 16

Page iii
 1: Introduction

1: Introduction
This document provides a summary of the major changes in release 2.7 of myWorld.

1.1 Intended Audience

This document is intended for administrators and customizers with a detailed technical knowledge of
myWorld.

Page 4
 2: Installation

2: Installation
The following changes relate to installation and upgrade.

2.1 Supported Browsers

myWorld 2.7 is supported on the following browsers:
l Internet Explorer (versions 8, 9, 10 and 11).
l Chrome (version 45).
l Firefox (version 41).
l Safari (version 9.0.1).
l Android native browser (Jelly Bean, KitKat, and Lollipop).

2.2 Alias File for Linux

The installation includes a new file Tools/myw_aliases for use on Linux. Sourcing this file removes the
need to quote wildcard arguments when using the command line tools.
For more details, see the Installation and Configuration Guide.

2.3 Database Upgrade

There are data model and other database changes at this release, including:
l Changes to the shape of the system layer -> feature association table.
l Addition of a system table for progress reporting during feature mutation.
l Changes to bookmark and query data to remove system-generated text.
l Migration of layer definitions to a new internal format.
l Addition of fields to the replication table_set object.
A database upgrade is provided to make these changes. You must upgrade your database using the
myw_db command line tool.
For more details, see Upgrading on page 16.

Page 5
 3: Server

3: Server
The following server-side changes have been made at this release.

3.1 Feature Tables now Creatable via GUI

It is now possible to create and mutate feature table structure from the Features configuration page.
(In previous releases, such changes could only be made by loading .def files using the myw_db
command.)
In addition, index tables are now rebuilt automatically regardless of table size; it is no longer necessary
to rebuild them manually after changing the configuration of a large table.
For more details, see the Installation and Configuration Guide.

3.2 Feature Definition Validation Improved

The data dictionary now performs additional validation checks before applying a feature definition, for
example to trap attempts to reference a non-existent field in a title expression or search. This reduces
the risk of a badly-formed feature definition leaving the myWorld database in an inconsistent state
(for example, with broken triggers or missing DD entries).

3.3 Layer-Feature Association now via Geometry Field

The Layers configuration page now allows you to add features to a layer on a per-geometry field basis.
This allows you to define drawing style and selection properties appropriately for features with
multiple geometries. For example, a feature type building could render its geographic location using a
point style and floorplan_boundary using a polygon style.
The database upgrade automatically populates all existing associations with the name of the primary
geometry (the_geom). If you are using secondary geometries as part of your internals model (or for
other purposes) you may need to update your layer definitions manually after the upgrade has run.
For more details, see Upgrading on page 16.

3.4 New Option in Vector Layers Definition

It is now possible to declare a vector layer as static, indicating that the system need not re-check the
database on each redraw. This can significantly improve drawing speed on high-latency connections.
Typical candidates for declaration as static are vectors layers presenting network data and objects
replicated from enterprise systems.
For more details, see the Layers config page.

Page 6
3: Server

3.5 New Options in LDAP Authentication

The LDAP authorisation engine supports new configuration parameters server_type and allow_
referrals which control details of the binding process.
For more details, see the Installation and Configuration Guide.

3.6 Other Changes

Other changes at this release are:
1. Query definitions no longer require a "Query: " prefix in their search description. (The search
results GUI now includes an icon to indicate result type). The database upgrade removes the
prefix, if present, from any existing queries.
2. Replication includes a new option to limit the levels of each tile file that are included in an
extract. For more details, see the Table Sets tab of the Replicas configuration page.

Page 7
 4: Client

4: Client
The following changes have been made to the JavaScript application at this release.

4.1 Search GUI Enhanced

The search user interface has been modified and extended as follows:
1. Search suggestions are now grouped according to their source (myWorld, Google or external).
These groups are updated asynchronously rather than waiting for all data sources to return
their suggestions before displaying anything. This improves usability when an external data
source has high latency or becomes unresponsive.
2. Each suggestion is now prefixed by an icon indicating its type (bookmark, query, object, place,
...). This replaces textual prefixes such as Bookmark: and Query:.
3. For query suggestions, the in window, in selection and all options are now selectable via a
separate sub-menu (rather than being presented as three separate suggestions). This helps
remove duplication from the suggestions list.
4. Object suggestions are preceded by a new entry Objects matching: <search term>. Selecting
this suggestion sends the full set of matches to the results tab.
5. The size of the object list is now limited to 10 suggestions (rather than 20 as in previous
releases). If there are further matches, the system displays an extra suggestion '...'. Clicking this
item sends the full set of matches to the results tab.
6. Search text is no longer modified when a suggestion is selected. This facilitates cycling and
refinement of search terms.
7. A search term consisting of a comma-separated pair of numbers is now interpreted as a
request to pan the map centre to that lat / long location.
For more details, see the User Guide.

4.2 Toolbar Handles Overflow

If screen space is limited, the rightmost entries of the main toolbar now 'overflow' into a pulldown
menu. This ensures that the myWorld Home Page button (Ubisense logo) is always accessible on
tablet devices.

4.3 Vector Rendering Performance Improved

The vector layer rendering code has been reformulated to reduce server calls. This can improve
performance on high latency connections.

Page 8
4: Client

Rendering performance can be further enhanced by setting the static flag in vector layer definitions,
where appropriate (see Server on page 6).

Page 9
 5: Configuration Pages

5: Configuration Pages
The following changes have been made to the configuration pages at this release.

5.1 Features Page Extended

The Features page has been extended to support creation and mutation feature table structure.
Changes include:
1. New buttons Add and Delete on the main page.
2. A new tab Geometry Fields on the details page.
3. New buttons Add, Remove and Reorder on the Stored Fields and Calculated Fields tabs.
4. All properties on the Stored Fields and Calculated Fields tabs are now editable.
In addition, the requirement to rebuild indexes manually using the myw_db command when changing
a large table has been removed. Indexes are now always updated as part of the configuration
operation.
For more information, see the Installation and Configuration Guide.

5.2 Layers Page Enhanced

The Layers page has been enhanced as follows:
1. The Features tab now shows a separate row for each geometry of the feature type. This permits
the configuration of appropriate selection parameters and drawing styles for secondary
geometries (see Server on page 6).
2. Layer type myworld_vector has a new property Static. This can be used to enable client-side
caching during rendering (see Server on page 6).
3. Layer types myworld_tiles, kml and wms have a new property Attribution. This can be used to
define an attribution string for display on the map.
4. The Category field is now an editable pulldown list (rather than free text).
For more details, see the Installation and Configuration Guide.

5.3 Replicas Page

The Replication page has been enhanced as follows:
1. The Tiles tab of a Table Set definition page now includes options to limit the zoom levels extracted
from each tile file. By default, all zoom levels are extracted.
For more details, see the Installation and Configuration Guide.

Page 10
5: Configuration Pages

5.4 Other Changes

Other configuration page changes at this release include:
1. Lists can now be sorted (by clicking in column headings).
2. Items that reference another definition (for example, application names in a role definition) now
support direct navigation to that definition via a popup View link.

Page 11
 6: Tools

6: Tools
The following changes have been made to the command line tools.

6.1 Native App Tools Moved to Core

The Native App command line tools myw_convert and myw_index, used for preparing SQLite
databases, have been moved to core:
1. myw_convert is replaced by a new option convert in the myw_db command.
2. myw_index is retained in its previous form but is now located in <myworld>/Tools (rather than
<nativeapp>/Tools).
For more details, see the Installation and Configuration Guide.

6.2 myw_db Command Enhanced

The following changes have been made to the myw_db command at this release:
1. There is a new operation convert that copies the database to SQLite format. This is used when
preparing databases for use with the NativeApps (see above).
2. Operation load no longer requires the postgres user to have read access to the input file when
using the --direct flag. In addition, --direct loads can now be run in parallel.
3. Operation list supports a new layout csv. This can be useful for generating simple database reports.
For more details, see --help.

6.3 myw_tilestore Command Enhanced

The following changes have been made to the myw_tilestore command at this release:
1. Operation load supports a new option --levels that allows you to limit the tile zoom levels that are
imported from the source data.
For more details, see --help.

Page 12
 7: Smallworld ETL

7: Smallworld ETL
The following changes have been made to the myWorld ETL for Smallworld component at this release.
1. The Feature Export Tool item Format now includes separate entries for CSV, well known text
(WKT), and extended well known text (EWKT) formats.
2. The feature export engine now culls duplicate co-ordinates at sector breaks in large geometries
and ensures that hole boundaries are correctly oriented.
3. The tile export engine now detects and culls tiles that are empty by virtue of being inside an
area that has no fill style.
For more details, see the ETL for Smallworld Guide.

Page 13
 8: JavaScript API

8: JavaScript API
The following changes have been made to the JavaScript customization API at this release.

8.1 Minification Process Changed

The JavaScript minification process has been modified as follows:
1. Leaflet and other 3rd party libraries are now shipped pre-minified in a single file myWorld-
lib.min.js.
2. myWorld Core code now minifies to a second file myWorld-client.min.js. The minification utility
has been renamed to reflect that change.
3. Custom code and other modules now minify to a third file myWorld-modules.min.js. A new
utility minify_modules is supplied to assist with this process (see modules/custom/utils). Note
that you may need to edit the JavaScript control file before running this utility.
For more details, see the Customization Guide.

8.2 Event Feature Collection Modified Extended

Application event featureCollection-modified now supports optional parameters indicating the
nature of the change:
l changeType: One of insert, update or delete.
l feature: Feature which has been modified.
This information, if provided, is used by the system to optimize display updates.
For more details, see the myWorld JS API documentation.

8.3 Feature Retrieval Functions Modified

The following Database functions are modified at this release:
1. getFeatures(): The default of value for parameter displayValues is now false
2. getFeaturesByValue(): Results returned by the function no longer include the displayValues
aspect. Use getFeatures() with displayValues=true if display values are required.
You may need to update your custom code for these changes.

Page 14
 9: Documentation

9: Documentation
The documentation set has been updated to reflect the new features described above. In addition:
l The User Guide has been revised and updated.
l The main guides are now shipped in HTML format (rather than in PDF, as in previous releases).

Page 15
 10: Upgrading

10: Upgrading
This section provides an overview of the upgrade process for this release.

10.1 Upgrading your myWorld Server

Upgrading your myWorld server installation involves:
1. Installing the myWorld software.
2. Porting your customizations.
3. Upgrading your database.
These steps are described in more detail in the Installation and Configuration Guide.
To upgrade your database use:
myw_db <db_name> upgrade 270

You may need to update your server-side configuration after upgrading (see below).

10.2 Upgrading your Smallworld ETL Configuration

Upgrading your myWorld ETL for Smallworld installation involves:
1. Installing the software.
2. Updating your images.
These steps are described in detail in the ETL for Smallworld Guide.
There are no ETL post upgrade steps at this release.

10.3 Post-upgrade Activities

As described above, layer-features associations are now made at the geometry field level (rather than
the feature level). The database upgrade converts all existing associations to use the primary
geometry field (the_geom). If any of your feature types has a secondary geometry you should:
1. Review your layer definitions, checking that features are associated on the correct geometry field.
Feature associations can be viewed using the Features tab of the Layer configuration details page.
For assistance with this task, please contact Ubisense Support.

Page 16
Copyright © 2015, Ubisense Limited 2010 - 2015. All Rights Reserved. You may not reproduce
this document in whole or in part without permission in writing from Ubisense at the
following address:
Ubisense Limited
St Andrew’s House
St Andrew’s Road
Cambridge CB4 1DL
United Kingdom
Tel: +44 (0)1223 532670
Fax: +44 (0)1223 535167
E-mail: [email protected]
WWW: http://www.ubisense.net
All contents of this document are subject to change without notice and do not represent a
commitment on the part of Ubisense. Reasonable effort is made to ensure the accuracy of
the information contained in the document. However, due to on-going product
improvements and revisions, Ubisense and its subsidiaries do not warrant the accuracy of
this information and cannot accept responsibility for errors or omissions that may be
contained in this document.
Information in this document is provided in connection with Ubisense products. No license,
express or implied to any intellectual property rights is granted by this document.
Ubisense encourages all users of its products to procure all necessary intellectual property
licenses required to implement any concepts or applications and does not condone or
encourage any intellectual property infringement and disclaims any responsibility related
thereto. These intellectual property licenses may differ from country to country and it is the
responsibility of those who develop the concepts or applications to be aware of and comply
with different national license requirements.
Windows® is a registered trademark of Microsoft Corporation in the United States and/or
other countries. The other names of actual companies and products mentioned herein are
the trademarks of their respective owners.