New answers tagged

0

The problem is you don't close <gml:MultiCurve> in <geometry>. I used Notepad++ with XML pluging to check syntax and correct the code: <?xml version="1.0" encoding="UTF-8"?> <FeatureCollection xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xlink="http://www.w3.org/1999/xlink" xmlns:gml="http://www.opengis.net/gml/3.2" gml:...


0

You didn't specify the version but I can't reproduce the no geometry problem in FME Desktop 2016.1.0.1. Reading a gpx and writing to a dynamic geopackage writer results in correct geometry tables for Track & Trackpoint and an unknow geometry table for metadata.


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 ...


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 ...


0

The data volumes seem low but I'm wondering what the size of the actual image is that you're going to output? That may be the problem. Can you try with a lower resolution and see if that helps. You may need to tile the data prior to going into the rasterizer if you're looking to produce a huge huge output raster.


0

You can checkout point2poly JavaScript application at geospatialearth.in site. Click link. In this application you can browse your csv file and upload. Your browser will show the preview and you need to select geometry type as Extend_poly and two corner coordinates from you csv table column name. You can then choose what do you want to save KML or Shapefile....


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

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

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


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.


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).


0

I have figured out what the issue was. I had to add the ArcGIS Online Reader for the existing Feature Layer before adding the ArcGIS Online writer. Then I had to copy the "Layer Definition" from the previously added ArcGIS Online reader for that Feature Layer. Then it worked as expected.


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....



Top 50 recent answers are included