#176: OSGB x/y coords should be converted to WGS84 lat/long at page save time. ------------------------+--------------------------------------------------- Reporter: Kake | Owner: kake Type: defect | Status: new Priority: normal | Milestone: Component: openguides | Version: svn Severity: normal | Keywords: ------------------------+--------------------------------------------------- Suppose a guide accepts geodata as OSGB x/y. When the page is saved, we use Geography::NationalGrid::GB to convert these to lat/long, and store those in the database as well. Unfortunately these are actually OSGB lat/long, whereas most people/applications will expect WGS84 lat/long. We hacked around this for Google Maps display by using Geo::!HelmertTransform to transform into WGS84 before talking to the Google API, but it would be better to do the transformation at page save time, so the lat/long is correct in the database, on the page, and in the RDF output.
This is likely an issue for OSIE guides as well.
#176: OSGB x/y coords should be converted to WGS84 lat/long at page save time. ------------------------+--------------------------------------------------- Reporter: Kake | Owner: Kake Type: defect | Status: assigned Priority: normal | Milestone: Component: openguides | Version: svn Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by Kake):
* status: new => assigned * owner: kake => Kake
Comment:
Nick suggests we also save the OSGB lat/long in the database, as local_lat and local_long, just in case anything ever wants them. And this also works as a marker for nodes whose coordinates haven't been corrected.
#176: OSGB x/y coords should be converted to WGS84 lat/long at page save time. ------------------------+--------------------------------------------------- Reporter: Kake | Owner: Kake Type: defect | Status: assigned Priority: normal | Milestone: Component: openguides | Version: svn Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Comment (by Kake):
Decision: we're just going to make sure that we always use wgs84_lat and wgs84_long in the templates.
#176: We should always use WGS84 lat/long variables in the templates. ------------------------+--------------------------------------------------- Reporter: Kake | Owner: Kake Type: defect | Status: assigned Priority: normal | Milestone: Component: openguides | Version: svn Severity: normal | Resolution: Keywords: | ------------------------+--------------------------------------------------- Changes (by Kake):
* summary: OSGB x/y coords should be converted to WGS84 lat/long at page save time. => We should always use WGS84 lat/long variables in the templates.
#176: We should always use WGS84 lat/long variables in the templates. ------------------------+--------------------------------------------------- Reporter: Kake | Owner: Kake Type: defect | Status: closed Priority: normal | Milestone: Component: openguides | Version: svn Severity: normal | Resolution: fixed Keywords: | ------------------------+--------------------------------------------------- Changes (by kake):
* status: assigned => closed * resolution: => fixed
Comment:
(In [1051]) Finish changing from use of "latitude" and "longitude" template variables to "wgs84_lat" and "wgs84_long" (the first lot of this was accidentally committed in [1049], sorry). Fixes #176.
openguides-tickets@lists.openguides.org