Export should export in same order as in preview window, or mark clearly, "raw" isn't enough

[jidanni]

Run

relation(id:14978108);
out geom;

and look in the data pane / data panel / preview (not the map pane / map panel )

Now export to GeoJson.

Surprise, the order is different than in the data pane.

So it is not an export after all. (Pick a "raw" choice, below GeoJson for a real export.)

Let's say we have a look at the Constitution.
Looks good. OK, we hit Export. Oh my, Article 11
ended up after the 14th Amendment.

[jidanni]

Or, in the export panel, mark clearly, which items will be in the same order as the preview vs. "no guarantee."

Yes, you might say to the judge "there is no bait and switch. The word "raw" implies the order is preserved."

No. People think you are only talking about the much different format. They didn't dream that of all the choices on the export panel, some will not be in the same order as in the preview window.

[mmd-osm]

I think the issue is that GeoJSON as a data format has no concept of an ordered sequence of points - ignoring LineString for a moment, which serves a different purpose and doesn't fit a list of bus stop nodes.

You could enrich the relation members with an additional "sequence id" tag in your query, but that's a bit involved.

[jidanni]

However the same problem exists for the KML and GPX buttons.

They could have their output in the same order as in the preview window but, alas...