New answers tagged fme
"string str" just means the text you want to test. Which is the attribute you're testing. The second string is your regex pattern. What attribute are you actually testing? Is it an FME attribute or one from your source data? If you want to check the actual geometry for multipolygons you can use a TestFilter or a Tester transformer to test the fme_type ...
You can get the field names across when your using dynamic schemas by selecting the writer right click and copy attributes from Feature Type... Then you can go to properties and delete the fields you do not require.
I'm not sure if this is a bug, or just some weirdness about XML, but generally if I have this XML: <?xml version="1.0" encoding="UTF-8"?> <FeatureCollection> <Course> <type>Desktop</type> <location>Vancouver, BC</location> ...
If you are willing to program python: arcpy has the "fromWKT" function, which can read a WKT string and return a geometry object. See http://resources.arcgis.com/en/help/main/10.1/index.html#//018v0000008s000000 . FME has a WKT reader also: http://docs.safe.com/fme/html/FME_ReadersWriters/Default.htm#wkt/wkt.htm
The point feature is a bit more straight forward once you have your table in excel (with your X and Y columns), save it out as a .csv and you may use the Make XY Event Layer tool to convert to event layer and then use Feature Class to Feature Class tool to convert to shapefile. The polyline and polygon are not as straight forward, you will have to build a ...
On the FME side of things you need to add a DateFormatter transformer into your workspace. Use it to convert the source date (20140522000000.000) to ISO DateTime (2014-05-22T00:00:00) Also make sure the GML Writer is set to use a DateTime for the output, and not a char field:
You seem to be using a dynamic workspace, which I don't think is right here. Assuming you want FME to create the new table, the following steps should be what you need to do: 1) Open the Generate Workspace dialog (Ctrl+G) 2) Enter Shape as the source format 3) Use the browse button and select ALL of the shape files to be converted 4) Set the output ...
Use the JSON Reader and then use a VertexCreator transformer. This transformer (which was previously called the 2DPointReplacer) will let you convert the X/Y coordinate values into a true spatial feature. Then you can simply write the data to your Geodatabase Writer. Make sure the Allowed Geometries field is set to geodb_point
Yes, that's it I think. They are probably libraries we aren't able to distribute, or we don't want to because they could interfere with your existing setup. This is another good resource page for setting up the connection. I'm thinking that if you have ArcGIS installed already then it's most the environment variables that need setting.
MS SQL server Create new table or add new column. Use STGeomFromWKB to convert WKB to Geometry , then in FME do following. Add "MS SQL spatial reader" , point it to correct table ( You can do this with SQLExecute too , that eliminates need for table containing geometry type and you can just use something like SELECT STGeomFRomWKB(wkb) as geom , id from xxx ...
I am not really sure about what exactly you need to do. Do yours 100 grid polygons snap to pixels of raster? (1 polygon = 1 pixel) And do you need to extract raster values into polygon grid? If it is sufficient for you only to extract raster pixel data and do have it in one table, you can firstly (in ArcGIS): convert raster to points (conversion->From ...
Top 50 recent answers are included