ETRS89 to BNG using Grid inQuest

MarcGellatly · ‎08-11-2010

Hi.

I'm hoping someone will entertain this query and apologies if it's been done to death.

I have a set of GPS coordinates - points near the coastline. I want to tranform them to British National Grid (BNG) so I can display against some raster mapping of land.

1. My initial solution was to take the spreadsheet of coords, convert from degrees/decimal minutes to decimal degrees. Then use the Convert (files) function of Grid inQuest to transform from ETRS89 to BNG. Then create XY data.

However, individual conversions work in Grid inQuest but every time I use the Convert (files) my results never produce a list in BNG.

2. I'm also attempting to use the Project function from Toolbox, however the Geographic Transformation option does not provide the tranformation I want, ETRS89 to BNG/OSGB36.

Thanks.

ChrisSnyder · ‎08-11-2010

Make sure you are specifying a negative longitude value if your coordinates are west (left) of the prime meridian. For example, using decimal degrees, Washington State (Pacific Coast) in the U.S. is located at about -120.0 longitude and 47.0 latitude.

MarcGellatly · ‎08-11-2010

Coordinates are indeed west of a meridian, and have a negative longitude set of values. The output from Grid inQuest appears to be in UTM rather than British National Grid.

Project tool from Toolbox doesn't appear to provide the correct tranformation from the pull-down.

ChrisSnyder · ‎08-11-2010

Not sure what inQuest is, but would it be possible to just import the raw DD coordinates (in .dbf format)straight into ArcGIS using th AddXYeventLayer tool, and then reprojecting using the ESRI prj tools?

MelitaKennedy · ‎08-11-2010

Hi.

I'm hoping someone will entertain this query and apologies if it's been done to death.

I have a set of GPS coordinates - points near the coastline. I want to tranform them to British National Grid (BNG) so I can display against some raster mapping of land.

1. My initial solution was to take the spreadsheet of coords, convert from degrees/decimal minutes to decimal degrees. Then use the Convert (files) function of Grid inQuest to transform from ETRS89 to BNG. Then create XY data.

However, individual conversions work in Grid inQuest but every time I use the Convert (files) my results never produce a list in BNG.

2. I'm also attempting to use the Project function from Toolbox, however the Geographic Transformation option does not provide the tranformation I want, ETRS89 to BNG/OSGB36.

Thanks.

ESRI doesn't have the same transformation that the Grid InQuest tool does: OSTN02 and variants. You could use one of our OSGB_1936_To_WGS_1984_xx ones, but we don't have any for OSGB36 / ETRS89.

I have the software but haven't tried using files with it. Can you post a sample row or two here? If your data is offshore, there's a possibility that Grid InQuest is treating it as out-of-range. I ran into that when working with the Irish grid file support. Can you convert one of those points via the GUI?

Melita

MarcGellatly · ‎08-12-2010

Melita.

I can transform individual coords via Grid inQuest's GUI; in fact I did this manually for a small set of coords, appended the results to my original spreadsheet, created XY feature from this set, added to ArcMap and they plot exactly where I want them to. It's the conversion of Batch Coords that doesn't work for me.

Set attached. Couldn't attach a .csv here, so added an .xls

Thanks.

MelitaKennedy · ‎08-12-2010

Melita.

I can transform individual coords via Grid inQuest's GUI; in fact I did this manually for a small set of coords, appended the results to my original spreadsheet, created XY feature from this set, added to ArcMap and they plot exactly where I want them to. It's the conversion of Batch Coords that doesn't work for me.

Set attached. Couldn't attach a .csv here, so added an .xls

Thanks.

Hi Marc,

Hmmm, the only problem I hit is that the setup for a batch file with lat/lon input wants ellipsoidal heights. I set it to use the ID column!

Here's what I got:

200265.66997,733823.81832,-53.716,Newlyn
200300.70257,733781.28443,-52.715,Newlyn
200310.16479,733829.14868,-51.715,Newlyn
200332.75046,733828.08217,-50.715,Newlyn
200337.75582,733868.72512,-49.715,Newlyn
200355.59868,733832.57778,-48.715,Newlyn
200364.98978,733813.55384,-47.715,Newlyn
200387.63967,733792.04441,-46.715,Newlyn
200412.40735,733749.99721,-45.714,Newlyn
200877.60236,733402.89597,-44.710,Newlyn
200931.57506,733194.10461,-43.710,Newlyn
201175.05237,733338.73290,-42.708,Newlyn
201152.79377,733324.91487,-41.708,Newlyn
201178.09471,733293.99534,-40.708,Newlyn
201187.59682,733299.12297,-39.708,Newlyn

Here are my steps. I'm using v6.6.0 build 1313.

File, Convert files.
Select the excel file. (Text File Decoding Wizard starts)
Click Next to use New Format.
On Select Rows to Decode, I set it to row 2. Next.
Coordinate Format: Geodetic. Next.
Select Data Fields:
   Right click column 1 and select ellipsoidal height
   R-click 2 and select latitude
   R-click 3 and select longitude
   Next
Geodetic Information: coordinate format: Projected (Eastings, Northings)
   (make sure it lists OSGB36 (OSTN02) in the projection section)
Output File: I specified a text file, output.txt. Next.
File format successfully defined.
Finish the tool...

I hope this is helpful,
Melita

MarcGellatly · ‎08-13-2010

Melita.

Thanks for your help on this. The converted cooprdinates you've shown are exaclty where I want them. You've confirmed that I've been using the tool correctly. However here is my set of results:

361780.838,6258878.527,-53.716,Newlyn
361816.476,6258836.520,-52.715,Newlyn
361825.238,6258884.503,-51.715,Newlyn
361847.831,6258883.766,-50.715,Newlyn
361852.243,6258924.466,-49.715,Newlyn
361870.605,6258888.593,-48.715,Newlyn
361880.269,6258869.713,-47.715,Newlyn
361903.224,6258848.542,-46.715,Newlyn
361928.594,6258806.872,-45.714,Newlyn
362398.663,6258466.684,-44.710,Newlyn
362455.654,6258258.761,-43.710,Newlyn
362696.934,6258406.878,-42.708,Newlyn
362674.885,6258392.741,-41.708,Newlyn
362700.626,6258362.202,-40.708,Newlyn
362710.050,6258367.466,-39.708,Newlyn

I am definitly modifying the output to OSGB36 when running through the wizard. Time to email Grid inQuest I think!

RolandBurkhard · ‎10-26-2010

Melita.

Thanks for your help on this. The converted cooprdinates you've shown are exaclty where I want them. You've confirmed that I've been using the tool correctly. However here is my set of results:

361780.838,6258878.527,-53.716,Newlyn
361816.476,6258836.520,-52.715,Newlyn
361825.238,6258884.503,-51.715,Newlyn
361847.831,6258883.766,-50.715,Newlyn
361852.243,6258924.466,-49.715,Newlyn
361870.605,6258888.593,-48.715,Newlyn
361880.269,6258869.713,-47.715,Newlyn
361903.224,6258848.542,-46.715,Newlyn
361928.594,6258806.872,-45.714,Newlyn
362398.663,6258466.684,-44.710,Newlyn
362455.654,6258258.761,-43.710,Newlyn
362696.934,6258406.878,-42.708,Newlyn
362674.885,6258392.741,-41.708,Newlyn
362700.626,6258362.202,-40.708,Newlyn
362710.050,6258367.466,-39.708,Newlyn

I am definitly modifying the output to OSGB36 when running through the wizard. Time to email Grid inQuest I think!

I am getting a similar mistake. My coordinates are out of bounds. They are from the Edinburgh area and I am pretty sure I have converted batch data from geodetic to OSGB36 before using GridInQuest. As said above, individual points transform perfectly.

What I find however is that the report always brings up a transformation into the irish grid although I set it to OSGB36.

I use the same version and build as above on windows XP SP3

Any ideas or advances with Quest Geo Solutions on this? I wrote them a mail too.

Thanks, Roland

BenO_Connor · ‎10-27-2010

Hi all,

I have had similar issues to what I see described in the previous posts and I believe it may be a bug which is triggered the first time you output to UTM using the "Convert file(s)..." feature. When subsequent batch conversions are performed the Grid InQuest software appears to remember the previous output coordinate setting being UTM and uses this over the output coordinate system manually chosen.

I've found that deleting a few registry keys can fix this issue.

In Registry Editor (Start > Run > regedit.exe) navigate to HKEY_CURRENT_USER\Software\Quest\. When I have had this issue I have deleted the entire contents under the Quest key, however it is likely that deleting the values "Destination Format", "Destination Zone", "Format", "Source Format" and "Source Zone" under HKEY_CURRENT_USER\Software\Quest\GridInQuest\Preferences\ will be sufficient.

Hope this helps!

Ben