Principles LORIKDBCARTOGRAPHER

LorikDBManager creates a cartographic database from existing GIS data sources.

This cartographic database keeps a link with the original data in order to make easier the update of produced maps.

It takes into account the enhancements and modifications brought to the GIS sources.

There are four main steps:

All these steps are available for each sheet. It means that you do not need to create the whole database for starting the publication.

Each sheet has its own life cycle.

 

LorikDBManager divides the geographical area to map into working units - called sheet - using a grid. The grid is computed for the entire workplane in order to create regular sheet. All sheets have the same width, the same height and are calculated using the x and y axis.

Each possible sheet is identified by a line and column number. They are computed in order to cover the entire workplane.

You can then create a sheet from this grid when you need to create the mapping data. Each sheet has also a name in order to be easily identified. You only have to create a sheet when you need to create the corresponding mapping data.

A sheet is a working unit. It is used for transferring data from GIS data  to the cartographic database. They are not bound to correspond to the final layout. Sheets creation is done when the project is set up, but it is possible to add, remove or rename the sheets.

When you transfer a sheet, two geometries are saved: one using the LorikSoftware format and an associated one (DIGEST).

LorikSoftware format is used to display and to edit data with LorikDBCartographer and for exporting layouts or digital files. For instance linear objects are stored as Bezier curves.

The "DIGEST" format is used to displayed data with other programs which are able to access a database. All attributes are saved in a set of tables which propose a structured organization of data and their attributes. For instance a table stores the curve types list, another one the text types list, etc. Objects are stored using the following scheme:

Extended attributes are also directly managed inside the database.

The DIGEST format can also be used to generate new database at another scale.

Creation / 1st publication

Once transferred the sheet can be edited by an operator using the LorikDBCartographer program. Only created sheets can be edited.

Once the edition is completed, the operator can validate the sheet, i.e. the sheet is ready for the publication.

Layout and paper publishing are done with the LorikPublisher program. Maps can be created one by one or using a batch processing.

LorikPublisher uses extractions to create the map, not the sheets. It means the layout can include a part of several working sheet.

The map can be edited in order to finalize margin information or bring local enhancement to the cartographic content.

You can also use the LorikDigital to export your data for Internet or mobile applications.

Once created the export project (paper or digital) is saved as a file apart. You can create an archive in order to be able to publish the map again even if the database has been modified.

Update

When the original sources have been modified (addition, modification or deletion) the administrator of the project can decide to transfer the new data to the database, sheet per sheet.

At this stage, when an operator opens a sheet he can see on the left-hand part the current map (the one which has been previously validated) et the new map on the right hand part.

All differences (addition, modification or deletion) are highlighted in the right-hand part.

The user then uses a set of tool to update the current map in order to fit the content to the new information.

Once this job is done, the manager can validate the map again.

Further publications

Once the cartographic database is validated, the operator just opens the existing map with LorikPublisher (or LorikDigital) and generates a new export (and a new archive).