-
Notifications
You must be signed in to change notification settings - Fork 91
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
Comments
Related to opensciencemap#122 and opensciencemap#123 Blocks #216 |
After @hjanetzek 's comment, possible cause seems being the Wondering what's its benefit specifically for Mapsforge maps. |
@andreynovikov can you test all these also from your side? |
I changed Rendering in zoom >17 with |
Having half tile size as |
I changed |
Sorry, didn't catch, what should I test? |
@andreynovikov do you use 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? |
In Mapsforge we had added extra checks in processPOIs and processWays for including only the elements in the requested tiles. |
No, I use default and do not have such issues. |
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 |
Pushed in
|
When we use a Mapsforge map with max rendering zoom >17, like
new MapFileTileSource(0, 18)
, we have artifacts at tile grid lines.The text was updated successfully, but these errors were encountered: