I am generating a set of maps using pygmt.info( data=myGeoDataFrame, spacing=4 ) to set the region. Now, one of the features I am plotting has vertices around -88.8˚S, resulting in a -R-48/128/-92/-76 region definition. As I parse this straight into pygmt.coast() and a Mercator projection, pygmt rightly complains about -92 being outside the -90/+90 degree range (this is for global features, so currently I am not worried too much about the projection).
As the geodataframe has an EPSG:4326 projection, I would have assumed that pygmt.info() is clever enough to just give -90 as southern boundary. The same happens also with OGR_GMT-formatted data ( @Je4326 in header) and gmt info.
Bug or feature request to limit the increment output of (py)gmt info for geographic data to -90/+90 degree range?
You are probably not telling GMT that your data are geographic lon/lat. When I use -fg and get a region out of bounds, GMT will say this:
gmt info t.txt -I7 -fg
gmtinfo [WARNING]: Using -I caused wesn[YLO] to become < -90. Reset to -90.
-R0/35/-90/-84
[Note to self: wesn[YLO] really? You could not just write south?]. Of course, we cannot prevent you from using this with a Mercator projection and there is no “default” latitude for that anyway other than < 90. If you plan to do this then you would be better off getting the w e s n values numerically and impose your own limits.
CLI GMT master now understands the EPGS4326 in an OGR/GMT file (and hence shape files) at least, but doing this for the dataframe will need to take place in PyGMT.