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

Mapsforge map artifacts for extraction zoom >17 #231

Closed
devemux86 opened this issue Nov 7, 2016 · 13 comments
Closed

Mapsforge map artifacts for extraction zoom >17 #231

devemux86 opened this issue Nov 7, 2016 · 13 comments
Labels
Milestone

Comments

@devemux86
Copy link
Collaborator

When we use a Mapsforge map with max rendering zoom >17, like new MapFileTileSource(0, 18), we have artifacts at tile grid lines.

artifacts

@devemux86 devemux86 added the bug label Nov 7, 2016
@devemux86
Copy link
Collaborator Author

devemux86 commented Nov 7, 2016

Related to opensciencemap#122 and opensciencemap#123

Blocks #216

@devemux86
Copy link
Collaborator Author

devemux86 commented Nov 7, 2016

After @hjanetzek 's comment, possible cause seems being the TileClipper used in MapDatabase.

Wondering what's its benefit specifically for Mapsforge maps.
Also at next line we have additional map element simplification.

@devemux86
Copy link
Collaborator Author

@andreynovikov can you test all these also from your side?

@devemux86
Copy link
Collaborator Author

I changed TileClipper buffer to half the tile size, like most tile buffers.
Nicely also described in TileMill Metatiles, hoping it isn't too much. 🙂

Rendering in zoom >17 with new MapFileTileSource(0, 18) seems fine now, need good testing by all.

@devemux86
Copy link
Collaborator Author

devemux86 commented Nov 7, 2016

There are still artifacts (1) at very large zooms >20 and elements disappear (2) if most of tile is outside screen, both with new MapFileTileSource(0, 18).

Artifacts:
1

Disappearance:
2

@devemux86
Copy link
Collaborator Author

devemux86 commented Nov 12, 2016

Having half tile size as TileClipper buffer seems not excellent for performance.. 🙁

@devemux86
Copy link
Collaborator Author

I changed TileClipper buffer to be scaled on dpi.

@andreynovikov
Copy link

Sorry, didn't catch, what should I test?

@devemux86
Copy link
Collaborator Author

devemux86 commented Nov 14, 2016

@andreynovikov do you use MapFileTileSource with default max zoom or >17 and see any artifacts?

I wonder of the purpose of tile clipping here and improved it to have a scaled buffer.

And in next line we have a simplify call, seems a bit redundant in Mapsforge maps?

@devemux86
Copy link
Collaborator Author

devemux86 commented Nov 14, 2016

In Mapsforge we had added extra checks in processPOIs and processWays for including only the elements in the requested tiles.

@andreynovikov
Copy link

No, I use default and do not have such issues.

@devemux86
Copy link
Collaborator Author

Large query zoom levels have also polygon artifacts as reported in #391.

The buildings cause that issue (as seen in urban areas), e.g. disabling them in the theme eliminates any artifacts.

Reason is in MapDatabase.processWays there is a check to not use TileClipper for buildings, probably due to opensciencemap#124.

@devemux86
Copy link
Collaborator Author

Pushed in MapDatabase at large query zoom levels:

  • Clip everything (also buildings)
  • Use enlarged clip buffer

@devemux86 devemux86 changed the title Mapsforge map artifacts for zoom >17 Mapsforge map artifacts for extraction zoom >17 Jan 9, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants