Tag Info

New answers tagged

0

Interesting question. I'm reasonably confident the answer is no. I've had a few cases where I basically wanted to do this and ended up having to create a convoluted workbench to pull one of a number of possible attributes (i.e. various spellings of "PostCode" "postcode" "POSTCODE " "Post code" etc). It's probably worth emailing support@safe.com and making ...


0

Those are great answers by Vince. I think he's spot on with how, for SDE, FME will need to possibly make changes to meet SQL Server specifications (like vertex ordering, removing duplicate points, etc). I did want to suggest, re the grid/coordinate issue, that you try the ArcSDEGridSnapper transformer. It simulates the effects of writing to ArcSDE (in terms ...


3

There's a piece of the puzzle that your workflow does not consider: Enterprise geodatabase shapes all pass though the ArcSDE API, which performs standardization of geometries (integer encoding, dropping duplicate vertices, reordering incorrectly wound rings, merging inversions into their parent ring, etc) This impacts you in two ways: The vertex ...


3

I have figured this one out. I ended up using the NeighborFinder as I initially suspected. The trick is to store all candidate details in a list (I called it NeighbourList). I then connected that to a ListExploder to create features from all elements in the list. Then I used a tester to filter out the features with a distance of zero. Finally, I used ...


0

As you might know, Minecraft data enters FME as a point cloud. Probably the best way to start is to divide the data by block type. Use the PointCloudSplitter to do this. You need to split by BlockID. If you've built a building using stone, then keep that ID, like so: You can find a list of block ID numbers in many places online, including here. In the ...


0

What a coincidence, I am currently working on a workspace that brings Minecraft data that never existed in any other form, to some "normal" GIS format. I see a lot of possibilities here, but it all begins from point cloud splitting by blockID. My current world has 166 types of blocks, and this is what slows me down, I am a bit afraid to go through this pile ...


4

It's not a very well-known feature, but you need the Feature Type Connections window. You access it like this (View > Windows > Feature Type Connections): In there select all the source feature types, select the transformer point to connect to, then click Connect:


2

As was mentioned in the comments, the transformer you're after is the Densifier. From the help: Adds vertices to each feature by interpolating new coordinates at fixed intervals. You have the option to make the vertices evenly spaced or at a defined interval. Of course, as mKurowsKi points out, there are many ways to do this in FME.


1

As is always the case with FME, there are many ways to accomplish this task. Here is one way that centers around Iterative Snipper (available from the FME Store):


2

For an FME solution, you might want to try searching for near-parallel lines and then merging attributes (FeatureMerger) if they are suitably "parallel". There are a few potential ways to do detect parallelism in FME listed here (none require perfectly parallel): https://safecommunity.force.com/CommunityAnswers?id=906a0000000d7pBAAQ The upside of an FME ...


1

Assuming I'm understanding the question correctly, this can be easily achieved using FME and the Generaliser transformer. If you use the "Thin" (or maybe "ThinNoPoint" depending on your use-case). This will remove any points that are more than 5km from the next. ...


2

You've probably already found it, but the hardware specs for FME are here: http://www.safe.com/fme/fme-desktop/tech-specs/ To answer your questions: RAM: The Linux FME is 64bit only; it should easily handle as much RAM as you can throw at it. I've had it running quite happily on a 32GB machine and using a bunch of it (it maxed out any single process using ...


3

There is no silver bullet for this kind of task and there is a risk that some of the work you would need to do manually, particularly verifying the correct lines's attributes were transferred as required. I would try multiple things and see how it goes: Make a backup of your datasets. Make sure you have custom unique ID field for each line segment in the ...



Top 50 recent answers are included