Lots of ways, but here's a suggestion
- CsmapReprojector to go from X/Y to Lat/Long
- CoordinateExtrator to extract the coordinates as attributes
- Excel writer
Reproject to Lat/Long using the Reprojector transformer.
Then create the attribute using the GeometryExtractor (creates a geometry attribute with the definition) or the CoordinateConcatenator (results in a comma separated string of Lat/Long coordinates in an attribute).
Lots of ways, but here's a suggestion
- CsmapReprojector to go from X/Y to Lat/Long
- CoordinateExtrator to extract the coordinates as attributes
- Excel writer
First off thanks for your quick reply, I now feel I'm almost there ... but not quite. My original data coordinate system is BritishNationalGrid. When I applie either LL84 or LL_WGS84 two things happen in the repojector.
1. The lat longs seem to be getting written out the wrong way round e.g. -1.5747253716770673,53.681833979608278 rather than 53.681833979608278, -1.5747253716770673
2. The location is consistency around 1.4m offset in a north west direction. E.g. true location using X Y is 428188.06, 420679.96, when processed through the workbench the lat long is 53.681833979608278, -1.5747253716770673 the X Y of this is 428186.96 420680.97
Can you suggest how to correct the offset which my workbench is creating and is there a way to switch the lat longs round?
I'm new to this type of functionality within FME so please bare with me. Thanks
First off thanks for your quick reply, I now feel I'm almost there ... but not quite. My original data coordinate system is BritishNationalGrid. When I applie either LL84 or LL_WGS84 two things happen in the repojector.
1. The lat longs seem to be getting written out the wrong way round e.g. -1.5747253716770673,53.681833979608278 rather than 53.681833979608278, -1.5747253716770673
2. The location is consistency around 1.4m offset in a north west direction. E.g. true location using X Y is 428188.06, 420679.96, when processed through the workbench the lat long is 53.681833979608278, -1.5747253716770673 the X Y of this is 428186.96 420680.97
Can you suggest how to correct the offset which my workbench is creating and is there a way to switch the lat longs round?
I'm new to this type of functionality within FME so please bare with me. Thanks
As for the switched lat/long values, how are you naming them in the CoordinateExtractor and how are you writing them out? Is it possible that you've switched them around and it's just a question of ordering them properly in the Writer?
You can also just use the AttributeReprojector, which doesnt require any geometry involved so that it might be more effective.
As for the switched lat/long values, how are you naming them in the CoordinateExtractor and how are you writing them out? Is it possible that you've switched them around and it's just a question of ordering them properly in the Writer?
the offset is a common issue though and is (often) due to the default projection transformation used to switch between the OSGB36 (BNG) datum and the WGS84 (LL) datum.
The default is nearly always pretty rough.
the best, most accurate, transformer to use is the GridInquest transformer that uses the OSTN02 grid transformation. If you're not down to the cm level though, you could use the CSMAPreprojector, picking the 7 param/petroleum transformation, or the ESRI reprojector, if you have ArcGIS desktop installed - again you need to pick the 7param/petroleum transformation.
the gridInquest Transformer outputs the coordinates in ETRS89, not WGS84 however, but the 2 are often seen as synonymous.
another gotcha with the gridinquest transformer is that the grid, containing the data that is used in the transformation, only extends 10Km offshore, so if you have offshore data use the other tools. I've created a wrapper for this in the fme store, which will direct you to the right transformer.
ESRI have published some good blogs on this subject.
the offset is a common issue though and is (often) due to the default projection transformation used to switch between the OSGB36 (BNG) datum and the WGS84 (LL) datum.
The default is nearly always pretty rough.
the best, most accurate, transformer to use is the GridInquest transformer that uses the OSTN02 grid transformation. If you're not down to the cm level though, you could use the CSMAPreprojector, picking the 7 param/petroleum transformation, or the ESRI reprojector, if you have ArcGIS desktop installed - again you need to pick the 7param/petroleum transformation.
the gridInquest Transformer outputs the coordinates in ETRS89, not WGS84 however, but the 2 are often seen as synonymous.
another gotcha with the gridinquest transformer is that the grid, containing the data that is used in the transformation, only extends 10Km offshore, so if you have offshore data use the other tools. I've created a wrapper for this in the fme store, which will direct you to the right transformer.
ESRI have published some good blogs on this subject.
I noticed you mention the coordinates getting swapped.
I do not what can cause that, but the CoordinateSwapper transformer could fix that issue.
First off thanks for your quick reply, I now feel I'm almost there ... but not quite. My original data coordinate system is BritishNationalGrid. When I applie either LL84 or LL_WGS84 two things happen in the repojector.
1. The lat longs seem to be getting written out the wrong way round e.g. -1.5747253716770673,53.681833979608278 rather than 53.681833979608278, -1.5747253716770673
2. The location is consistency around 1.4m offset in a north west direction. E.g. true location using X Y is 428188.06, 420679.96, when processed through the workbench the lat long is 53.681833979608278, -1.5747253716770673 the X Y of this is 428186.96 420680.97
Can you suggest how to correct the offset which my workbench is creating and is there a way to switch the lat longs round?
I'm new to this type of functionality within FME so please bare with me. Thanks
Are you sure you've calculated that offset right, the offset I see when reprojecting back to BNG is 1.4558657187077331e-006
Thank you all for your advice, I ended up using the offsetter transformer to adjust the coordinates and have managed to reduce the error to 0.5m which will be sufficient for this analysis. I really appreciate your help.