We are currently looking for a GIS specialist. The job description can be found here:
https://jobs.winterthur.ch/?yid=1755&sid=6k9afr49m011jjoe5rsjb72802
Please apply if you are interested.
About things that happened to me at work.
Thursday, 19 October 2017
Tuesday, 12 September 2017
Warning: An exception occurred in FDO component.
I got the following warning in MapGuide log file:
Warning: An exception occurred in FDO component.
Zeichenfolge ist kein gültiger Ausdruck.
StackTrace:
- MgStylizationUtil.ExceptionTrap() line 231 file SE_ExpressionBase.cpp
The message means "string is invalid expression".
In my case it seems the issue is related to text label style. The text label was originally published using MTEXT as style. Later on - due to a bug in MapGuide - I changed the text style to TEXT. But since I changed TEXT back to MTEXT the message doesn't appear in the log files anymore.
Autodesk Infrastructure MapServer 2017
Warning: An exception occurred in FDO component.
Zeichenfolge ist kein gültiger Ausdruck.
StackTrace:
- MgStylizationUtil.ExceptionTrap() line 231 file SE_ExpressionBase.cpp
The message means "string is invalid expression".
In my case it seems the issue is related to text label style. The text label was originally published using MTEXT as style. Later on - due to a bug in MapGuide - I changed the text style to TEXT. But since I changed TEXT back to MTEXT the message doesn't appear in the log files anymore.
Autodesk Infrastructure MapServer 2017
Thursday, 17 August 2017
File based Industry Model - how to modify views
When you use a file based Map Industry Model (IM) you might want to extend the data model and add attributes to one of the tables. If you are not familiar with databases, SQL and the concept of "table" and "view" this blog post will explain some basic concepts behind Map IMs and also show how you can add attributes to both tables and views.
https://en.wikipedia.org/wiki/View_(SQL)
Nothing prevents you from storing all your data in just one big table. But there are disadvantages to it and therefore data is usually split across multiple tables. Here is more information on why:
https://en.wikipedia.org/wiki/Database_normalization
When you have data across multiple tables you need to combine data in order to get the information you need - "views" are one way to achieve that.
In Autodesk Infrastructure Administrator (AIA) tables and views appear the same at first glance. But if the Data Model was set up properly a view will have a display name ("caption") containing the word "view". Whenever you create a new table or attribute in AIA you need to enter a name but you can also enter a "caption" - a more descriptive name:
The caption will be used in AIA and Map, not the name of the object:
Whenever you need to work directly in the database you first need to find out the name of the table/view. The names are shown in AIA as well - just look below the tree view where the caption and the name of the table/view (in brackets) are displayed:
You will also notice another convention - in a databases a view name often contains "_v_" to indicate that it is a view and not a table.
Example: in WA Industry Model there is a table called: "Fitting" (see screenshot above):
"Fitting" - display name for table "WA_FITTING" shown in AIA and Map
"WA_FITTING" - name of the table in the database (WA indicating that the table belongs to the WA Industry Model)
"Fitting View" - display name for view "WA_V_FITTING" shown in AIA and Map
"WA_V_FITTING" - name of the view in the database
In AIA you can easily add attributes to a table. If you add an attribute you usually want to have the attribute shown on your form as well in order to be able to enter data. So you need to open the form for the table in AIA Form Designer and add the new attribute there as well. In case the new attribute is also needed to style features in your drawing you need to incorporate it in your layer definition.
But layers in Display Models often are based on views and not on tables. In this case adding an attribute to a table is not sufficient - the attribute also needs to be added to the view in question. Now, here is a limitation of AIA - you cannot create or modify an existing view the same way you can create or modify a table. For a view the context menu function "Add attribute" is not available:
In order to do that you need to use a tool called "SQL Sheet" which comes with AIA - we will come to that in a second.
How do you know whether a layer in Display Model is based on a table or on view?
After generating graphics using the Display Model in question you can check either by hovering the mouse on top of the layer name in Display Manager - a flyout will show the layer's data source (table/view name, not the caption) -
or open the StyleEditor for the layer and the table/view name is displayed there as well on the top:
If the name contains "_V_" you can be quite certain its a view.
By the way - the layer name as shown in Display Manager is often different from the table/view names the layer is based on. You have three different names by now:
- the actual table/view name as used in the database
- the caption for a table/view as shown in AIA and Map
- the layer name in DisplayManager
All point to the same thing - a certain table or view - but might have (slightly) different names.
Example - add a new attribute to the Fitting table and also use the attribute when styling the layer in Map. As the layer in Map is based on a view (see screenshot above) we need to modify it as well.
1) add new attribute to table
2) in Form Designer drag and drop attribute to the form
3) save drawing (important!)
4) open SQL Sheet (File menu, choose "SQL Sheet"),
5) choose "SqLite" and your drawing file (containing the file based IM, drawing should not be opened in Map at the same time)
4) in top right corner choose "Views" to get a list of all views in your current IM
5) select the view to modify - WA_V_FITTING - on the right hand side below the list you will see the attributes of the view
6) right-click on view name and choose "Modify View" - in the left side panel the view definition will be shown
CREATE VIEW WA_V_FITTING AS select g.GEOM,g.ORIENTATION, g.FID, a.NAME_NUMBER
from WA_POINT g, WA_FITTING a
where g.FID_ATTR = a.FID
As you can see the view takes data from two tables - WA_POINT and WA_FITTING.
WA_POINT stores the geometry of a feature, WA_FITING stores all attributes which are useful for fittings. We added a new attribute to WA_FITTING earlier. This attribute needs to be added to the view as well.
You can also notice a letter after each table name (g and a) - they are called "alias" in order to shorten then whole expression. Without alias (which could be a word not just a single letter) the statement would read like this:
CREATE VIEW WA_V_FITTING AS select WA_POINT.GEOM,WA_POINT.ORIENTATION, WA_POINT.FID, WA_FITTING.NAME_NUMBER
from WA_POINT, WA_FITTING
where WA_POINT.FID_ATTR = WA_FITTING.FID
The alias or table name is given to indicate from which table a certain attribute comes from (required in cases where the same attribute name is used in more than one table).
Now you only need to add your attribute name (including the alias) - don't forget to add an additional comma between the last attribute and the new attribute:
CREATE VIEW WA_V_FITTING AS select g.GEOM,g.ORIENTATION, g.FID, a.NAME_NUMBER
, a.MA_SIZE
from WA_POINT g, WA_FITTING a
where g.FID_ATTR = a.FID
Attribute name needs to be upper cases.
Click on the green triangle to execute the statement - you will get the following error message:
...
SQL execution error number 0, table WA_V_FITTING already exists
...
We cannot overwrite a view - we have to delete the old one first and re-create it afterwards. Add the following line before the CREATE VIEW statement:
DROP VIEW WA_V_FITTING;
CREATE VIEW WA_V_FITTING AS select g.GEOM,g.ORIENTATION, g.FID, a.NAME_NUMBER
, a.MA_SIZE
from WA_POINT g, WA_FITTING a
where g.FID_ATTR = a.FID
Execute the query again, result should be:
SQL> DROP VIEW WA_V_FITTING
Command executed (0).
SQL> CREATE VIEW WA_V_FITTING AS select g.GEOM,g.ORIENTATION, g.FID, a.NAME_NUMBER
, a.MA_SIZE
from WA_POINT g, WA_FITTING a
where g.FID_ATTR = a.FID
Command executed (0).
If you receive an error message like this:
SQL execution error number 0, no such column: a.MA_SIZE
'CREATE VIEW WA_V_FITTING AS select g.GEOM,g.ORIENTATION, g.FID, a.NAME_NUMBER
, a.MA_SIZE
Did you save your drawing after adding the attribute to your table? If you haven't saved the drawing SQLSheet doesn't seem to "see" the new attribute.
7. close SQL Sheet
8. Close AIA
9. open AIA and reload your drawing, check the view in Data Model tree view - the attribute is now available in the view as well:
Before modifying your data base with SQL Sheet - back up your drawing file.
Tables and views
AutoCAD Map comes with ready-to-use Industry Models. These IMs contain many tables, views, forms, labels and so on. Tables actually store data, views only provide a "view" on one or more tables and do not contain any data. Look here for more details:https://en.wikipedia.org/wiki/View_(SQL)
Nothing prevents you from storing all your data in just one big table. But there are disadvantages to it and therefore data is usually split across multiple tables. Here is more information on why:
https://en.wikipedia.org/wiki/Database_normalization
When you have data across multiple tables you need to combine data in order to get the information you need - "views" are one way to achieve that.
In Autodesk Infrastructure Administrator (AIA) tables and views appear the same at first glance. But if the Data Model was set up properly a view will have a display name ("caption") containing the word "view". Whenever you create a new table or attribute in AIA you need to enter a name but you can also enter a "caption" - a more descriptive name:
 |
| Feature class name and caption |
 |
| List of all tables/views in "Point" - column "Feature Class" shows captions |
Whenever you need to work directly in the database you first need to find out the name of the table/view. The names are shown in AIA as well - just look below the tree view where the caption and the name of the table/view (in brackets) are displayed:
 |
| For a selected item the name and caption is shown in the status bar below the Data model tree view. |
You will also notice another convention - in a databases a view name often contains "_v_" to indicate that it is a view and not a table.
Example: in WA Industry Model there is a table called: "Fitting" (see screenshot above):
"Fitting" - display name for table "WA_FITTING" shown in AIA and Map
"WA_FITTING" - name of the table in the database (WA indicating that the table belongs to the WA Industry Model)
"Fitting View" - display name for view "WA_V_FITTING" shown in AIA and Map
"WA_V_FITTING" - name of the view in the database
In AIA you can easily add attributes to a table. If you add an attribute you usually want to have the attribute shown on your form as well in order to be able to enter data. So you need to open the form for the table in AIA Form Designer and add the new attribute there as well. In case the new attribute is also needed to style features in your drawing you need to incorporate it in your layer definition.
But layers in Display Models often are based on views and not on tables. In this case adding an attribute to a table is not sufficient - the attribute also needs to be added to the view in question. Now, here is a limitation of AIA - you cannot create or modify an existing view the same way you can create or modify a table. For a view the context menu function "Add attribute" is not available:
 |
| For a view "Add Attribute" is not available |
In order to do that you need to use a tool called "SQL Sheet" which comes with AIA - we will come to that in a second.
How do you know whether a layer in Display Model is based on a table or on view?
After generating graphics using the Display Model in question you can check either by hovering the mouse on top of the layer name in Display Manager - a flyout will show the layer's data source (table/view name, not the caption) -
 |
| Layer data source name is shown in fly out for layer in Display Manager |
or open the StyleEditor for the layer and the table/view name is displayed there as well on the top:
 |
| Layer data source name is shown in Style Editor |
If the name contains "_V_" you can be quite certain its a view.
By the way - the layer name as shown in Display Manager is often different from the table/view names the layer is based on. You have three different names by now:
- the actual table/view name as used in the database
- the caption for a table/view as shown in AIA and Map
- the layer name in DisplayManager
All point to the same thing - a certain table or view - but might have (slightly) different names.
Modify an existing view
Example - add a new attribute to the Fitting table and also use the attribute when styling the layer in Map. As the layer in Map is based on a view (see screenshot above) we need to modify it as well.
1) add new attribute to table
2) in Form Designer drag and drop attribute to the form
3) save drawing (important!)
4) open SQL Sheet (File menu, choose "SQL Sheet"),
5) choose "SqLite" and your drawing file (containing the file based IM, drawing should not be opened in Map at the same time)
4) in top right corner choose "Views" to get a list of all views in your current IM
5) select the view to modify - WA_V_FITTING - on the right hand side below the list you will see the attributes of the view
6) right-click on view name and choose "Modify View" - in the left side panel the view definition will be shown
CREATE VIEW WA_V_FITTING AS select g.GEOM,g.ORIENTATION, g.FID, a.NAME_NUMBER
from WA_POINT g, WA_FITTING a
where g.FID_ATTR = a.FID
As you can see the view takes data from two tables - WA_POINT and WA_FITTING.
WA_POINT stores the geometry of a feature, WA_FITING stores all attributes which are useful for fittings. We added a new attribute to WA_FITTING earlier. This attribute needs to be added to the view as well.
You can also notice a letter after each table name (g and a) - they are called "alias" in order to shorten then whole expression. Without alias (which could be a word not just a single letter) the statement would read like this:
CREATE VIEW WA_V_FITTING AS select WA_POINT.GEOM,WA_POINT.ORIENTATION, WA_POINT.FID, WA_FITTING.NAME_NUMBER
from WA_POINT, WA_FITTING
where WA_POINT.FID_ATTR = WA_FITTING.FID
The alias or table name is given to indicate from which table a certain attribute comes from (required in cases where the same attribute name is used in more than one table).
Now you only need to add your attribute name (including the alias) - don't forget to add an additional comma between the last attribute and the new attribute:
CREATE VIEW WA_V_FITTING AS select g.GEOM,g.ORIENTATION, g.FID, a.NAME_NUMBER
, a.MA_SIZE
from WA_POINT g, WA_FITTING a
where g.FID_ATTR = a.FID
Attribute name needs to be upper cases.
Click on the green triangle to execute the statement - you will get the following error message:
...
SQL execution error number 0, table WA_V_FITTING already exists
...
We cannot overwrite a view - we have to delete the old one first and re-create it afterwards. Add the following line before the CREATE VIEW statement:
DROP VIEW WA_V_FITTING;
CREATE VIEW WA_V_FITTING AS select g.GEOM,g.ORIENTATION, g.FID, a.NAME_NUMBER
, a.MA_SIZE
from WA_POINT g, WA_FITTING a
where g.FID_ATTR = a.FID
Execute the query again, result should be:
SQL> DROP VIEW WA_V_FITTING
Command executed (0).
SQL> CREATE VIEW WA_V_FITTING AS select g.GEOM,g.ORIENTATION, g.FID, a.NAME_NUMBER
, a.MA_SIZE
from WA_POINT g, WA_FITTING a
where g.FID_ATTR = a.FID
Command executed (0).
If you receive an error message like this:
SQL execution error number 0, no such column: a.MA_SIZE
'CREATE VIEW WA_V_FITTING AS select g.GEOM,g.ORIENTATION, g.FID, a.NAME_NUMBER
, a.MA_SIZE
Did you save your drawing after adding the attribute to your table? If you haven't saved the drawing SQLSheet doesn't seem to "see" the new attribute.
7. close SQL Sheet
8. Close AIA
9. open AIA and reload your drawing, check the view in Data Model tree view - the attribute is now available in the view as well:
Before modifying your data base with SQL Sheet - back up your drawing file.
Friday, 4 August 2017
Uploading MapGuide package - Exception
Uploading MapGuide package - Exception
If you modify a MapGuide package make sure that you zip the correct files and folders afterwards.
I unzipped a MapGuide package, changed some values and zipped the folder but received the following error message when trying to upload the file:
Maestro error message:
value cannot be nul
Parametername: entry
System.ArgumentNullException: value cannot be nul
Parametername: entry
bei ICSharpCode.SharpZipLib.Zip.ZipFile.GetInputStream(ZipEntry entry)
bei Maestro.Packaging.PackageBuilder.UploadPackageNonTransactional(String sourceFile, UploadPackageResult result) in C:\working\JenkinsCI\home\slave_win\jobs\Maestro trunk\workspace\Maestro.Packaging\PackageBuilder.cs:Zeile 217.
MapGuide error message:
ERROR_MESSAGE: An exception occurred in DWF component. File not found in archive
STACK_TRACE: - MgLibraryRepositoryManager.LoadResourcePackage() line 183 file c:\working\build_area\mapguide\2.5.2\x64\mgdev\server\src\services\resource\LibraryRepositoryManager.cpp - MgResourcePackageLoader.Start() line 150 file c:\working\build_area\mapguide\2.5.2\x64\mgdev\server\src\services\resource\ResourcePackageLoader.cpp - MgResourcePackageLoader.CreateByteReader() line 108 file c:\working\build_area\mapguide\2.5.2\x64\mgdev\server\src\services\resource\ResourcePackageLoader.cpp - MgZipFileReader.ExtractArchive() line 61 file c:\working\build_area\mapguide\2.5.2\x64\mgdev\server\src\services\resource\ZipFileReader.cpp
My mistake was to zip the top level folder - which I got when I unzipped the package. But you need to zip the content of the top level folder, not the top level folder itself.
AIMS 2017
If you modify a MapGuide package make sure that you zip the correct files and folders afterwards.
I unzipped a MapGuide package, changed some values and zipped the folder but received the following error message when trying to upload the file:
Maestro error message:
value cannot be nul
Parametername: entry
System.ArgumentNullException: value cannot be nul
Parametername: entry
bei ICSharpCode.SharpZipLib.Zip.ZipFile.GetInputStream(ZipEntry entry)
bei Maestro.Packaging.PackageBuilder.UploadPackageNonTransactional(String sourceFile, UploadPackageResult result) in C:\working\JenkinsCI\home\slave_win\jobs\Maestro trunk\workspace\Maestro.Packaging\PackageBuilder.cs:Zeile 217.
MapGuide error message:
ERROR_MESSAGE: An exception occurred in DWF component. File not found in archive
STACK_TRACE: - MgLibraryRepositoryManager.LoadResourcePackage() line 183 file c:\working\build_area\mapguide\2.5.2\x64\mgdev\server\src\services\resource\LibraryRepositoryManager.cpp - MgResourcePackageLoader.Start() line 150 file c:\working\build_area\mapguide\2.5.2\x64\mgdev\server\src\services\resource\ResourcePackageLoader.cpp - MgResourcePackageLoader.CreateByteReader() line 108 file c:\working\build_area\mapguide\2.5.2\x64\mgdev\server\src\services\resource\ResourcePackageLoader.cpp - MgZipFileReader.ExtractArchive() line 61 file c:\working\build_area\mapguide\2.5.2\x64\mgdev\server\src\services\resource\ZipFileReader.cpp
My mistake was to zip the top level folder - which I got when I unzipped the package. But you need to zip the content of the top level folder, not the top level folder itself.
AIMS 2017
Friday, 9 June 2017
Map-Plot extension - iusse with FDO hatches in a rotated viewport
As mentioned already - back then for Map 2013 - there is an issue with hatches in a rotated viewport when using Map (FDO) layers. For details see here. The issue has not been resolved yet (Map 2017 SP1).
To get around it we basically replaced the problematic Map layer hatch with an AutoCAD hatch. We created 3 drawings (one for each of the print scales: 1:500, 1:1000 and 1:2000) containing only the hatches which cause issues, these hatches are plain AutoCAD hatches which print fine in a rotated viewport. These drawings were created by Map-DWG export.
As we use our own batch plot extension (as mentioned here) I just needed to extend it in order to attach one of the three drawings as XREF automatically before the layout gets printed off.
Map 2017, SP1
To get around it we basically replaced the problematic Map layer hatch with an AutoCAD hatch. We created 3 drawings (one for each of the print scales: 1:500, 1:1000 and 1:2000) containing only the hatches which cause issues, these hatches are plain AutoCAD hatches which print fine in a rotated viewport. These drawings were created by Map-DWG export.
As we use our own batch plot extension (as mentioned here) I just needed to extend it in order to attach one of the three drawings as XREF automatically before the layout gets printed off.
Map 2017, SP1
...
IPlot plot = myLibrary.FindPlot(FIDPlot);
PltPlotRenderer r = PltPlotRendererFactory.CreateRenderer(RendererConfiguration.Plot, plot, RenderingCompatibility.CurrentVersion);
r.Render(); // renders the plot as AutoCAD layout
...
// xrefs
string xref_pfad = "S:\\GIS\\Va\\Map3D2017\\Startbilder\\";
string xref_500 = "Wald_500.dwg";
string xref_1000 = "Wald_1000.dwg";
string xref_2000 = "Wald_2000.dwg";
...
string plotname = plot.Name;
string xref = xref_500;
if (plotname.Contains("500"))
xref = xref_500;
else if (plotname.Contains("1000"))
xref = xref_1000;
else
xref = xref_2000;
//attach matching xref
attachDrawing2(xref_pfad, xref);
//send xref to bottom
toBack();
// regenerate all viewports
RegenAll();
....
//copy and paste from AutoCAD forum ? - didn't keep the link,
public static void RegenAll()
{
Document doc = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument;
Editor ed = doc.Editor;
Database db = doc.Database;
Viewport vp;
using (DocumentLock docLock = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument.LockDocument())
{
using (Transaction tr = db.TransactionManager.StartTransaction())
{
LayoutManager lm = LayoutManager.Current;
if (lm.CurrentLayout.ToLower() == "model") db.TileMode = false;
lm.CurrentLayout = lm.CurrentLayout;
Layout layout = tr.GetObject(lm.GetLayoutId(lm.CurrentLayout), OpenMode.ForRead) as Layout;
ObjectIdCollection vpIds = layout.GetViewports();
if (vpIds.Count < 2) { ed.Regen(); return; }
ed.SwitchToModelSpace();
for (int i = 1; i < vpIds.Count; i++)
{
vp = tr.GetObject(vpIds[i], OpenMode.ForWrite) as Viewport;
ed.SwitchToModelSpace();
Autodesk.AutoCAD.ApplicationServices.Application.SetSystemVariable("Cvport", vp.Number);
ed.Regen();
ed.SwitchToPaperSpace();
}
tr.Commit();
}
}
}
...
//copy and paste from :_http://through-the-interface.typepad.com/through_the_interface/2015/11/attaching-autocad-xrefs-and-inserting-them-at-the-origin-using-net.html
public void attachDrawing2(string filepath, string filename)
{
Database acCurDb;
acCurDb = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument.Database;
string f = filepath + filename;
if (!File.Exists(f))
return ;
string name = Path.GetFileNameWithoutExtension(f);
try
{
using (var tr = acCurDb.TransactionManager.StartOpenCloseTransaction())
{
DocumentLock docLock = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument.LockDocument();
using (docLock)
{
var xId = acCurDb.AttachXref(f, name);
if (xId.IsValid)
{
BlockTable acBlkTbl;
acBlkTbl = tr.GetObject(acCurDb.BlockTableId, OpenMode.ForRead) as BlockTable;
var btr = tr.GetObject(acBlkTbl[BlockTableRecord.ModelSpace], OpenMode.ForWrite) as BlockTableRecord;
Point3d insPt = new Point3d(0, 0, 0);
var br = new BlockReference(insPt, xId);
btr.AppendEntity(br);
tr.AddNewlyCreatedDBObject(br, true);
}
tr.Commit();
}
Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument.Editor.Regen();
}
}
catch (Autodesk.AutoCAD.Runtime.Exception e)
{
MessageBox.Show(e.ToString());
}
}
...
//send XREF to bottom of draw order, copy and paste - didnt keep link
public void toBack()
{
Database acCurDb;
acCurDb = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument.Database;
try
{
using (var tr = acCurDb.TransactionManager.StartTransaction())
{
DocumentLock docLock = Autodesk.AutoCAD.ApplicationServices.Application.DocumentManager.MdiActiveDocument.LockDocument();
using (docLock)
{
//var bt = (BlockTable)tr.GetObject(acCurDb.BlockTableId, OpenMode.ForRead);
//var ms = (BlockTableRecord)tr.GetObject(bt[BlockTableRecord.ModelSpace], OpenMode.ForRead);
var bt = tr.GetObject(acCurDb.BlockTableId, OpenMode.ForRead) as BlockTable;
var ms = tr.GetObject(bt[BlockTableRecord.ModelSpace], OpenMode.ForWrite) as BlockTableRecord;
DrawOrderTable drawOrderTab = tr.GetObject(ms.DrawOrderTableId, OpenMode.ForWrite) as DrawOrderTable;
ObjectIdCollection ids = new ObjectIdCollection();
// Loop through the contents of the modelspace
foreach (var id in ms)
{
// We only care about BlockReferences
var br = tr.GetObject(id, OpenMode.ForRead) as BlockReference;
if (br != null)
{
// Check whether the associated BlockTableRecord is
// an external reference
var bd = (BlockTableRecord)tr.GetObject(br.BlockTableRecord, OpenMode.ForRead);
if (bd.IsFromExternalReference)
{
ids.Add(br.ObjectId);
}
}
}
if(ids.Count> 0)
drawOrderTab.MoveToBottom(ids);
}
tr.Commit();
}
Wednesday, 24 May 2017
Map Industry Model Plot Extension
If you use Map Industry Model Plot Extension make sure that the layers in your main display model do not contain a spatial filter. A spatial filter is automatically created when you save a display model. In order to remove the spatial filter you need to open the .layer file in an editor and remove the filter setting:
<Filter>GEOM ENVELOPEINTERSECTS GeomFromText('POLYGON XYZ ((698785 258855 0, 700411 258855 0, 700411 260393 0, 698785 260393 0, 698785 258855 0))')</Filter>
to
<Filter></Filter>
It seems that Map applies the filter from the layer file when generating a Map plot. If the spatial filter does not match with the area you want to create a plot for the layer content will not be shown.
Map 2017, Sp1
<Filter>GEOM ENVELOPEINTERSECTS GeomFromText('POLYGON XYZ ((698785 258855 0, 700411 258855 0, 700411 260393 0, 698785 260393 0, 698785 258855 0))')</Filter>
to
<Filter></Filter>
It seems that Map applies the filter from the layer file when generating a Map plot. If the spatial filter does not match with the area you want to create a plot for the layer content will not be shown.
Map 2017, Sp1
Thursday, 4 May 2017
simple web site for converting drawing file into 3d pdf using FME
Once in while our CIVIL users want to convert a drawing file into a 3d PDF file. As they are not familiar with FME and dont have access to it anyway I set up a web page where a drawing file can be uploaded and gets converted to a 3d PDF. FME 32bit is installed on the server just for this purpose.
The website consists of two frames. The first frame allows to upload the drawing file, the second frame just lists the contents of the folder on the server where the PDF file gets stored.
Here is the PHP code for the upload. After uploading it triggers the execution of a BATCH file (see below) which starts the FME workbench. The workbench is a simple ACAD drawing reader connected to an 3d PDF writer. Everything is kept very simple.
The batch file content:
The website consists of two frames. The first frame allows to upload the drawing file, the second frame just lists the contents of the folder on the server where the PDF file gets stored.
Here is the PHP code for the upload. After uploading it triggers the execution of a BATCH file (see below) which starts the FME workbench. The workbench is a simple ACAD drawing reader connected to an 3d PDF writer. Everything is kept very simple.
<html>
<body>
<script>
//refresh download frame in order to list newly created PDF file
parent.frames['download'].location.reload();
</script>
<h1>DWG zu 3D PDF</h1>
<form action="<?php echo $_SERVER["PHP_SELF"]; ?>" method="post" enctype="multipart/form-data">
DWG auswählen:
<input type="file" name="uploaded" id="fileToUpload"><br><br>
DWG hochladen:
<input type="submit" value="DWG hochladen" name="submit">
<br><br>
Nach dem Hochladen kann es einige Zeit dauern, bis die DWG konvertiert wurde. Bitte warten, bis eine Meldung erscheint.<br><br>
Im unteren Fenster sollte nach erfolgreicher Erstellung der PDF diese zum Download aufgelistet sein - falls nicht die gesamte Webseite aktualisieren.
<br><b>PDF bitte herunterladen (rechte Maustaste >> "Link speichern unter") - im Webbrowser werden keine 3d PDFs angezeigt.</b>
<br>
</form>
</body>
</html>
<?php
// PHP.INI
// upload_max_filesize = 20M
// --> if files are too big variables such as $_FILES['uploaded']['name'] and others are empty
// max_execution_time = 90
// FastCGI PHP in IIS execution time set to 90 secs
// Upload folder : set permissions
error_reporting(E_ALL);
if ($_POST['submit'] == '') die();
$target = "E:/www_fme_3dpdf_batch/uploads/";
$target = $target . basename( $_FILES['uploaded']['name']) ;
if(move_uploaded_file($_FILES['uploaded']['tmp_name'], $target))
{
//sending message to browser - doesnt work with IIS it seems :-(
//ob_implicit_flush(true);
//ob_start();
//ob_flush();
echo "<br><br>Datei <b>'". basename( $_FILES['uploaded']['name']). "'</b> hochgeladen.";
echo "<br><br>Dateikonvertierung gestartet....<br><br>";
echo "<small><pre>";
system("cmd /c E:/www_fme_3dpdf_batch/run_fme_acad2pdf.bat 2>&1", $output);
echo "</small></pre>";
}
else
{
echo "Problem aufgetreten. Datei nicht hochgeladen.";
}
?>
The batch file content:
SET SOURCE="E:\www_fme_3dpdf_batch\uploads"
SET OUTPUT="E:\www_fme_3dpdf_batch\downloads"
DEL /Q %OUTPUT%\*.*
FOR %%F IN ("%SOURCE%\*.dwg") DO (
C:\apps\FME32\fme.exe acad2pdf.fmw --SourceDataset_ACAD "%%F"^
--DestDataset_PDF "%OUTPUT%\%%~nF.pdf"^
--LOG_FILE "%OUTPUT%\%%~nF_load.log"
)
DEL /Q %SOURCE%\*.*
Subscribe to:
Posts (Atom)