Subscribe to this thread
Home - Cutting Edge / All posts - Manifold System 9.0.174.4
adamw


9,738 post(s)
#19-Jul-21 12:59

9.0.174.4

Here is a new build.

manifold-9.0.174.4-x64.zip

SHA256: 0c7200e78c6c464b2b9e3fe57e806cea5f3aed878ab4de353ff4522a44f75791

manifold-viewer-9.0.174.4-x64.zip

SHA256: 7046c46eb4390f37ec189fec08035f06c149aacf05135e51f3a20c55029661bb

This build contains several significant improvements for the query engine as well as improvements for GDB and LAS. There were some adjustments to our development plans with several new features related to all our products being given priority. We will see these new features in the coming weeks.

adamw


9,738 post(s)
#19-Jul-21 13:04

Changes

Support for LAS / LAZ is updated to 3.4.3. This fixes several bugs in encoding and decoding.

(Fix) Reading LAS files with extra field values no longer sometimes fails.

ESRI FILE GDB modules are updated to 1.5.2.308 (64-bit modules only, the new version of the ESRI SDK does not contain 32-bit modules, so they continue to be 1.5.1.253). This fixes a couple of issues which occur pretty rarely.

The GDB dataport attempts to work around a frequent issue that occurs in geodatabases created by late versions of ArcGIS Pro, that makes a newly created table fail to register completely. The dataport examines the state of the geodatabase and if the table has been created and is operable, reports that the table has been created and marks it in the metadata to execute additional logic on the side of Manifold that compensates for the table not being registered completely in the geodatabase.

The GDB dataport no longer reports indexes on tables returned by the FILE GDB modules as BTREExxx, as they can only be efficiently used to search for individual records, with other operations being unoptimized. This lets the query engine plan around not having these indexes instead of being tricked into using them with subpar results. Built-in indexes on the OBJECTID field continue to be reported as BTREE, with all operations optimized internally by the dataport.

Exporting a drawing to GDB no longer creates a feature data set. (Creating a feature data set for each drawing, eg, when exporting a map with multiple layers, was simply unnecessary. Now we only create a feature class and leave adding the desired feature data sets to the user.)

The query engine allows enclosing identifiers in double quotes ("...", in addition to [...]). We were already allowing enclosing identifiers in double quotes in the ODBC driver, because double quotes are the default for many tools. The change extends this to work for queries ran interactively or through scripts.

The GeomWithin query function optimizes tests for zero distance.

There are new GeomOverlayWithin / GeomOverlayWithinPar query functions that take a primary drawing, an overlay drawing, and a distance in the coordinate system of the primary drawing, and return all pairs of geoms in the primary drawing and the overlay drawing that are within the specified distance.

There are new GeomOverlayWithinFilter / GeomOverlayWithinFilterPar query functions that take a primary drawing, an overlay drawing, and a distance in the coordinate system of the primary drawing, and return all geoms in the primary drawing for which there is at least one geom within the specified distance in the overlay drawing.

The GeomOverlayXxx (non-topology) query functions skip normalizing geoms whenever possible for performance. This frequently produces a significant performance gain, particularly for cases when the overlaid drawings have many overlaps.

The query engine optimizes unindexed INNER / LEFT / RIGHT joins with a condition of the type: f(a) = b.x (where 'a' and 'b' are tables and 'x' is a field, a very common condition). The performance gains depend on the number of records in the involved tables and are typically really big, similar to the performance differences between indexed and unindexed joins.

(The reason we added the above optimization is that while it is always advisable to build appropriate indexes on fields you are using in queries, this is not always possible or desirable. For example, the table you want to index might reside in a data source that does not support indexes, or you might not have permissions to alter the data source. Adding an index on such a table would mean making a copy of it and indexing that, this both takes time and can be inconvenient.)

The query engine allows specifying properties for fields of a table created by SELECT INTO: SELECT ... INTO t (PROPERTY ..., ...) ...; This allows using SELECT INTO with data sources like GDB or GPKG which require additional configuration for geometry fields at the time the table is created (coordinate system, geometry type, whether the geometry is 2d or 3d, etc).

Example use:

--SQL9

SELECT [area][code][name][geom]

INTO [gdb]::[states] (

  PROPERTY 'FieldGeomType.geom' 'area' -- the default would be 'point'

FROM [states];

The query engine puts the final name of the table created by SELECT INTO into the 'createdname' / 'creatednamequoted' pragmas for further statements that might want to create components linked to the created table. This is similar to what is done for CREATE.

End of list.

antoniocarlos

603 post(s)
#19-Jul-21 17:37

Great stuff as always. Could you expand on the development plans note.


How soon?

Dimitri


6,713 post(s)
#20-Jul-21 07:10

Adamw routinely publishes short comments as part of release notes. Read the prior ones and you get the benefit of guidance already published... there's a lot there, so you can see stuff roll out as the builds come out.

If you're interested in more, start engaging by following the tips in the Suggestions page. That naturally gets you more detailed lookahead. Plenty of people are doing that.

Looking over this build's notes I can see lots of things prompted by users who have made really spectacular contributions. Art Lembo, for example, has been a real powerhouse in terms of astute analysis and very productive suggestions. In the "very minor contributions" area, I'm proud to have been one of the agitators for adding double quote " delimiters throughout. :-)

artlembo


3,201 post(s)
#22-Jul-21 16:10

What are the valid FieldGeometryType values? The user manual only give an example for area. Does it support multipoint, multiline, multiarea, etc?

adamw


9,738 post(s)
#22-Jul-21 16:26

Valid geometry type values vary with dataport. For GDB, they are: area, line, point, pointmulti. Other dataports also support: any (and when they support that, it is the default, no need to specify it).

artlembo


3,201 post(s)
#23-Jul-21 14:38

That works perfectly, thanks. BTW, is there any problem in handling multipart polygons like the Hawaiian islands or the Florida Keys?

adamw


9,738 post(s)
#27-Jul-21 14:57

For GDB, all polygons should go into a geometry field with the type set to 'area'. We are not aware of any problems with multipart polygons.

ranger.sean103 post(s)
#20-Jul-21 02:23

Are the improvements to labelling signaled in a previous update still on the cards sometime soon?

Dimitri


6,713 post(s)
#20-Jul-21 07:17

I've always found adamw's guidance to be solid. If you want to get more detailed lookahead than what he's posted, the way to do that is to join the process. That starts by sending in Suggestions. Besides being a positive way to contribute, participating in the process indicates something is important enough to you to ask an engineer for a custom update.

In any event, if you want to talk about something not specifically in a build announcement, please launch a new thread. If it's a follow on to something posted in a different build announcement, post in that thread. That helps keep this thread focused on what the title says, items specific to build 174.4

adamw


9,738 post(s)
#21-Jul-21 12:51

Yes. As I posted in a different thread:

The improvements to labels and some other things have been temporarily pushed away by other priorities. We are doing these improvements in a separate code branch, they will come a little later -- in a couple of weeks.

bdg61 post(s)
#02-Aug-21 13:14

It seems downloads were disabled with the change to to https. I had to copy the URL and add the "s" to get the download to happen.

EDIT: The folders in the zip are empty.

Dimitri


6,713 post(s)
#02-Aug-21 14:32

It seems downloads were disabled with the change to to https.

? Not so. I just visited the Product Downloads page on the web site, clicked on the various download links, and everything worked perfectly.

EDIT: The folders in the zip are empty.

? Not so. I just downloaded the Edge build and the zip file is exactly the way it's supposed to be, containing the portable installation.

bdg61 post(s)
#02-Aug-21 16:42

A chrome thing perhaps? I'll try again after a reboot.

bdg61 post(s)
#02-Aug-21 17:17

Confirmed, clicking links near the top of this page does nothing in Chrome.

Does work in MS Edge.

Dimitri


6,713 post(s)
#02-Aug-21 19:19

Confirmed, clicking links near the top of this page does nothing in Chrome.

Works perfectly for me in Chrome. The links at the top of this thread work fine.

lionel

769 post(s)
#02-Aug-21 20:32

My version of Windows 10 Professionnal is 21H1 build 19043.1110

1) for edge Version 92.0.902.62 (Official build) (64-bit)

no problem , the download work

2) for chrome Version 92.0.4515.107 (Build officiel) (64 bits)

the issue/problem is that the web site server use 2 differents protocols and two name server :

The downloads.shtml page use https (a)but the link inside this page use http protocol (b)

(a) https://manifold.net/updates/downloads.shtml

(b) http://www.manifoldgis.com/updates/working/manifold-9.0.174.4-x64.zip ( not secure)

I mix the 2 for test https://manifold.net/updates/working/manifold-9.0.174.4-x64.zip

the capture is here only to show where i click and show the https

in chrome if i paste in the url http://manifold.net/updates/working/manifold-9.0.174.4-x64.zip

chrome convert it to https://manifold.net/updates/working/manifold-9.0.174.4-x64.zip

so the browser goes and show html page "Resource not found"

in chrome if i paste https://manifold.net/updates/working/manifold-9.0.174.4-x64.zip

chrome return html page " Resource not found"

in chrome if i click on link ....does chrome internally behave like " Resouce not found " ?

Attachments:
edge_download_page1link.png
ressourceNotfound.png


union, doc , APIand most important deepl & keyboard shortcut

Dimitri


6,713 post(s)
#03-Aug-21 07:24

I mix the 2 for test https://manifold.net/updates/working/manifold-9.0.174.4-x64.zip

That does not make sense. You cannot invent links and expect them to work. :-) You have to use the links on the page.

Manifold downloads, by the way, are perfectly secure: they all have SHA hashes.

I hope Francophiles enjoy the resource not found photo, of the famous derailment at Gare Montparnasse.

lionel

769 post(s)
#06-Aug-21 11:47

there is no voodoo in computing and there is an explanation for everything. Attached is a video showing that chrome does not download the file. It works for some people but it doesn't work for others ! This video is original without modifications! it is true that I do not have time to debug the web page ..... later maybe.

Attachments:
chrome_downoad_fail.mp4


union, doc , APIand most important deepl & keyboard shortcut

Dimitri


6,713 post(s)
#06-Aug-21 13:19

Chrome won't download that file on a direct click because the manifoldgis.com link didn't use https. Google Chrome does not allow downloads from http links on an https web site.

There are two ways to get around that:

1. Right click on the button and copy the link, and then open a new tab in Chrome and paste the link. It will then download it.

2. Manifold has temporarily added https to manifoldgis.com. Refresh the page and now it should work. But that's using an old certificate that was not updated as part of the ongoing rectification of the various web sites, so it will be replaced in the next couple of weeks.

lionel

769 post(s)
#02-Aug-21 20:52

https://telecharger.tomsguide.fr/Google-Chrome,0301-22858.html

en français

"Avec sa version 90 Chrome va permettre aux utilisateurs de surfer de façon encore plus sécurisée sur le web. En effet, cette version ouvre automatique les sites en protocole https (même si le lien suivi ne proposait pas ce protocole sécurisé). Pour découvrir les autres fonctionnalités n'hésitez pas à lire notre article"

in english

With its version 90 Chrome will allow users to surf the web even more securely. Indeed, this version automatically opens sites in https protocol (even if the link followed did not offer this secure protocol). To discover the other features please read our article

....Is this the end of the story? ( thread? )

I hope what I write makes sense !


union, doc , APIand most important deepl & keyboard shortcut

dchall8
880 post(s)
#04-Aug-21 18:19

I hope what I write makes sense !

Your English (translation) has improved immensely.

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