GeoTools
  1. GeoTools
  2. GEOT-376

ExpressionBuilder cannot parse bbox

    Details

    • Type: Bug Bug
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 2.1.M0, 2.1.M1, 2.1.M2
    • Fix Version/s: 2.7-M0
    • Component/s: main
    • Labels:
      None
    • Environment:
      Udig 0.7.RC3 Selection Tool, Windows XP

      Description

      The Selection tool allows users to create a filter using a bounding box on screen, and to edit the Filter in a text field.

      The tool progamatically creates the following:
      [ the_geom bbox POLYGON ((170.3242645263672 -46.868011474609375, 170.3242645263672 -39.650882720947266, 175.37625122070312 -39.650882720947266, 175.37625122070312 -46.868011474609375, 170.3242645263672 -46.868011474609375)) ]

      I assume this is the result of a toString() on the generated Filter.

      This text is not parsed back into the system, say when the user changes (170.3242645263672 to 170.0):

      The following error message is produced:

      cntry00
      ^
      Encountered "bbox" at line 1, column 12.

      Was expecting one of:

      <AND> ...

      <OR> ...

      <EQ> ...

      <NEQ> ...

      <GT> ...

      <LT> ...

      <GTE> ...

      <LTE> ...

      "]" ...

      "+" ...

      "-" ...

      "*" ...

      "/" ...

      "(" ...

        Issue Links

          Activity

          Hide
          Jody Garnett added a comment -
          The above error message references the featureType name.

          I am probably going to need to ask for the Query concept of a getHandle(), udig Users may rename a Layer to any name they want, passing this name in as a handle would allow the error messages to be expressed in user's terms.

          Darn - the error message is correctly talking about the FeatureType. I really need FeatureType metadata so I can give the FeatureType its proper title.

          I have this information on the udig side of the fense - it will have to wait for geotools to adopt an approach for metadata.
          Show
          Jody Garnett added a comment - The above error message references the featureType name. I am probably going to need to ask for the Query concept of a getHandle(), udig Users may rename a Layer to any name they want, passing this name in as a handle would allow the error messages to be expressed in user's terms. Darn - the error message is correctly talking about the FeatureType. I really need FeatureType metadata so I can give the FeatureType its proper title. I have this information on the udig side of the fense - it will have to wait for geotools to adopt an approach for metadata.
          Hide
          Andrea Aime added a comment -
          Hummm... we have CQL and ECQL these days... time to deprecate ExpressionBuilder and remove it from the sources after we cut 2.7.0?
          Show
          Andrea Aime added a comment - Hummm... we have CQL and ECQL these days... time to deprecate ExpressionBuilder and remove it from the sources after we cut 2.7.0?
          Hide
          Jody Garnett added a comment -
          Actually Andrea that was already done (remove ExpressionBuilder) ages ago.

          The only expression builder left is my StyleBuilder/ExpressionBuilder experiment, which has nothing to to with parsing.
          Show
          Jody Garnett added a comment - Actually Andrea that was already done (remove ExpressionBuilder) ages ago. The only expression builder left is my StyleBuilder/ExpressionBuilder experiment, which has nothing to to with parsing.

            People

            • Assignee:
              Unassigned
              Reporter:
              Jody Garnett
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: