-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
To what does the geodeticDatum (occurrences) field relate? #7
Comments
This relates to the underlying ALA service that delivers the data - ALA4R just wraps that service. I've asked the ALA devs for comment, will report here. |
Nice package. Over the last 24 hours the occurrences function is producing errors that I haven't seen previously. Any ideas? e.g.
|
Back to the geodeticDatum question. From the ALA devs: "Generally it appears to operate like this:
Your example http://biocache.ala.org.au/ws/occurrence/5400e754-d39c-4814-82ca-2f29b40fb3e2 is (2). The processed location is using the unrecognised datum. If supplying a valid raw datum the raw location and processed location datums do vary http://sandbox.ala.org.au/ws/occurrences/8580591d-80ba-44c9-9572-96a3d292581e" I'll close the issue here. If more info is needed, suggest raising an issue on the repo that provides the underlying service: https://github.com/AtlasOfLivingAustralia/biocache-service |
Thank very much Ben. The occurrence function started functioning normally again about 24 Wonderful package - so useful. I've stuck a RMarkdown doc on Rpubs to Cheers, On 23/04/2015 5:00 PM, Ben Raymond wrote:
Scientific Support Officer /Our vision for PNG: This email has been checked for viruses by Avast antivirus software. |
Consider
x <- occurrences('Diplolaena grandiflora', fq='geospatial_kosher:true', download_reason_id=10)
.Is
x$data$geodeticDatum
the datum associated withx$data$latitude
andx$data$longitude
, or have the coordinates given in those fields already been transformed to WGS84 (or GDA94? - though they are basically identical AFAIK)?If they have been transformed, then:
perhaps the name "geodeticDatumOriginal" might be more appropriate; and
What does this mean for the following row:
If the datum is unrecognised, and it's not assumed to be WGS84, what datum is assumed? In this case
latitudeOriginal
andlongitudeOriginal
matchlatitude
andlongitude
, so it seems no transformation has taken place. Note also that the originaloccurrences()
query requestedgeospatial_kosher
records only - should records such as5400e754-d39c-4814-82ca-2f29b40fb3e2
be omitted?The text was updated successfully, but these errors were encountered: