Neapoljs comes along with a wide choice of functions which are individually configurable and can be assigned to user groups. This means, that along with the templates concept, every user can basically have its own application, which can dramatically differ from others in look & feel and functionality. The functionality of Neapoljs includes:

• Neapoljs Toolbar: Functions which are accessed using the toolbar.

• Neapoljs Elements: Other page elements beside the toolbar.

• Search Options: Definition of search criteria in many different ways.

• Maps & Layers: Definition on how maps & layers can be accessed.

• Information Query: Which information can be queried on each map.

• Printing: Using HTML and PDF templates.

See the movie about  Neapoljs Projects to see how to create content and assign functions.

Neapoljs Toolbar

The Neapoljs toolbar can be positioned and configured in any way you like. The available elements, subdivided by their main functionality, are the following:

Navigation

The navigation comprises zoom in (click or drag a zoom window), zoom out, pan (drag the map around), back and forth to any state, home (zoom to initial view) and zoom using an overview map:

In addition, following navigation elements are available:

Zoom slider for fixed zoom levels:

Zoom defining a specific map width:

Information and printing

Following tools for information query and printing are available:

• Information query: Query map objects. One can configure which layers and attributes can be queried in a map and the way they are displayed using specific templates. See more details below.

• Measurement of distance and area.

• Printing via HTML or PDF (see specific printing page).

• Online Help.

• Feedback mail to administrator.

Redlining
 

The functionality called "Redlining" allows one to digitize temporary drawings, optionally using points, lines, polygons or text. Drawings can optionally be exported to GPS formats or to KML (Google Earth).

Neapoljs Elements

In addition to the toolbar, there are following elements one can add:

• Embedded Info: The results of information queries can be embedded in the main page (optionally instead of "mouse over" or "pop-up". See as well below).

• Embedded Legends: The map legends can be embedded in the main page.

• Language Selector: The language can be chosen inside the application.

• Quick Help: Dynamic help for the toolbar.

• Custom Text: Any number of custom text objects.

• Custom Images: Any number of custom image objects.

Search Options

Neapoljs offers different ways to search for geographical locations which covers almost every case:

• One parameter search: i.e. for street name or parcel number, definable as drop down list, alphabetical list or suggestion list.

• Two or three parameters search: same as above with two or three parameters, i.e. city and street, definable as drop down lists or suggestion lists.

• Address search: search for addresses on street and address layers.

• POI search: search for Points of Interest using categories and names.

• Query by Example: QBE are basically predefined SQL queries.

Examples:

Example of a Query by Example on linked tables (parcels and owners):

Maps & Layers

Maps & Layers controls can be defined in many different ways, where "layers" can be single layers or layer groups:

• Single maps only, optionally categorized

• One background map and single layers, optionally categorized

• Several background maps and single layers, optionally categorized

• Combined maps and layers

Samples:

Sample with Tree:

Information Query

Information query can be implemented in three different ways:

• Mouse over: Dynamically displayed information on point objects when moving the mouse over the object.
• Embedded: Information displayed embedded in the main page
• Pop-up: Information shown in a separate pop-up Window

Using the content management, the administrator can define which attributes shall be queried on which layer. In addition, for each attribute, aliases can be defined.

Sample of mouse-over info:

Linked Tables

Tables can as well be linked to be able to search or query on relational tables (such as on a properties layer linked to an owners table, which is normally an n:m relationship).

Example: