+22If you need a polygon,line or a point as input for a workspace then it would be nice if the user interface provides a map component to draw the object so you can use it.
For now I use a custom form with some javascript: Wicket
But it would be nice to have it implemented into the standard web interface of FME server.
+63
+14
+7That's a great idea. What about if this was a type of parameter? It could return FME Binary type geometry so it can be processed easily in the workspace.
+19Great idea @stalknecht one little addition...make it available via the shareable URL!
+8Or just a simple lat/long box. I guess that's just a polygon with a constraint on how it is drawn.
+21Hi @stalknecht,
This has been released for FME Server 2020.0. For a walkthrough on how to use the new functionality, please see the article Using the Geometry Picker in FME Server.
'
It's a great parameter, but unfortunately it's inconvenient in the Eastern Hemisphere, since the longitude values would always be negative values.
For instance, the parameter generated this GeoJSON text when I drew a polygon in Tokyo, Japan.
{"type":"Polygon","coordinates":[[[-220.238907,35.678354],[-220.239697,35.676346],[-220.236298,35.675663],[-220.234599,35.677504],[-220.238907,35.678354]]}
We have to offset x-coordinates by +360 before using the resulting polygon as a spatial filter...
'
Ah, this seems to be depending on which hemisphere the initial bounds is belonging to. After I set the initial bounds as an area in Tokyo, longitudes became correct positive values.
Then, I noticed that the "Zoom Initial Bound" moves the map to Surrey always...
'
It seems that there still is a room to improve it.
In addition, it would be ideal if these configuration would be added to the parameter definition.
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
