tumic0 / GPXSee-maps

GPXSee maps
https://maps.gpxsee.org
The Unlicense
35 stars 10 forks source link

Add topographic maps of Russia #15

Closed sikmir closed 6 years ago

sikmir commented 6 years ago

Maps hosted by https://nakarte.tk:

tumic0 commented 6 years ago

Can you add some bounds to the maps? As I understand them, most of them are for Russia only, so some bounding rectangle covering only Russia would make them more user friendly (you get a better view rectangle when you open the map and you do not get "lost in white space" so much when scrolling).

sikmir commented 6 years ago

Well, let's define bounds from extreme points:

Northernmost: 81.84306° N Southernmost: 41.18528° N Westernmost: 19.63861° E Easternmost: 169.0167° W

So we have:

<bounds top="81.84306" bottom="41.18528" left="19.63861" right="-169.0167"/>

What leads to:

5: Invalid left/right bounds combination

Is there a way to "cross antimeridian"?

tumic0 commented 6 years ago

Not at the moment. If there are some map tiles beyond the dateline, then let the maps without the bounds. Otherwise I would suggest to set the right bound to 180, even if you loose the east-most part of Russia ;-)

sikmir commented 6 years ago

Well, updated:)

tumic0 commented 6 years ago

I see some strange artifacts (map tiles "jumping" on some border) even when I set the right bounds to 179. So maybe going back to the full world bounds will be at the end better...

tumic0 commented 6 years ago

So the results is, that TMS maps are broken at the moment, if the bounds are not the full osm bounds. So please remove the bounds and I will fix this somehow in the next version.

sikmir commented 6 years ago

Removed.

tumic0 commented 6 years ago

Thanks. It's even a little bit worse - all maps, not only TMS maps, are broken near the bounds when the bounds are not the full bounds. This was introduced when fixing the zoom 0 issue.