Open yvonnefroehlich opened 1 year ago
Hmm, a few things:
contextily.bounds2img
. Specifically these lines
https://github.com/GenericMappingTools/pygmt/blob/91e29f1c1b4ebef1244051e6b1e3742f16bc34a4/pygmt/datasets/tile_map.py#L27-L30
https://github.com/GenericMappingTools/pygmt/blob/91e29f1c1b4ebef1244051e6b1e3742f16bc34a4/pygmt/src/tilemap.py#L57-L60contextily
(or xyzservices?), and we should at least try to open up an issue to see if they're interested in handling it. I actually need to check if EPSG:3857 and EPSG:4326 tile servers actually support returning cross-dateline tiles. If not, then we may need to add the logic of fetching tiles to the West and East of the international dateline separately and stitch them back together.2. Ideally, the cross dateline support can be added upstream into
contextily
(or xyzservices?), and we should at least try to open up an issue to see if they're interested in handling it.
Sounds good.
pygmt.Figure.coast
and the remote datasets (plotted viapygmt.Figure.grdimage
) support that the longitude is given either as -180° to 180° East or as 0° to 360° East. However, it looks like the later longitude range is not supported bypygmt.Figure.tilemap
. When plotting tiles for a region exceeding 180° East, the area after 180° East remains empty.Output figure: