Is there a way to extract a specific part of an aggregate by it's index other than deaggregating and testing the resulting features to find the one where _part_number = index.
I'm thinking there might be a way to use XQuery/GeometryPartExtractor
Userlevel 1
+12
- Contributor
- 220 replies
-
13 December 2016
Not really an answer as its just a different way of doing it, but what about using the GeometryExtractor to record the geometry as an attribute,before the aggregation (assuming you are doing this in a step prior) and then just using a ListIndexer and a GeometryReplacer to get the specific geometry you want.
+22
- Contributor
- 1963 replies
-
13 December 2016
Not really an answer as its just a different way of doing it, but what about using the GeometryExtractor to record the geometry as an attribute,before the aggregation (assuming you are doing this in a step prior) and then just using a ListIndexer and a GeometryReplacer to get the specific geometry you want.
In this particular case, the data input is already aggregated.
Userlevel 2
+17
- Contributor
- 7539 replies
-
14 December 2016
Hi @jdh, yes, you can use the GeometryPartExtractor (Advanced Editor). This is a possible syntax if the input geometry is a one level aggregate or a Multi geometry. Just be aware that a part of the aggregate has to be specified with 1-based index.
(: extract the 2nd part from a one level aggregate or a multi :)
number(/geometry/geometry[2]/@fme_id)- Contributor
- 1963 replies
-
14 December 2016
Hi @jdh, yes, you can use the GeometryPartExtractor (Advanced Editor). This is a possible syntax if the input geometry is a one level aggregate or a Multi geometry. Just be aware that a part of the aggregate has to be specified with 1-based index.
(: extract the 2nd part from a one level aggregate or a multi :)
number(/geometry/geometry[2]/@fme_id)- Contributor
- 1963 replies
-
14 December 2016
Hi @jdh, yes, you can use the GeometryPartExtractor (Advanced Editor). This is a possible syntax if the input geometry is a one level aggregate or a Multi geometry. Just be aware that a part of the aggregate has to be specified with 1-based index.
(: extract the 2nd part from a one level aggregate or a multi :)
number(/geometry/geometry[2]/@fme_id){fme:get-attribute(x)} instead of {fme:get-attribute("x")}
Userlevel 2
+17
- Contributor
- 7539 replies
-
15 December 2016
Minor issue with the advanced editor, when you reference a feature attribute using the left panel it does not wrap the attribute name in quotes as required.
{fme:get-attribute(x)} instead of {fme:get-attribute("x")}
Userlevel 4
+13
- Contributor
- 3726 replies
-
15 December 2016
yeah, have to say it's a kind of bug. @daleatsafe, please fix it.
Seems like a quick fix...thanks for pointing it out.
+22
- Contributor
- 1963 replies
-
15 December 2016
Seems like a quick fix...thanks for pointing it out.
Userlevel 4
+13
- Contributor
- 3726 replies
-
15 December 2016
There should be a case for it, as I pointed it out to support this morning.
+9
- Safer
- 89 replies
-
8 January 2017
And the fix is going in as I type this. Wish everything was that easy.... Thanks for pointing it out.
Reply
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.