search

OpenHistoricalMap / issues

File your issues here, regardless of repo until we get all our repos squared away; we don't want to miss anything.
Creative Commons Zero v1.0 Universal
19 stars 1 forks source link

Improve clarity "mushy" looking rail lines at browser z=8 and 9 #769

Open jeffreyameyer opened 6 months ago

jeffreyameyer commented 6 months ago

Style change requested

Current rail lines / casings in the primary "Historical" layer look mushed together at zoom=8 and 9.

See: https://www.openhistoricalmap.org/#map=8/56.664/-3.685&layers=O&date=1903-12-26&daterange=1500-01-01,2023-12-31

Monosnap OpenHistoricalMap 2024-04-26 16-53-07

The fact that there are rails that look quite different in different areas at this zoom make me wonder if some of these should be tagged differently (they are all just railway=rail, but I'm wondering if there's a treatment that can avoid this result, regardless of tagging.

Similar results on the "Railway" layer:

Monosnap Way: 199543551 | OpenHistoricalMap 2024-04-26 17-00-05

@natfoot @Luke04 @flha127

vknoppkewetzel commented 6 months ago

I can look into trying a different dashed pattern at this zoom, or other solution. Thanks for flagging this one

vknoppkewetzel commented 5 months ago

I think that #812 relates to this in some way, and also, maybe should remove patterns at mid-level zooms, possibly. Ultimately complex clustering of many "up and down/sharp turns' will result in "patterns disappearing".

The other option is to simplify line data further at mid-level and high zooms. TECHNICALLY cartographically and performance wise, this is also a good idea, but not sure of other implications

Bauer33333 commented 5 months ago

I can look into trying a different dashed pattern at this zoom, or other solution.

For short line segments it does sometimes help to start the dashes not with a dash but a gap, or half a gap. Not sure if that works here, but it could be worth a try