diff --git a/.travis.yml b/.travis.yml
index 41462d6a5a..49b67b4d5b 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -64,6 +64,7 @@ jobs:
- sleep 10
- sudo systemctl status docker.service
# Pull Docker images required for integration tests
+ - echo "$DOCKER_PASSWORD" | docker login -u "$DOCKER_USERNAME" --password-stdin
- docker pull kartoza/postgis
- ./build.sh integrationStage
# Killing background sleep loop
@@ -84,6 +85,7 @@ jobs:
script:
# Output something every minute lest Travis kills the job
- while sleep 1m; do echo "=====[ still running after $SECONDS seconds... ]====="; done &
+ - echo "$DOCKER_PASSWORD" | docker login -u "$DOCKER_USERNAME" --password-stdin
- mkdir -p build/target
- ./build.sh product -a ${ARCH} -o ${PLATFORM} ${ADDITIONAL_FLAGS} ${PRODUCT}
# Killing background sleep loop
diff --git a/CHANGELOG.md b/CHANGELOG.md
index b5bbb853aa..0a3d8d3336 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -2,6 +2,43 @@
All notable changes to this project will be documented in this file.
See the [change log guidelines](http://keepachangelog.com/) for information on how to structure the file.
+## [Unreleased]
+
+## [4.1.0]
+
+### Added
+
+- Support for selecting multiple files during schema and the data import
+- END-related schemas added in presets
+- Support to remove a single schema from the project view
+- Support to export the source and the transformed data to Shapefiles using GeoTools
+- Support for missing time zone information when parsing timestamps
+- Support for creating a spatial index when writing GeoPackage files
+- Support for Java 8 date/time classes in Groovy
+
+### Changed
+
+- Activated XML pretty printing by default in the writer settings dialog page when exporting XML/GML
+
+### Removed
+
+- xtraserver plugin
+
+### Fixed
+
+- Fix application not starting on macOS
+- Fix duplicate imports of the same schema when the schema locations differ only in the scheme part
+- Fix use of IProxyService to apply proxy configuration in the UI
+- Fix validity check of the hale»connect export dialog
+- Fix loading of projects in case user context is not supported
+- Fix ArcString interpolation handling
+- Fix handling of HTTPS schema locations in schema resolver
+- Fix for failing PostGIS integration tests
+- Fix the last modified check when loading Groovy snippet from file
+- Fix failing of CRS without remarks for geopackage
+- Fix use of correct preferred bundle when loading geometry types
+- Fix to not append time zone information when writing xmlDate
+
## [4.0.0]
### Added
@@ -360,6 +397,8 @@ See the [change log guidelines](http://keepachangelog.com/) for information on h
Changes so far have been documented in the [hale help](http://hale.igd.fraunhofer.de/2.9.4/help/topic/eu.esdihumboldt.hale.doc.user/html/new/2_9_0.xhtml?cp=2_1_0).
+[Unreleased]: https://github.com/halestudio/hale/compare/4.1.0...HEAD
+[4.1.0]: https://github.com/halestudio/hale/compare/4.0.0...4.1.0
[4.0.0]: https://github.com/halestudio/hale/compare/3.5.0...4.0.0
[3.5.0]: https://github.com/halestudio/hale/compare/3.4.1...3.5.0
[3.4.1]: https://github.com/halestudio/hale/compare/3.4.0...3.4.1
diff --git a/README.md b/README.md
index 6e3689e45b..33d1263cac 100644
--- a/README.md
+++ b/README.md
@@ -48,6 +48,7 @@ To contribute please check the [contribution guidelines](CONTRIBUTING.md) and re
* [hale Community Forum](http://discuss.wetransform.to)
* [hale Community Blog](https://www.wetransform.to/category/news/)
* [hale Video Tutorial (4 Minutes)](https://www.youtube.com/watch?v=95Krki4thgs)
+* [hale in-depth Video Tutorial (37 minutes)](https://www.youtube.com/watch?v=BKNMV-Jp9HM)
## License
diff --git a/app/plugins/eu.esdihumboldt.hale.app.cli.commands/META-INF/MANIFEST.MF b/app/plugins/eu.esdihumboldt.hale.app.cli.commands/META-INF/MANIFEST.MF
index cfc3249099..aeb64ea8f6 100644
--- a/app/plugins/eu.esdihumboldt.hale.app.cli.commands/META-INF/MANIFEST.MF
+++ b/app/plugins/eu.esdihumboldt.hale.app.cli.commands/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: hale CLI Default Commands
Bundle-SymbolicName: eu.esdihumboldt.hale.app.cli.commands;singleton:=true
-Bundle-Version: 4.0.0.qualifier
+Bundle-Version: 4.1.0.qualifier
Bundle-Vendor: wetransform GmbH
Bundle-RequiredExecutionEnvironment: JavaSE-1.8
Require-Bundle: eu.esdihumboldt.util.cli;bundle-version="2.9.5",
diff --git a/app/plugins/eu.esdihumboldt.hale.app.cli/META-INF/MANIFEST.MF b/app/plugins/eu.esdihumboldt.hale.app.cli/META-INF/MANIFEST.MF
index d1111d306c..954ebd3506 100644
--- a/app/plugins/eu.esdihumboldt.hale.app.cli/META-INF/MANIFEST.MF
+++ b/app/plugins/eu.esdihumboldt.hale.app.cli/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: hale CLI application
Bundle-SymbolicName: eu.esdihumboldt.hale.app.cli;singleton:=true
-Bundle-Version: 4.0.0.qualifier
+Bundle-Version: 4.1.0.qualifier
Bundle-Vendor: wetransform GmbH
Bundle-RequiredExecutionEnvironment: JavaSE-1.8
Import-Package: eu.esdihumboldt.hale.common.core,
diff --git a/app/plugins/eu.esdihumboldt.hale.app.transform.test/META-INF/MANIFEST.MF b/app/plugins/eu.esdihumboldt.hale.app.transform.test/META-INF/MANIFEST.MF
index 6a43391bda..2cfac466c5 100644
--- a/app/plugins/eu.esdihumboldt.hale.app.transform.test/META-INF/MANIFEST.MF
+++ b/app/plugins/eu.esdihumboldt.hale.app.transform.test/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Transformation Application Tests
Bundle-SymbolicName: eu.esdihumboldt.hale.app.transform.test
-Bundle-Version: 4.0.0.qualifier
+Bundle-Version: 4.1.0.qualifier
Bundle-Vendor: data harmonisation panel
Bundle-RequiredExecutionEnvironment: JavaSE-1.8
Require-Bundle: eu.esdihumboldt.hale.app.transform;bundle-version="2.9.0",
diff --git a/app/plugins/eu.esdihumboldt.hale.app.transform/META-INF/MANIFEST.MF b/app/plugins/eu.esdihumboldt.hale.app.transform/META-INF/MANIFEST.MF
index 3d353f3c55..42ce6da686 100644
--- a/app/plugins/eu.esdihumboldt.hale.app.transform/META-INF/MANIFEST.MF
+++ b/app/plugins/eu.esdihumboldt.hale.app.transform/META-INF/MANIFEST.MF
@@ -2,7 +2,7 @@ Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: Application for command line transformation
Bundle-SymbolicName: eu.esdihumboldt.hale.app.transform;singleton:=true
-Bundle-Version: 4.0.0.qualifier
+Bundle-Version: 4.1.0.qualifier
Bundle-Vendor: data harmonisation panel
Bundle-RequiredExecutionEnvironment: JavaSE-1.8
Require-Bundle: org.eclipse.core.runtime;bundle-version="3.7.0",
diff --git a/build/build.gradle b/build/build.gradle
index e17b8d740e..813313dbfa 100644
--- a/build/build.gradle
+++ b/build/build.gradle
@@ -147,7 +147,7 @@ ext {
'eu.esdihumboldt.hale.ui.feature.linux': ['linux'],
'eu.esdihumboldt.hale.ui.feature.macosx': ['macosx']
]
-
+
/*
* List of bundles that are not platform specific, even if they are detected as such.
*/
@@ -156,9 +156,8 @@ ext {
]
// URL to the directory containing mirrored artifacts (Maven, JRE, ...)
- //artifactsCommit = '6589f561a36b8a6fe4cd6a115fdc892bbf812c68'
- //artifactsMirrorUrl = "https://gitlab.wetransform.to/hale/hale-build-support/raw/${artifactsCommit}"
- artifactsMirrorUrl = "http://build-artifacts.wetransform.to/hale-build-support-96b81f6"
+ artifactsCommit = '6431f1d635126138b32611dcc47467a401448c8e'
+ artifactsMirrorUrl = "https://gitlab.wetransform.to/hale/hale-build-support/raw/${artifactsCommit}"
// Names of zip files containing Java Runtimes (sorted by their respective platform)
jreArtifacts = [
@@ -172,12 +171,14 @@ ext {
'gtk': [
'x86_64': 'OpenJDK8U-jre_x64_linux_hotspot_8u232b09.tar.gz'
]
- ]/*, -- not available right now
+ ], //Make sure when `tar.gz` is extracted then the hirarchy should be `
+ The formatted string function enables users to access attribute values and project variables to create concatenated string values. Enter text in the text field and double click on any available attribute value displayed in the function dialog to add the value. Alternatively press
+The calculate length function computes the length of a given geometry in the source data and
+assigns the resulting value to the target property.
+The aggregate function combines the input source features to create MultiLineString, MultiPoint or MultiPolygon geometries. The aggregate function performs a check to ensure that the input features have the same source CRS. In the cases of input multi geometries, a new multi geometry is created.
+When different input geometry types are aggregated, you will receive a warning in the transformation log but the function will combine the geometries in a generic GeometryCollection.
+In the case of lines the aggregate function tries to combine them to create a MultiLineString in which the individual lines are connected (i.e. end vertex of one line is the start vertex of the next one).
+If this is not possible there is no guaranteed order in the MultiLineString.
+This function is used to create a centroid (or geometric center) for each feature geometry in the source dataset. The resulting
+centroids are mapped to the target property as point features.
+The compute extent function uses the source data geometries to derive the geometric extent and map it to the target geometry.
+Three different options are available for extent computation: Bounding Box, Convex Hull and Union. Visual examples are
+provided below.
+Lines
+The network expansion function creates a buffer around the geometry of the source data and applies it to the target data. The example
+below shows a comparison of the unbuffered source data (left) to the buffered target data (right).
+Spatial joins can join objects from multiple feature types together based on the spatial relationship between their geometries.
+Spatial joins support the relation types contains, covered by, covers, crosses, equals, intersects, overlaps, touches, and within.
+The date extraction function enables users to extract a date from a string type in the source data and assign the value to the target attribute.Example mapping:
+ Ctrl+Space
to access available variables and project variables. The entered values are concatenated to create string values in the target attribute.
+
+
+
+
+
+ IOProvider.execute(ProgressIndicator progress)
and used when
+ * importing multiple schemas or instances. The method is overloaded with
+ * resourceIdentifier because for every file selected by the user a new
+ * resource identifier has to be generated so that every schema
+ * in @link{SchemaServiceImpl} gets a new ID for the selected schema.
+ *
+ * @param progress the progress indicator, may be null
+ * @param resourceIdentifier identifier of the provided resource. Null if a
+ * new resource id needs to be generated.
+ * @return the execution report
+ *
+ * @throws IOProviderConfigurationException if the I/O provider was not
+ * configured properly
+ * @throws IOException if an I/O operation fails
+ * @throws UnsupportedOperationException if the operation to load multiple
+ * files is not supported.
+ */
+ public IOReport execute(ProgressIndicator progress, String resourceIdentifier)
+ throws IOProviderConfigurationException, IOException, UnsupportedOperationException;
+
}
diff --git a/common/plugins/eu.esdihumboldt.hale.common.core/src/eu/esdihumboldt/hale/common/core/io/impl/AbstractImportProvider.java b/common/plugins/eu.esdihumboldt.hale.common.core/src/eu/esdihumboldt/hale/common/core/io/impl/AbstractImportProvider.java
index 1ab9b890fd..1fcffccf3f 100644
--- a/common/plugins/eu.esdihumboldt.hale.common.core/src/eu/esdihumboldt/hale/common/core/io/impl/AbstractImportProvider.java
+++ b/common/plugins/eu.esdihumboldt.hale.common.core/src/eu/esdihumboldt/hale/common/core/io/impl/AbstractImportProvider.java
@@ -74,6 +74,21 @@ public IOReport execute(ProgressIndicator progress)
return super.execute(progress);
}
+ /**
+ * @see eu.esdihumboldt.hale.common.core.io.impl.AbstractIOProvider#execute(eu.esdihumboldt.hale.common.core.io.ProgressIndicator,
+ * java.lang.String)
+ */
+ @SuppressWarnings("javadoc")
+ @Override
+ public IOReport execute(ProgressIndicator progress, String resourceIdentifier)
+ throws IOProviderConfigurationException, IOException, UnsupportedOperationException {
+
+ if (resourceIdentifier == null) {
+ this.resourceIdentifier = generateResourceId();
+ }
+ return super.execute(progress);
+ }
+
/**
* Generate the unique resource identifier.
*
diff --git a/common/plugins/eu.esdihumboldt.hale.common.core/src/eu/esdihumboldt/hale/common/core/io/impl/GZipEnabledImport.java b/common/plugins/eu.esdihumboldt.hale.common.core/src/eu/esdihumboldt/hale/common/core/io/impl/GZipEnabledImport.java
index e23952ca1a..1334e7c60f 100644
--- a/common/plugins/eu.esdihumboldt.hale.common.core/src/eu/esdihumboldt/hale/common/core/io/impl/GZipEnabledImport.java
+++ b/common/plugins/eu.esdihumboldt.hale.common.core/src/eu/esdihumboldt/hale/common/core/io/impl/GZipEnabledImport.java
@@ -64,6 +64,12 @@ public URI getUsedLocation() {
return getLocation();
}
+ /**
+ * @return the wrapped LocatableInputSupplier
+ */
+ public LocatableInputSupplier extends InputStream> getSource() {
+ return source;
+ }
}
/**
diff --git a/common/plugins/eu.esdihumboldt.hale.common.core/src/eu/esdihumboldt/hale/common/core/io/supplier/FilesIOSupplier.java b/common/plugins/eu.esdihumboldt.hale.common.core/src/eu/esdihumboldt/hale/common/core/io/supplier/FilesIOSupplier.java
new file mode 100644
index 0000000000..7db7976c2c
--- /dev/null
+++ b/common/plugins/eu.esdihumboldt.hale.common.core/src/eu/esdihumboldt/hale/common/core/io/supplier/FilesIOSupplier.java
@@ -0,0 +1,175 @@
+/*
+ * Copyright (c) 2021 wetransform GmbH
+ *
+ * All rights reserved. This program and the accompanying materials are made
+ * available under the terms of the GNU Lesser General Public License as
+ * published by the Free Software Foundation, either version 3 of the License,
+ * or (at your option) any later version.
+ *
+ * You should have received a copy of the GNU Lesser General Public License
+ * along with this distribution. If not, see null
+ */
+ public ListGeneral explanation
+
+
+
+
+The example below shows how the length of the geometry contained in the LineString property of the River source dataset
+is calculated and assigned to the length property of the Watercourse target dataset. The function is executed by
+clicking the Finish button.
+
+
+
+ General explanation
+
+
+The aggregate function is often used in combination with the type level merge function. The use of the aggregate function is necessary to combine the geometries to create multi geometries and avoid selecting just one geometry from the merged source geometries.
+
+
+
+
+ General explanation
+
+
+
+
+In the example below, the centroid function was applied to populate the target geometry with the centroids of the source geometry features.
+Note that for mapping centroids the target source has to have a point geometry.
+
+
+
+The picture below shows the result of the centroid function, where for each element of the target source data (left) a centroid was added.
+
+
+
+ General explanation
+
+
+
+
+Bounding Box
+
+The bounding box option maps the smallest rectangle shape that encloses the source data geometries to the target data geometry.
+
+
+
+
+
+Convex Hull
+
+The convex hull option maps the smallest convex shape that encloses the source data geometries to the target data geometry.
+
+
+
+ General explanation
+
+The interior point algorithm finds an interior vertex which is closest to the centroid of the line string.
+
+Areas
+The interior point algorithm computes sections along a horizontal scan line in the interior of the polygon. The final interior point is the midpoint of the widest computed section in the interior of the polygon.
+For properties with multiple geometries, the interior point function selects the first geometry.
+
+ Source:JTS Technical Documentation
+
+ General explanation
+
+
+
+
+Defining the buffer width
+
+The buffer width can be specified either by a plain value, a mathematical expression or a groovy script.
+
+
+
+Plain value
+
+
+To define the buffer size using a plain value, enter the value of the desired buffer size (e.g. 500) in the function dialog.
+
+
+
+Mathematical expression
+
+To apply a mathematical expression, a variable need to be added in the first step so that it can be used in the buffer
+width expression in the second step. In the example below the variable 'width' was added and multiplied by the value 2 to
+create a buffer around the source geometry.
+
+
+
+Groovy script
+
+Similar to the mathematical expression, a groovy script can be applied to create the desired buffer for the target data.
+
+ General explanation
+
+
+Spatial joins are implemented based on the DE-9IM model.
+
+CONTAINS: Every point of the argument geometry is a point of this geometry, and the interiors of the two geometries have at least one point in common. Geometries do not contain their boundary.
+If a geometry A is a subset of the points in the boundary of a geometry B, B.contains(A) = false
.
+CONTAINS is the converse of WITHIN.
+
+COVEREDBY: Every point of this geometry is a point of the argument geometry.
+This predicate is similar to WITHIN but is more inclusive (i.e. returns true for more cases).
+COVEREDBY is the converse of COVERS
+
+COVERS: Every point of the argument geometry is a point of this geometry. This predicate is similar to CONTAINS but is more inclusive (i.e. returns true for more cases). Unlike CONTAINS it does not distinguish between points in the boundary and in the interior of geometries. For most situations, COVERS should be used in preference to CONTAINS.
+COVERS is the converse of COVEREDBY.
+
+CROSSES: The geometries have some but not all interior points in common.
+
+EQUALS: Tests whether this geometry is topologically equal to the argument geometry.
+
+INTERSECTS: The geometries have at least one point in common.
+
+OVERLAPS: The geometries have at least one point each not shared by the other (or equivalently neither covers the other), they have the same dimension, and the intersection of the interiors of the two geometries has the same dimension as the geometries themselves.
+
+TOUCHES: The geometries have at least one point in common, but their interiors do not intersect.
+
+WITHIN: Every point of this geometry is a point of the argument geometry, and the interiors of the two geometries have at least one point in common. The boundary of the geometry is not within the geometry.
+If a geometry A is a subset of the points in the boundary of a geometry B, A.within(B) = false
.
+WITHIN is converse of CONTAINS
+
+Source:JTS Technical Documentation
+
+
+
+
+
+
+ General explanation
+
+
+
+The date format must be specified by the user to achieve the correct result. In the example below the date is specified by month (MM),
+day of month (dd) and year (yyyy).
+
+
+
+ Functions
parameters.
- Note: The functions available in hale studio represent only + Note: The functions available in hale»studio represent only a small subset of possible relations - if you find that you are not - able to express a relation through the given functions, hale studio offers an + able to express a relation through the given functions, hale»studio offers an extension point to integrate additional functions.
There are two basic types of functions, functions that represent @@ -32,7 +32,7 @@
A type relation describes how types from the source schema are to be translated to a type in the target schema.
- The most simple type relation in hale studio is represented by the hale»studio is represented by the Retype function, which expresses that a source and target type are semantically equal. For the transformation this means that for each diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/concepts/project_vars.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/concepts/project_vars.html index 64bec8fbe0..720acc5b1a 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/concepts/project_vars.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/concepts/project_vars.html @@ -19,7 +19,7 @@
Go to Window→Settings and then to Project→Variables - to define project variables from within halestudio. Any variable you + to define project variables from within hale»studio. Any variable you add here is stored in the project when you next save it.
- When loading a source data set in hale studio, the data is partitioned + When loading a source data set in hale»studio, the data is partitioned into instances. Those instances can be inspected in the Source Data view. When a mapping/alignment is defined, the transformation is executed on the diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/concepts/what_is_schema.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/concepts/what_is_schema.html index 00ae10712f..ff92da4344 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/concepts/what_is_schema.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/concepts/what_is_schema.html @@ -21,10 +21,10 @@
- In hale studio we define the schema mapping on the conceptual level, + In hale»studio we define the schema mapping on the conceptual level, between classes/types and properties. For the complete transformation process however, information about the data format is needed. The - approach used in hale studio can deal with both kinds of schemas, + approach used in hale»studio can deal with both kinds of schemas, abstracting a conceptual view for logical schemas, while using the information from the logical schema for the transformation process. For conceptual schemas, no transformation can be applied, but the diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/contributors.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/contributors.html index 4b23da13af..ea41e004d5 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/contributors.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/contributors.html @@ -6,7 +6,7 @@
Thanks to all who contributed to make hale studio what it is!
+Thanks to all who contributed to make hale»studio what it is!
New Groovy Function Features | Groovy Functions help when the functions we - ship with hale studio don't match specific requirements. To make + ship with hale»studio don't match specific requirements. To make them more powerful, we have added several new capabilities. The first of these is to output multiple features from a single Groovy Retype, Groovy Merge or Groovy Join function. You can use this @@ -144,7 +144,7 @@ | ||||||||||||||||||||||||||||||||||||||||||||
Read MS Access Databases | MS Access databases are one of the most
- common formats used in reporting and statistics. In hale studio,
+ common formats used in reporting and statistics. In hale»studio,
you can now use MS Access databases to load source schemas and
source data.
Thanks to the European Environmental Agency for funding this diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_1_0.xhtml b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_1_0.xhtml index 66f4d7def2..7957e76919 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_1_0.xhtml +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_1_0.xhtml @@ -3,12 +3,12 @@ -What's new in hale studio 3.1?+What's new in hale»studio 3.1?-hale studio 3.1 brings a couple of improvements and fixes. These + hale»studio 3.1 brings a couple of improvements and fixes. These are the most notable changes:
Microsoft SQL Server |
- hale studio now supports Microsoft SQL
+ | hale»studio now supports Microsoft SQL
Server as an additional type of database out of the box. This also
includes support for geography and geometry data types.
| @@ -80,7 +80,7 @@ Code lists in SKOS format are in wide use -
not only for Linked Data. Now you can load SKOS resources as code
- lists in hale studio, a SKOS concept represents an individual code.
+ lists in hale»studio, a SKOS concept represents an individual code.
| @@ -95,7 +95,7 @@ value restrictions in a schema, but also bring less safety in respect to validation. To check the data you create in respect to values from code lists you can now simply associate a code list to - a property - hale studio compares your data against the loaded code + a property - hale»studio compares your data against the loaded code list and informs you in case different values are used. @@ -110,7 +110,7 @@ On your source schema you can define
contexts for the mapping that are specified through a condition on
a type or property, or an index of a property. When you have source
- data loaded in hale studio you can now see directly how many
+ data loaded in hale»studio you can now see directly how many
instances and values there are, that match these contexts.
| diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_2_0.xhtml b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_2_0.xhtml index abebd718f7..b718f0d37e 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_2_0.xhtml +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_2_0.xhtml @@ -3,10 +3,10 @@ -What's new in hale studio 3.2?+What's new in hale»studio 3.2?Multiple validators |
| - hale studio's feature to validate exported XML and GML files has + hale»studio's feature to validate exported XML and GML files has been extended. It is now possible to configure multiple validators. Furthermore, a new type of validator, the Project validator has been added which allows validation of the export result based @@ -75,7 +75,7 @@ WFS request pagination support |
| - When loading from WFS sources, hale studio now supports request + When loading from WFS sources, hale»studio now supports request pagination, a capability that was introduced with the WFS 2.0 standard. This allows loading larger datasets from a WFS where previously this may have been limited by a server-side limit of retrievable features @@ -91,8 +91,8 @@ Better UI support for project variables |
| - The use of project variables, a feature that was introduced with hale - studio 3.0, is now easier as several wizards in hale studio have been + The use of project variables, a feature that was introduced with hale»studio 3.0, + is now easier as several wizards in hale»studio have been extended to provide content assistance. Simply press Ctrl+Space when inside a text field and choose the desired variable from a list. The content assistant will take care of the correct syntax. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_0.xhtml b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_0.xhtml index 9b235053fb..bac427c55a 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_0.xhtml +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_0.xhtml @@ -3,13 +3,13 @@ -What's new in hale studio 3.3?+What's new in hale»studio 3.3?
Load and share hale connect transformation projects |
+ Load and share hale»connect transformation projects |
| - hale studio now comes with built-in support for the online - collaboration platform hale connect, where you can share + hale»studio now comes with built-in support for the online + collaboration platform hale»connect, where you can share transformation projects and discuss alignments with your colleagues. You can also browse transformation projects published by others, extend them and share them back publicly or within your organization. @@ -72,7 +72,7 @@ Arbitrary SQL queries as a source for schemas and data |
| - Database support in hale studio was further extended by + Database support in hale»studio was further extended by the possibility to tailor the schema and data import by custom SQL queries. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_1.xhtml b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_1.xhtml index 402feb350d..13dbf74632 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_1.xhtml +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_1.xhtml @@ -3,13 +3,13 @@ -What's new in hale studio 3.3.1?+What's new in hale»studio 3.3.1?
Save transformation projects directly to hale connect |
+ Save transformation projects directly to hale»connect |
| - hale studio extends its integration with the online + hale»studio extends its integration with the online collaboration platform by allowing to save projects directly to - hale connect. This allows for a true online workflow + hale»connect. This allows for a true online workflow where your changes to a project that was saved to or loaded from - hale connect will be saved directly to the remote project + hale»connect will be saved directly to the remote project without the need of another export. You can switch back to an offline workflow at any time by saving your project to a local file on your computer. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_2.xhtml b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_2.xhtml index 38ea3e74d3..2971ee4f04 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_2.xhtml +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_3_2.xhtml @@ -3,13 +3,13 @@ -What's new in hale studio 3.3.2?+What's new in hale»studio 3.3.2?
Improved hale connect integration |
+ Improved hale»connect integration |
| - This release of hale studio improves the integration - with the online collaboration platform hale connect in + This release of hale»studio improves the integration + with the online collaboration platform hale»connect in a couple of ways. Firstly, it is now possible to select which organisation should own an uploaded transformation project for cases where the currently logged-in user is member of more than - one organisation. Furthermore, hale studio now supports + one organisation. Furthermore, hale»studio now supports a relogin with same or different credentials without having to clear the credentials stored in preferences. @@ -57,7 +57,7 @@
| When loading source data, the user is prompted to provide the - CRS of the contained coordinates. hale studio now + CRS of the contained coordinates. hale»studio now facilitates this by providing the content of the srsName attribute (in case of a GML source) or the WKT definition found in the projection file (.prj) that accompanies a Shape @@ -77,7 +77,7 @@ Importing a schema or source data from a Shapefile requires the user to select the encoding of the Shapefile. In cases where the Shape is accompanied by a Codepage file (.cpg), - hale studio can now read the encoding from that file + hale»studio can now read the encoding from that file a prefill the character set selection dialog. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_4_0.xhtml b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_4_0.xhtml index 5a4e8fd00c..c1f6c3c20c 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_4_0.xhtml +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_4_0.xhtml @@ -3,10 +3,10 @@ -What's new in hale studio 3.4?+What's new in hale»studio 3.4?diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_5_0.xhtml b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_5_0.xhtml index 7350998398..a456a6d3e9 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_5_0.xhtml +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/3_5_0.xhtml @@ -3,10 +3,10 @@ -What's new in hale studio 3.5?+What's new in hale»studio 3.5?
| A bit like the Geoserver App-Schema and Xtraserver configuration, it is now also - possible to generate deegree feature store configurations from hale studio alignments. + possible to generate deegree feature store configurations from hale»studio alignments. This feature is currently not available in the command line interface. @@ -53,7 +53,7 @@ GML output partitioning by spatial extent |
| - The GML/XML writer in hale studio already supported several partitioning modes, + The GML/XML writer in hale»studio already supported several partitioning modes, e.g. by Feature Type, or simply by feature count. We have now added support to partition output by spatial extent, using either a custom or a standard tile grid. @@ -70,14 +70,14 @@Support for plugin installation via update sites |
|
- The way to install plugins in hale studio has been improved: plugins can now be installed
+ The way to install plugins in hale»studio has been improved: plugins can now be installed
and updated from within the application via The App-Schema plugin by Geosolutions is the first plugin that uses the new installation - method. Their corresponding update site is configured as a default in hale studio. + method. Their corresponding update site is configured as a default in hale»studio. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/4_0_0.xhtml b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/4_0_0.xhtml index f622fa5534..2822f6fbbe 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/4_0_0.xhtml +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/new/4_0_0.xhtml @@ -3,10 +3,10 @@ -What's new in hale studio 4.0?+What's new in hale»studio 4.0?If you are a user of the hale studio pro plugins, you need to upgrade these as well. + target="_blank">hale»studio pro plugins, you need to upgrade these as well. Please reach out to the Servicedesk to get the new plug-ins. @@ -53,7 +53,7 @@ It doesn't have issues such as 11 character attribute limits, unknown encodings, missing or incomplete projection files, and is very fast to access.- For these reasons, there have been several requests to add GeoPackage to the list of supported formats for hale studio. + For these reasons, there have been several requests to add GeoPackage to the list of supported formats for hale»studio. We have now added a Reader and a Writer. The Writer can create GeoPackages from scratch, including the schema and metadata. This means you can even use an XML schema and then write your data to a GeoPackage. However, the required model transformations to make this work in complex cases are planned for the next release. @@ -71,7 +71,7 @@
|
XPlanung is a standard for all kinds of spatial plans that is currently implemented by thousands of agencies all across Germany.
- To make the work with XPlanGML in hale studio easier, we have added two features - Schema Presets for all releveant XPlanGML versions,
+ To make the work with XPlanGML in hale»studio easier, we have added two features - Schema Presets for all relevant XPlanGML versions,
and a writer that creates XPlanAuszug files without requiring manual configuration.
This writer furthermore supports writing the data to one file per plan object - so you will get a file that has, for example the What's new in hale»studio 4.1?+ +
+ For a full list of changes, please check out the changelog on GitHub + + +To avoid any compatibility issues when using an existing workspace, we recommend starting with a fresh one when you install + hale»studio 4.1.0 + +The development work for this release was co-funded by the European Health and Digital Executive Agency (HaDEA) under Action No 2018-EU-IA-0093. + +
CQL FilterThe Common Query Language (CQL) is used to define expressions - and filters in several parts of hale studio. It can be used to define - conditions on schema elements or to filter instances. hale studio also + and filters in several parts of hale»studio. It can be used to define + conditions on schema elements or to filter instances. hale»studio also supports the extended CQL (ECQL) syntax as defined by Geotools. @@ -218,7 +218,7 @@Example filtersproject provided in the Get started with hale studio guide, using the + alt="command link">Get started with hale»studio guide, using the Transformed Data view.Comparisons@@ -234,7 +234,7 @@Nulldetails.address.city IS NOT NULL Supported filter operationsFollowing is a list of filter operations that have been tested - with hale: + with hale»studio:Equal (=)
@@ -334,7 +334,7 @@
Spatial operations (CONTAINS,BBOX,...)literals defined must rely on source data having a specific reference system that is previously known.Note that spatial CQL filters only work on attributes that are - marked as geometry attributes in hale. It is right now not possible + marked as geometry attributes in hale»studio. It is right now not possible to apply them to parent attributes of geometry attributes directly. ExamplesCONTAINS(areaAttr, POINT(2 0)) @@ -420,7 +420,7 @@Filter functionsUnsupported operations-These are CQL filter operations that have been verified to not work with hale: +These are CQL filter operations that have been verified to not work with hale»studio: GeoPackage Data Export++ The GeoPackage Writer can create GeoPackages from scratch, including the schema and metadata. + You can also use an XML schema and write your data to a GeoPackage, however the writer does not support complex structures. + The XML schema must consist of simple properties or properties that directly use a geometry type. + +
+
+
+
+ + +
+
+
+
+ + +
+
+
+
diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/html_mapping.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/html_mapping.html
index 4f760d9241..de2ee12baa 100644
--- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/html_mapping.html
+++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/html_mapping.html
@@ -15,7 +15,7 @@ + + HTML Mapping Documentationthe example project from the Get started with hale studio + alt="command link">Get started with hale»studio guide is provided as an example.To create the mapping documentation for your project, export the diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/images/geopackage.png b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/images/geopackage.png new file mode 100644 index 0000000000..83f43fa98b Binary files /dev/null and b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/images/geopackage.png differ diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/jdbc.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/jdbc.html index c08e2a309f..6b85d41a50 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/jdbc.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/jdbc.html @@ -6,10 +6,10 @@ Database Export-hale studio writes to databases using JDBC. hale studio + hale»studio writes to databases using JDBC. hale»studio offers support for PostgreSQL and PostGIS databases out of the box, support for other databases can be added through plug-ins. -The database export in this version of hale studio is + The database export in this version of hale»studio is deemed experimental. This means it does not have the full functionality we want to provide for a database export feature. However, within its limits it is functional and may be useful to you. @@ -26,7 +26,7 @@Database Exportidentifier assigned during transformation will be replaced by the auto-generated value.When storing geometries in PostGIS, hale studio will try to detect the + When storing geometries in PostGIS, hale»studio will try to detect the spatial reference system associated to the target column and transform them appropriately. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/mssql.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/mssql.html index e30064fba9..99364439ab 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/mssql.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/mssql.html @@ -7,15 +7,15 @@ MsSQL Server Export- Support for MsSQL Server in hale studio is based on the generic hale»studio is based on the generic Database export based on JDBC, and thus has the - same limitations. For instance hale studio needs the database schema to + same limitations. For instance hale»studio needs the database schema to already exist in SQL server, thus you can only write to database that have already been prepared and loaded as target schema. - hale studio supports writing both geometry and geography spatial data types + hale»studio supports writing both geometry and geography spatial data types of MsSQL Server but if any objects does not contain spatial reference system then (EPSG:4326) will be used as a default reference system. However, within this limit it is functional and may be useful to you. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/sqlite.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/sqlite.html index 46b7a6af77..e23bc6bd2b 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/sqlite.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/sqlite.html @@ -7,13 +7,13 @@ SQLite and SpatiaLite Export- Support for SQLite and SpatiaLite in hale studio is based on the generic hale»studio is based on the generic Database export based on JDBC, and thus has the - same limitations. For instance hale studio needs the database schema to + same limitations. For instance hale»studio needs the database schema to already exist, thus you can only write to files that have already been prepared and loaded as target schema. -The database export in this version of hale studio is + The database export in this version of hale»studio is deemed experimental. This means it does not have the full functionality we want to provide for a database export feature. However, within its limits it is functional and may be useful to you. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/wfs.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/wfs.html index 8a34ef91ac..9b6328c464 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/wfs.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/wfs.html @@ -6,7 +6,7 @@Transactional WFS-hale studio supports publishing your transformed GML data to a WFS with + hale»studio supports publishing your transformed GML data to a WFS with support for transactions. Currently supported are Transactional Web Feature Services following the OGC WFS 1.1.0 or WFS 2.0.0 specifications. There are two different providers for publishing to @@ -25,7 +25,7 @@ Transactional WFSTransactional WFS-The publishing to WFS in this version of hale studio is + The publishing to WFS in this version of hale»studio is deemed experimental. This means it does not have the full functionality we want to provide for a WFS publishing feature. However, within its limits it is functional and may be useful to you. @@ -49,15 +49,15 @@Transactional WFSmessages in the transformation and export reports. There is no automatic recovery, features may have to be deleted manually if they are not desired to be published.- hale studio behaves like this because both transformation and GML + hale»studio behaves like this because both transformation and GML export aim to provide you a result even if there are small errors or inconsistencies. - Target location for the WFS-T export is the POST URL for the - WFS Transaction operation. The hale studio user interface provides a helper to + WFS Transaction operation. The hale»studio user interface provides a helper to determine that URL from the WFS capabilities. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/xml_data.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/xml_data.html index 6baaa56cd6..f6f3c34c6c 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/xml_data.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/xml_data.html @@ -25,7 +25,7 @@ XML Data Export- When writing the transformed data, hale studio will try to find a + When writing the transformed data, hale»studio will try to find a valid XML path to write each of the transformed instances. If there are geometry objects contained in an instance, they are written as a GML geometry if possible. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/xplan_data.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/xplan_data.html new file mode 100644 index 0000000000..c78eed8c3f --- /dev/null +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/export/xplan_data.html @@ -0,0 +1,35 @@ + + + + +XPlanGML Data Export+
+ The support for exporting XPlanGML is covered by the XML Export. The XPlanGML Writer creates XPlanAuszug files without requiring manual configuration.
+ The Writer also supports writing the data to one file per plan object - so you will get a file that has, for example the + +
+
+
+
+ + +
+
+
+
diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/csv.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/csv.html
index ddb29547d5..f08607e977 100644
--- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/csv.html
+++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/csv.html
@@ -7,12 +7,12 @@
+ + CSV Import- Comma separated value (CSV) files can be used as a data source in hale studio, + Comma separated value (CSV) files can be used as a data source in hale»studio, with the schema definition also being derived from the CSV file. General CSV Import Options- When loading a CSV file, hale studio will try to auto-detect the + When loading a CSV file, hale»studio will try to auto-detect the settings for reading the file, i.e. which character is used to separate the values and what the quote and escape characters should be. You can correct the settings manually by choosing other characters diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/geopackage.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/geopackage.html new file mode 100644 index 0000000000..4543e044e4 --- /dev/null +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/geopackage.html @@ -0,0 +1,17 @@ + + + + +GeoPackage Data Import++ hale»studio supports the import of GeoPackages. + The GeoPackage first needs to be imported as schema, and then as data. + + ++ + + diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/gml_data.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/gml_data.html index f9cef3912b..4648ca9153 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/gml_data.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/gml_data.html @@ -21,7 +21,7 @@ GML Data ImportLoad data from a WFS- hale studio offers the possibility to load data based on a WFS GetFeature + hale»studio offers the possibility to load data based on a WFS GetFeature KVP request. You can specify the request URL manually or use the ... button to launch a wizard assisting you in building the URL from the service capabilities. @@ -35,7 +35,7 @@Load data from a WFSWhen loading from WFS sources, hale studio supports request pagination, a capability that + When loading from WFS sources, hale»studio supports request pagination, a capability that was introduced with the WFS 2.0 standard. You can activate or deactivate request pagination on the XML/GML settings page. If activated, the number of features that will be retrieved per request can also be set. @@ -43,7 +43,7 @@ Load data from a WFSEven though pagination was introduced in the WFS 2.0 standard, there are WFS server implementations available that support this feature for WFS 1.1.0 requests as well. If you know that the queried WFS supports this and activate - pagination, hale studio will paginate the requests also for WFS 1.1.0 requests. + pagination, hale»studio will paginate the requests also for WFS 1.1.0 requests.
diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/gml_schema.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/gml_schema.html
index 9cf689b8f3..926c666a90 100644
--- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/gml_schema.html
+++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/gml_schema.html
@@ -17,7 +17,7 @@
GML Application Schema ImportLoad a schema from a WFS- hale studio offers the possibility to load a schema based on a WFS DescribeFeatureType + hale»studio offers the possibility to load a schema based on a WFS DescribeFeatureType KVP request. You can specify the request URL manually or use the ... button to launch a wizard assisting you in building the URL based on the service capabilities. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/jdbc.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/jdbc.html index 1aca765d0a..98080533de 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/jdbc.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/jdbc.html @@ -6,7 +6,7 @@Database Import-Database schemas and data are imported in hale studio using JDBC. hale studio + Database schemas and data are imported in hale»studio using JDBC. hale»studio offers support for Microsoft SQL Server, PostgreSQL and PostGIS databases out of the box, support for other databases can be added through plug-ins. The database import currently has the following known limitations: @@ -53,7 +53,7 @@Data importthose types that are marked as mapping relevant.Before loading the data it is recommended to enable the selection of a sub-set as sample data (First n instances per type), so a - potentially big database is not loaded completely into hale studio just for + potentially big database is not loaded completely into hale»studio just for the analysis and mapping. This can be enabled in the tool bar or the project's source data settings. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/mssql.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/mssql.html index ccdc93378b..4ab1b6cfed 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/mssql.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/mssql.html @@ -7,12 +7,12 @@ MsSQL Server Import- hale studio supports MsSQL Server database (tested version 2012 and 2014) import like generic + hale»studio supports MsSQL Server database (tested version 2012 and 2014) import like generic Database import based on JDBC. Thus has the same limitations. - hale studio supports both geometry and geography spatial data types + hale»studio supports both geometry and geography spatial data types of MsSQL Server but there are some limitations on curved spatial data objects. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/shapefile.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/shapefile.html index c22bd1060d..2acecd8d01 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/shapefile.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/shapefile.html @@ -7,7 +7,7 @@ Shapefile (SHP) Import- Shapefiles can be used as a data source in hale studio, with the + Shapefiles can be used as a data source in hale»studio, with the schema definition also being derived from the Shapefile. Before importing a Shapefile as source data, you have to import it as source schema. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/sqlite.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/sqlite.html index 2882bc2c16..a737a91b04 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/sqlite.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/sqlite.html @@ -7,7 +7,7 @@ SQLite and SpatiaLite Import- Support for SQLite and SpatiaLite in hale studio is based on the generic hale»studio is based on the generic Database import based on JDBC, and thus has the same limitations. For convenience, you can simply select a diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/xls.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/xls.html index bbbb6228eb..a1be5dba56 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/xls.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/xls.html @@ -7,7 +7,7 @@ Excel File (XLS, XLSX) Import- Excel files can be used as a data source in hale studio. The + Excel files can be used as a data source in hale»studio. The schema definition can/should also be derived from this excel file, by using a headline or user input to define attribute names. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/xml_schema.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/xml_schema.html index 8e91b7b816..d5f7e2e0e5 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/xml_schema.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/xml_schema.html @@ -7,7 +7,7 @@XML Schema Import- hale studio supports loading schemas from XML Schema Definition (XSD) + hale»studio supports loading schemas from XML Schema Definition (XSD) files. XML elements and types will be analyzed in a given schema file, as well as in the included and imported additional schemas. Complex properties are supported, as well as cycles, substitutions, groups and diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/xplan_data.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/xplan_data.html new file mode 100644 index 0000000000..efdb041132 --- /dev/null +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/import/xplan_data.html @@ -0,0 +1,24 @@ + + + + +XPlanGML Data Import++ The hale»studio GML import supports XPlanGML. For more + information please see the GML Data Import + + ++ +
+
+
+
diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/spatialite_common.xhtml b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/spatialite_common.xhtml
index abf7fef14e..4dbc8a681d 100644
--- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/spatialite_common.xhtml
+++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/reference/spatialite_common.xhtml
@@ -11,18 +11,18 @@
To support SpatiaLite the
+ + GML Data Import + +mod_spatialite
extension for SQLite must be available. For Windows users the
- extension is provided together with hale studio, for other
+ extension is provided together with hale»studio, for other
operating systems you may find it in your package manager or can
compile it yourself.
- hale studio specifically supports version 3 and 4 of SpatiaLite, but + hale»studio specifically supports version 3 and 4 of SpatiaLite, but should also work with previous versions. Please let us know if you experience any problems working with your files. SpatiaLite on Windows
- hale studio ships with the SQLite extension Resources and Support+ +This section contains a list of links to a wide variety of helpful resources. + + Absolute beginners should start here + +The Getting Started section contains instructions on how to use the hale»studio help and how to navigate the UI. It also contains tutorial sections on core workflows in hale»studio. + + + Search for free text in the online help + + The hale»studio help page offers free text search to help you find the information you are looking for. + + + hale»studio desktop software offers a number of example transformation projects that you can load directly. The example projects contain mappings which use a variety of the functions available in hale»studio. + The example projects are a great way to gain familiarity with common use scenarios.The example projects can be accessed from the Help menu in hale»studio. + + +
+
+ + + + + Watch the introductory webinar + + wetransform offers webinars on challenging topics throughout the year. Register for a webinar on our website. + + + Use the Support Forum + + We offer a support forum where you can post questions and view discussions going on in the user community. + + + Arrange an individual training (remote or on-premise) + + Call us at +49 6151 6290890. Wetransform offers a wide range of trainings and workshops on various topics including INSPIRE, and advanced use of hale»studio. + + + Get a professional support subscription + + A professional support contract can help you to achieve your goals more quickly. We provide complete end-to-end services, alleviating the need to struggle with complex requirements. In addition, we can provide you with the tools and training to do the work yourself. Please contact us at info@wetransform.to for more information. + + + + + diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/define_custom_function.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/define_custom_function.html index 683902af57..5568f9c214 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/define_custom_function.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/define_custom_function.html @@ -6,9 +6,9 @@ Define a custom function-hale studio comes with a set of pre-defined transformation functions + hale»studio comes with a set of pre-defined transformation functions that cover most basic mapping cases. If you need other functionality - the easiest way is to define a custom function directly in hale studio. In a + the easiest way is to define a custom function directly in hale»studio. In a custom function you can use Groovy to determine the output, based on input and parameters, similar to the Groovy script function. The main difference to the Groovy script function is, that with a custom @@ -93,7 +93,7 @@ Specify function behaviorFunction explanation-hale studio generates an explanation for mapping cells that reference specific + hale»studio generates an explanation for mapping cells that reference specific transformation functions. As a last step you have the opportunity to specify how this explanation is created for your custom function. The explanation can be a fixed text, or it can be a template @@ -104,12 +104,12 @@ Function explanationTo support both text and HTML explanations with a single template, - hale studio provides Markdown support using the hale»studio provides Markdown support using the pegdown Markdown processor. - To render the template hale studio uses the hale»studio uses the GStringTemplateEngine. The variables available to you in the template are the following: diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/edit.png b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/edit.png index dc0e3b4097..e946dd4de1 100644 Binary files a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/edit.png and b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/edit.png differ diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/entity_selection.png b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/entity_selection.png index 5c2267836d..680c9cc9f1 100644 Binary files a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/entity_selection.png and b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/entity_selection.png differ diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/function_create.png b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/function_create.png index a1c37fceb8..9fca357259 100644 Binary files a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/function_create.png and b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/function_create.png differ diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/function_select.png b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/function_select.png index 9cc3668b6d..4c0a7ecc02 100644 Binary files a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/function_select.png and b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/function_select.png differ diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/remove.png b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/remove.png index a32ec88532..81ffa7eaa1 100644 Binary files a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/remove.png and b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/images/remove.png differ diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/mapping_schema_elem.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/mapping_schema_elem.html index 3fd11a7332..0a37447396 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/mapping_schema_elem.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/mapping_schema_elem.html @@ -7,7 +7,7 @@ Mapping schema elements- The main purpose of hale studio is of course not to just inspect + The main purpose of hale»studio is of course not to just inspect schemas, but to map the elements of these schemas with the goal of transforming corresponding (geo)data sets. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/type_relations.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/type_relations.html index dd21d089fd..78a70ca2cc 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/type_relations.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/alignment/type_relations.html @@ -90,13 +90,13 @@Conditional relationsIdentify each type relationFor the type correspondences as the next step you need to - identify how they can be expressed as relations in hale. + identify how they can be expressed as relations in hale»studio.
The most simple kind of relation is a 1:1 relation - a correspondence
between a single source and a single target type, where all
information needed to populate a target instance is present in a
single source instance - like in our River/Watercourse example.
- This kind of relation is represented in hale by the hale»studio by the Retype
function. Save the transformation resultIf you have defined a mapping and loaded source data in the - application, hale studio performs the transformation derived from the + application, hale»studio performs the transformation derived from the mapping on the source data. This happens on every change to the mapping, to instantly show the user what consequences his changes have. @@ -31,7 +31,7 @@ Save the transformation resultwork based on a XML target schema.- Supported data export formats in hale studio are: + Supported data export formats in hale»studio are: Transform external dataTo transform your data you don't need to load all of it into - hale studio. Usually it's a better practice to only load a representative + hale»studio. Usually it's a better practice to only load a representative sample of your data, to help you verify the mapping and quickly get feedback on its transformation. Once you have defined the mapping you have the possibility to transform your data without loading it into diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/data/validate_data.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/data/validate_data.html index 0cb7818f6f..9934012ead 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/data/validate_data.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/data/validate_data.html @@ -10,11 +10,11 @@ Validate the transformed datatransformation result to not only follow the schema's structure, but to also meet the other constraints defined by the schema, like mandatory properties or restrictions on property values. -Validation of instances in hale studio currently is supported for XML + Validation of instances in hale»studio currently is supported for XML based schemas. Validation can be done on the exported transformation result or on the transformed instances currently available in the application. -In addition to schema-based checks, hale studio supports validation of the + In addition to schema-based checks, hale»studio supports validation of the exported transformation result with Schematron. To perform Schematron validation, you can add the Schematron validator to the list of validators and configure it when exporting the transformed instances. @@ -35,7 +35,7 @@ Validation of exported dataproduces a report about errors found during the validation and informs you whether the file is valid or not. -Validation inside hale studio+Validation inside hale»studioIf a mapping exists and source data is loaded, each mapping change will trigger the live transformation (if activated). When the transformed data changes, schema-based validation is started @@ -73,10 +73,10 @@ Validation inside hale studioThis kind of validation inside hale studio is very convenient, but may + This kind of validation inside hale»studio is very convenient, but may not be as accurate as the validation on export for some cases. This is due to the fact that the export itself may change the result slightly - from what is available in hale studio. This could for instance be encodings + from what is available in hale»studio. This could for instance be encodings that are only replied when writing certain properties, or values like identifiers that are generated when missing. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/data/working_source_data.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/data/working_source_data.html index 9022571b74..02c3f27765 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/data/working_source_data.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/data/working_source_data.html @@ -8,12 +8,12 @@Working with a source data setThe term source data refers to data according to the source - schema loaded in hale studio. Loading source data therefore always + schema loaded in hale»studio. Loading source data therefore always requires that the corresponding source schema has already been imported.
- Loading source data in hale studio serves to provide feedback on the
+ Loading source data in hale»studio serves to provide feedback on the
current mapping by transforming this data in the application. The Source Data view can be used
to inspect the source data, while the Working with a source data set
You have the possibility to load only a sub-set of your data in
- hale studio, to use it as a sample for the data analysis and transformation
+ hale»studio, to use it as a sample for the data analysis and transformation
debugging. You can enable it in the tool bar or the project's source
data settings. To open the settings use tool bar button highlighted
below: Loading the datachoose the one that applies.- Supported data import formats in hale studio are: + Supported data import formats in hale»studio are: Login- From hale studio you can login to your hale connect account + From hale»studio you can login to your hale»connect account either via the File menu or the Welcome page.
@@ -19,7 +19,7 @@ LoginSave credentials checkbox. Your user name and password will be stored in a secure way. When you store your credentials for the first time, you will need to setup a master password for the secure - storage to protect it against unauthorized use. hale studio + storage to protect it against unauthorized use. hale»studio will query you for this password once every time the application is restarted as soon as the secure store is accessed for the first time. @@ -29,11 +29,11 @@LoginPreferencesYou can edit the stored user name and password in the application - preferences dialog under hale connect. The credentials + preferences dialog under hale»connect. The credentials are saved by clicking Apply or closing the preferences dialog with OK. By clicking Validate credentials you can check whether the entered credentials are accepted by - hale connect. To remove stored credentials press + hale»connect. To remove stored credentials press Clear credentials or choose Log out and clear credentials from the File menu. diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/images/hale_connect_welcome.png b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/images/hale_connect_welcome.png index 6dcdf0267d..64ad36e4b7 100644 Binary files a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/images/hale_connect_welcome.png and b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/images/hale_connect_welcome.png differ diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/loadproject.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/loadproject.html index 073ffc6e56..5b4bba2cea 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/loadproject.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/loadproject.html @@ -2,22 +2,22 @@ -Load a project from hale connect+Load a project from hale»connect- You can open hale connect transformation projects directly from - within hale studio. When you load a project from hale connect, + You can open hale»connect transformation projects directly from + within hale»studio. When you load a project from hale»connect, you can also save any changes you make directly back there. When a - project is loaded from hale connect, a [hale connect] label + project is loaded from hale»connect, a [hale connect] label will be shown in the application title. - To look for available projects online in hale connect, use the + To look for available projects online in hale»connect, use the File→Open Alignment Project command and switch - to the From hale connect tab. In case you have not logged into - hale connect before, you can use the Login button on + to the From hale»connect tab. In case you have not logged into + hale»connect before, you can use the Login button on the screen shown below to log in.
@@ -37,7 +37,7 @@
Load a project from hale connectTo continue, select the project you want to open from the list, and - press Finish twice to download the project into hale studio. + press Finish twice to download the project into hale»studio. \ No newline at end of file diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/shareproject.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/shareproject.html index ceaa401f6a..14fb99699d 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/shareproject.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/haleconnect/shareproject.html @@ -9,23 +9,23 @@Publishing a projectThere are two ways to publish a transformation project on - hale connect: + hale»connect: On the first screen of the wizard you are asked to provide the project @@ -33,21 +33,21 @@ Publishing a projectOn the next page you are requested to provide the export destination. - In case you have not logged into hale connect before, you can + In case you have not logged into hale»connect before, you can use the Login button on the screen shown below to log in. - You can choose to either create a new project on hale connect + You can choose to either create a new project on hale»connect or update an existing one. In case the currently opened project - was loaded from hale connect, updating the loaded project + was loaded from hale»connect, updating the loaded project will be selected by default. You must also choose whether you will be the owner of the uploaded - project on hale connect or one of your organizations. You must + project on hale»connect or one of your organizations. You must select which of the organisations that you belong will own the uploaded project via the dropdown. Note that only the first option is available in cases where you are not allowed to add projects in the name of any of @@ -61,11 +61,11 @@ OptionsEnable versioning? |
- Enables versioning of the hale connect transformation project. |
+ Enables versioning of the hale»connect transformation project. |
Allow public access? |
- If selected, the created or updated project will be publicly available on hale connect. |
+ If selected, the created or updated project will be publicly available on hale»connect. |
Include web resources? |
@@ -74,7 +74,7 @@ OptionsExclude source data? |
- If selected, no source data will be uploaded to hale connect. This option is
+ If selected, no source data will be uploaded to hale»connect. This option is
enabled by default to prevent the inadvertent upload of large datasets.
|
Saving your work- hale studio allows you to save your mapping, together with the + hale»studio allows you to save your mapping, together with the configuration which schemas and source data sets are used in an alignment project. The project also includes additional settings, e.g. the list of mapping relevant types and the map styles. You can @@ -40,7 +40,7 @@ Saving your workUsing INSPIRE GML data modelsexchange formats for INSPIRE. One application of those exchange formats is the provision of data through INSPIRE Download services.
- To use an INSPIRE GML data model in hale studio all you have to do is
+ To use an INSPIRE GML data model in hale»studio all you have to do is
loading the corresponding GML Application Schema as source or target
schema (see Loading
and browsing schemas). Using INSPIRE GML data modelshref="https://inspire.ec.europa.eu/data-specifications/2892" target="_blank">https://inspire.ec.europa.eu/data-specifications/2892 -hale studio provides some pre-defined schema locations you can choose + hale»studio provides some pre-defined schema locations you can choose from - currently the INSPIRE schemas for Annex I, II and III in versions 3.0 and 4.0 are listed:
@@ -44,7 +44,7 @@ Using INSPIRE GML data modelstarget="_blank">http://inspire.ec.europa.eu/draft-schemas/ (Draft schemas)The schemas available there are not meant for download - instead their URLs should be used to load them into - hale studio (e.g. by browsing the repository and using "Copy Link + hale»studio (e.g. by browsing the repository and using "Copy Link Location" for a schema file to copy its URL to the clipboard and further providing it in "From URL" when importing a schema). @@ -53,7 +53,7 @@ Code listsThe INSPIRE data models make heavy use of code lists. A lot of these code lists are provided through the INSPIRE - code list register. With hale studio you can easily load them to use them + code list register. With hale»studio you can easily load them to use them for a convenient selection from the available values. In the code list import, select "From INSPIRE registry" to download the current list of code lists and select a code list to load into the diff --git a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/schema/load_browse_schema.html b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/schema/load_browse_schema.html index 8f1729bb5e..4c375b19a2 100644 --- a/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/schema/load_browse_schema.html +++ b/doc/plugins/eu.esdihumboldt.hale.doc.user/html/tasks/schema/load_browse_schema.html @@ -10,7 +10,7 @@Loading and browsing schemasstart with the creation of a mapping you have to determine what the source and target schemas are.- Loading a schema in hale studio provides you with the possibility to + Loading a schema in hale»studio provides you with the possibility to browse the schema in the Schema Explorer and to get detailed information on the defined types and their properties. @@ -50,7 +50,7 @@ Target schemaSupported schema formats- hale studio supports the following formats for schema import: + hale»studio supports the following formats for schema import:
|