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

maxweight=maxweight instead of maxweight in OsmAnd's taginfo project #322

Open
goldfndr opened this issue Jul 26, 2019 · 3 comments
Open

Comments

@goldfndr
Copy link

Taginfo's maxweight projects table includes OsmAnd with only a maxweight value, which isn't correct. It should only include the key, not the value.

@goldfndr
Copy link
Author

goldfndr commented Aug 8, 2020

Although the generic key is in now, the maxweight value persists. Likewise, maxheight=maxheight is also present.

@vshcherb
Copy link
Member

We support various values of maxweight i.e. any float + tons. So it we don't know how to express it correctly.

@goldfndr
Copy link
Author

The description could be changed to the above instead of the generic "Used to create maps"; perhaps a post-processing step?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants