[Mapbender-commits] r6844 - trunk/documents/presentations/FOSS4G2010/hands_on

svn_mapbender at osgeo.org svn_mapbender at osgeo.org
Mon Aug 30 14:01:53 EDT 2010


Author: astrid_emde
Date: 2010-08-30 18:01:53 +0000 (Mon, 30 Aug 2010)
New Revision: 6844

Added:
   trunk/documents/presentations/FOSS4G2010/hands_on/conf.py
   trunk/documents/presentations/FOSS4G2010/hands_on/config
Modified:
   trunk/documents/presentations/FOSS4G2010/hands_on/Mapbender_hands_on_FOSS4G_20010.pdf
   trunk/documents/presentations/FOSS4G2010/hands_on/mapbender_quickstart.rst
Log:
printable version of hands-on workshop material for FOSS4G 

Modified: trunk/documents/presentations/FOSS4G2010/hands_on/Mapbender_hands_on_FOSS4G_20010.pdf
===================================================================
(Binary files differ)

Added: trunk/documents/presentations/FOSS4G2010/hands_on/conf.py
===================================================================
--- trunk/documents/presentations/FOSS4G2010/hands_on/conf.py	                        (rev 0)
+++ trunk/documents/presentations/FOSS4G2010/hands_on/conf.py	2010-08-30 18:01:53 UTC (rev 6844)
@@ -0,0 +1,307 @@
+# -*- coding: utf-8 -*-
+#
+# Introduction to Mapbender documentation build configuration file, created by
+# sphinx-quickstart on Thu Aug 26 22:44:08 2010.
+#
+# This file is execfile()d with the current directory set to its containing dir.
+#
+# Note that not all possible configuration values are present in this
+# autogenerated file.
+#
+# All configuration values have a default; values that are commented out
+# serve to show the default.
+
+import sys, os
+
+# If extensions (or modules to document with autodoc) are in another directory,
+# add these directories to sys.path here. If the directory is relative to the
+# documentation root, use os.path.abspath to make it absolute, like shown here.
+#sys.path.append(os.path.abspath('.'))
+
+# -- General configuration -----------------------------------------------------
+
+# If your documentation needs a minimal Sphinx version, state it here.
+#needs_sphinx = '1.0'
+
+# Add any Sphinx extension module names here, as strings. They can be extensions
+# coming with Sphinx (named 'sphinx.ext.*') or your custom ones.
+extensions = ['sphinx.ext.autodoc','rst2pdf.pdfbuilder','sphinx.ext.intersphinx']
+
+# Add any paths that contain templates here, relative to this directory.
+#templates_path = ['_templates']
+
+# The suffix of source filenames.
+source_suffix = '.rst'
+
+# The encoding of source files.
+#source_encoding = 'utf-8-sig'
+
+# The master toctree document.
+master_doc = 'mapbender_quickstart'
+
+# General information about the project.
+project = u'Introduction to Mapbender'
+copyright = u'2010, Astrid Emde'
+
+# The version info for the project you're documenting, acts as replacement for
+# |version| and |release|, also used in various other places throughout the
+# built documents.
+#
+# The short X.Y version.
+version = '1.0'
+# The full version, including alpha/beta/rc tags.
+release = '1.0'
+
+# The language for content autogenerated by Sphinx. Refer to documentation
+# for a list of supported languages.
+#language = None
+
+# There are two options for replacing |today|: either, you set today to some
+# non-false value, then it is used:
+#today = ''
+# Else, today_fmt is used as the format for a strftime call.
+#today_fmt = '%B %d, %Y'
+
+# List of patterns, relative to source directory, that match files and
+# directories to ignore when looking for source files.
+exclude_patterns = ['_build']
+
+# The reST default role (used for this markup: `text`) to use for all documents.
+#default_role = None
+
+# If true, '()' will be appended to :func: etc. cross-reference text.
+#add_function_parentheses = True
+
+# If true, the current module name will be prepended to all description
+# unit titles (such as .. function::).
+#add_module_names = True
+
+# If true, sectionauthor and moduleauthor directives will be shown in the
+# output. They are ignored by default.
+#show_authors = False
+
+# The name of the Pygments (syntax highlighting) style to use.
+pygments_style = 'sphinx'
+
+# A list of ignored prefixes for module index sorting.
+#modindex_common_prefix = []
+
+
+# -- Options for HTML output ---------------------------------------------------
+
+# The theme to use for HTML and HTML Help pages.  See the documentation for
+# a list of builtin themes. # vorher default
+html_theme = 'default'#'mapbender'
+
+# Theme options are theme-specific and customize the look and feel of a theme
+# further.  For a list of options available for each theme, see the
+# documentation.
+#html_theme_options = {}
+
+# Add any paths that contain custom themes here, relative to this directory.
+html_theme_path = ['./themes']
+
+# The name for this set of Sphinx documents.  If None, it defaults to
+# "<project> v<release> documentation".
+html_title = 'Mapbender Workshop FOSS4G 2010 Barcelona'
+
+# A shorter title for the navigation bar.  Default is the same as html_title.
+#html_short_title = 'Mapbender Workshop'
+
+# The name of an image file (relative to this directory) to place at the top
+# of the sidebar.
+html_logo = './images/project_logos/logo-Mapbender.png'
+
+# The name of an image file (within the static path) to use as favicon of the
+# docs.  This file should be a Windows icon file (.ico) being 16x16 or 32x32
+# pixels large.
+html_favicon = './images/favicon.ico'
+
+# Add any paths that contain custom static files (such as style sheets) here,
+# relative to this directory. They are copied after the builtin static files,
+# so a file named "default.css" will overwrite the builtin "default.css".
+html_static_path = ['_static']
+
+# If not '', a 'Last updated on:' timestamp is inserted at every page bottom,
+# using the given strftime format.
+html_last_updated_fmt = '%b %d, %Y'
+
+# If true, SmartyPants will be used to convert quotes and dashes to
+# typographically correct entities.
+#html_use_smartypants = True
+
+# Custom sidebar templates, maps document names to template names.
+#html_sidebars = {}
+
+# Additional templates that should be rendered to pages, maps page names to
+# template names.
+#html_additional_pages = {}
+
+# If false, no module index is generated.
+#html_domain_indices = True
+
+# If false, no index is generated.
+#html_use_index = True
+
+# If true, the index is split into individual pages for each letter.
+#html_split_index = False
+
+# If true, links to the reST sources are added to the pages.
+#html_show_sourcelink = True
+
+# If true, "Created using Sphinx" is shown in the HTML footer. Default is True.
+html_show_sphinx = True
+
+# If true, "(C) Copyright ..." is shown in the HTML footer. Default is True.
+html_show_copyright = True
+
+# If true, an OpenSearch description file will be output, and all pages will
+# contain a <link> tag referring to it.  The value of this option must be the
+# base URL from which the finished HTML is served.
+#html_use_opensearch = ''
+
+# If nonempty, this is the file name suffix for HTML files (e.g. ".xhtml").
+#html_file_suffix = ''
+
+# Output file base name for HTML help builder.
+htmlhelp_basename = 'IntroductiontoMapbenderdoc'
+
+
+# -- Options for LaTeX output --------------------------------------------------
+
+# The paper size ('letter' or 'a4').
+latex_paper_size = 'a4'
+
+# The font size ('10pt', '11pt' or '12pt').
+#latex_font_size = '11pt'
+
+# Grouping the document tree into LaTeX files. List of tuples
+# (source start file, target name, title, author, documentclass [howto/manual]).
+latex_documents = [
+  ('index.rst', 'IntroductiontoMapbender.tex', u'Introduction to Mapbender',
+   u'Astrid Emde', 'manual'),
+]
+
+# The name of an image file (relative to this directory) to place at the top of
+# the title page.
+#latex_logo = None
+
+# For "manual" documents, if this is true, then toplevel headings are parts,
+# not chapters.
+#latex_use_parts = False
+
+# If true, show page references after internal links.
+#latex_show_pagerefs = False
+
+# If true, show URL addresses after external links.
+#latex_show_urls = False
+
+# Additional stuff for the LaTeX preamble.
+#latex_preamble = ''
+
+# Documents to append as an appendix to all manuals.
+#latex_appendices = []
+
+# If false, no module index is generated.
+#latex_domain_indices = True
+
+
+# -- Options for manual page output --------------------------------------------
+
+# One entry per manual page. List of tuples
+# (source start file, name, description, authors, manual section).
+man_pages = [
+    ('mapbender_quickstart', 'introductiontomapbender', u'Introduction to Mapbender',
+     [u'Astrid Emde'], 1)
+]
+
+
+# -- Options for PDF output --------------------------------------------------
+
+# Grouping the document tree into PDF files. List of tuples
+# (source start file, target name, title, author, options).
+#
+# If there is more than one author, separate them with \\.
+# For example: r'Guido van Rossum\\Fred L. Drake, Jr., editor'
+#
+# The options element is a dictionary that lets you override 
+# this config per-document.
+# For example, 
+# ('index', u'MyProject', u'My Project', u'Author Name', 
+#  dict(pdf_compressed = True))
+# would mean that specific document would be compressed
+# regardless of the global pdf_compressed setting.
+
+pdf_documents = [ 
+('mapbender_quickstart', u'Introduction to Mapbender', u'Introduction to Mapbender', r'Astrid Emde\\Christoph Baudson'),
+]
+
+# A comma-separated list of custom stylesheets. Example:
+pdf_stylesheets = ['sphinx','kerning','a4']
+
+# Create a compressed PDF
+# Use True/False or 1/0
+# Example: compressed=True
+#pdf_compressed = False
+
+# A colon-separated list of folders to search for fonts. Example:
+# pdf_font_path = ['/usr/share/fonts', '/usr/share/texmf-dist/fonts/']
+
+# Language to be used for hyphenation support
+pdf_language = "en_US"
+
+# Mode for literal blocks wider than the frame. Can be
+# overflow, shrink or truncate
+#pdf_fit_mode = "shrink"
+
+# Section level that forces a break page.
+# For example: 1 means top-level sections start in a new page
+# 0 means disabled
+#pdf_break_level = 0
+
+# When a section starts in a new page, force it to be 'even', 'odd',
+# or just use 'any'
+#pdf_breakside = 'any'
+
+# Insert footnotes where they are defined instead of 
+# at the end.
+#pdf_inline_footnotes = True
+
+# verbosity level. 0 1 or 2
+#pdf_verbosity = 0
+
+# If false, no index is generated.
+pdf_use_index = True
+
+# If false, no modindex is generated.
+#pdf_use_modindex = True
+
+# If false, no coverpage is generated.
+#pdf_use_coverpage = True
+
+# Name of the cover page template to use
+#pdf_cover_template = 'sphinxcover.tmpl'
+
+# Documents to append as an appendix to all manuals.    
+#pdf_appendices = []
+
+# Enable experimental feature to split table cells. Use it
+# if you get "DelayedTable too big" errors
+#pdf_splittables = False
+
+# Set the default DPI for images
+pdf_default_dpi = 1200
+
+# Enable rst2pdf extension modules (default is only vectorpdf)
+# you need vectorpdf if you want to use sphinx's graphviz support
+#pdf_extensions = ['vectorpdf']
+
+# Page template name for "regular" pages
+pdf_page_template = 'cutePage'
+
+# Show Table Of Contents at the beginning?
+#pdf_use_toc = True
+
+# How many levels deep should the table of contents be?
+pdf_toc_depth = 9999
+

Added: trunk/documents/presentations/FOSS4G2010/hands_on/config
===================================================================
--- trunk/documents/presentations/FOSS4G2010/hands_on/config	                        (rev 0)
+++ trunk/documents/presentations/FOSS4G2010/hands_on/config	2010-08-30 18:01:53 UTC (rev 6844)
@@ -0,0 +1,24 @@
+# This is an example config file. Modify and place in ~/.rst2pdf/config
+[general]
+# A comma-separated list of custom stylesheets. Example:
+# stylesheets="fruity.json,a4paper.json,verasans.json"
+stylesheets=""
+# Create a compressed PDF
+# Use true/false (lower case) or 1/0
+# Example: compressed=true
+compressed=false
+# A colon-separated list of folders to search for fonts. Example:
+# font_path="/usr/share/fonts:/usr/share/texmf-dist/fonts/"
+font_path=""
+# Language to be used for hyphenation support
+language="en_US"
+# Default page header and footer
+header='Mapbender Workshop'
+footer='FOSS4G 2010 Barcelona'
+# What to do if a literal block is too large. Can be
+# shrink/truncate/overflow
+fit_mode="shrink"
+# What is the maximum level of heading that starts in a new page.
+# 0 means no level starts in a new page.
+break_level=0
+

Modified: trunk/documents/presentations/FOSS4G2010/hands_on/mapbender_quickstart.rst
===================================================================
--- trunk/documents/presentations/FOSS4G2010/hands_on/mapbender_quickstart.rst	2010-08-30 18:00:29 UTC (rev 6843)
+++ trunk/documents/presentations/FOSS4G2010/hands_on/mapbender_quickstart.rst	2010-08-30 18:01:53 UTC (rev 6844)
@@ -71,11 +71,11 @@
 Geoportal Framework
 ===================
 
-`Mapbender <http://www.mapbender.org>`_ is a graduated OSGeo project. It is a web based geoportal framework to publish, register, view, navigate, monitor and grant secure access to spatial data infrastructure services.
+`Mapbender <http://www.mapbender.org>`_ is a graduated OSGeo project. It is a web based geoportal framework to publish, register, view, navigate, monitor and grant secure access to spatial data services.
 
 Mapbender is the tip of the iceberg, a meta layer of software providing access to SDI components adhering to international standards. Mapbender allows users to easily create customised browser clients from a wide range of widgets (without any/with minimal) programming required. Widgets integrate with server functionality to provide advanced functionality like security proxying, digitizing, auto snapping and more.
 
-Mapbender management applications are straight forward and easy to use providing highly focused functionality for the operation of large scale distributed SDI components. It is the tool of choice for SDI administrators who need to maintain, categorize and monitor map and feature services. Mapbender grants access to individuals, groups and manages machine to machine access. Adherence to standardized services, such as OGC WMS and transactional WFS allows to take advantage of interoperable services from a multitude of server platforms.
+Mapbender administration applications are straight forward and easy to use providing highly focused functionality for the operation of large scale distributed SDI components. It is the tool of choice for SDI administrators who need to maintain, categorize and monitor map and feature services. Mapbender grants access to individuals, groups and manages machine to machine access. Adherence to standardized services, such as OGC WMS and transactional WFS allows to take advantage of interoperable services from a multitude of server platforms.
 
 The Mapbender client side is based on HTML and JavaScript using the jQuery and jQuery UI libraries which provide lots of browser widgets. The server side is implemented in PHP and PostgreSQL/PostGIS. 
 
@@ -150,9 +150,9 @@
   * load a Web Map Service (OGC WMS)
   * configure WMS
   * create an individual application
+  * create a user and a group and assign applications to them
   * load a WFS
   * configure feature type and create an application with WFS search and digitize functionality
-  * create a user and a group and assign applications to them
 
 .. raw:: pdf
 
@@ -180,7 +180,7 @@
   .. image:: images/screenshots/800x600/mapbender_welcome.png
      :scale: 80
 
-After successful login you are directed to the *application overview*.
+After a successful login you are directed to the *application overview*.
 
 
 .. raw:: pdf
@@ -203,20 +203,23 @@
 
 The applications are listed in *categories*. Later you can define your own category and add your applications to the category you want.
 
+.. raw:: pdf
 
+    PageBreak 
+
 Administration applications
 ===========================
 
 *Administration applications* allow for example to load services, create user, to set up new applications. 
 
-Each *administration application* provides different functionality. Later with your application your can set up your own *administration applications* with the functionality you would like to provide.
+Each *administration application* provides different functionality. Later with your application you can set up your own *administration applications* with the functionality you would like to provide.
 
 After installation user *root* has access to
    * admin2_en - WMS, application, user/group handling
    * admin_en_services - focus on WFS and metadata handling and owsproxy    
    * admin1 - template with all administration elements 
 
-The following image shows admin2_en. At the left side you can see the menu with the possibilities which this appilcation offers.
+The following image shows admin2_en. At the left side you can see the menu with the possibilities which this application offers.
 
   .. image:: images/screenshots/800x600/mapbender_admin2_en.png
      :scale: 80
@@ -281,12 +284,12 @@
 
 Copy or rename an application
 =============================
-You also can create a new application by copying an existing application. Go to *Application Management --> Rename/copy application*, choose the application you want to copy and define a name for the new application. This functionality not only copies the application, it also copies the Services of the application and the user/groups (optional). That means that the new application already has map services and the user and groups which have access to the copied application will have access to the new application too.
+You also can create a new application by copying an existing application. Go to *Application Management --> Rename/copy application*, choose the application you want to copy and define a name for the new application. This functionality not only copies the application, it also copies the services of the application and the user/groups (optional). That means that the new application already has map services and the user and groups which have access to the copied application will have access to the new application too.
 
 
 Delete an application
 =====================
-You can delete an application with *Application Management --> Delete application*. Only the applications is deleted, not the services which were part of the application. 
+You can delete an application with *Application Management --> Delete application*. Only the application is deleted, not the services which were part of the application. 
 You are not allowed to delete applications which also belong to other users.
 
 Export an application
@@ -307,14 +310,23 @@
 ========================
 You can load OGC Web Map Services (WMS) to your application.
 
-A WMS gives back an XML-file when the when getCapabilities is requested. This file is parsed by Mapbender and Mapbender gets all the necessary information about the service from this XML
+A WMS returns an XML-file when the getCapabilities document is requested. This file is parsed by Mapbender and Mapbender gets all the necessary information about the service from this XML
 
-.. tip:: You should first check the getCapabilities-document in your browser before you try to load it with Mapbender
+.. tip:: You should first check the getCapabilities document in your browser before you try to load it with Mapbender
 
 #. Go to *admin2_en* and choose *WMS Management --> Load WMS*. Choose the application which shall contain the WMS. Link to the WMS getCapabilities URL in the text field and choose **Load**
 
-#. Here are some example WMS which you can use to load to your appliction
 
+**Here are some example WMS which you can load to your application**:
+
+Cadastre of spain
+
+http://ovc.catastro.meh.es/Cartografia/WMS/ServidorWMS.aspx?VERSION=1.1.1&REQUEST=GetCapabilities&SERVICE=WMS
+
+Geoportal Barcelona (Geoportalbcn)
+
+http://www.bcn.cat/geoportal/es/geoserveis.html
+
 Demis World Map 
 
 http://www2.demis.nl/wms/wms.asp?wms=WorldMap&VERSION=1.1.1&REQUEST=GetCapabilities&SERVICE=WMS
@@ -336,9 +348,9 @@
 
 
 
-You can load more than one WMS in an application. Choose *WMS applications settings* to change the order of the WMS or remove a WMS from your application.
+You can load more than one WMS in an application. Choose *WMS application settings* to change the order of the WMS or remove a WMS from your application.
 
-The WMS with index 0 is used for the overview map. This WMS also defines the EPSG and start extent of the map on start of the application. 
+The WMS with index 0 defines the default coordinate reference system and the extent of the map.
 
 
 .. tip:: Create a container application and upload every WMS just once to this container application. When you update the WMS the possible changes will appear in all applications that contain this WMS. You easily can copy a WMS from one to another application with the menu entry *Link WMS to application*.
@@ -350,13 +362,13 @@
 
 Configure WMS
 =============
-After upload of a WMS you can configure the WMS for you specific application. Maybe you don't want to provide all layer or you want to change the order or titles of the layer or disable the feature info or change the maxscale for a layer.
+After upload of a WMS you can configure the WMS for your specific application. Maybe you don't want to provide all layers or you want to change the order or titles of the layer or disable the feature info or change the maxscale for a layer.
 
 .. image:: images/screenshots/800x600/mapbender_wms_application_settings.png
   :scale: 80
 
 * on/off - enable/disable a layer for this individual application
-* sel - selectable in geodataexplorer
+* sel - selectable in geodata explorer
 * sel_default - layer is active when the application starts
 * info / info default - layer provides feature info requests, info default activates the feature info functionality
 * minscale / maxscale - the scale range in which the layer should be displayed, 0 means no scale limitation
@@ -371,24 +383,24 @@
 **************************
 Configure your application
 **************************
-Now you should get an idea of how easy it is to change a Mapbender application without changes in the code. 
+Now you should get an idea how easy it is to change a Mapbender application without changes in the code. 
 
-When you select an element for example **mapframe1** by click on the radiobutton you see that the element has a lot of attributes. These attributes are html-attributes. By defining a Mapbender element you define a html-element. On start of your application Mapbender will put all elements together to a html-page.
+When you select an element for example **mapframe1** by click on the radiobutton you see that the element has a lot of attributes. These attributes are HTML attributes. By defining a Mapbender element you define an HTML element. On start of your application Mapbender will insert all elements into to an HTML page.
 
 	* id - unique name for the element
 	* on/off - enable/disable an element
 	* title - name of the element which will be displayed as tooltip
-	* HTML-TAG/CLOSE-TAG - type of html-element to create for example div, img
-	* top, left - define the position of the elment
+	* HTML-TAG/CLOSE-TAG - type of HTML element to create for example div, img
+	* top, left - define the position of the element (for fixed layouts)
 	* width/height - define the size of the element
 
-Some elements have element variables which allows the user to set parameter for an element. The element variables can be Java-Script variables, php-variables, references to css-files or css text definitions. 
+Some elements have element variables which allows the user to set parameters for an element. The element variables can be JavaScript variables, PHP variables, references to CSS files or CSS text definitions. 
 
 Examples for element variables:
 
 * the copyright element has an element variable to set the copyright text
 * the overview element (overview map) has an element variable to define which WMS is used for the overview map
-* treeGDE (geodataexplorer) has element variables to define the style of the geodataexplorer
+* treeGDE (geodata explorer) has element variables to define the style of the geodata explorer
 
 
 Try it yourself
@@ -453,7 +465,7 @@
 **************
 WFS management
 **************
-Mapbender supports OGC Web Feature Service WFS 1.0.0 and 1.1.0 (not stable). A WFS can be used in Mapbender applications for different functionalities:
+Mapbender supports OGC Web Feature Service WFS 1.0.0 and 1.1.0. A WFS can be used in Mapbender applications for different functionalities:
 
 * search
 * spatial search
@@ -465,7 +477,7 @@
 
 Afterwards you have to grant access to your new feature type configuration to an application before you can use it.
 
-If you want to set up an application with WFS digitizing you need a WFS which support transactions (WFS-T). You can for example use the software GeoServer or deegree to set up a WFS-T.
+If you want to set up an application with WFS digitizing you need a WFS which supports transactions (WFS-T). You can for example use the software GeoServer or deegree to set up a WFS-T.
 
 .. raw:: pdf
 
@@ -475,7 +487,7 @@
 ============================
 The modules to configure WFS are integrated in the administration application **admin_de_services**.
 
-.. tip:: You should first check the WFS getCapabilities-document in your browser before you try to load it in Mapbender.
+.. tip:: You should first check the WFS getCapabilities document in your browser before you try to load it in Mapbender.
 
 #. Go to *admin_en_services* and choose *WFS Management --> Load WFS*. Choose any application in the application list. Link to the WFS getCapabilities URL in the text field and hit **Load**.
 
@@ -491,7 +503,7 @@
 
     PageBreak
 
-Create a WFS feature types configuration
+Create a WFS feature type configuration
 ========================================
 The next step is to set up a configuration for a feature type. After the configuration and authorization of an application, the configuration can be used in your applications.
 
@@ -548,9 +560,9 @@
 To enable your feature type configuration in an application go to *admin_en_services -> Edit application elements* choose your application and go to the element gazetteerWFS. The elements has an element variable *wfsConfIdString*. Here you can list you WFS configuraton ids (comma separated).
 
 .. image:: images/screenshots/800x600/mapbender_wfsConfIdString.png
-     :scale: 100 
+     :scale: 80 
 
-Have a look how the search could appear in an pplication
+Have a look how the search could appear in an application. In this example there is a search frame at the left where you can search for Mapbender User. You can run a spatial search and define a region to search or you can do an alphanumeric search. The search results are displayed in a result table. On click on a result entry Mapbender zooms to the location and detail information is displayed.
 
 .. image:: images/screenshots/800x600/mapbender_WFS_search.png
      :scale: 100
@@ -562,11 +574,13 @@
     PageBreak
 
 Set up a WFS digitize functionality
-==============================================
-The easiest way to get an application that supports WFS digitizing is to copy gui_digitize. Now you only have to connect a WMS layer with your feature type configuration. This is done in *WMS application settings* with the button *set WFS* in the layer-list. Hit the button an select your configuration id.
+===================================
+The easiest way to get an application that supports WFS digitizing is to copy gui_digitize. Now you only have to connect a WMS layer with your feature type configuration. This is done in *WMS application settings* with the button *set WFS* in the layer-list. Hit the button and select your configuration id.
 
 .. tip::Make sure that the WMS layer which is connected with the WFS configuration id supports feature info. This is how Mapbender decides whether to send a WFS getFeature request or not.
 
+Now you can search with the spatial search at the right for existing objects which are displayed in a *seach result* frame. The objects can be updated (move object, add basepoint, edit attributes, split line, continue line, merge polygons...). You also can create new objects.
+
 .. image:: images/screenshots/800x600/mapbender_gui_digitize.png
      :scale: 80 
 



More information about the Mapbender_commits mailing list