Subscribe to this thread
Home - Cutting Edge / All posts - Radian Studio 9.0.158.x
adamw


7,129 post(s)
#01-Feb-17 16:57

9.0.158.x

Converted to a public update.

Changes for 9.0.158.x final build

Changes for 9.0.158.3

Changes for 9.0.158.2

Changes for 9.0.158.1

Dimitri

4,118 post(s)
#02-Feb-17 07:49

Quick update for beta testers who are awaiting a free license before buying. Sales wants to get these out this week. I've encouraged a quicker response since beta testers cannot move on to the working build without a fresh serial number. Here's hoping that will get done sooner.

BerndD
75 post(s)
#16-Feb-17 18:09

Did the new serial numbers go out, yet?


The Future of Spatial Data // www.drahola-technologies.com // www.digiterra.de // www.drahola.mn

Dimitri

4,118 post(s)
#16-Feb-17 19:01

Not a question for this forum. Contact Manifold directly for all business with Manifold.

Dimitri

4,118 post(s)
#17-Feb-17 04:05

Didn't mean to come off harsh... apologies if I did (posting late last night). What I should have written is that I should not have made the comment I did in this forum but instead should have posted it to the beta forum where the original note had appeared. Follow that note and if no results follow up as the note indicates.

Again, sorry for late night posting without circuits necessary for thought fully engaged...

adamw


7,129 post(s)
#08-Feb-17 16:09

9.0.158.1

Changes

(Fix) Opening an SQLITE database with spatial data no longer spams log window with messages about 'mfd_meta' not being found (the messages themselves are harmless and indicate no errors).

(Fix) Transferring WKB data from PostgreSQL to dataports other than PostgreSQL automatically converts EWKB (PostgreSQL extension) to WKB.

(Fix) Tools - Scan Raw Binary File / Scan Raw Text File dialogs write configuration files in new format as requested by RWB / RWT dataports (JSON instead of XML).

(Fix) Importing data from GPKG and similar files correctly waits until all components are discovered. (Previously, the import could miss components like images due to a race with discovery thread.)

(Fix) Map window reloads layers after changes to their table references. (Example: changing the properties of a drawing so that the drawing refers to a different table will automatically refresh the drawing in all opened windows.)

(Fix) Attempting to access a virtual component on a slow data source no longer fails to wait until the data source completes component discovery if that data source has already been opened in the Project pane and slowly populates itself.

(Fix) ODBC driver no longer sometimes fails with an error when asked to return statistics for an index (a fairly rarely used ODBC function).

(Fix) Copy / pasting or importing images from SQLITE / GPKG no longer fails due to wrong metadata.

Activation dialogs no longer suggest to correct proxy server settings on failure.

TerraServer images in MAP files created by 8 are automatically converted to Bing Maps images on migration. TerraServer has been discontinued for some time.

The Project pane context menu for tables includes a command to edit table schema. This allows freely altering tables on data sources which allow some changes only when the table is not used in any running statements (ie, SQLITE disallows dropping an rtree index on a table that is currently being fetched via SELECT - and a table window can keep SELECT opened / re-opened until the window is closed, if the table is long enough).

(Fix) Dropping components from the Project pane into the query builder window ignores folders.

End of list.

adamw


7,129 post(s)
#08-Feb-17 16:11

9.0.158.2

Changes

(Fix) Parsing coordinate system encoded as PRJ / WKT no longer sometimes fails due to a race condition. (The failure requires multiple threads to invoke the parser simultaneously, this may occur, for example, when the same component with the coordinate system encoded as WKT is rendered in multiple windows at the same time.)

(Fix) TIFF dataport correctly parses user-defined ellipsoids.

(Fix) BIL and other exports that produce .MAPMETA write JSON values for local scales and local shifts as numbers. (This is a minor fix, the values were being correctly parsed back even as strings.)

(Fix) SQLITE and GPKG dataports correctly adjust coordinate system for images that use units other than meters or degrees.

(Fix) RWT dataport no longer sometimes misreads the last pixel.

(Fix) MDB and other dataports that use OLE DB no longer sometimes fail on strings ending with double zeros.

MDB, XLS and other dataports based on Jet support runtimes for Access 2010 (ACE 14) and Access 2013 (ACE 15).

XLS export skips fields with binary data like GEOM or TILE.

MDB export creates starter file using the latest version of Jet / ACE installed on the system. Previously, the export was using a copy of a blank MDB file stored in EXT.DLL, this could potentially fail the export if the installed version(s) of Jet / ACE were incompatible with the version used to create the fixed file.

XLS export creates starter file using the latest version of Jet / ACE installed on the system.

DB and WKx exports are removed as outdated, following latest versions of ACE.

(Fix) FLT export no longer requires the exported image to use FLOAT64 pixels (can use pixels of any numeric type). Byte order is switched from MSB to LSB.

BIL dataport recognizes multi-channel data interleaved by band and by pixel.

(Fix) E00 export uses correct padding for pixel values.

E00 dataport is better at reading pixel values that are not correctly padded.

Renamed query functions: GeomBox -> GeomBoundsRect, GeomUnionBoxes -> GeomUnionRects, GeomUnionBoxesPair -> GeomUnionRectsPair, GeomOrtho -> GeomSnapToGrid.

New query function: GeomBoundsRectRotated - takes a geom value and returns minimal enclosing rect as an area. The rect might have a smaller area than the bounding box, because it is not forced to align with XY axes. Transform template: Enclosing Rect, Rotated.

New query function: GeomBoundsCircle - takes a geom value and returns minimal enclosing circle as an area. Transform template: Enclosing Circle.

GeomClip query function allows clipping a line with another line. (Examples: Intersecting 0:0-5:0 with 3:0-8:0 produces 3:0-5:0. Subtracting 3:0-8:0 from 0:0-5:0 produces 0:0-3:0.)

GeomClip query function allows clipping a (multi)point with another (multi)point or a line.

New query function: GeomIntersectLinesPair - takes two lines and returns their intersection points as a (multi)point.

Map window allows refreshing components. The View - Refresh command (F5) refreshes the opened component if it is not map, and all map layers otherwise. The Refresh command in the context menu for layer tab (Ctrl-F5) refreshes the active layer.

End of list.

KlausDE
6,013 post(s)
#08-Feb-17 17:13

Please keep on updating localization files on Github. Probably better than feeding the webside with the english original for every working update.

The first language files on the webside where rather outdated and are removed now. There still is a typo in the example on webside

adamw


7,129 post(s)
#09-Feb-17 07:21

We will be shipping latest UI.TXT in the archive for portable.

I have brought UI.TXT on Github to 9.0.158.2, but we can't rely on that repository, it is restricted to the beta testers. We might create a public repository in the future.

Dimitri

4,118 post(s)
#09-Feb-17 08:01

There still is a typo in the example on webside

What is the example (on which page) and what is the typo?

KlausDE
6,013 post(s)
#09-Feb-17 10:35

On page Localization the example for GERMAN UI.DE.TXT FILE

There are probably some more and please everybody feel free to report errors and improve this community resource.

The corrected version for 9.0.157 is on Github and attached here.

Attachments:
ui.de.txt
Web.jpg

tjhb

7,387 post(s)
#08-Feb-17 22:23

This is really terrific, especially (obviously this is subjective) minimal enclosing rectangle and circle, and even more especially these functions.

GeomClip query function allows clipping a line with another line. ...

GeomClip query function allows clipping a (multi)point with another (multi)point or a line.

New query function: GeomIntersectLinesPair - takes two lines and returns their intersection points as a (multi)point.

These represent extremely helpful upgrades over the built-capacities functions in Manifold 8, it feels like a real treat to have them. Thanks very much for the time and effort you have saved us here, and the extra possibilities opened up.

adamw


7,129 post(s)
#16-Feb-17 16:43

9.0.158.3

Changes

Images stored in MAP files are rendered with bilinear filtering. This improves the visual quality of the images (thin lines no longer sometimes break, thick lines have more stable width, labels are much more legible, staircase effects - particularly with shading - are removed) at a small performance cost.

Images in all file dataports are rendered with bilinear filtering.

Images in imageserver dataport are rendered with bilinear filtering. In addition to improving legibility, this also reduces the amount of data fetched from the server, making the image render noticeably faster.

(Fix) Map window automatically adjusts shading strength according to current zoom level.

The Style dialog for images allows specifying Z scale to use during shading. The specified value is a ratio of Z scale to XY scale, ie, if the image pixels are 5x5 meters and the height is expressed in meters as well, Z scale should be set to 1/5 = 0.2. (In the future, we are going to set this value automatically from the coordinate system.)

(Fix) Map window no longer sometimes blinks multiple times or closes dialogs after changes to big components.

(Fix) Export to E00 supports exporting images with any pixel type (have to be single-channel).

(Fix) Export to E00 writes pixel stats in the STA section with correct alignment.

(Fix) E00 dataport no longer sometimes fails to construct part of areas.

(Fix) IMG ERDAS dataport no longer sometimes reverses channels for 1-bit / 2-bit / 4-bit multi-channel images.

(Fix) ADF, TIFF and other dataports correctly merge image registration data (local offset / local scale) into coordinate system.

CSV dataport has been reworked to perform significantly faster.

CSV dataport allows text values to contain quotes escaped as double quotes. CSV export automatically doubles quotes in string values.

CSV dataport automatically detects Unix and Mac line ends in addition to Windows line ends.

CSV dataport automatically detects delimiter using the following list: , (comma), (tab), ; (semicolon), : (colon), | (vertical line). (Previously the dataport always used commas.)

CSV dataport automatically detects UTF8 and UTF16 (both low-endian and big-endian) encodings. The default encoding remains ANSI. CSV export uses UTF8 (always).

CSV dataport is better at determining field types and determining whether or not the first line contains field names.

Portable installation package includes default localization file (DEFAULT.UI.TXT).

End of list.

adamw


7,129 post(s)
#16-Feb-17 16:48

Regarding the performance of CSV - here are typical times for 9.0.158.0 vs 9.0.158.3 vs Access Text Driver (ODBC):

9.0.158.0 (native CSV) - Import: ....csv (224.762 sec)

9.0.158.0 (Access Text Driver, using SELECT INTO query) - Query: ... (31.542 sec)

9.0.158.3 (native CSV) - Import: ....csv (15.595 sec)

tjhb

7,387 post(s)
#16-Feb-17 21:14

Regarding the performance of CSV (without testing myself)... that is a 14x speedup!

Images stored in MAP files are rendered with bilinear filtering. ...

Images in all file dataports are rendered with bilinear filtering.

(Fix) Map window automatically adjusts shading strength according to current zoom level.

The bilinear filtering looks fantastic--and it feels just as fast as before. Normalising the vertical scaling has made a similar difference.

So, shaded relief now looks absolutely fantastic--flawless at all scales.

I think it's great you're using bilinear interpolation for smoothing. Bilinear fully respects any and all data, ecumenically. (Bicubic can look finer for RGB pictures, but introduces unwelcome overshoots at sharp transitions, which is especially noticeable for elevation and class-based data.)

Specifically on vertical scaling:

The Style dialog for images allows specifying Z scale to use during shading. The specified value is a ratio of Z scale to XY scale, if the image pixels are 5x5 meters and the height is expressed in meters as well, Z scale should be set to 1/5 = 0.2. (In the future, we are going to set this value automatically from the coordinate system.)

This is fine. It's a manual gearbox, sure, but it makes perfect sense, and it's great to have full control.

I hope that if automation (eventually) maps 1 planar unit to 1 vertical unit, it will still allow us to control exaggeration, by manually entering a Z scale other than 1.0. That will remain useful.

Dimitri

4,118 post(s)
#17-Feb-17 04:17

shaded relief now looks absolutely fantastic

It's much better, agreed but I think it still needs improvement. It still looks too contrasty to me in some settings, like in the image below:

Would be nice to overlay lighter shadows, like partially transparent shading. I know Radian is not supposed to be a GIS but I cannot resist... :-)

Attachments:
bathymetry.png

tjhb

7,387 post(s)
#17-Feb-17 05:25

That's interesting Dimitri, since rereading...

The Style dialog for images allows specifying Z scale to use during shading. The specified value is a ratio of Z scale to XY scale, if the image pixels are 5x5 meters and the height is expressed in meters as well, Z scale should be set to 1/5 = 0.2.

...it's not immediately clear what to do if planar (XY) coordinates are expressed in degrees (or other angular units), but vertical (Z) measurements are expressed in metres (or some other linear measure).

That's generally the case unprojected elevation data, and I think it's why you get far too much contrast in your example (too much for my taste as well).

The elevation image I tested on with a flawlessly impressive result, was (I can't resist either) apples orthogonal to apples, i.e. planar and vertical measures both in metres.

Perhaps we can use a rough but plausible ratio to relating degrees of latitude to metres.

I'm not sure if your data is GEBCO, ETOPOx, or something else (I could probably guess from past posts but I'm being lazy).

Taking 3-second SRTM data as an example, what would happen if we took 1 / (3 seconds ~> 90 metres of latitude) ~> 0.011 (recurring) as a Z scale for unprojected data (at 3 seconds per pixel, mutatis mutandis)?

tjhb

7,387 post(s)
#17-Feb-17 06:27

Similarly for unprojected elevation data at 1 second per pixel, a Z scale of 1 / (1 second ~> 30 metres of latitude) ~> 0.033 (recurring) looks about right.

(I've attached examples using Z=0.033333 and Z=1. Same data.)

(It's Mt. Taranaki.)

Attachments:
SRTM 1s @ Z=0.033333.png
SRTM 1s @ Z=1.0.png

adamw


7,129 post(s)
#17-Feb-17 07:04

Exactly, the way to fix the contrasty image in Dimitri's post is to adjust Z scale. For now, this has to be done manually (for images in lat/lon one has to compute average width / height of a pixel in metric units at the approximate parallel of the image), in the future we will do this automatically and allow manual adjustment.

Dimitri

4,118 post(s)
#17-Feb-17 07:20

Right you both are... here is the image using Z at 0.011

I had tried it with variations on Z but not with enough variations. The particular image is SRTM of some data that I had lying around on my hard disk. It is a really old project and was not imported properly so one of these days I have to try to find the original source and re-import it again.

Attachments:
bathymetry2.png

adamw


7,129 post(s)
#17-Feb-17 07:00

I hope that if automation (eventually) maps 1 planar unit to 1 vertical unit, it will still allow us to control exaggeration, by manually entering a Z scale other than 1.0. That will remain useful.

Yes, of course, we'll allow editing the parameter directly (we'll likely have that parameter be a multiplicative adjustment for the automatically determined scale ratio).

adamw


7,129 post(s)
#20-Feb-17 15:23

9.0.158.x final build

Changes

(Fix) SHP export no longer writes wrong data values for some fields.

ArcGIS REST, TMS, WMTS images are rendered with bilinear filtering.

Oracle GEORASTER images are rendered with bilinear filtering.

(Fix) New Field dialog in table window no longer fails to add a new component via Add Component.

(Fix) Style dialog skips computing field / channel stats for equal intervals and exponential intervals.

End of list.

Manifold User Community Use Agreement Copyright (C) 2007-2017 Manifold Software Limited. All rights reserved.