Skip to content
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

Add mercator profile for output tiles #6

Closed
Gigas002 opened this issue Jun 6, 2019 · 5 comments
Closed

Add mercator profile for output tiles #6

Gigas002 opened this issue Jun 6, 2019 · 5 comments
Assignees
Labels
enhancement New feature or request grabbed Someone's already working on this issue
Milestone

Comments

@Gigas002
Copy link
Owner

Gigas002 commented Jun 6, 2019

Why
To implement more functionality of original gdal2tiles.py, that would be good to create an option to make mercator tiles too.

Where to start / alternatives
The gdal2tiles.py is a good base point, some maths can be used from it and rewritten on C#.

@Gigas002 Gigas002 added the enhancement New feature or request label Jun 6, 2019
@Gigas002
Copy link
Owner Author

Gigas002 commented Jul 4, 2019

Approximate plan looks like this:

  • Open input geotiff;
  • Check projection and stuff;
  • Convert to mercator, if needed;
  • Get mercator coordinates from file metadata;
  • Calculate mercator tile numbers dictionary for each zoom;
  • Generate tiles;

@carnegiea
Copy link

Any help I can provide in this matter? It seems like my previous issue was due to mercator / geodesic tile numbering as well, therefore i got confused even at openlayer.

@Gigas002
Copy link
Owner Author

Gigas002 commented Jul 6, 2019

TLDR: I'm not yet working on that feature.

Long explanation:
Well, I supposes 1-4 paragraphs are pretty easy to implement through gdal library in-code. The difficulties are starting with maths, when calculating tile numbers from mercator coordinates and calculating zones for tiles to read/write.
I haven't yet looked on all that stuff, but I'm pretty sure there's enought info about how-to-do-that in original gdal2tiles.py script.
The point is also not to change too much in GTiff2Tiles.Core existing code, so that'll take some time to implement. I should also change some names because of that (for example RepairTifOptions enum is needed only to convert tif to geodetic, but it will be kind of confusing to use that property to "reapair" mercator tif).
But anyway, thanks for your desire to help!

Gigas002 pushed a commit that referenced this issue Jul 14, 2020
@Gigas002 Gigas002 self-assigned this Jul 14, 2020
@Gigas002
Copy link
Owner Author

Logics in GTiff2Tiles.Core for this feature complete and will be availibale in GTiff2Tiles nuget package starting from v2.0.0-ci436 or higher.
It'll be added to GTiff2Tiles.Console and GTiff2Tiles.GUI in next major stable release (2.0.0).

@Gigas002 Gigas002 added the grabbed Someone's already working on this issue label Jul 21, 2020
@Gigas002 Gigas002 added this to the 2.0.0 milestone Aug 5, 2020
@Gigas002
Copy link
Owner Author

Gigas002 commented Aug 5, 2020

As I said above, work in Core for this feature complete and new options will appear in new stable release in both Console and GUI apps.
To avoid confusion, I'm closing this issue.

@Gigas002 Gigas002 closed this as completed Aug 5, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request grabbed Someone's already working on this issue
Projects
None yet
Development

No branches or pull requests

2 participants