-
Notifications
You must be signed in to change notification settings - Fork 6
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
Wrong location for destination:ref and destination:symbol when also using :to #9
Comments
Hi,
But:
If you make a sign without the int_ref and the items above changed, it looks like it should: |
Ok, thank you very much for responding so quickly, and sorry for the inconvenience. Is there on the osm wiki any page that illustrates in which order should de tags go? |
For destination tags it is:
I also made a more general overview here:
Sure, I can't promise a date, but I can look into it. To get started I need a set of general rules (e.g. on a motorway -> green, destination:ref starts with 'F' -> blue) and a couple of examples (image + link to the OSM object) |
Hi!, here you have a little explanation of how our signs are:
Right now I don't have any OSM examples at hand, maybe the next weekend I can work on it. For road refs, it's very complex, as it depends on the region. I could explain later how it is on each region, but I think this will require a lot of work. I know a little bit of programming, so If you can explain me what files need to be modificated in order to create this profile, I could try to make it by myself and then do a pull request. |
Hi! I really like your app for checking if my mapping is done correctly, but today I found a bug.
As you can see on the screenshot, I put the key "airport" for a destination on the first lane, but in your app It shows the airport icon on a destination in both lanes. Also, the road refs for the first lane are not displayed correctly with their own destination. Colors aren't working neither when using :to, so I think that the problem is having this las suffix.
Thank you for your work!!
The text was updated successfully, but these errors were encountered: