diff --git a/nodes/SegmentCoverageAnalyzer/src/org/unina/spatialanalysis/RouteStepAnalyzer/RouteStepAnalyzerNodeDialog.java b/nodes/SegmentCoverageAnalyzer/src/org/unina/spatialanalysis/RouteStepAnalyzer/RouteStepAnalyzerNodeDialog.java index 8101c46..3cfc6b3 100644 --- a/nodes/SegmentCoverageAnalyzer/src/org/unina/spatialanalysis/RouteStepAnalyzer/RouteStepAnalyzerNodeDialog.java +++ b/nodes/SegmentCoverageAnalyzer/src/org/unina/spatialanalysis/RouteStepAnalyzer/RouteStepAnalyzerNodeDialog.java @@ -2,10 +2,14 @@ import java.awt.Label; +import javax.swing.ToolTipManager; + import org.knime.core.node.defaultnodesettings.DefaultNodeSettingsPane; import org.knime.core.node.defaultnodesettings.DialogComponentFileChooser; +import org.knime.core.node.defaultnodesettings.DialogComponentNumberEdit; import org.knime.core.node.defaultnodesettings.DialogComponentString; import org.knime.core.node.defaultnodesettings.DialogComponentStringSelection; +import org.knime.core.node.defaultnodesettings.SettingsModelIntegerBounded; import org.knime.core.node.defaultnodesettings.SettingsModelString; /** @@ -22,13 +26,26 @@ */ public class RouteStepAnalyzerNodeDialog extends DefaultNodeSettingsPane { - + private static final String MIN_TIME_TOOLTIP = "" + + "This value (seconds) is used to determine wether two subsegquent visit to the same" + + "
visit to the same segment should be considered as distinct.
" + + "
Visits that are less than this time apart from the last valid visit will be discarded.
" + + ""; /** * New dialog pane for configuring the node. The dialog created here * will show up when double clicking on a node in KNIME Analytics Platform. */ protected RouteStepAnalyzerNodeDialog() { super(); + + ToolTipManager.sharedInstance().setDismissDelay(15000); + + SettingsModelIntegerBounded minTimeBetween = RouteStepAnalyzerNodeModel.createMinTimeSettings(); + DialogComponentNumberEdit minTimeSelector = new DialogComponentNumberEdit(minTimeBetween, "Ignore all visits that are less than this value(seconds) away from the last one : ", 10); + minTimeSelector.setToolTipText(MIN_TIME_TOOLTIP); + minTimeBetween.setEnabled(true); + addDialogComponent(minTimeSelector); + } } diff --git a/nodes/SegmentCoverageAnalyzer/src/org/unina/spatialanalysis/RouteStepAnalyzer/RouteStepAnalyzerNodeFactory.xml b/nodes/SegmentCoverageAnalyzer/src/org/unina/spatialanalysis/RouteStepAnalyzer/RouteStepAnalyzerNodeFactory.xml index d4a85f0..79fe751 100644 --- a/nodes/SegmentCoverageAnalyzer/src/org/unina/spatialanalysis/RouteStepAnalyzer/RouteStepAnalyzerNodeFactory.xml +++ b/nodes/SegmentCoverageAnalyzer/src/org/unina/spatialanalysis/RouteStepAnalyzer/RouteStepAnalyzerNodeFactory.xml @@ -24,9 +24,9 @@
  • destination_id, the OSM id of the destination node.
  • tags, the OSM tags associated to the ways to which the origin and destination nodes both belong.
  • the_geom, a String representation of a route formatted as WKT Linestring.
  • - The best way to obtain such a table from a specific route is using the Map Matcher Node of the - KNOT toolkit. + The best way to obtain such a table is using the Map Matcher Node of the + KNOT toolkit. A table containing the following information: