Special software
This part contains special software
This part contains special software
The Diversity GIS Editor is a tool to create, visualize, edit and archive samples within a geographical environment. It may be used as a stand-alone application or as a component of the Diversity Workbench by other applications, e.g. DiversityCollection or DiversitySamplingPlots.
In combination with a background map, equipped with world coordinates, collections of Microsoft SQL Geometry Objects (points, lines and areas) may be displayed and edited in their geographical context. The screen and world coordinates of the objects will be calculated and shown in the status line. Color, thickness and transparency of the elements can be adjusted. The working area which keeps the maps and objects may be shifted or zoomed.
The background map could either be loaded from a storage device or created with an online map server tool provided by the editor. Other maps without world coordinates may be adjusted to the background map easily by setting 3 pairs of reference points on the background and the new map. The calculated world coordinates will be assigned and stored when the new map is saved.
A GPS functionality has been integrated. If a GPS device is connected, the current position will be displayed and - if an applicable background map is loaded - marked on the map.
The data transfer between application and GIS editor is made by interface function calls. In that way geometry objects of a Diversity database may be loaded to the editor, modified or extended and sent back to the application, which then updates the data base.
The layout of the Diversity GIS Editor could be divided into 3 regions:
The Control Panel consists of the following elements:
to switch to a new object, if
the current sample is composed of multiple lines or areasThe Sample List is the container for added maps or objects. Each entry is composed of the following elements:
The toggle button is illustrated with a small picture of the associated sample. Switching these controls using the left mouse button will hide or show the corresponding sample. Using the right mouse button will effect all samples except the corresponding one and the background map:
If the number of samples in the list do not fit into the window area, a scroll bar will be displayed.
This is the drawing space containing loaded maps and objects. In Shift mode the area could be moved or zoomed.
The GIS Editor has 7 operation modes which are described in the following chapters:
When starting the GIS Editor as a stand-alone application the start-up operating mode usually is the Map mode. This is to remind the user that a background map with world coordinates is necessary to work with geographic objects.
In Map mode the editor connects via Internet to the SNSB Google Maps
service or alternatively to the Open Street Maps service, regarding on
the GIS-Editor Settings, and displays an online
map which can be moved, zoomed and switched as usual. The status area
shows the
or
respectively the
symbol. The
size of the map area adapts to the size of the working area, even when
resizing the window.
In case of Google the controls for moving, zooming and map type are displayed by default. The overview window in the bottom right corner can be switched manually. The map can be adjusted to the user’s needs as follows:
In case of Open Street Maps the pan and zoom control is displayed by
default. It can be switched off or on by clicking the left mouse button
anywhere within the map area. The layer switch control is hidden and can
be opened by pressing the or closed
again by pressing the
button on the
right side. The map can be adjusted to the user’s needs as follows:
If an appropriate area has been selected, just press the Add button
, then the area will be scanned and added to
the Sample List as a reference map. A little image of the map will
appear on the toggle button in the Sample List. The controls should be
switched off before adding to get a neat map image.
Then the mode will be switched to Shift mode automatically and the
status symbol will change to
indicating
that world coordinates are present. The screen and world coordinates
will be shown in the status lines if the mouse is moved over the map
surface.
The maps are subject to the Mercator projection, which is the GIS Editor’s precondition for every bitmap used as a reference map. While the screen coordinates are linear in horizontal and vertical direction, the world coordinates are non linear in vertical direction.
This is the quasi default mode of the GIS Editor. The cursor changes to
a move shape
when touching the
background map. The map is “frozen” and exists as an image sample on the
sample list. Changing the map region or resolution is no longer
possible. But the Shift Mode provides 2 features:
Press and hold the left mouse button and move the mouse to shift the working area within the display window. This is useful when having loaded a map from a storage unit which is larger than the GIS Editor’s window, or in combination with zooming the working area.
Place the mouse cursor at the slider control, press and hold the left mouse button and move the control left to zoom out or right to zoom in the working area. The range of the zoom is from factor 0.6 to 3.0. The current value is displayed beneath the zoom control. Double click the slider control to reset the zoom to default value 1.0.
Enlarging the working area makes it more easy to place objects precisely. The relevant area then could be selected by moving the zoomed working area. Downsizing the working area gives an overview of large map regions.
Note that the resolution of the map itself does not change any more when zooming in. But objects on the map are created in vector graphics, so the markers, lines or areas will remain sharp and clear while zooming. And they will adapt there thickness smoothly to the size.
This mode is used to create areas (polygons) on the background map. The cursor changes to a cross line when touching the background map. Each click on the left mouse button sets a new point of the polygon. Every click on the right mouse button clears the last point set. The closed polygon defined by the points is displayed completely at any time. When holding the left mouse button the point can be placed while the lines of the polygon are shown as a “rubber band” display.
To create more than one area for a sample, just click the
button. This will finish the current
polygon and start another one. It could be repeated without limitation
of the number of polygons.
The areas are created as filled polygons, this means they have a border line (stroke) and a filling. The color of stroke and filling can be set independently or simultaneously by clicking the appropriate check boxes beneath the Color list box. Clicking on the list box will open a drop down menu with the complete set of 141 predefined brushes. Use the scroll bar to navigate to the preferred color and select it with the left mouse button.
Besides the color the transparency of the area could also be set for stroke and filling. In each edit mode the slider control is used for that. The area stroke or filling changes smoothly from invisible at the left till completely opaque on the right slider position. The value beneath the slider control indicates the opaqueness in a range from 0% to 100%. The default settings are 100% for stroke and 25% for filling.
Before adding the polygon to the Sample List an Identifier (ID) and a Description (Text) should be written to the text boxes in the control panel.
Clicking the Add button will put the
current area(s) as one sample into the Sample List. The toggle button
will show a small picture of the first area of the sample. The ID will
be displayed above the button. Furthermore a tool tip will be created
for the sample holding the ID and Description, which will pop up when
moving the mouse over the toggle button or over the polygon in the
working area.
This mode is used to create line strings on the background map. The
usage is adequate to the Area Mode. The cursor
changes to a cross line when touching the background map. The points of
the line strings can be set or cleared by clicking the mouse buttons.
Clicking the
button will switch to the
next line string for the sample. The distance of the last drawn line
string section is displayed beneath the status area.
Color and transparency can be set for the line strings using the appropriate controls, but only for stroke, because the line strings do not have a filling. Thus checking the Fill box will have no effect. After adding the lines to the sample list a small picture of the first line string will appear on the toggle button.
This mode is used to create Points (object markers) on the background
map. The usage is similar to the Area Mode. The
cursor changes to a cross line when touching the background map. The
object markers can be set by clicking the left mouse button, clicking
the right mouse button will clear the last markers one by one again. The
button has no impact, because each Point
represents a complete object and needs not to be finished before
creating the next one.
The shape of the object markers can be selected from a number of predefined Point symbols and icons within the Settingswindow, e.g.:
| Pin: | ![]() |
| Diamond: | ![]() |
| Needle: | ![]() |
| Cross: | ![]() |
| Pyramid: | ![]() |
| X: | ![]() |
| Cone: | ![]() |
| Square: | ![]() |
| Questionmark: | ![]() |
| Circle: | ![]() |
| Minus: | ![]() |
| Myxomycete: | ![]() |
| Fungus: | ![]() |
| Lichen: | ![]() |
| Bryophyt: | ![]() |
| Plant: | ![]() |
| Evertebrate: | ![]() |
| Mollusc: | ![]() |
| Assel: | ![]() |
| Insect: | ![]() |
| Echinoderm: | ![]() |
| Vertebrate: | ![]() |
| Fish: | ![]() |
| Reptile: | ![]() |
| Bird: | ![]() |
| Mammal: | ![]() |
Color can be set for the symbol markers using the appropriate controls. It depends on the selected point symbol, whether it just has a stroke (e.g. “Cross”) or also a filling (e.g. “Pin”). Transparency can be set for both, the symbol and icon markers. The stroke thickness and the size of the markers can be set in the Settings menu. After adding the object markers to the sample list a small picture of the collection will appear on the toggle button.
This mode is used to modify all samples (objects and images) which are currently visible on the working area. It applies to the elements of the Sample List as well as to the current sample.
To change an object one has to move the vertices (“corner points”) which
are defining it. To do so just move the mouse close to a vertex to
localize it. As soon as the corner has been grabbed the cursor changes
its shape to a hand symbol
.
Now press the left mouse button and hold it, then move the mouse to change the position of the vertex accordingly. The shape of the object or the marker will change in the same manner. Release the mouse button when the preferred position has been set.
Note that areas and line strings cannot be moved in total while keeping their shapes!
Images (e.g. maps) can be moved completely (keeping their aspect ratio), scaled in horizontal and vertical direction and skewed within an affine transformation. Editing an image can be divided into 4 stages by grabbing and moving the following corners:
Color and transparency can be set independently (or simultaneously) for the objects using the appropriate controls and check boxes for Stroke or Fill. The setting will affect all visible objects, so objects which should not be changed have to be switched off before with their toggle buttons. The color of images could not be changed, of course, but the transparency can be set if the Fill box is checked. The transparency of the background map cannot be changed.
Essential for visualizing Geographical Objects is a background map with world coordinates. The GIS Editor’s Map mode offers a convenient way to create such a map, but it is restricted for the use of Google or OSM maps which are present in the web and are providing world coordinates. It would be nice to load scans of e.g. topographical or even historical maps into the working area and use them as background maps, but the problem is how to assign world coordinates to them.
The Adapt mode solves this in an easy way by executing the following steps. As a precondition a background map having world coordinates (e.g. a Google map) must be present which covers the area of interest of the new map to be referenced.
Load the new map image using the Load button
. The image will be placed top
left inside the working area.
Select Adapt mode by checking the Adapt radio button. The cursor
changes to a pointer symbol
having a green border when touching the new image and having a red
one when touching the background map.
Now 3 reference points must be set alternately on background and new
map to assign the appropriate locations (e.g. distinctive landmarks
like road crossings). The last point can be modified as long as the
map is not changed. The cursor always tells you what reference point
will be set, according to its color and the number of dots in the
middle:

Note: It is reasonable to select distant points close to the edges
of the new map, because this will give more accurate results.
.
Sometimes it is difficult to place the new map and the reference map side by side, because the window is too small, and zooming out would blur the details needed for setting the reference points. If the new map covers the background map, the reference points can be set anyway
for the new map by making it opaque with the transparency slider
for the background map by making the new map transparent (less than 10% opacity) with the slider
Note: The Fill box must be checked to change the transparency of the new map. The background map’s transparency cannot be changed.
A background map is required before objects (areas, line strings,
points) can be loaded. If no background map is available, the GIS Editor
will extract the appropriate area from the sample file data and
automatically adjust the map viewer to cover the region. The user is
prompted to wait until the map has been established completely and then
press
. If no map is displayed (e.g.
because there is no internet connection), the user may press
and load a local map instead, or
to cancel the loading of the
shapes.
When loading a shape file, the objects will be displayed at the background map according to their coordinates and added to the Sample List automatically. The GIS Editor is able to read MS-SQL Geo Object files (.shp1), TAB separated text files (.shp2), GPS Exchange Format files (.gpx) as well as ArcView Shape Files (.shp).
The assumption of the type of input file is made according to the extension of the file, so e. g. a TAB separated input file of an external source might have to be renamed to .shp2 before it is loaded by the GIS Editor. The input parameters of the first text line are determined, a dialog window will open and show them on the left.
Then you have to assign certain input values to the GIS Editor attributes, wich are displayed in the middle of the window. Select an input parameter using the radio button on the left, then assign it to one or more sample attributes by clicking the appropriate checkbox in the middle. The assigned values are shown on the right side of the window. Values in gray are default parameters, which are used if the attribute has not been assigned. There is just one mandatory attribute which has to be set, the Geography Data (SQL Geo Object). If there is no SQL Geo Object available in the input file, a point object will be created automatically when assigning longitude and latitude parameters.
To assign up to 10 input parameters simultaneously to the adjacent 10
sample attributes, just click on the
button.
This is helpful if the input file has been created with the GIS Editor
itself, so the input values are already in the right order.
To remove all assigned values, click on the
button.
If the assignment is done, click on the
button
to show all geographic objects of the input file according to the
assigned parameters. Each object will be added to the list as a separate
sample. To put all objects together as one single sample, check the
“Save as one object” box.
Click on the
button to cancel the load
operation.
The last assignment is saved by the GIS Editor and can be used for the
next input file, if it has the same structure as the previous one. Just
click on the
button to assign the same
input parameters as before.
The GIS Editor supports ArcView Shape Files (.shp) using geographical, UTM or Gauß-Krüger coordinates. The type of the coordinates (Geographic/Gauß-Krüger or UTM) has to be selected first in the GIS-Editor Settings, in case of UTM also the zone and the hemisphere. If an ArcView attribute file (.dbf) is available, a window will open and show the attributes of the first shape. The user may select the attributes which should be used to create the sample ID and description. Check one or more appropriate boxes and assign them by clicking the “ID” or “Text” button. A separator string may be defined to combine the selected attributes to the final text string. If no attribute is selected, the name of the ArcView file is assigned to the sample description.
To access the dBase attributes file for reading or writing, the Microsoft ACE OLEDB 12.0 driver must be installed on the computer. If it is missing, the attributes cannot be evaluated and a warning will be displayed. The shapes will be loaded properly, anyway, but no description will be added.
When loading an image without world coordinates, it will be displayed
top left in the working area. If no background map is loaded yet, the
Screen symbol
is shown in
the status line, followed by the screen coordinates of the current
cursor position.
When loading an image with world coordinates and no background reference
map exists, it will be displayed top left in the working area. The World
symbol
is
shown in the status line, followed by the screen coordinates and the
world coordinates of the current cursor position.
When loading an image with world coordinates having an existing reference map, it will be embedded in the background map according to its coordinates. If the new image does not overlap with the reference map, the image exists virtually in the coordinate system, but possibly could not be seen because it is too far away from the reference map.
Loaded images with world coordinates are immediately added to the Sample
List. When loading an image without world coordinates it is displayed,
but not yet added to the Sample List. The user has to add it manually by
pressing the Add button . This is because
the user should have the opportunity to adapt the image to the
background map to be stored later on with applicable coordinates.
To save a background map which is currently displayed in Map mode just
press the Save button instead of the Add
button
. A save file dialog will pop up to
name the file, the map and its coordinates will be saved and added to
the sample list.
A background map is required before objects and images can be saved.
Saving samples means saving their type, attributes and world coordinates
in files. When pressing the Save button ,
it applies to all visible samples on the working area, except the
background map. A current sample will be added to the sample list before
it is saved.
If objects are visible, a save file dialog will open and a name for the target file(s) must be set. Objects (areas, line strings, points) will be saved in respect to the selected formats of the GIS-EditorSettings:
If images are in the Sample List, they are already present on disk and will not be saved twice. Instead for each image an XML file will be created with the calculated world coordinates of the image and will be stored under the same location and name as the image. This does not apply to the current background map.
If Save Working Area is enabled in the GIS-EditorSettings, a scan of the complete working area
including its objects is made and stored in an image file, which name
has been set in the save file dialog.
To save only a part of the working area the Frame box must be checked in
the GIS-Editor Settings, too. Then a
rectangular frame of the given dimensions is displayed, which defines
the part of the working area that will be saved. It can be dragged to
the right position using the left mouse button (click, hold and shift),
and it can be resized by grabbing and moving the corners of the frame.
To delete a single object of the Sample List just press the small Delete button .
If no device is detected the button will be released. If a device has
been found the button changes the color according to the numbers of
satellites which have been fixed by the device: Red
up to 3 satellites, yellow
up to 5 and green
if 6 satellites or more are available.
The number of satellites, longitude, latitude and altitude delivered
from the GPS device are displayed in the info line of the Control Panel
beneath the status.
The current position will be shown by a GPS marker
if an appropriate background map has
been loaded. If GPS Track in the Settingswindow is checked, the movement of the position
will be drawn as a line string on the background map. The color and
stroke thickness are similar to the last adjustment for lines. When
switching off the GPS button again, the track will be added to the
sample list automatically and could be saved for future documentation
purposes.
Pressing the Settings button in the
Control Panel will open a dialog to adjust these GIS Editor settings
which are not frequently changed:
ArcView is a common Desktop GIS tool and stores its
data in binary files. The GIS Editor is able to read these files and
display the included geography objects. But because ArcView does not
necessarily provide a dedicated information about the GIS format of the
contained data, the user has to know and select it in advance.
The GIS Editor currently supports WGS84 geographic coordinates,
Gauß-Krüger coordinates (Potsdam datum) und WGS84 UTM coordinates. If
“Geographic / GK” is selected, the program will choose the right format
by checking the binary values. In case of UTM the user must select the
hemisphere (N/S) and the UTM zone (1-60) to ensure that the objects will
be displayed at the correct location.
The ArcView data files may contain complex geographic shapes (e.g. polygons or line strings) which are combined by the GIS editor to one multi object (e.g. multipolygon) by default. To split up the shapes into single objects the option “Split shapes into single samples” has to be selected. Then they are placed into the sample list separately. This could be helpful to avoid out-of-memory errors if very large shapes should be converted to SQL geography strings.
At the moment 3 formats for object files are supported:
Microsoft SQL Geo Objects are part of a standard for
storing geometry and geography data in an SQL database, as used by the
DiversityWorkbench modules. They are a well defined text string
containing the geometrical type (e.g. Polygon, Line, Point) and the
geographical coordinates (longitude, latitude, optional altitude) of an
object.
Together with the GIS Editor attributes (e.g. color, transparency) they
are stored in a proprietary GIS Editor shape file in ASCII text format.
This file can easily be read and changed using a text editor.
TAB separated text files are widely used as an interchange data file format. The content of a file is more or less the same as above, but the parameters of each object are placed in a single text line, separated by tabulator characters. Additionally to the SQL Geo Object the “envelope center point” (longitude and latitude) of it is saved separately in the file.
The GIS Editor can also create ArcView compatible files to store the samples, which then may be read from ArcView GIS tools. 3 files are required for each type of shape: A data file with extension “.shp”, an index file with extension “.shx” and a description file in dBase format with extension “.dbf”.
The advantage of the first format is the transparency and readability of the data file, which is just one single text file. But storing huge samples is time consuming, because they have to be converted to SQL geography strings. If the samples consist of more than 100,000 points, an warning message is shown and the user may decide whether to continue or not:
While saving the shapes, a progress bar will be displayed to indicate the status of the task:
Using the ArcView format makes the data files compatible with many applications. Huge samples can be stored much faster. But each type of sample requires a separate set of output files, because different types of objects within one file are not supported so far. So a sample list containing 10 objects will produce 30 data files (file name with an appended index, which is incremented for each sample). Furthermore the attributes like color, transparency and stroke thickness will not be saved.
Currently there is just one format supported for storing image coordinates. They are written into an XML file which is also used in DiversityMobile modules. Saving the coordinates in this format is required for the GIS Editor, so it cannot be disabled.
Selecting this check box and later on pressing the Save button
will additionally scan the working area
including all visible objects and save it as an image file under the
name provided in the save file dialog, see SaveSamples. This is useful for documentations.
Note: There are copyright restrictions on maps or aerial images
which are created with the Google maps viewer. Please contact Google
before using them for publications to grant a license, or use Open
Street Maps captures, which could be used freely under the
Creative Commons Attribution Share Alike license
conditions.
When checking the “Frame” box just a rectangular part of the working area is saved. The size (in pixels) of the frame has to be defined in the adjacent “Width” and “Height” fields. This is convenient if the resulting image should have well defined dimensions, e.g. fit the resolution of a smartphone display. After closing the Settings window a rectangular frame of these dimensions is displayed on the working area which defines the part to be saved. The frame is only visible in Shift Mode. It can also be adjusted using the mouse: Place the cursor within the frame, press the left mouse button und hold it, then shift the frame by moving the mouse. Or change the size of the frame by grabbing a corner: When the cursor changes, press the left mouse button und hold it, then adjust the size by moving the mouse.
When checking this box the movement of the GPS marker on the background map will be tracked by a line string. After switching off the GPS button the line string will be added to the sample list automatically.
This box applies to MS-SQL Geo Objects only. If checked, the appropriate altitude of the object points (longitude, latitude) will be stored in the file, too. This is not recommended for sample objects with a lot of points or vertices, because for every point the Geonames server has to be contacted to request the associated altitude value. This could slow down the saving procedure immensely.
The stroke thickness for area, line strings and point symbols can be set by using the appropriate slider. The value of the thickness is shown in the label box left of the slider. Double clicking the slider will reset the thickness to its default value 1.
The symbol for the points can be selected from the drop down menu. The symbol size can be set using the slider below the menu. The point symbol display will change accordingly.
The samples on the working area may be switched off and on with the mouse buttons. If the switched off objects would become invisible, it will be difficult to switch them on again, because you don’t see them. For this the opacity of the switched off samples can be adjusted between 0% (invisible) and 100% (fully visible) with the slider. E.g. a value of 25% will make the samples transparent, but one can still see and touch them on the map.
It is essential to set a suitable baudrate for a connected GPS device according to its specification. The rate can be selected from the list of the drop down menu. If no GPS device is available, Demo mode could be chosen to see the behaviour of the functionality.
The radio buttons offer the choice of the viewer for creating a background map. Currently Google Maps and Open Street Maps are provided.
Clicking the Info button will display a window containing GIS Editor version and license information.
Finally pressing the OK Button will save the settings, pressing the Cancel button will discard them.
Since GIS Editor version 2.2.3.0 the Sample Detection offers a new convenient tool to digitize sample markers e. g. of a scanned and georeferenced analog paper sheet.
The tool will try to detect “points” on an image according to the
detection parameters which can be adjusted in the Sample Detection
Parameters window, which will open when clicking the
button.
The decision what belongs to a sample and what is just background on the loaded image is made by defining a color range of the object to be found. Looking at the example picture above, we can see that the collector has marked samples using a “black” pen on a reddish scale paper. The points appear as dark grey scatterplots. To detect these points we must define the color range of interest from “mid grey” to “black”.
The grey range can be easily set by moving the “Grey” sliders for minimum and maximum values. The sliders for the 3 color channels will move simultaneously, adjusting the channel values in parallel. In the example above we found a range from 0 (black) to 150 (mid grey) which covers the colors of the samples and excludes the background colors. It is visualized in the color boxes for min and max values and as a linear gradient color brush.
If we’d look with a magnifying glass on a single point, we would discover that in fact it is an array of pixels (picture elements) in various shades of grey. To reduce this “cloud” to a single point coordinate the program uses several algorithms. The result can be improved by setting the parameter for the minimum point distance in pixels to an appropriate value (e. g. 4).
The resulting sample points would be displayed as a point collection to be (potentially) edited and added as one sample to the GIS Editor sample list. In contrast, clicking the check box beneath will split up the found sample points into single samples and add them immediately to the sample list including an enumeration. The sample names will then be composed by Identifier and Enumeration (start value, will be incremented) as defined in the text boxes under it. Pressing the OK button will start the detection and deliver the detected points as object markers.
Not only grey points may be detected, but markers of any color tone. The ranges for the red, green and blue color channels can be adjusted individually by moving the sliders for min and max values. The gradient color brush gives you a hint about the resulting color range, but it needs much experience to define a color range properly to get the expected results.
The samples which have been created or loaded may be switched off and on in several ways:
Switching the toggle buttons of the Sample List with the left mouse
button will hide or show the corresponding sample.
Using the right mouse button will effect all samples except the
corresponding one and the background map:
Since version 2.2.9.0 the samples may also be switched directly on the working area in a similar way:
To be able to locate the ‘invisible’ switched off samples on the working
area (e.g. to switch them on again) the opacity of them can be set in
the GIS-Editor Settings. 100% means fully
visible, 0% means invisible.
Note: The opacity has to be set before the samples are loaded or
created! The value is part of the corresponding object and cannot be
changed afterwards.
If there is a big amount of samples loaded to the working area it might be desirable to make a preselection before switching them one by one. For this select Shift mode and enable the Frame in the GIS-EditorSettings. Adjust the position and size of the Frame, then click on the Frame area with the right mouse button to switch on all samples within the frame and switch off all samples outside.
Der Bayernflora-Editor ist eine Software zum einfachen Editieren, mit dem Bestimmungen der Einzelbeobachtungen und -funde und Angaben des floristischen Status überarbeitet werden können. Er ergänzt die anderen DiversityCollection Editierwerkzeuge wie den kartengestützten Tabellen-Editor mit umfangreichen Möglichkeiten TK25 Rasterdaten zu bearbeiten.
Die Optionen zum Export von Daten:
Im Tab Quelle wird die Datei eingeleseh. Über den Button
Export von Taxa wie in Liste öffnet sich ein Formular in das man mit dem Button Quelle einlesen ein Liste von Taxa importieren kann. Vorher muss man angeben ob die Liste Namen oder IDs einhält sowie das Encoding (e.g. UTF8).
Mit dem Button Quelle Abgleichen kann man die eingelesenen Daten dann mit dem Inhalt der Datenbank DiversityTaxonNames_Plants abgleichen. Eindeutige Zuordnungen werden mit grün hinterlegt. Nicht eindeutige mit blau und Taxa für die keine Entsprechung gefunden wurde mit rot. Mit dem Button Ausgewählten Namen abgleichen können die noch nicht eindeutig zugeordneten Taxa zugeordnet werden.
Im Tab Hierarchie und Synonyme kann man die gefundenen Taxa um Ihre Synonyme und untergeordneten Taxa ergänzen. Einfach auf den Button clicken, dann wir die Datenbank nach den entsprechenden Einträgen durchsucht und die Liste entsprechend ergänzt.
Im Tab Export kann man die gefundenen Taxa mit dem Button in die angezeigte Tabelle übernehmen. Danach kann man die gewünschten Datensätze aus dieser Tabelle e.g. in eine Excel-Datei kopieren.
Im Hauptformular erreicht man mit dem Button das Formular zur Erzeugung und Ausführung von SQL Abfragen sowie dem Export der Ergebnisse.
Dieser Bereich ist nur für Administratoren zugänglich.
Hiermit können Funde gesucht werden, deren Fundorte ausserhalb Bayerns liegen und ein Grund für die Sperrung eingetragen werden. Die Sperrung wird ins Feld DataWithholdingReason der Tabelle CollectionSpecimen eingetragen und der Beleg für die Publikation gesperrt.
Übernehmen von Status aus DiversityTaxonNames sofern noch keiner in DiversityCollection eingetragen ist.
Es wird zunächst das Projekt ausgewählt dessen Daten bearbeitet werden sollen. Optional können Synonyme in DTN in die Suche eingeschlossen werden. Für die Suche in DiversityCollection kann auf die Quelle sowie das
Datum des Imports eingeschränkt werden.
Mit der Schaltfläche
Suche starten wird dann nach fehlenden Statusangaben gesucht.
Danach können die gefundenen Statusangaben mit der Schaltfläche
Eintragen eingetragen werden.
Hiermit lassen sich innerhalb von bestimmten Quadranten gefundene Belege ausgewählten Projekten zuordnen.
Mit dem Schaltffläche Datei einlesen wird zunächst eine Quelldatei eingelesen welche die zu erfassenden TKs und Quadranten enthält.
Es kann auf ein Quellprojekt eingeschränkt werden, sowie Projekte aus der Suche ausgeschlossen werden. Bitte die Schaltflächen
bw.
für die Bearbeitung der Liste auszuschliessender Projekte verwenden.
Mit der Schaltfläche Quadranten suchen wird die Suche gestartet. Werden Objekte gefunden können diese mit der Schaltfläche
Projekt eintragen in das Zielprojekt übernommen werden.
Bereitstellung von Daten aus der DiversityWorkbench für die GUC
Beim Start des Programms müssen zunächst die Login Daten eingegeben werden.
Danach startet das Programm mit dem Hauptfenster.
Das Setup für das Programm liegt bereit unter:
For users that need more detailed information about the software including database design etc.
-- setting the timestamp
delete from [dbo].[Artcode_LastChange] where Tabelle = 'ArtcodeTemp'
TRUNCATE TABLE [dbo].[Artcode_ArtID];
INSERT INTO [dbo].[Artcode_ArtID](NameID)
select T.ID
FROM ArtcodeTemp AS T
where T.Art_ID IS NULL
-- Setting the Art_ID for missing names
UPDATE T SET T.Art_ID = '9P0#' + REPLICATE('0', 6 - LEN(CAST(A.ID AS varchar))) + CAST(A.ID AS varchar)
-- select T.Art_ID, '9P0#' + REPLICATE('0', 6 - LEN(CAST(A.ID AS varchar))) + CAST(A.ID AS varchar)
FROM ArtcodeTemp AS T INNER JOIN [Artcode_ArtID] A ON T.ID = A.NameId
WHERE T.Art_ID IS NULL
-- Setting the family
TRUNCATE TABLE [dbo].[Artcode_Family]
INSERT INTO [dbo].[Artcode_Family]
([NameID]
,[FamilyNameID]
,[Family])
SELECT
T_0.NameID,
CASE WHEN T_1.TaxonomicRank = 'fam.' THEN T_1.NameID
ELSE
CASE WHEN T_2.TaxonomicRank = 'fam.' AND T_2.IgnoreButKeepForReference = 0 THEN T_2.NameID
ELSE
CASE WHEN T_3.TaxonomicRank = 'fam.' AND T_3.IgnoreButKeepForReference = 0 AND H_2.IgnoreButKeepForReference = 0
THEN T_3.NameID ELSE
CASE WHEN T_4.TaxonomicRank = 'fam.' AND T_4.IgnoreButKeepForReference = 0 AND H_3.IgnoreButKeepForReference = 0
THEN T_4.NameID
ELSE NULL
END END END END AS FamilyNameID,
CASE WHEN T_1.TaxonomicRank = 'fam.' THEN T_1.GenusOrSupragenericName ELSE CASE WHEN T_2.TaxonomicRank = 'fam.' AND
T_2.IgnoreButKeepForReference = 0 THEN T_2.GenusOrSupragenericName ELSE CASE WHEN T_3.TaxonomicRank = 'fam.' AND
T_3.IgnoreButKeepForReference = 0 AND
H_2.IgnoreButKeepForReference = 0 THEN T_3.GenusOrSupragenericName ELSE CASE WHEN T_4.TaxonomicRank = 'fam.' AND
T_4.IgnoreButKeepForReference = 0 AND H_3.IgnoreButKeepForReference = 0 THEN T_4.GenusOrSupragenericName ELSE NULL
END END END END AS Family
FROM dbo.TaxonHierarchy AS H_3 INNER JOIN
dbo.TaxonName AS T_4 ON H_3.NameParentID = T_4.NameID AND H_3.ProjectID = 1128 RIGHT OUTER JOIN
dbo.TaxonName AS T_3 INNER JOIN
dbo.TaxonHierarchy AS H_2 ON T_3.NameID = H_2.NameParentID AND H_2.ProjectID = 1128 ON
H_3.NameID = T_3.NameID RIGHT OUTER JOIN
dbo.TaxonHierarchy AS H_1 INNER JOIN
dbo.TaxonName AS T_2 ON H_1.NameParentID = T_2.NameID AND H_1.ProjectID = 1128 RIGHT OUTER JOIN
dbo.TaxonHierarchy AS H_0 INNER JOIN
dbo.TaxonName AS T_0 ON H_0.NameID = T_0.NameID AND H_0.ProjectID = 1128 INNER JOIN
dbo.TaxonName AS T_1 ON H_0.NameParentID = T_1.NameID AND H_0.ProjectID = 1128 ON H_1.NameID = T_1.NameID AND H_1.ProjectID = 1128 ON
H_2.NameID = T_2.NameID AND H_2.ProjectID = 1128
-- family for synonyms
INSERT INTO [dbo].[Artcode_Family]
([NameID]
,[FamilyNameID]
,[Family])
SELECT S.NameID, F.FamilyNameID, F.Family
FROM [Artcode_Family] F
INNER JOIN dbo.TaxonSynonymy S ON S.SynNameID = F.NameID AND S.ProjectID = 1128
AND NOT EXISTS(SELECT * FROM [Artcode_Family] A WHERE A.NameID = S.NameID)
UPDATE T SET T.fam = UPPER(SUBSTRING(F.Family, 1, 3)), T.id_fam = AF.Art_ID
-- select T.fam, UPPER(SUBSTRING(F.Family, 1, 3)), T.id_fam, AF.Art_ID
FROM ArtcodeTemp AS T INNER JOIN Artcode_Family F ON T.ID = F.NameID
INNER JOIN ArtcodeTemp AS AF ON AF.ID = F.FamilyNameID
--Ausgabesperre, Statistiksperre, Eingabesperre, SAP
UPDATE T SET T.Ausgabesperre = NULL, T.Statistiksperre = NULL, T.Eingabesperre = NULL, T.saP = NULL
-- select T.Ausgabesperre, Statistiksperre, Eingabesperre, SAP
FROM ArtcodeTemp AS T WHERE T.Ausgabesperre = 0
-- setting the rank
UPDATE T SET T.rang = R.rang_id
-- select T.rang, R.rang_id
FROM ArtcodeTemp AS T INNER JOIN [dbo].[Artcode_Rang] R ON R.Code = T.TaxonomicRank
-- setting the rank for synonyms
UPDATE T SET T.rang = 'syn'
-- select T.rang, 'syn'
FROM ArtcodeTemp AS T INNER JOIN TaxonSynonymy S ON T.ID = S.NameID and S.ProjectID = 1128 --and (T.rang is null or T.rang = '')
-- setting the Art_ID_Gueltig for synonyms
UPDATE T SET T.Art_ID_Gueltig = A.Art_ID
-- select T.Art_ID, T.Art_ID_Gueltig, A.Art_ID
FROM ArtcodeTemp AS T INNER JOIN TaxonSynonymy S ON T.ID = S.NameID and S.ProjectID = 1128 AND T.Art_ID_Gueltig IS NULL
INNER JOIN ArtcodeTemp A ON S.SynNameID = A.ID
-- Eintrag Art_ID_Gueltig wo er fehlt
UPDATE A SET A.Art_ID_Gueltig = CASE WHEN E.ExternalNameURI IS NULL THEN NULL ELSE E.ExternalNameURI END
-- SELECT A.Art_ID_Gueltig, CASE WHEN E.ExternalNameURI IS NULL THEN NULL ELSE E.ExternalNameURI END AS Art_ID_Gueltig_E
FROM dbo.TaxonNameExternalID AS E INNER JOIN
dbo.TaxonName AS N ON E.NameID = N.NameID AND E.ExternalDatabaseID = 1003 AND (N.IgnoreButKeepForReference = 0)
INNER JOIN ArtcodeTemp AS A ON A.ID = N.NameID AND A.Art_ID_Gueltig IS NULL
-- setting the Autor_Pos
UPDATE T SET T.Autor_Pos = 1
-- select T.Autor_Pos, 1, T.rang, N.TaxonNameCache, N.TaxonomicRank, ar.DisplayOrder
FROM ArtcodeTemp AS T
inner join TaxonName N on T.id = N.NameID and N.SpeciesEpithet = N.InfraspecificEpithet and N.BasionymAuthors <> ''
inner join Artcode_Rang as AR on N.TaxonomicRank = ar.Code and ar.DisplayOrder < 170
-- setting the Autor_Pos
UPDATE T SET T.Autor_Pos = 2
-- select T.Autor_Pos, 2, T.rang, N.TaxonNameCache, N.TaxonomicRank, ar.DisplayOrder, T.Autor
FROM ArtcodeTemp AS T
inner join TaxonName N on T.id = N.NameID and N.SpeciesEpithet like 'x %' and N.BasionymAuthors <> ''
inner join Artcode_Rang as AR on N.TaxonomicRank = ar.Code and ar.DisplayOrder < 170
-- setting Verantwortung Bayerns
UPDATE T SET T.VeraB = A.AnalysisValue
FROM ArtcodeTemp AS T INNER JOIN [dbo].[TaxonNameListAnalysis] A ON T.ID = A.NameID AND A.AnalysisID = 5
-- setting Verantwortung Deutschlands
UPDATE T SET T.VeraD = A.AnalysisValue
FROM ArtcodeTemp AS T INNER JOIN [dbo].[TaxonNameListAnalysis] A ON T.ID = A.NameID AND A.AnalysisID = 4
-- setting Gefährdung nach Roter Liste Bayern 2003
UPDATE T SET T.RLB = A.AnalysisValue
-- select T.RLB, A.AnalysisValue
FROM ArtcodeTemp AS T INNER JOIN [dbo].[TaxonNameListAnalysis] A ON T.ID = A.NameID AND A.AnalysisID = 1
-- setting Gefährung nach Roter Liste Deutschland 2018
UPDATE T SET T.RLD = A.AnalysisValue
FROM ArtcodeTemp AS T INNER JOIN [dbo].[TaxonNameListAnalysis] A ON T.ID = A.NameID AND A.AnalysisID = 62
-- setting Schutzstatus in Bayern
UPDATE T SET T.Schutz_BNatSchG = case when A.AnalysisValue = '§§' then 's' else 'b' end
FROM ArtcodeTemp AS T INNER JOIN [dbo].[TaxonNameListAnalysis] A ON T.ID = A.NameID AND A.AnalysisID = 7
UPDATE T SET T.sensu = N.NonNomenclaturalNameSuffix
-- select T.sensu, N.NonNomenclaturalNameSuffix
FROM ArtcodeTemp AS T INNER JOIN [TaxonName] N ON T.ID = N.NameID and N.NonNomenclaturalNameSuffix <> ''
-- setting Schutzstatus in Bayern
UPDATE T SET T.Schutz_BNatSchG = case when A.AnalysisValue = '§§' then 's' else 'b' end
FROM ArtcodeTemp AS T INNER JOIN [dbo].[TaxonNameListAnalysis] A ON T.ID = A.NameID AND A.AnalysisID = 7
-- setting id_agg
UPDATE T SET T.id_agg = case when P.Art_ID_Gueltig is null then P.Art_ID else P.Art_ID_Gueltig end
-- select T.id_agg, case when P.Art_ID_Gueltig is null then P.Art_ID else P.Art_ID_Gueltig end
FROM ArtcodeTemp AS T INNER JOIN [dbo].[TaxonHierarchy] H ON T.ID = H.NameID AND H.ProjectID = 1128
inner join ArtcodeTemp P on H.NameParentID = P.ID
inner join dbo.TaxonAcceptedName A on T.id = A.NameID and A.ProjectID = 1128
-- setting id_agg for not accepted names
UPDATE T SET T.id_agg = case when P.Art_ID_Gueltig is null then P.Art_ID else P.Art_ID_Gueltig end
-- select T.id_agg, case when P.Art_ID_Gueltig is null then P.Art_ID else P.Art_ID_Gueltig end
FROM ArtcodeTemp AS T INNER JOIN [dbo].[TaxonHierarchy] H ON T.ID = H.NameID AND H.ProjectID = 1128
inner join ArtcodeTemp P on H.NameParentID = P.ID
WHERE T.id_agg IS NULL OR T.id_agg = ''
-- setting id_agg for not synynyms missing a hierarchy
UPDATE T SET T.id_agg = case when P.Art_ID_Gueltig is null then P.Art_ID else P.Art_ID_Gueltig end
-- select T.id_agg, case when P.Art_ID_Gueltig is null then P.Art_ID else P.Art_ID_Gueltig end
FROM ArtcodeTemp AS T
INNER JOIN [dbo].[TaxonSynonymy] S ON S.NameID = T.ID AND S.ProjectID = 1128
INNER JOIN [dbo].[TaxonHierarchy] H ON S.SynNameID = H.NameID AND H.ProjectID = 1128
inner join ArtcodeTemp P on H.NameParentID = P.ID
WHERE T.id_agg IS NULL OR T.id_agg = ''
-- setting BOLD_ID
UPDATE T SET T.BOLD_ID = E.ExternalNameURI
FROM ArtcodeTemp AS T INNER JOIN [dbo].[TaxonNameExternalID] E ON T.ID = E.NameID and E.ExternalDatabaseID = 1010
-- setting Bayernstatus
UPDATE T SET T.staby = B.staby
FROM ArtcodeTemp AS T INNER JOIN [dbo].[TaxonNameListAnalysis] A ON T.ID = A.NameID AND A.AnalysisID = 2
INNER JOIN [dbo].[Artcode_Bayernstatus] B ON B.[AnalysisValue] = A.AnalysisValue
INSERT INTO [dbo].[Artcode_LastChange] ([Tabelle])
VALUES ('ArtcodeTemp')
-- setting the timestamp
delete from [dbo].[Artcode_LastChange] where Tabelle = 'Artcode'
TRUNCATE TABLE [dbo].[Artcode]
INSERT INTO Artcode
(Ordnung, Art_ID, Synonym, Art_ID_Gueltig, Gattung, Art, Autor, Autor_Pos, Name_Deutsch, RLB, RLD, FFH_Anh2, FFH_Anh4, FFH_Anh5, VSR_Anh1, Status_IUCN, Schutz_BNatSchG, Ausgabesperre, Statistiksperre,
Eingabesperre, saP, saP_ABC, saP_BC, saP_ZR, rang, sensu, id_agg, staby, VeraB, VeraD, WnASA, EUBrd, BASVO, BOLD_ID, NAME_DG, fam, id_fam, pruefung, ID)
SELECT Ordnung, Art_ID, Synonym, Art_ID_Gueltig, Gattung, Art, Autor, Autor_Pos, Name_Deutsch, RLB, RLD, FFH_Anh2, FFH_Anh4, FFH_Anh5, VSR_Anh1, Status_IUCN, Schutz_BNatSchG, Ausgabesperre, Statistiksperre,
Eingabesperre, saP, saP_ABC, saP_BC, saP_ZR, rang, sensu, id_agg, staby, VeraB, VeraD, WnASA, EUBrd, BASVO, BOLD_ID, NAME_DG, fam, id_fam, pruefung, ID
FROM ArtcodeTemp
INSERT INTO [dbo].[Artcode_LastChange] ([Tabelle])
VALUES ('Artcode')Nach einem Click auf den Button Export Artcode im Hauptformular öffnet sich ein Fenster wie unten dargestellt.
Mit den Buttons kann man den Inhalt der ausgewählten Tabellen nach jedem Schritt überprüfen.
graph TD;
DTN[<i class="fa-fw fas fa-database"></i> Taxa in DiversityTaxonNames_Plants] -->GUC_TransferTaxa(<i class="fa-fw fas fa-arrow-alt-circle-down"></i> Prozedur GUC_TransferTaxa:<br>Transfer der Daten) --> GUC[<i class="fa-fw fas fa-database"></i> Taxon Tabellen in DiversityCollectionCacheGUC]
GUC -->GUC_Artcode
GUC_Artcode(<i class="fa-fw fas fa-arrow-alt-circle-down"></i> Procedur GUC_Artcode:<br>Transfer aus den Taxon Tabellen in ArtcodeTemp<br><i class="fa-fw fas fa-eye"></i> GUC_ArtcodeTemp<br><i class="fa-fw fas fa-long-arrow-alt-down"></i> <br><i class="fa-fw fas fa-table"></i> ArtcodeTemp)
GUC_Artcode--> ArtcodeTemp[<i class="fa-fw fas fa-table"></i> ArtcodeTemp]
ArtcodeTemp --> GUC_AnpassungArtcodeTemp( <i class="fa-fw fas fa-edit"></i> Prozedur GUC_AnpassungArtcodeTemp:<br>Überarbeitung der Daten in Tabelle ArtcodeTemp<br><i class="fa-fw fas fa-caret-right"></i> Eintrag Art_ID = NameID bei neuen Namen<br><i class="fa-fw fas fa-caret-right"></i> Eintrag Familie<br><i class="fa-fw fas fa-caret-right"></i> Eintrag rang<br><i class="fa-fw fas fa-caret-right"></i> ...)
GUC_AnpassungArtcodeTemp --> Artcode[<i class="fa-fw fas fa-table"></i> Artcode]
Artcode --> SQLite[<i class="fa-fw fas fa-database"></i> SQLite]
Mit einem Click auf den Button Ordner kann man das Verzeichnis in dem die SQLite Datenbank gespeichert ist öffnen. Mit einem geeigneten Tool kann man diese dann öffnen. Die Software selbst stellt hierfür keine Option bereit. Beim Versuch die Datenbank aus dem Programm heraus zu öffnen wird ein entsprechender Fehler angezeigt.
Vor dem Export für GUC müssen die Daten der hierfür relevanten Projekte in der DiversityCollectionCache_BayernFlora aktualisiert werden.
Vor dem Export für GUC müssen die Daten in der Tabelle Artcode aktualisiert werden.
Mit einem Click auf den Button wird die Prozedur TransferToGUC (s. unten) gestartet. Diese Überträgt die Daten aus der Datenbank DiversityCollectionCache_BayernFlora in Abhängigkeit der ausgewählten Optionen in die Tabellen der Datenbank DiversityCollectionCacheGUC und bereitet diese für den Export auf.
---
title: PROCEDURE TransferToGUC
---
graph TD;
1{ } -->|1| Clear[Clear the export tables]
1 -->|2| Status[Tabelle <br><u>_Status</u><br> füllen]
1 --> |3|Identification[Tabelle <br>_Identification<br> füllen]
1 --> |4|FehlendeTaxa[Daten ohne Code aus <br>_Identification<br> entfernen]
1 --> |5|NACHWEIS[Tabelle <br>NACHWEIS<br> füllen]
FehlendeTaxa --> Identification
Identification --> NACHWEIS
Status --> EintragStatus
NACHWEIS --> Jahresangaben(In NACHWEIS Entfernen der Daten ohne Jahresangaben)
Jahresangaben --> EintragStatus(In NACHWEIS Eintrag des Status)
EintragStatus --> Quellentyp(In NACHWEIS Eintrag des Quellentyp)
Quellentyp --> verbleib_nachname(In NACHWEIS verbleib_nachname eintragen)
verbleib_nachname --> Projekt(In NACHWEIS Projekt eintragen)
Projekt --> VERORTUNG_PUNKT_WKT(In NACHWEIS VERORTUNG_PUNKT_WKT eintragen)
VERORTUNG_PUNKT_WKT --> status_code_lfu(In NACHWEIS status_code_lfu eintragen)
1 --> |6|FUNDORT[Tabelle <br>FUNDORT<br> füllen]
FUNDORT --> TK(In FUNDORT TK eintragen)
TK --> TOPONYM(In FUNDORT TOPONYM eintragen)
TOPONYM --> Hoehe(In FUNDORT Hoehe eintragen)
Hoehe --> LEBENSRAUM(In FUNDORT LEBENSRAUM eintragen)
LEBENSRAUM --> WGS84(In FUNDORT WGS84 eintragen)
WGS84 --> NATURRAUM(In FUNDORT NATURRAUM eintragen)
NATURRAUM --> Landkreis(In FUNDORT Landkreis eintragen)
Landkreis --> naturraum_code_lfu(In FUNDORT naturraum_code_lfu eintragen)
naturraum_code_lfu --> landkreis_code_lfu(In FUNDORT landkreis_code_lfu eintragen)
1 --> |7|SAMMLER[Tabelle <br>SAMMLER<br> fuellen]
Der Zeitbedarf sowie die Zahl der betroffenen Datensätze wird im Log angezeigt
Um die Daten als SQLite zu exportieren einfach auf den Export nach SQLite Button clicken.
Nach einem Click auf den Button TK25 öffnet sich ein Fenster wie unten dargestellt.
Ein Click auf den Button startet die Prozedur TK25.TransferToQuadrant mit den ausgewählten Parameter für das Jahr und den tax. Rang. Diese Prozedur füllt die Tabelle TK25.Quadrant und TK25.Identification.
---
title: PROCEDURE TransferToQuadrant
---
graph TD;
Clear[Clear the export tables] --> Identification[Insert the taxa in table<br><u>Identification</u>]
Identification --> former(Remove the former identifications in table Identification)
former --> year(Remove those before the given year in table Identification)
year --> accepted(Set the synonyms to the accepted names in table Identification)
accepted --> higher(Setting the higher taxa in table Identification)
Identification --> Quadrant[Fill table <br><u>Quadrant</u>]
Um die Daten als Textdatei zu exportieren auf den Export Button clicken. Dadurch wird im Projektverzeichnis eine Datei mit dem Name TK25export.txt erstellt.