1ec5 left a comment (openstreetmap/openstreetmap-website#6234)
> Or, we find a way to do the conversion to GeoJSON on the source
That would be elegant and probably improve performance, but I think this
MapLibre conversion will already be large enough just trying to maintain
compatibility with existing server-side functionality. Let’s split this out as
a separate issue so we can investigate further without taking focus away from
the essential steps.
> It would, hover, require us to find a shared way to define how what lines we
> consider an area. I see that osm2geojson-ultra does this [in a static
> file](https://github.com/dschep/osm2geojson-ultra/blob/main/src/polytags.json).
> iD and OSMCha use a different approach, AFAIK both
> https://github.com/ideditor/id-area-keys which is not updated ATM. Maybe we
> should try to revitalize this projects?
I don’t think this needs to be perfect right out of the gate.
osm2geojson-ultra’s file already manages to be more comprehensive than
[leaflet-osm’s hard-coded list of area
keys](https://github.com/openstreetmap/leaflet-osm/blob/9af3c9e86a3723b02b4cfdfc3283246e6494713d/leaflet-osm.js#L92).
Any improvements from dschep/osm2geojson-ultra#8 would be transparent to
osm-website, even if it means a transitive dependency on id-area-keys.
--
Reply to this email directly or view it on GitHub:
https://github.com/openstreetmap/openstreetmap-website/issues/6234#issuecomment-3678599033
You are receiving this because you are subscribed to this thread.
Message ID:
<openstreetmap/openstreetmap-website/issues/6234/[email protected]>
_______________________________________________
rails-dev mailing list
[email protected]
https://lists.openstreetmap.org/listinfo/rails-dev
