Harmonize file names

[MoritzStefaner]

growbikenet    amsterdam-betweenness_centrality-grid_with-bikenw.geojson
fixbikenet     Brussels.geojson.geojson          <- doubled extension, no layer name
linkbikenet    Budapest-largest_closest.geojson
superblockify  Amsterdam_betweenness.gpkg        <- underscore, TitleCase, different container

That is four parsers on our side, one of which has to guess: anything FixBikeNet ships that we
don't recognise is assumed to be a gap network.

Ask: <city>-<tool>-<algorithm>-<layer>[-<variant>].geojson, lowercase, single extension.
Example: amsterdam_nl-growbikenet-betweenness-grid-with_bikenw.geojson

Fix status:

• growbikenet (@mszell)
• fixbikenet (@Manuel-Knepper)
• linkbikenet (@Manuel-Knepper, after conferring with @mszell)
• superblockify (potentially @cbueth , otherwise @marianamirandapessoa with a conversion script)

[mszell]

Thx makes total sense. I suggest to try to use just one word for the algorithms, so instead of betweenness_centrality to just use betweenness. For lbn we still need to find good names.

There is the added complication that there is Brest, which is a city in both France and Belarus, which is why we switched in the dataexport to name the city with its alpha-2 country-code, like this: athens_gr

In gbn, fbn, and lbn, it should be doable to specify a city_id (at least in gbn we already do) which allows this custom city-id, but it might be a hassle in sb. We might need to write a script that adds the country-code, or we find another more temporary solution to leave out country codes, since it is just one problematic city name in Europe. but given how there are many many duplicate city names in the world, I prefer a long-term solution.

My suggestion for assignments:
gbn,fbn - @mszell
lbn - @Manuel-Knepper (after we have found good names)
sb - @cbueth , potentially

[mszell]

@moritz, there is the added issue that some geojsons are not about algorithms but metadata. Like city boundaries, seed points etc. We should probably find a good harmonized solution for these too. Maybe with a "metadata" or so in the filename? Let me know if you have any concrete scheme in mind.

[mszell]

Just to be clear @MoritzStefaner , can you please give an example what you mean exactly by <city>-<algorithm>-<layer>[-<variant>].geojson?

[MoritzStefaner]

Just to be clear @MoritzStefaner , can you please give an example what you mean exactly by <city>-<algorithm>-<layer>[-<variant>].geojson?

e.g. amsterdam-betweenness_centrality-grid-with_bikenw
(- separates parts, _ separates within parts)

But any system is fine, really, as long as it's consistent and can be parsed unambiguously.

[mszell]

Ah ok, I wasn't sure if algorithm refers to growbikenet etc. Would you want that distinction too?

[MoritzStefaner]

Ah ok, I wasn't sure if algorithm refers to growbikenet etc. Would you want that distinction too?

Ah, yes, would be good to include it, just to be safe.
amsterdam-growbikenet-betweenness_centrality-grid-with_bikenw

[mszell]

Ok, I'll edit your first post to include that info with an example