Tag Info

New answers tagged

0

As for the automation part - "5 minutes increments" - that's usually what FME Server is used for. However, you could use a tool or script of some sort to simply run your workspace from the command line at set intervals (or a cron command if you're on on linux) When you run the workspace in Workbench, the very top lines of the log window will tell you what ...


0

Try putting a Deaggregator transformer before the SpatialFilter. Technically the SpatialFilter is using OGC spatial relationship tests. However, these spatial relations are not defined for aggregate geometries. So if your data is a set of aggregate features, it won't be OGC compliant, but deaggregating would solve the problem. Alternatively use a different ...


1

PointOnAreaOverlayer should achieve the same task if you can't get the SpatialFilter working.


1

Here is an older workspace reading json from our google geocoder (we have enterprise license to do this). The process is simple it sends a request out to the service [most api's will return json or xml] which returns the json file which then will be processed and reformatted Note:we had to use a decelerator transformer because FME was processing the inputs ...


2

Very interesting answer from Mark, thanks ! As the initial message asks for alternative solutions, you can also use FME to upload your data in PostgreSQL/PostGIS and use the pgRouting extension. There is a specific function pgr_trsp that deals with turn restrictions. Thanks to the dynamic definition of the network and turn restriction using SQL queries, ...


0

OK, I had a think about this. With the current functionality, it is possible, but I don't think you're going to like how! What you would need is for your network junctions to look like this: Basically turns become a separate network line/link/edge. Black circles are nodes and the red lines are the main network. You would need separate features for the ...


0

If you have a dataset of the tight turns, I would suggest to remove the connections between (read: vertex creating the connection => filter roadsegments intersecting the turn > chop them to vertices > remove turn vertice > rebuild paths) those roads. If it is a turn in a roadsegment you can filter those out segments from your dataset.


0

FME does not provide the tools to do this with the available transformers. This solution describes how the coordinate check can be done using python (PythonCaller). It is based on an answer to a question at stackoverflow. This is the proposed procedure: Coordinates are made an attribute A list of candidate coordinates is established and written to disk ...


1

Ok, I've figured this out. Steps are as follows: Use a PolylineAnalyzer and output segments only (this method is better, but slower than just using a Chopper transformer as it outputs angles of segments). Intersect the segments using an Intersector transformer and output nodes. Store incoming segments in a list. Ensure the intersection nodes are not ...


1

PolylineAnalyzer (from the FME Store) you can type 'PolylineAnalyzer' on the workbench worksheet and download from there. Takes polylines and polygons and analyzes relationships between their components - vertices and segments. FME Store link https://store.safe.com/transformers/polylineanalyzer usage: You can work the angle out and then use a ...


1

If the LineOnLineOverlayer (According to the help files) does indeed give a list of the lines associated with the intersection. You could get the line start and end vertices for each line (CoordinateExtractor) perhaps after clipping to a small area around the intersection. Then it's into the 'ExpressionEvaluator' for some back to basics trigonometry to get ...


2

Yes, I think we could implement this in FME pretty easily. I've filed an enhancement request with our developers and we'll see what they say. If you contact our support team (http://safe.com/support) and let them know you are interested then they can add your contact details to the request. The reference number is PR#61198 Also, do please add it to the ...


2

GDAL/OGR supports Elasticsearch, which means that FME could support it reasonably easily. I reckon you might like to hit up the FME people on Twitter and put in a request. Try Mark Ireland @FMEEvangelist or Dale Lutz @DaleAtSafe and Don Murray @DonAtSafe. But anyway, you could use a FME script to prepare your data, then write it to a temporary file, and ...


3

Give this recent talk by Paul Ramsey a view: http://blog.cleverelephant.ca/2015/03/magical-postgis.html He suggests that the PostgreSQL Full Text search make ElasticSearch unnecessary... Something to consider anyway...


2

As I'm reading it, the only part you haven't done within FME is to force it only pick stuff within a speed limit. This is actually very simple. 1) Insert a Tester transformer between your shapefile input and your ShortestPathFinder. Make sure PASSED feeds into the SPF. 2) For the Left Value, Click on the empty space -> drop-down -> Attribute Value ...


0

I'm not sure I see the point of filtering all of your geometries and writing them to a feature class. It's true that a Microstation cell is (or can be) made up of multiple geometry types. However, Microstation sees them as one object. If you filter all of your geometries and write them all to points, you're going to end up with duplicates. A better ...


0

All of the igds attributes will remain as they were when exiting the CenterPointReplacer Transformer. You could try using a GeometryCoercer to force the geometry to a point. Here's a demo on using the Geometry Coercer. You could also try removing the igds_type attribute, as you will likely not need it in the resulting Feature Class. You can delete it ...


-1

Convert your DGN to a DXF and then use the tool convert CAD to Vector.


1

OK, so you basically need to compare each of the records in table 2 against each record in table 1. To me that suggests you are going to need a loop of some sort. You could either use a loop (or nested loops) inside a Custom Transformer, or you could do an alternative type of loop using a list. For the Custom Transformer, check out this FMEpedia example, or ...


0

I am a bit confused by your image. It looks like you're trying to join two tables. But your resulting table appears to have incorrect values in Field 2. I'm going to assume you're trying to join the two tables based on the ID field. This is a fairly straightforward process in FME. You can use the FeatureMerger Transformer. Connect Table 1 to the ...



Top 50 recent answers are included