If you can find a tool to apply Travelling Salesman routing to the nodes that would be fantastic!

keep up the good work and let me know what you settle on!

I’m certain some of the tags like direction would be very useful to ensure the timetable and spatial data can properly reference one another

for referencing the variant unless the timetable refers to variant 1, 2, 3 we probably want to avoid arbitrary values? (there seems to be some exceptions to references to external sources, perhaps we could use the variant id from the timetable data?) but somehow reference all route relationships as part of a single route.

The other issue is how do you mark the main varient

What do people expect? Do you have a wiki page for describing your schema? and what some of those variant terms mean?

How does it compare to the one of the existing transport schemas, and what does it offer in addition?

Why is the meta data index bobby444:variant required at all? When routes are added or removed without updating the index you will lose contiguity.

:direction and the like will distinguish the routes. Even if there wasn’t any to make them unique. Identically tagged routes with differing members will be self evidently variations of the route. Better would to be explicit in making a relation of relations, then the relation itself can handle the issue of numbering/ordering

What do you want to do with flagged imports? If I do a small import of one village or town and manually check, conflate and edit every building then it lacks the issue that large or automated imports have.

The wiki says this on the matter:

https://wiki.openstreetmap.org/wiki/Key:loading_gauge

I’m afraid I don’t know what FIA is. Is there a reason you suggest it as a suffix on a tag? it suggests you can have different widths and heights on one feature?

Is loading_gauge:height=2438 missing something critical?

Excellent news. Would attributes similar to highways for speed limits and restrictions be suitable. Or would we need a new restriciton schema?

They now mention OSM in their licencing page. This morning there are new buildings in the UK whose outlines I recognise as OSM

Just remember that in the UK (and some other countries) the final tag would become turn:lanes:both_ways=right

Thanks, it appears a lot of the typos lead to a feature which has also got a lot of other misused tags such as set of place:* being used as an address. Complex enough that it is a case of asking what the author meant. One feature had name for the feature name but then Name for the author’s name and brand as the company the author was working for.

Is there a way of getting the feature ids to fix the typos?

Hi Mateusz,

Thank you for your tool, I would be very interested if you could produce a report for Devon, UK

Thanks!