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

8,069 post(s)
#17-Feb-18 18:26

Update:

We updated the install files to prevent the build from expiring before the next build is available. The checksums below have been updated, with the old checksums kept for reference. We expect the next build to arrive around Saturday.

9.0.165.3

manifold-9.0.165.3-x64.zip

SHA256: 5fa9c2dd8cc4820fea798f23ffcfb1acfef62f808db4802098d2849fc47aa2b9

SHA256 (February build): 1703f27b551cb9c529a0e3b623b45cc8be5da433f3e920f00283ada0e3bdf8d4

manifold-viewer-9.0.165.3-x64.zip

SHA256: 54dbb26811af5cd7c97c3497e17d8ba32b38970e31d781271fc846df62584a66

SHA256 (February build): 697eb30636b056e6ae523fe29c0b4c09ec99a75a000321e9bab34c7d7ed5b73a

adamw

8,069 post(s)
#17-Feb-18 18:28

Changes

There are new query functions for spatial overlays that can be used as filters for the primary data set:

  • GeomOverlayAdjacentFilter takes a source drawing and an overlay drawing, finds all objects in the source drawing that are adjacent to any object in the overlay drawing, and filters the source drawing leaving only objects which are adjacent to at least one object in the overlay drawing. Unlike the result table of GeomOverlayAdjacent, the result table of GeomOverlayAdjacentFilter contains all fields from the source drawing and no fields from the overlay drawing. GeomOverlayAdjacentFilter also performs faster than GeomOverlayAdjacent.
  • GeomOverlayAdjacentFilterPar computes the same data as GeomOverlayAdjacentFilter but allows using more than one thread.
  • GeomOverlayContainedFilter / Par, GeomOverlayContainingFilter / Par, GeomOverlayIntersectingFilter / Par, GeomOverlayTouchingFilter / Par are analogous to GeomOverlayAdjacentFilter / Par, but use different spatial criteria.

The result tables returned by GeomOverlayXxxFilter / Par functions contain all indexes from the source table and are writable. It is possible to chain calls to these functions as well as calls to SelectionXxx functions. (For example, the following query returns all states touching selected parcels: EXECUTE CALL GeomOverlayTouchingFilter(states, CALL Selection(parcels, TRUE), 0)).

The result tables returned by GeomOverlayXxxFilter / Par and SelectionXxx query functions perform faster when used from multiple threads.

New templates in the Select pane: Geoms Adjacent, Geoms Contained, Geoms Containing, Geoms Intersecting, Geoms Touching. Each template selects data in a drawing using an overlay drawing and the specified criteria. (Note that the meaning of Geoms Contained / Containing is reversed compared to transforms for Overlay Contained / Containing due to the wording.)

New templates in the Transform pane: Geoms Adjacent, Geoms Contained, Geoms Containing, Geoms Intersecting, Geoms Touching. The templates are similar to those in the Select pane and add the objects that would have been selected as a new component, controlling transferred fields.

Queries generated by the Select pane for map layers refer to layer components instead of to their tables.

Queries generated by the Edit Query button in the Select pane ignore the select mode specified in the pane. (The purpose of the query generated by the Edit Query in the Select pane is to show what the system does to apply a specific template and to produce a reasonable starting point for customizing the query further. The code for combining the output of the template detracts from that. We'd also recommend combining multiple selections differently anyway - through saved selections.)

The map window displays a preview for Geoms Adjacent, Geoms Contained, Geoms Containing, Geoms Intersecting, Geoms Touching templates from both the Select and Transform panes. For the transforms, objects that participate in the transform and have matches in the overlay drawing are shown using the regular blue preview color, and objects that participate in the transform but do not have any matches in the overlay drawing are shown using a lighter shade of the blue preview color. (Currently, the accuracy of the preview for Geoms Adjacent and, rarer, for other new templates might be a bit off in that some of the matches might not be picked up and vice versa. This happens because previews operate on simplified versions of the objects. We are going to fix this.)

Web dataports prioritize fetching tiles closer to the center of the requested area whenever possible. This produces a usable picture noticeably faster than fetching tiles in XY or YX order.

Creating new data source for CSV allows forcing all fields to text, specifying whether the first line contains field names, specifying characters used for list delimiter, decimal separator and text qualifier. The defaults for all options are to autodetect their values from file content. It is possible to keep some options on autodetect and set other options to explicit values. If option values conflict, the dataport ignores the value for the less important option (ie, if list separator is set to autodetect and scanning the file discovers that list separator is a comma, the dataport disallows decimal separator to also be a comma).

End of list.

lionel

457 post(s)
#17-Feb-18 23:16

strange , idon't know if i am in a specific context but if you look at the cpature screen i have a drawing that behave like a map . the drawing type of name inside has 2 tabs of names "inside" and "drawing" !!

Can someone explain why i have this ? so we can slide drawing inside another drawing .....need to read the documentation !!

regard's

Attachments:
drawing_with_tab.mxb
drawing_with_tab_like_map.png


join image "Because my dad promised me" interstellar from Manifold: Time by Stephen Baxter. power Math destruction

tjhb

8,227 post(s)
#17-Feb-18 23:30

You are correct. This is a virtual map (or temporary map). See the notes for 9.0.163.1, 9.0.163.8 (or do a forum search on "virtual map"). Also notice the Edit > Save as Map command, which turns the virtual map into a persistent Map component.

I don't know if this is covered in the online documentation yet. Save as Map is covered under the Edit Menu topic. Temporary maps are covered under the Drawings and Images topics (see the headings "Layers in {Drawings|Maps} are Temporary". Also covered in Example: Use a Transform Expression to Create Buffers in a Drawing.

lionel

457 post(s)
#18-Feb-18 00:50

yes there is many "virtual" words use in many new manifold version post ( search word "virtual " in manifold future change log but also in radian ) but howto /why use/create it ? I don't know if the word virtual is use in the same context !! The word to search seem to be "temporary" rather than virtual

  • http://manifold.net/doc/mfd9/example__use_a_transform_dialog_expression_to_create_buffers_in_a_drawing.htm
  • http://www.manifold.net/doc/mfd9/temporary_databases.htm
  • http://www.manifold.net/doc/mfd9/file_-_print_preview.htm
  • http://www.manifold.net/doc/mfd9/images.htm
  • http://www.manifold.net/doc/mfd9/queries.htm "command"

9.0.165.2 The dataport for Enterprise storages supports folders. In addition, all virtual components exposed by an Enterprise storage are put into a special folder.

9.0.165The new File - Print Preview command creates a virtual layout component for the current component that can be adjusted as needed and printed. The Edit - Save as Layout command allows saving virtual layout as a regular, persistent component for future use.

9.0.164.1 The map window supports the File - Print Preview command, which creates a virtual layout component. If the map window displays a virtual map, customizations made to that virtual map are ignored (save the virtual map as a regular component first).

The layout window supports the Edit - Save as Layout command, which saves the virtual layout as a regular component in the opened MAP file. If the MAP file is read-only, the command is disabled. Saving the virtual layout as a regular component selects the created component in the Project pane.

9.0.163.13 The background color edited in the Layers pane is always a property of a map. Opening a drawing, image or labels component and attempting to edit the background color will change the background color of a temporary virtual map and will not write these changes to the component. (This is similar to how altering the opacity of such a component using the Layers pane will not save the change to the component - this is a property of a map.)

9.0.164.3 Copying and pasting virtual components for shared components on Enterprise storages removes internal bookkeeping properties.

9.0.164.2 (Fix) Virtual tables for shared components on Enterprise storages are made read-only. (Attempts to edit always failed, but the read-only nature of the data was not reflected in the table schema and so the table window / map window assumed the components were editable.)

(Fix) Removing a virtual component for a shared component on an Enterprise storage cleans all relevant metadata to avoid re-creating the virtual component on next connection.

9.0.164.1 The map window supports the File - Print Preview command, which creates a virtual layout component. If the map window displays a virtual map, customizations made to that virtual map are ignored (save the virtual map as a regular component first).

The layout window supports the Edit - Save as Layout command, which saves the virtual layout as a regular component in the opened MAP file. If the MAP file is read-only, the command is disabled. Saving the virtual layout as a regular component selects the created component in the Project pane.

9.0.163.15 The Oracle and SQL Server dataports support deleting virtual tables used to expose SDE data.

The Oracle dataport supports renaming and deleting of virtual images created for native Oracle rasters.

The PostgreSQL dataport supports renaming and deleting of virtual images created for native PostgreSQL

9.0.163.13

The background color edited in the Layers pane is always a property of a map. Opening a drawing, image or labels component and attempting to edit the background color will change the background color of a temporary virtual map and will not write these changes to the component. (This is similar to how altering the opacity of such a component using the Layers pane will not save the change to the component - this is a property of a map.)

9.0.163.8A virtual map created by opening a drawing / image / labels and dropping other components into the window from the Project pane can be saved as a persistent map using Edit - Save as Map.

9.0.163.7 (Fix) Database dataports create virtual drawings based on views in addition to tables.

regard's


join image "Because my dad promised me" interstellar from Manifold: Time by Stephen Baxter. power Math destruction

adamw

8,069 post(s)
#19-Feb-18 08:35

"Temporary" and "virtual" aren't the same thing.

In the case of being able to open a drawing and then drop additional layers into the map window that shows the drawing, perhaps "temporary map" would work as well as "virtual map". We will think about maybe changing it.

Here is an example of where something "virtual" cannot really be called "temporary":

9.0.165.2 The dataport for Enterprise storages supports folders. In addition, all virtual components exposed by an Enterprise storage are put into a special folder.

Here the components aren't temporary, they are persistent. But they are virtual in that if you, say, connect to the same database from some other product, you will not see them. You will see a bunch of tables named MFD_XXX with binary data in them. The dataport determines the contents of that binary data and exposes it as components which you can look at and interact with in regular ways. Maybe we should have just omitted the word "virtual" above and just said "components", but it's definitely not "temporary".

adamw

8,069 post(s)
#26-Feb-18 15:29

A heads up: 9.0.165.4 is coming in a few days. We are finishing a pretty substantial addition to analysis.

adamw

8,069 post(s)
#01-Mar-18 12:10

An update:

We updated the install files to prevent the build from expiring before 9.0.165.4 is available. We expect 9.0.165.4 to arrive around Saturday. See the first post.

(Duplicating the message in the first post to make the thread visible.)

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