Do you have the grid data as a polygon dataset or so?
If you use spatial relator and test for intersects and build a list of your GRID IDS, you can then use two ListIndexers to get the first and last GRID_IDs in the list which will correspond to the start and end points of your line
Another option is to only test for polygons which the line starts or ends in, then you can use an attributecreator to transfer the two list elements to the attributes you want
If you use spatial relator and test for intersects and build a list of your GRID IDS, you can then use two ListIndexers to get the first and last GRID_IDs in the list which will correspond to the start and end points of your line
Another option is to only test for polygons which the line starts or ends in, then you can use an attributecreator to transfer the two list elements to the attributes you want
Thank you for @ebygomm for the help! Although when I follow this process I just get null values in the grid id columns. I've attached a screenshot of the workspace.
Thank you for @ebygomm for the help! Although when I follow this process I just get null values in the grid id columns. I've attached a screenshot of the workspace.
Are both datasets in the same coordinate system? If you inspect the data coming out the spatialrelator do they have a related candidates count of 0?
Are both datasets in the same coordinate system? If you inspect the data coming out the spatialrelator do they have a related candidates count of 0?
@ebygomm Both datasets are in the same coordinate system yes. When I inspect the data coming out of the spatial relator yes the related candidates are all 0.
@ebygomm Both datasets are in the same coordinate system yes. When I inspect the data coming out of the spatial relator yes the related candidates are all 0.
That suggests that your lines and polygons don't overlap. Do they appear to overlap in the data inspector
That suggests that your lines and polygons don't overlap. Do they appear to overlap in the data inspector
They most definitely overlap. I've checked in arcmap
They most definitely overlap. I've checked in arcmap
@ebygomm is there anything else I could do to check this?
@ebygomm is there anything else I could do to check this?
Can you see that they overlap in the inspector?
Hi @reidm35, I don't think that the first/last elements in the list generated by the SpatialRelator always indicate the grid polygons related to the start/end nodes of the line segment. Which grid polygon intersects start/end nodes of the line segment depends on the input order of the grid polygons.
A possible workaround is:
- GeometryExtractor: Save the line geometry as a feature attribute.
- Chopper (Mode: By Vertex, Maximum Vertices: 1): Split the line segment into individual vertices - i.e. start node point and end node point.
- Clipper or SpatialFilter: Merge GRID_ID of grid polygons to the points individually.
- Aggregator: Aggregate the points in the input order (from start to end) and store the GRID_IDs into a list attribute.
- AttributeManageter: Rename the list elements and remove unnecessary attributes.
- GeometryReplacer: Restore the original line segment geometry.
See also the attached workspace example: none2none.fmwt (FME 2019.1.3.1)
Hi @reidm35, I don't think that the first/last elements in the list generated by the SpatialRelator always indicate the grid polygons related to the start/end nodes of the line segment. Which grid polygon intersects start/end nodes of the line segment depends on the input order of the grid polygons.
A possible workaround is:
- GeometryExtractor: Save the line geometry as a feature attribute.
- Chopper (Mode: By Vertex, Maximum Vertices: 1): Split the line segment into individual vertices - i.e. start node point and end node point.
- Clipper or SpatialFilter: Merge GRID_ID of grid polygons to the points individually.
- Aggregator: Aggregate the points in the input order (from start to end) and store the GRID_IDs into a list attribute.
- AttributeManageter: Rename the list elements and remove unnecessary attributes.
- GeometryReplacer: Restore the original line segment geometry.
See also the attached workspace example: none2none.fmwt (FME 2019.1.3.1)
Hi @takashi. Thank you for the advice! Although when I run, I get zero features exiting the inside part of the Clipper transformer. Is there something wrong with my data?
Hi @reidm35, I don't think that the first/last elements in the list generated by the SpatialRelator always indicate the grid polygons related to the start/end nodes of the line segment. Which grid polygon intersects start/end nodes of the line segment depends on the input order of the grid polygons.
A possible workaround is:
- GeometryExtractor: Save the line geometry as a feature attribute.
- Chopper (Mode: By Vertex, Maximum Vertices: 1): Split the line segment into individual vertices - i.e. start node point and end node point.
- Clipper or SpatialFilter: Merge GRID_ID of grid polygons to the points individually.
- Aggregator: Aggregate the points in the input order (from start to end) and store the GRID_IDs into a list attribute.
- AttributeManageter: Rename the list elements and remove unnecessary attributes.
- GeometryReplacer: Restore the original line segment geometry.
See also the attached workspace example: none2none.fmwt (FME 2019.1.3.1)
Hi again @takashi. I'm still getting Null values in the my writer feature type. Although this workflow definitely worked. The Geometry Replacer have the correct attributes, but FME is not transferring these over to the writer! Any tips?
