Tag Info

New answers tagged

0

I reviewed the log file and noticed that the translation log after reading C:\Users\Dell\Desktop\POWIERZCHNIE\Dotyk\Powierzchnie_dotyk.tab is incomplete. I am unable to see if this was successful or it failed! ( I assume you have posted the complete log). Can you try inspecting this data (C:\Users\Dell\Desktop\POWIERZCHNIE\Dotyk\Powierzchnie_dotyk.tab) using ...


0

A slighty more exteme version than that posted by @Guy, would be the following. 1). Break the Polygons into constituent linestring. You can do this using ST_Dump and two sets of generate series offset by one, to get each pair of adjacent points, which is then handed to ST_MakeLine. 2). Get a list of distinct linestrings. ie, removing duplicates, as this ...


0

Assuming they exactly align, then you can load in your polygons into a PostGIS table a and your lines into table b and use the following in SQL to return confirmation SELECT ST_Covers(ST_Collect(b.line), ST_Collect(ST_ExteriorRing(a.polygon)) FROM a,b (untested) There are plenty of ways you could achieve the same result, but it really depends on the size ...


0

After all I created the table with the compound key in pgAdmin and I used an SQLExecutr transformer in FME with an INSERT query. This way I avoid the problem although I don't know if there is another, cleaner solution.


2

You need to check that your attributes have been passed through the workspace. Click on arrow (1 in the image). This should show your attributes at the featuremerger. You can then map the attributes across manually by clicking the arrow against the attribute (2 in the image) and then clicking the corresponding arrow at the writer (3 in the image). ...


1

No solution, but a workaround: in SQLExecutor transformer select Microsoft Access (MDB_ADO) as the format, edit the SQL string, press ok, save, execute notepad++, open fmw-file, search&replace MDB_ADO with XLS_ADO, add some additional lines (XLS_ADO_SHOW_NAMED_RANGES, XLS_ADO_FIRST_ROW_IS_HEADING), save. Start working. Obviously FME2014+ recognizes the ...


1

It may be because you're using the Postgres format, which FME would class as non-spatial (or tabular). If you used PostGIS instead it might show you the geometry column. Regardless, I agree with the other poster that the more usual approach would be to use a Writer, rather than trying to pass data through the SQLExecutor. Then geometry is handled ...


2

I believe this page will answer your question: http://blog.safe.com/2011/05/fmeevangelist79/ It sounds like using the 'Joiner' transformer in your workflow will work. The crucial part you mention makes it sound like you don't actually want to merge the two, but rather add a relationship between the table and the shapefile.


0

Assuming that it's point data (X Y Coordinates) in your Excel file, you could use the 2DPointReplacer 'Transformer' to create the point geometry, choosing your x and y coordinates accordingly. It may then easier to use a PostGIS 'Writer' to insert the data into the database and let FME take care of the spatial table creation.


0

I imagine that these lines are actually composed of multiple line features (called an Aggregate in FME terminology, that the CAD format you're writing to doesn't support aggregates, and so FME writes them as a block so that the relationship is preserved. If you do want them as lines, and don't care about the relationship so much, insert a Deaggreator ...


4

You can go with the SQLExecuter, the initiator would need to be a list of database values [keys] you want to delete. Then using something similar the SQL statement below to execute the delete query should work. DELETE FROM table WHERE key = '@Value(key)'; Or you can use the DatabaseDeleter


4

One option its to make use of 2 coordinateExtractors , 1 for index 0 (1st coordinate) and another with index -1 (last coordinate) .


1

The fastest way is to create a generate a 'dynamic shapefile' reader and writer This assumes that the shapefiles are one feature type. File> Generate Workspace select your shapefiles workflow options (dynamic) Full documentation http://docs.safe.com/fme/2014beta/html/FME_Workbench/Default.htm#Filling_in_the_Workspace_Dialog.htm


4

You can use the Snapper transformer, with End Point Snapping and a tolerance of 6.


0

The non-automatical way would be to use the snapping function. So select the feature and then drag the specific point of it to another with active snapping for sure. After that select both features and use the Merge Selected Features option. Now you should have one feature at the end. If this is not a solution for your please describe the issue a bit more ...


3

Mapperz is right, the Snapper and Anchored Snapper are the ones to use. If you don't want to move the lines after you generalise them, then stick with the Anchored Snapper. Your lines will go into the Anchor port and your points into the Candidate port. The points will snap to the lines. I have recently applied this exact workflow (Generalize and ...


1

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.


2

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


1

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.



Top 50 recent answers are included