Hot answers tagged

3

You want Writers > Update Feature Type from the menubar - though re-importing the table and deleting the existing one will work just as well.


3

With FME you'd probably read the data as plain CSV and then use the 2DBoxReplacer transformer to convert the four different fields into a true polygon geometry. The GeometryReplacer is more for creating geometry from an attribute containing XML, JSON, or WKT - which it doesn't sound like you have.


3

With ArcGIS the simplest way to do this is to use Python. Copy the following code in the Python window of ArcCatalog or ArcMap and you should get it done (first change the input table, output feature class and field names in the cursor if necessary): import arcpy table = r"D:\temp\Coords.txt" out_fc = r"D:\temp.gdb\polygons" polygons = [] with arcpy.da....


2

Do you mean the Insertion Scale Units? Defining a template file for the DWG writer works as well.


2

Right now the closest you can get is to set the End Cap Style to square and the Stroking Density to 1. Inside corners get a single point, but outside corners get two points, meaning it's probably not quite what you want. However, the Bufferer was updated for FME2017 and now includes parameters that would allow you to do keep angles intact. If you're OK with ...


2

So, it appears that your TIF is in REAL32 which isn't supported by ECW. It's interesting that you're getting an error, because the writer documentation states that: Any non-eight-bit source data will be rescaled to eight-bit. However, you can force the data to be 8-bit by using a RasterInterpretationCoercer. I would set your output to RGB24 depending ...


1

GEODB reader, Excel reader, featuremerger (objectid), VertexCreator (replace point), GEODB writer (update, objectid). The SDE writer can create new tables but also, insert rows and update rows. I'm by no means an SDE export but I think OBJECTID is the unique ID created by SDE. This way only the rows that are merged with excel will get a new coordinate and ...


1

You can either set 'Table Definition' to 'Automatic' when adding your writer... ...or set this behaviour under 'User Attributes' tab in the Feature Type Properties (double click writer).


1

Can you store your labels in a separate table? Then just filter them out in FME (maybe a GeometryFilter transformer) and don't write to that table. You would need to ensure Overwrite Existing Database is set to No, but that all the tables have Drop Table set to Yes. As long as you don't write any features to the label table, it won't get dropped or ...


1

You should be able to make use of the Insert/Delete/Update options in FME database writers. For example, here's the dialog for PostGRES database (didn't see it for Spatialite). Note in that dialog there is also an attribute called fme_db_operation which you can populate somewhere in your workflow. I'm not sure if it is supported for Spatialite, however....



Only top voted, non community-wiki answers of a minimum length are eligible