FME2008 Post-CD Fixes
From fmepedia
This page is a table of updates that were made after the FME2008 CD went to press, but that have been back-ported into a new FME2008 build.
Note: This doesn't mean the 2008 CD is bad, it's just that we want to pump out a few fixes this way rather than force users into moving to the 2009 beta. You could call them updates/patches/service packs/fixes.....
Updated builds will be made available on our web site downloads page, but you should only really need them if you are affected by any of the following issues.
No, really! Any fixes are for rare problems, and you aren't likely to need to update just for the sake of it.
| Table of contents |
Build Releases
Which builds are released and their date:
| Build # | Upload Date |
|---|---|
| 5200 | 25th April 2008 |
| 5204 | 23rd May 2008 |
| 5206 | 5th June 2008 |
| 5209 | 26th June 2008 |
FME Desktop
Issues that primarily relate to the Desktop product
Bug Fixes
| Problem | Symptoms | Fix Build | PR# |
|---|---|---|---|
| FME can't read Big-Endian WKB (Well-Known Binary) data | FME wrongly reports the WKB is invalid. FME writers create little-endian WKB data, so only non-FME-created WKB data would be at risk | 5198 | PR#15415 |
| FME may crash when scanning DWG files | A potential crash may occur when adding a DWG reader. Reported only in the Map3D Object Data reader, but the ACAD reader may also be at risk | 5199 | PR:15384 |
| FME can't read Shape datasets greater than 2.14Gb in size | FME would fail to read a Shape dataset greater than 2.14GB. | 5199 | PR:15467 |
| Search Envelope for SQL Server Geographic data creates a bad query | Setting a search envelope when reading Geographic (lat/long or <now> long/lat) data SQL Server spatial results in a bad query. NB: the problem will only arise after Microsoft's next beta (May CTP: CTP-6 Refresh) of SQL Server when they change the coordinate ordering for Geographic Data types. Using an earlier SQL Server version with a newer FME is perfectly acceptable. | 5200 | N/A |
| Memory leak in pyfme | A minor memory leak was reported in FME's Python support, specifically when using factory pipelines. Also available as a special hotfix for FME2007. | 5200 | PR:15577 |
| DateTime problems in SQLServer to MapInfo translation | Parts of DateTime attributes were reported lost during a SQLServer to MapInfo TAB translation. | 5200 | PR:15560 |
| Failure to create Oracle database index | Because of a change to database functionality, FME might try to create an index with an invalid name. | 5200 | N/A |
| Potential intersection crash | The Safe testsuite reported a potential crash in Intersection operations, in a rare case with degenerate arc data | 5200 | N/A |
| Bug in PolygonFactory handling of 3-point arcs | Arcs that are identical but in opposite directions would get different vertices when stroked. | 5201 | PR:15523 |
| Reading multiple WMS layers causes SRS to be ignored | Coordinate system wrongly defaults to EPSG:4326 | 5201 | PR:14629 |
| Fault in formula used by SecondOrderConformer | Incorrect results caused by reversal of two terms. G((y-B)^2 - (x-A)^2) should be G((x-A)^2 - (y-B)^2). Won't be noticeable where G (and H which is similarly affected) are very small. When G or H is a larger value then it will be more obvious. | 5203 | N/A |
| SQL Server search envelope fails to work in FME Objects applications, including the FME Universal Viewer | The full table is returned, not just a specific envelope. | 5203 | N/A |
| Source dataset settings dialog help incorrect | Help buttons for certain formats link to the wrong topic. | 5203 | PR:15606 |
| COORDSYS gui fields don't appear in the navigator pane | Any coordinate system selection in a transformer settings dialog would not appear in the navigator pane - hence can't be published. | 5203 | PR:15801 |
| xsi:nil flag not supported | The flag would be dropped from the schema. | 5203 | PR:15574 |
| Oracle writer fails for specific polygon feature | Error is ORA-13354: incorrect offset in ELEM_INFO_ARRAY | 5203 | PR:15708 |
| WKT coordinates overly-precise | WKT coordinates have greater precision (more decimal places) than is appropriate to the data | 5203 | N/A |
| The SpatialRelator is supposed to be able to accept multiple attributes with different predicates. | SpatialRelator - does not accept multiple attributes for predicate | 5204 | PR:15945 |
| Transformer search ignores localized (ie non-English) transformer descriptions | Searching with non-English keywords would not work | 5204 | PR:15988 |
| <space> characters in WMS Feature Types should be replaced with %20 | The WMS reader would wrongly replace <space> with + | 5206 | PR:16127 |
| Oracle fixed length strings have incorrect memory allocation | Potential for "garbage" characters at the end of strings | 5206 | PR:15276 |
| Error in FeatureTypeFilter transformer | Features not emerging properly from 'unfiltered' port | 5206 | PR:15156 |
| Error in ListSorter transformer | Translation would potentially fail with TCL related error message | 5206 | PR:16077 |
| Number of issues in converting geometries to wkt/wkb | FME crash (Issue originally reported in EDIGEO to PostGIS translation) | 5206 | PR:15746 |
| No support for xref fields in GML reader/writer | - | 5207 | PR:15573 |
| DistanceSnipper Fails to Snip to End of Line | Fails when the start or the end setting is 0 or (sometimes) when the end_length = line_length | 5207 | PR:15688 |
| Geodatabase Annotation Font Size Cannot be Set - a geodb_font_size attribute is required | Output font size bears no relation to geodb_text_size | 5207 | PR:9103 |
| Spaces not supported in dataset fanout prefix setting | Errors out with "ERROR |A fatal error has occurred." | 5208 | PR:15963 |
| Spaces wrongly encoded in WMS URLs | unknown | 5209 | PR:16127 |
| epsg numbers of the form "urn:ogc:def:crs:EPSG:[n].[n].[n]:[epsg code]" and "urn:x-ogc:def:crs:EPSG:[n].[n].[n]:[epsg code]", where [n]s are natural numbers would not be recognized (GML reading?) | unknown | 5209 | N/A |
| Problem with GML reader auto generated xfmap. | GML reader only returns bounding box | 5209 | PR:16386 |
Enhancements
| Feature | Enhancement | Fix Build | PR# |
|---|---|---|---|
| IGDS (DGN) tag writing is not supported | It is now! v8 files only. Phase 1 of support requires user defined list attributes (the same attributes read from a dataset with tags) | 5202 | PR:14804 |
| FME translates gml:id on a feature (e.g. <enc31:LAKARE gml:id="F_ENC_8908">) but not on the geometry (e.g. <gml:Polygon gml:id="L_113027_15704">) | gml:id for GML geometries is now mapped as an FME geometry trait (gml_id) | 5202 | PR:15571 |
| FDO support not up to date | Added FDO support for AutoCAD Map 2009 & upgraded FDO_FME libraries to version 3.3 | 5209 | PR:15921 | PR:15691 |
FME Server
Not fixes to the Server product as such, but Desktop fixes that relate to server functionality
| Problem | Symptoms | Fix Build | PR# |
|---|---|---|---|
| FMEServer Download Wizard | Problem where an empty repository will show a bad entry (workspace with no name) under the "Workspace" items | 5199 | |
| FMEServer Publish Wizard | Problem where check boxes on the "Register Workspace" page would turn into text edit on double click. | 5199 | |
| FMEServer Download/Publish Wizard | Problem where empty repositories will not show up in the list of "repositories". | 5199 | PR:15483 |
| Encoded parameter values invalid in transformation requests | Encoded parameters could cause a truncated command line and default values for some parameters | 5199 | PR:14585 | PR:15508 |
| FMEServer Publish Wizard: Problems with workspaces with published parameters that contain a list of multiple files. | Causes the upload option to be greyed out. On publishing the workspace the parameters would be jumbled up. | 5201 | PR:15713 | PR:15715 |
| FMEServer Publish Wizard: Multi-file datasets (eg Shape) could not be uploaded | Only a single file could be selected in the dialog. Subdirectory structures (eg for file geodatabase) are not yet supported | 5201 | PR:15593 |
| FMEServer: Does not support protected/"encrypted" workspaces | Unsure - probably rejected by server as not valid | 5201 | PR:15480 |
| FME Server hangs reading SDE dataset | Caused by failing to properly complete username and password information. Fixed in build 5201 (not 5199 as first reported) | 5201 | PR:14749 |
| The upload check box defaults to unchecked. | The upload check box is now checked (turned on) by default. | 5202 | PR:15778 |
| Data in a sub-directory of the workspace will not be read correctly when the workspace is uploaded to the server | Data will be reported missing. Caused by replacement of path with $(FME_MF_DIR). Now, when data is not uploaded with the workspace, source locations are changed to absolute paths | 5202 | PR:15674 |
| Need to be able to set job priority in ServerJobSubmitter | No settings available. | 5203 | PR:15888 |
| Values for both !FME_AUTO_DIR_NAME! and !FME_AUTO_FILE_NAME! (used in SpatialDirect to make the results directory and zip file name) have the machine name at the beginning. | This is now not done by default. The client can specify this manually with the auto name prefix directives. | 5203 | PR:14534 |
| 'International' (eg Japanese) workspace names are not supported. | Such workspaces would get scrambled on being published. This is now fixed for cases where the client and server use the same encoding. | 5203 | PR:15844 |
| FME Server related help updates | n/a | 5206 | n/a |
| Path to source data is lost after publishing to server | After publishing, the path to source data is replaced the location of the workspace, File/Filter is set to some pieces of the path ('Documents', 'My', 'and', 'co2000p020.shp') | 5206 | PR:16111 |
| GUI problem with ServerJobSubmitter | ServerJobSubmitter Repositories List does not clear after changing the server name | 5207 | PR:16180 |
| ServerJobSubmitter doesn't handle repository names with space characters | Translation fails if repository name has space | 5207 | PR:16170 |
| API doc not up to date | The API doc doesn't include a list of all TMDirectives | 5208 | PR:16184 |
| Value for !FME_AUTO_DIR_NAME! has the machine name at the beginning. | This is now not done by default. !FME_AUTO_FILE_NAME! was already fixed in build 5203 | 5208 | PR:14534 |
Extensions
Desktop fixes that relate to extensions
| Problem | Symptoms | Fix Build | PR# |
|---|---|---|---|
| ArcGIS extension fails to read GeoRSS datasets | The ArcGIS Extension was wrongly assuming that file names starting with "http" & "ftp" would be on the local file system. | 5199 | PR:15427 |
| GeoMedia data server setting incorrect coordinate system parameters | Bad handling of State Plane projections for users of our Geomedia GDO Provider. | 5199 | PR:15512 |
.
