Questions in topic: "styling"

Legend creation for a raster map

塞维达 — 星期二2019年10月29日14:24:20 GMT

Hi,

I am trying to create a map in a raster format and write it to MSWord ( using MSWordStyler) however I seem not to be able to create a legend for my map. ( a table holing the name of the attributes visualised on the map and their symbology on the next column) in my case the symbology is easy. just colored circles.

Does any one have an experience with this orhave an idea what transformer to use in order to get this result?

the part of my work space that creates the raster map:

Microstation Symbology from Oracle to PostGIS

FMECO. — Fri，06 Sep 2019 09:07:01 GMT

我们有一个Oracle（定位器）数据库，在那里我们已经存储了通过MicroStation生成的几何对象。数据库还包含与对象的符号系统有关的属性。这些属性是：

- 包含一个数字

的样式列 - 一个角度列，其设置为0对于非点几何形状

- x-scale列，其设置为0 for for for for non-point-geometries

-y刻度列，该列设置为0对于非点几何形状

-a Cellname列，这对于非点几何来空，但包含用于点几何形象的DGN单元/符号学的名称

将这些属性发布到另一个数据库（例如postgis）不是问题。但是，在另一个（GIS）应用程序中读取此数据库时，如何查看相同的符号系统？

是我需要在fme工作区中设置的东西，通过设置这些属性需要的某个位置被解释为特殊的乐观性属性？或者是我需要在GIS应用程序本身内设置的东西？

我甚至如何实现它？

MapTextLabeller介绍

dmitribagh — Mon, 19 Nov 2018 15:31:41 GMT

YouTube演示http://www.youtube.com/watch?v=z-Jm2LG9QkI“target=”#blank“>使用FME和#39的地图标签基础；s MapTextLabeller，第1部分http://www.youtube.com/watch?v=Xk-W8Itjj2Q“target=”#blank“>使用FME和#39的地图标签基础；s MapTextLabeller，第2部分

简介

在FME 2013中，我们添加了一个名为MapTextLabeller的新变压器，这是一个用于自动高质量地图标签的额外成本插件。底层技术由
对于大比例尺地图，该值应该非常低-在为温哥华市制作标签的测试中，我们使用了0.5到5之间的值。

对于小比例尺地图，例如罗宾逊投影中的世界地图，我们使用了更高的值-15000。

对于不列颠哥伦比亚省，1000运行良好。

变压器的下一部分用于指定输入端口和属性。

；图层名称；列将创建输入端口。“The”；属性；列允许用户通过名为"；的附加对话框手动键入属性；编辑属性". Alternatively, attributes can be imported (the "Import" button) from feature types present in the workspace. When the number of attributes is low, this is an easy way to get all the necessary attributes into the transformer. When feature type contains a lot of attributes but only a couple are needed for labelling, it might be easier to type them in.

The most interesting dialog in this transformer shows up when we press the "Configure" button. We will discuss this in the next section. Once all the configuring is done, the transformer and its parameters look something like the following:

Styling and Rules

Once the "Configure" button is pressed, FME passes the relay to MapText. The FME help system contains detailed documentation about the MapText Label Manager; here we only give a quick overview of the Label Manager GUI.

All the layers previously set in the transformer are shown in the Label Manager dialog:

Before we continue, it is important to mention that MapText uses its own terminology, which is different from terminology used in FME. For example, "feature type" in the MapText world is what we call "geometry type" in FME.

One of the first steps we have to take in the Label Manager is to select a correct "Feat(ure) Type" - it can be either a point, a line, an area, or a general 'obstacle', which won't be labelled but will be considered when MapText tries to place labels.

Once the "Feat Type" is selected, it cannot be changed. If the wrong type was chosen, we will have to re-create the entry.

The second step we should take before defining placement rules is styling (the "Style..." button), which opens the following dialog:

Here we specify an attribute or an expression for labelling, the font name and style, font size, and color. If we multiply the font size by the value used in the "Ground Units per Font Point" parameter, we will get the size of the label in ground units.

In the image above, we use font size 9, which, multiplied by 5 as set in the MapTextLabeller main dialog (the image even higher above), makes the label height equal to 45 ground units (meters in this case).

The next step is setting up rules (the "Rule..." button). MapText offers a rich set of rules that allow fine-tuned label placement. Below, you can see the different "Rule Properties" dialogs:

For points

For lines

For areas

After the rules are set, we can check the boxes in the "Label" column. The transformer is now ready for labelling. Each layer can get a unique set of rules, or a rule can be shared between several layers.

Examples

Now let's go through several examples, try some of the MapTextLabeller capabilities, and see how FME can make the labelling process even more powerful. Most examples use data downloaded from the Open Data website provided by the City of Vancouver (http://vancouver.ca/your-government/open-data-catalogue.aspx).

Simple Labelling

The first example takes a Shapefile containing the areas representing Vancouver neighborhoods, and places labels with 25 ground units per font point, using Times New Roman font, size 10 (that makes 250 meter high characters):

The MapTextLabeller creates only 16 labels for 23 neighborhoods.

Note that MapTextLabeller reports how successful the labelling process was by logging the following message:
MapTextLabeller(LabelEZFactory):
**************************************
* Input: Neighborhoods
* Feature Count: 24
* Number of Label Requests: 24
* Number of Placed Labels: 16
* Success rate (%): 66.6667
**************************************
The Strathcona neighborhood is an aggregate feature consisting of two pieces. It requested two labels, and this is why we see "Feature Count" and "Number of Label Requests" equal to 24 instead of 23.

Now we change a single rule in the "Rule Properties" dialog, which allows placing labels on two or more lines:

The MapTextLabeller will create 23 labels for all areas (Strathcona was labelled with a single label):

Download Vancouver Neighborhoods Example.

The Power of FME

Now let's see how FME can help with some situations that cannot be handled directly in the MapTextLabeller. This time we will try labelling the countries of the world.

Amalgamation

If we send an aggregate feature, for example, an archipelago such as the Philippines, to the MapTextLabeller, the transformer will deaggregate it first and label all parts that satisfy transformer settings. In many cases, this cannot be called a desirable result. With the Amalgamator transformer, FME can combine such archipelagos into single features, which will be labelled much better:

With No Amalgamation

With Amalgamation

Character manipulations

With FME, we can pre-calculate how long a label can be and add spaces between characters for better visibility (check the SpaceAdder custom transformer in the world labelling example):

No Spaces Added

Spaces Added:

Similarly, FME can be used for inserting multiple line breaks between words (not included in this example):

Many more manipulations are possible by enriching features with their metric and non-metric properties and changing text strings accordingly.

Second Round of Labeling

The MapTextLabeller does not guarantee that all incoming features will be labelled - it might be simply impossible with some styling/rule settings:
MapTextLabeller(LabelEZFactory):
**************************************
* Input: AVERAGE_COUNTRIES
* Feature Count: 89
* Number of Label Requests: 89
* Number of Placed Labels: 65
* Success rate (%): 73.0337
**************************************

With FME, we can easily find features that weren't labelled and try to run the labelling process again - this time with different settings or with a different attribute. For example, if country names do not fit into some small countries, we can find them using the FeatureMerger transformer (joining countries and the labels and taking the output from the INCOMPLETE port), then we can number them using the Counter transformer and use the attribute with unique numbers for the second round of labelling.

To avoid collisions between the existing labels and the labels being created with the second MapTextLabeller, we should replace the former with bounding boxes and send these bounding boxes into the transformer as obstacles:

Download World Countries Example.

Parallel Processing

Parallel processing allows splitting an FME translation into a series of smaller tasks and executing them simultaneously using multi-core, multi-processor systems. Parallel processing was introduced in FME 2012.

Using parallel processing for making labels shows significantly better performance than running the workspace in a single process, and in some cases, might even be necessary to avoid problems with memory. Configuring groups for parallelism can be challenging due to the nature of map labelling - each group must be spatially independent from the others in order to guarantee that the labels created in different processes won't overlap.

The advantages of parallel processing are especially noticeable on big data volumes. In order to test how the MapTextLabeller works in a parallel environment, we used the Vancouver Parcels dataset. It contains over 100,000 parcels and over 300,000 parcel boundaries, which we try to label in this example. Parcels serve as a source of parcel unique identifiers, which have to be placed in the middle of each parcel at the dominant angle, and parcel boundaries will make labels showing their lengths.

In our tests, a normal workspace with no parallelism on a 32-bit version of FME wasn't able to complete the job and reported an insufficient memory problem:

Insufficient memory available -- error code was 2 - please read the FME Help section 'Adjusting Memory Resources' for workarounds.

64-bit FME finished the process in about one hour (of course, all numbers used here will be different depending on processing power of each particular machine).

When a MapTextLabeller along with a FeatureMerger and Bufferer (used for finding and visualizing boundaries that didn't get any labels) were wrapped up into a custom transformer, the workspace with a Moderate level of parallelism and 24 groups represented by Vancouver Neighborhood areas from our first example finished in about 20 minutes on both 32 and 64-bit versions of FME:

Note that you have to use FME 2013 SP1 in order to use the parallel processing option.

Download Vancouver Parcel Labelling Example.

MapTextStyler

Now let's have a look at the following example. We have a Rapid Transit dataset consisting of three layers: Skytrain lines, Skytrain stations, and the Vancouver boundary. Stations are point features, which we replace with circles for better visibility. However, in order to apply point placement rules, we have to send points - not circles - into the MapTextLabeller. As a result, the transformer may create labels that overlap the circles, simply because the MapTextLabeller is not aware of their existence. The MapTextStyler transformer "educates" the MapTextLabeller about the sizes of the features that are passed through it. In the MapTextStyler parameters, we can specify how much space should be left around a point, along a line, or from a polygon boundary, to ensure labels do not touch or overlap other geometries.

Compare these two fragments of the map:

With no MapTextStyler

With MapTextStyle

The example includes two workspaces - one that does not use MapTextStyler, and another that does use it.

Download MapTextStyler example.

Target Format Nuances

In the previous examples, we simply routed our output to the FME Data Inspector, which is among 6 different target systems supported by the MapTextLabeller. The "FME Generic" target works well with the Inspector as well as with the TextStroker transformer, which makes labels suitable for rasterization with the ImageRasterizer. The other five target systems are suitable for making labels for non-FME environments.

The following example again uses the Vancouver Open Data website. This time we try to label Vancouver streets, parks, and the rapid transit system (Skytrain). We send the output to eight different formats, including the 6 target systems, Adobe Geospatial PDF, and a raster.

As in the examples above, we not only create labels, but also prepare their "parent" features for the output, which may include (but not necessarily) setting colors, layers or levels, display order, etc. This makes the examples a bit bigger and more complex; however, it also displays how a complete labelling solution may look.

Due to different natures of CAD and GIS systems and differences in feature styling, the workspaces for target systems are quite different from each other. The part involving the MapTextLabeller, on the other hand, stays the same through all examples - "Target Format" is the only parameter we have to change in order to adjust labels to the requirements of the destination system.

The following table contains thumbnails of all the workspaces used in this example:

DGN (left), DWG (right):

ArcGIS (left), MapInfo (right):

Geomedia (left), PDF (right)

FME Generic + Raster

The workspaces for each particular format are included in the appropriate format sections below. All examples also include the output data.

FME Generic and Raster

This example makes labels according to FME Data Inspector requirements. The workspace sets up colors, replaces points representing Skytrain stations with circles, and replaces polylines representing Skytrain lines with buffered polygons. It includes a TextStroker transformer, which creates polygons from true type fonts because FME cannot rasterize fonts directly. The workspace also creates an _order attribute, which defines the order that features will be rasterized - that is, which feature will be on top of the others.

Data Inspector:

PNG Image:

Here is an interesting detail - the Data Inspector recognizes the font name assigned by the MapTextStyler. If the Inspector receives a text feature with an _ez_font_name attribute containing a font name, it will display the text with the correct font. There is no other way in FME 2013 to use fonts other than the default one, so this trick can be used for any text visualization. Simply create an _ez_font_name attribute and set its value to a correct font name.
Download Vancouver Street Labelling example for Data Inspector and Rasterization (the template includes the output raster in PNG format).

DWG

DWG as a target format works similarly to FME Generic. AutoCAD displays features in the same order as they were written to the file, so it makes sense to sort features before writing (use an AttributeCreator for each layer with the order number and a Sorter). The DWGStyler transformer is used to set colors and fonts.

Download Vancouver Street Labelling example for Autodesk DWG.

DGN

DGN is probably the trickiest target format of all. MicroStation supports different kinds of fonts; however, with the MapTextLabeller it has to use true type fonts. There is also a difference in font handling in V7 and V8.

MicroStation V7

For MicroStation V7, we have to add true type fonts through a special utility within MicroStation called the Font Installer (Menu->Utilities->Install Fonts...). This utility allows a user to control which fonts will be imported into the font resource file (font.rsc, which can be located, for example, here - C:\Program Files (x86)\Bentley\Workspace\system\symb). Through this utility, we can also control the number that will identify the font for FME. With the AttributeCreator transformer we should create a format attribute igds_font and set the font number for each font name used in the MapTextStyler. For example, if in MicroStation V7 we added "Arial Narrow Bold" and set its number to 251, and in the MapTextLabeller we defined a style using "Arial Narrow Bold", then igds_font should also be set to this number. Note that in V7, the font numbers cannot exceed 255.

The DGNStyler transformer can be used for setting colors. In this case, "Color Index" is a better option than "RGB" as it allows using colors pre-set in a seed file.

MicroStation V8

V8 works with fonts quite differently than V7. V8 uses a seed file to store fonts with their numbers. When we set up a project, we should add fonts that we need to the seed file by placing their samples. This will also create a font number. Arial seems to always get the number 1025, and other fonts receive numbers starting from 1024. Then we can inspect the seed file with the FME Data Inspector to get all the numbers, and use them in the workspace by setting igds_font with an AttributeCreator transformer. Of course, before writing a DGN V8 file, we should not forget to select the seed file containing fonts in the Workbench Navigator.

Again, using a DGNStyler transformer with the "Color Index" option is recommended for choosing colors set within a seed file.

Download Vancouver Street Labelling Example for Bently MicroStation V8 (the template includes the output DGN).

MapInfo

The workspace targeting MapInfo does not require ordering control - this should be done directly in MapInfo by arranging layers in "Layer Control" and saving the result within a MapInfo workspace (*.WOR file).

The MapInfoStyler allows setting colors, symbols, and polygon patterns, so this transformer is actively used in our example.

Download Vancouver Street Labelling example for MapInfo (the template includes the output TAB files and the MapInfo Workspace file VancouverStreets.WOR).

ArcGIS

ArcGIS requires minimal setup in FME. Labels should be output as geodb_annotation geometries. All the styling and layer ordering should be performed within ArcGIS and can be saved as a *.MXD file.

Download Vancouver Street Labelling example for ArcGIS (the template includes the output - ArcGISLabels.gdb and ArcGISVancouverLabels.mxd file).

Geomedia

Writing to Geomedia is also pretty simple - styling and ordering should be done within Geomedia. Labels should be written as fm0_text geometries. In "Display Properties" in Geomedia, we may need to select the "Nominal Map Scale" (12,500 for this example).

Download Vancouver Street Labelling example for Geomedia (the template includes the output Geomedia MDB and the workspace .gws file).

PDF

Geospatial PDF can be written using ArcGIS as a target format.

In order to correctly write fonts, the PDF writer should know where it should search for them. This is controlled by "TrueType Font Directories" in the PDF writer parameters in the Navigator. Usually, the path points to C:\Windows\Fonts.

We also should expose the pdf_text_font format attribute on the destination feature type, to which we are going to write the labels, and connect it to the _ez_font_name attribute present on the features entering the writer.

The PDFStyler transformer also can be used for coloring, line styles, and fonts.

Download Vancouver Street Labelling example for Adobe Geospatial PDF (the template includes the ouput PDF).

从ArcSDE阅读造型/样式

sigtill — Thu, 05 Jul 2018 09:12:08 GMT

Is there a way to read styling from ArcSDE? Similar to when you read DWG you get styling also. If not, any workarounds?

点特征类 - 符号系统

anilkb1105 — Fri, 10 Nov 2017 15:26:29 GMT

嗨 @ mark_1spatial

我正在进行中通过创建FME 2016 Workbench（FMW）将Oracle空间数据转换为AutoCAD.DWG格式，我需要为特定点要素类（在我现有的templation.dwg中不可用）创建/定义自己的符号系统/块），FME中有任何选项，我们可以创建/定义自己的符号系统/块，以获取需要在.dwg输出文件中显示的点特征类。

将得到任何帮助。

DXF (or DWG) to XML

FMECO. — Wed, 01 Nov 2017 07:16:27 GMT

Hi,

I'm trying to import a Microstation cell library as symbology in QGIS. I've managed to change the .cel files (the cell library) to a dxf file. I've also managed to convert that dxf file to xml in FME, with just a reader and a writer (no transformers). The translation went succesfull acooording to FME. However, when I import the symbology in QGIS, I get an error:

Incorrect root tag in style: fme:xml-tables.

What am I doing wrong? Should I use some kind of transformer?

I just applied the default parameters/settings when translating. Should I change a setting in order fot the translation to succeed?

在属性中存储CAD Symbology

dheeraj. — Wed, 06 Sep 2017 08:17:10 GMT

Hi,

How can i store color symbology from CAD Layers in an attribute and apply it to layers in File GDB after translation?

Thanks in advance.

pdfstyler处理线型

吉尔曼普利 — Tue, 13 Jun 2017 18:47:53 GMT

It would be really helpful if the PDF Styler could handle more than just dashed lines. For, example, a dashed dot; symbology for waterlines ( -w-w-w-w-) or powerpoles (-p-p-p-), pipelines (-//-//-) etc. Overall it would be awesome if it could read/incorporate ALL autocad linetypes (from a .lin file)

基于属性值的Excel中的样式单元格

erik_jan — 妈,03年4月2017 16:03:30 GMT

基于这个问题（以及答案，以用户友好方式无法实现）：

https：//knowledge.s亚搏在线afe.com/questions/42334/styling-excel-cells-in-the-writer.html

I would like to suggest allowing the Styling options in the Excel writer to take attribute values.

This would allow conditional styling values for different cell values.

FME数据检测器2016 - 返回覆盖源复选框

ebygomm — Mon, 05 Sep 2016 13:19:58 GMT

在FME 2015中，改变显示的绘图样式时，有一个复选框，您可以解除恢复原始值。此功能似乎在2016年缺少，一旦显示已覆盖，就无法恢复。

Create common syle for ArcGIS shapefile

zoe — Tue, 28 Jun 2016 07:47:11 GMT

Hi,

I have tons of styled MapInfo datasets need to transfer to ArcGIS format, and I hope keep these styles automatically in ArcGIS. As there are some styler transformers, such as MapInfoStyler, KMLStyler, is there any way to create common style for ArcGIS shapefile/geodatabase.

Looking forwards to hearing any suggestions.

@takashi I followed your answers to solve many questions, hope and appreciate you may have solution for this question.

Update styler to use SLD files

Marko. — Fri, 03 Jun 2016 11:03:09 GMT

更新或将各种样式的变压器（PDF，MapInfo，CAD等）变为STYLE Manager Super Cramvertor。允许从其他数据集和表以及从JSON和SLD（整个地图样式）和SVG + PNG（个人特征样式）文件导入样式。

诸如操作系统之类的各种代理使用SLD样式文件。例如，如果可以在FME-Color和其他样式字段中转换数据和其他样式字段中可以打开样式文件并转换数据，则OS MasterMap在组织样式时会更少疼痛。如果此信息自动转移到其他写入格式，那么更好。

如果您还可以在样式管理器中预览样式，如点标记和透明度，并且在SVG或PNG格式中打开新的样式标记，那么FME就会在地图方面开始看起来像GIS一样强大创建。如果样式管理器也可以连接到Mapnnik光栅化程序，这将是惊人的。

外部KML样式文件

Arnold_bijlsma. — 星期四，2016年5月5日16:21:38 GMT

< p >有人试图创建一个< >强external Style.kml file that is being referenced by other KML/KMZ files? I have seen several blogs where the KML StyleMap is defined by creating a Style feature, and I've got that working fine. But I've got 500+ KML files (all regionalised etc.), and the result is that each of them has the same StyleMap definitions in the top of the KML. I would like to define all my Style definitions in a separate KML/KMZ file, and each KML file to reference just this file.

The Google KML documentation shows this is possible, and all you need is a line like this:

style.kml#counties

But how to get this in FME? I have been playing around with the kml_style_url_* and kml_target_style_* attributes, but have been unable to crack it, and there doesn't seem to be any documentation on all these kml_* attributes.

如何将KMZ转换的PAPIMARK大小增加到MICROSTATION V7 DGN

jodell — Fri, 29 Apr 2016 21:26:18 GMT

Hi Folks,

New user here so I appreciate your feedback (and understanding). I am working with a KMZ and while I am able to write it to a MicrostationV7 format, it falls in the right place but I am only getting a simple line style as my only feature in place of the Placemarks. I would like to give them style and weight as they are so tiny I can barely see them in my map. Is this possible? Or am I looking at having to work in Microstation to "amp up" the symbology (points and lines).

Thank you for your feedback! Enjoy your day.

htmlreportgenerator - allow for layer colour to be linked to attributes

Marko. — 星期五，2016年4月29日13:26:04 GMT

Currently the HTMLReportGenerator only allows colour change of features through parameters or by the colour picker. It would be amazing to be able to asign colours and transpecnery through attributes so that features can be styled differntly.