R Help,

I posted a question on StackOverflow yesterday regarding an issue I've been 
having with the RgoogleMaps packages' displaying of axes.  Here is the text of 
that submission:
http://stackoverflow.com/questions/6258408/rgooglemaps-axes

"I can't find any documentation of the following problem I'm having with the 
axis labels in RGoogleMaps:
library(RgoogleMaps)
datas <-structure(list(LAT =c(37.875,37.925,37.775,37.875,37.875),
                   LON =c(-122.225,-122.225,-122.075,-122.075,-122.025)),
                   .Names=c("LAT","LON"),class="data.frame",
                   row.names =c(1418L,1419L,1536L,1538L,1578L))
# Get bounding box.
boxt <-qbbox(lat =datas$LAT,lon =datas$LON)
MyMap<-GetMap.bbox(boxt$lonR,boxt$latR,destfile ="Arvin12Map.png",
maptype ="mobile")
PlotOnStaticMap(MyMap,lat =datas$LAT,lon =datas$LON,
                axes =TRUE,mar =rep(4,4))

When I run this on my computer the horizontal axis ranges from 300W to 60E, but 
the ticks in between aren't linearly spaced (300W, 200W, 100W, 0, 100E, 160W, 
60W). Also, the vertical axis moves linearly from 300S to 300N. It seems that 
no matter what data I supply for datas, the axes are always labeled this way.
My question is:
1. Does this problem occur on other machines using this code?
2. Does anyone have an explanation for it?
and
3. Can anybody suggest a way to get the correct axes labels (assuming these are 
"incorrect", but maybe i'm somehow misinterpreting the plot!)?
Thank you for your time."

There has been no answer other than that I ought to contact the package 
maintainer.  Since it would be nice to have a publicly displayed solution, I 
opted to post here first before doing so.  Does anyone have any insight to 
share?
Thank you very much for your time,

-Erik Gregory
CSU Sacramento, Mathematics
Student Assistant, California Environmental Protection Agency

______________________________________________
R-help@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-help
PLEASE do read the posting guide http://www.R-project.org/posting-guide.html
and provide commented, minimal, self-contained, reproducible code.

Reply via email to