Release 2.1.4 (Build 2)
- Layer Properties menu reorganised around Tabs
- Tools>Preferences>GeoRaptor now organised under tabs.
- Pan and zoom percentage (in/out) now a preference. - Search radius (in pixels) now a slider. - Colour used when zooming by rectangle, creating circles etc in spatial view now a property.
- Ability to recalculate a layer's MBR at next redraw.
Handy if applied predicate (where clause) to default SQL or USER_SDO_GEOM_METADATA for geodetic data is set to -180..180/-90..90 but data only in a small area.
- Each layer is now tagged by its geometry type on addition to the view
(based on first row). Icon in layer shows whether layer contains point... polygon data. Icon can be reset in layer properties via user determined sample via discover button and process.
- Polygon fill and point marker colour can now be set to be random or based
on a column in a table. Table column must be varchar2 or numeric. If varchar2 then the string must contain RGBA values as comma separated values in range 0..255 etc. For example, for Red: 255,0,0,255. The alpha value is optional: if not supplied the colour will be solid. If the column is numeric then it should contain a bit shifted colour value: - red component in bits 16-23, - green component in bits 8-15, - blue component in bits 0-7.
- Point marker symbol size can be set via a numeric column in a table in the range 4..72points.
Thus, if you have temperature data in that range (you can normalise via a SQL query or via a view) you can get GeoRaptor to resize its marker symbol according to that data.
- Additional Point Markers have been added
- NONE (no point marker is drawn), - ASTERISK - BOAT - PLUS - FISH - HASH - HOURGLASS - HEXAGON - HEPTAGON - OCTAGON - TICK - PENTAGON
- A spatial query can now be executed against an existing layer in the spatial view.
- Right mouse click menu option added to allow you to execute SDO_INSIDE, SDO_TOUCH etc queries against a layer. Menu reduces depending on whether layer/view is geodetic and depending on type of search feature. Generated SQL can be reviewed before execution. Can "save" result of query as a new Query Layer that is saved between SQL Developer sessings or the existing Graphic Layer that holds the results of the query in memory but cannot be saved between SQL Developer sessions.
- Can now request a layer be permanently drawn using its selection colours. This can be
toggled via a right mouse click menu for the layers in the spatial view or set in the layer preferences dialog.
- Right mouse click menu for recordsets/tables reorganised under sub-menu
- When execting an Identify, a small circle appears showing the search radius (a preference)
- Changes to handling of networks
- Introduction of layer/view coordinate preference as against layer tolerance. Preferences are
now capable of being set independently of USER_SDO_GEOM_METADATA tolerance. Preferences are used when creating geometries (point, line, circle, polygon etc) and in Query themes to limit coordinate numbers to their correct values. Application of preferences respects internationalisation formats.
- Creation of initial SQL for a layer has been modified to include support for all columns in
the host table (not just rownum, sdo_geometry). Mixed case columns and columns with spaces in their names are now supported via quoting. The addition of extra columns in the initial SQL will not affect draw performance as only those columns that are required for drawing are retrieved from the database. However, Identify will return all columns in the defining SQL statement.
- Any predicates added to a layer's initial SQL are honoured in drawing and query.
- SRID Type handling improved across the board, with SRID Type property of spatial layer now
exposed in layer properties dialog.
- Layer/View SRID mismatch bug fixed (apparent when adding new table to a spatial view and eithe r one had a NULL SRID value);
- Layer Properties mislabelling correct;
- Bug with visualisation of attributes after Identify.