pg_tileserv VS openstreetmap-carto

Fine for a POC but there are much better libraries for serving MVT, for instance: https://github.com/CrunchyData/pg_tileserv

If it's small as in the couple-of-MB range you could convert to GeoJSON, serve it as a static file fed into a small web app like u/techmavengeospatial suggested that handles filtering by query, and update the file as new data comes in. Alternatively if you want something more robust you can feed it into PostgreSQL and serve with something like pg_tileserv (with equivalent filtering in the web client).

ArcGIS Online could be the right move as long as you set up the service correctly. You could also load the shapefile into a database like PostgreSQL and connect to the database via an API like Geoserver FastVector, or pg_tileserv. This would cause a lot more time, cost, and knowledge on your end though to host a database and api vs loading the data into the ESRI ecosystem.

One thing I will recommend -- because it seems like you are simple using flask to query the DB and render to the frontend (just from looking through the code) you **MAY** be able to use https://github.com/CrunchyData/pg_tileserv and cut out the need to even have flask as a the server side language. Curious what your thoughts would be because I am currently working on a few web apps and in the past i've mainly used geodjango and flask as server side but recently created an entire application with postgres, pg_tileserv, leaflet

I wouldn't compare osm-website and osm-carto at all. The commit logs are very different.

openstreetmap-website: https://github.com/openstreetmap/openstreetmap-website/commi... . Numerous commits most days.

openstreetmap-carto: https://github.com/gravitystorm/openstreetmap-carto/commits . So far in 2024; one small regression fixed, one niche bit of tagging added to an existing style, some largely pointless code style tidying. That's it.

There are even two separate PRs to fix it that are pretty much ready to merge https://github.com/gravitystorm/openstreetmap-carto/pull/4456 https://github.com/gravitystorm/openstreetmap-carto/pull/4714

Looks like sense prevailed the following year. https://github.com/gravitystorm/openstreetmap-carto/issues/1654

Of course, natural=valley itself is widely used. I got curious why it isn't rendered on OSM Carto but place=locality is and stumbled on some interesting discussions on the issue tracker (1 and 2). The takeaway seems to be to avoid place=locality in favour of more specific tags.

It is strange to me that the pedestrian area gets rendered above the building... would you like to create a topic about this at community.openstreetmap.org ? I think this should be handled differently. I guess the next instance then would be to open an issue at https://github.com/gravitystorm/openstreetmap-carto (probably but I'm not 100% sure) or maybe here https://github.com/openstreetmap/operations

I think the best bet then is to see if there's anything to contribute to the conversation at https://github.com/gravitystorm/openstreetmap-carto/issues/3596 or whether a PR would be welcome.

Yes, it is the same style! In addition to info from /u/epicbirble, the style is called carto. It looks like Floodmap is using the OpenStreetMap standard layer, rendered using carto style, as its basemap.