Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Mapsforge maps v5: variable tag values #1006
With this modification, all OSM-tag values (such as numerical and string values) can be saved in mapsforge .map format without specify a fixed value term in
The map-writer can be used for older versions too, if tag-values are disabled. If not, new specification doesn't allow older readers to read new one. New Readers won't have a problem to read them all. The tag-value bit in file header is not needed, but I set it, because I can't decide if assumes a role for later versions.
The writing performance keeps very similar. I inherited some S3DB-tags, (especially height tag) and the map file size only increases around 0,24% in my case.
Why is it useful?
Let me know what you think of ;D
referenced this pull request
Oct 16, 2017
Sorry for the confusion, had opened wrong map file, the sea is rendered fine.
If you have it ready, can post a PR in order to check them in parallel, as Mapsforge cannot render extrusions and would be interesting to see how VTM plays with v5 maps.