Skip to main content

Data

Using readers and writers to extract and load data.

  • 7,318 Posts
  • 26,880 Replies
7318 Posts
j_geo
Contributor
j_geoContributor
 Data
mi
 Data
notaguru
 Data
rmcculley
 Data
Missing Features in Output

I'm new to FME.I've created a workspace that reads one Microstation V8 (dgn) file, and several shapefiles. It reads all features from the .dgn as well as all features from the shapefiles and outputs them into two new .dgn files. The first output file contains all features read, while the second one only contains the features from the shapefiles and not the features from the .dgn.Now, I actually need this to run on a whole bunch of datasets, so I exposed all of the input files as parameters and run it from a batch file. The default value of all the parameters is the files for the test dataset I was using. When I run the the workspace on the test dataset either in FME Workbench, or on the command line, everything works perfectly. When I run it on any other dataset, none of the features from the shapefiles is written to the output .dgn files. FME reports warnings, but the translation is always successful.I've attached the workspace file, as well as logs from a successful

1640
fmelizard
Safer
pratap
Contributor
pratapContributor
 Data
candimk
 Data
ben
 Data
GUI DYNAMIC_MULTI_SELECT_COMMAS and undefined macro

Hi,in my reader, I use the GUI TYPE "DYNAMIC_MULTI_SELECT_COMMAS" [1] so a user can selects/types some values. The sections in my metafile are:DEFAULT_MACRO HOST localhostDEFAULT_MACRO PORT 8080! ...some more codeDEFAULT_VALUE HOST $(HOST)GUI STRING HOST Host:DEFAULT_VALUE PORT $(PORT)GUI RANGE_SLIDER PORT 0%65535%0%OFF Port:DEFAULT_VALUE LAYERLIST $(LAYERLIST)GUI OPTIONAL DYNAMIC_MULTI_SELECT_COMMAS LAYERLIST HOST,$[HOST],PORT,$[PORT] Layer Names:This works fine, but  whenever I start a translation, I get the error:Undefined macro `HOST_MYREADER_1' dereferenced in file `C:\Users\User\AppData\Local\Temp\wb-xlate-1456160185578_8088'Program TerminatingTranslation FAILED.caused by $[HOST] in the DYNAMIC_MULTI_SELECT_COMMAS line. I can fix this by generating a Published Parameter called HOST_MYREADER_1 in my workspace, but I would like to understand the error. What is the problem here? I have created a macro called Host (and Port), why does FME crashes here?Another solution is  DEFAULT_VAL

673
adam
 Data
philippeb
Enthusiast
philippebEnthusiast
 Data
dfresh
dfresh
 Data
kenneedham
 Data
kseadawy
 Data
koen
Contributor
koenContributor
 Data
Inserted related records in Oracle protected by Oracle Rule Framework

For a client we are working on a large fme workbench which has to insert data in multiple oracle tables which are related with several foreign keys.In earlier versions we got a lot of 'parent key not found' errors while running, so we put writing of parent tables in separate writers so they would be executed first, and that would solve that problem.The problem now is that the system also has Oracle Rule Framework to guard several business rules on the database. Rule Framework will test these rules on every commit to check if all rules are met, if not it will rollback everything.This leaves us with a problem since our separate writers will each commit when finished and than our rules are not all met and everything will be rollbacked. So to comply with the rules all feature types should be written by only one writer and be committed only ones. But than we have the first problem with our foreign keys again.Removing the foreign keys, even temporary, is not an option for our custome

840
koen
Contributor
mrobinso_gpc
 Data
aquamarine
 Data
parashari
parashari
 Data
bigharv10
 Data
t1
 Data
pratap
Contributor
pratapContributor
 Data
jpvo
Contributor
jpvoContributor
 Data
Call Stored procedure returning a ref cursor

Hi all,I am calling a stored procedure in oracle. The procedure returns a "ref cursor" data type.When calling with SQL Developer I have this result:select bddoc_mgr.get_file_status_fme('w:\rwa005\energis\data\dwg\bp\geo','l144152-3.dwg') from dual{<FILE_ID=1,S_FILE_STATUS=2,S_STATUS=4,N_VERSION=1000,L_USERID=IAA543    >,}When calling with SQLCreator I have this error:Could not understand type information: type=116, size=8, scale=0, precision=0ORACLE Reader: Executing SQL Statement `select bddoc_mgr.get_file_status_fme('w:\rwa005\energis\data\dwg\bp\geo','l144152-3.dwg') from dual' to obtain features for feature type `QueryFactory_SQLExecute'Unable to define column number 1: error was `ORA-01024: invalid datatype in OCI call'. (serverType=`ORACLE8i', serverName=****, userName=****, password=`***', dbname=`')When calling with python I can parse the result easily:Is there a way to reach similar result using an SQLCreator?import fmeimport fmeobjectsimport cx_Oracle# Template Function

2870
erik_jan
Contributor
mattenvsys
Contributor
mattenvsysContributor
 Data
Potential Bug? FME attempting to write INT32 raster with a bit depth of 4

Hey everyone I wasn't sure where to post this as I thought it may be a bug.I'm running FME Desktop 2016.0.0.0 Build 16167 - WIN64I have a workbench that takes in multiple rasters, does some reclassifying and then some raster maths by adding them together.When it gets to the writing stage, the process fails with this error message: GEOTIFF writer: Failed to process a band with interpretation 'INT32' with the number of bits per cell set to '4'. The band bit depth must be the minimum value of (8, 16, 32) that is greater than or equal to the specified bits per cell. For example: to write 1-bit data the band interpretation should be 8-bit; to write 12-bit data the band interpretation should be 16-bit; to write 19-bit data the band interpretation should be 32-bitA fatal error has occurred. Check the logfile above for detailsI have gone into the advanced parameters of the geotiff writer and set the bits per cell to 32 but it still attempts to write at 4 bit.I think t

980
mattenvsys
Contributor
pratap
Contributor
pratapContributor
 Data
tp
 Data
Microstation V7 DGNs --> Clipper --> Microstation DGNs (wrong resulting colour)

Good day, everyone!I'm fairly new to FME (a couple of weeks of usage). I'm currently using FME 2015.1.Right now, I have a number of source Microstation V7 DGNs (from 2 different folders, which are being fed into a couple of DGN readers) that I'm feeding into a Clipper to clip them up into portions. I'm able to get the results (with a lot of help from a colleague). The issue I'm seeing so far:- Original DGNs, when the mouse hover over a, say, line, it says "Complex Chain \\ Line String" then "Level: 01_DUCT." But the resulting DGNs, the "Level" just says "60." I guess the "60" string is coming from the reader's Level Name field:- Original lines are DARK BLUE in colour, but resulting lines have some sort of a LIGHT PURPLE in colour.- Original arrow heads (for showing dimensions, I guess) are solid DARK BLUE. Whereas the resulting arrow heads are hollow.I have exposed the followings:- igds_glass- igds_color-

620
kflaw
 Data
guha
 Data
Show more activity

Badge Winners

Show all badges

Community Stats

32,938
Posts
124,881
Replies
41,798
Members
Terms & ConditionsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.