Apache Baremaps: online maps toolkit(baremaps.apache.org) |
Apache Baremaps: online maps toolkit(baremaps.apache.org) |
Here is the fullscreen demonstration for those who are interested. https://demo.baremaps.com/
Lately I’ve revisited the idea and found that with wasm, SharedArrayBuffer for parallelism, and more maturing libraries, it may be possible to provide a much richer set of analytical tools.
Is this an idea you’ve explored? This would be my “if I won the lottery, what would I work on?” project.
I’m not a raster or EO person so I can’t speak to GDAL’s availability, but I’m dubious that the browser is a good interface for that kind of work, or for a full GIS more generally.
Assume Apache Baremaps uses an Apache license, it might be more wasm-friendly than most GIS software…
Things like map libs for mobile and the web with advanced things like 3d, navigation, elevation and the likes?
I feel like we need a go to solution that unchains away from the commercial solutions to power osm solutions across devices and use cases.
How is baremaps different to it? Does baremaps also work without PostgreSQL? Or is PostgreSQL required and then it does support real time updates or similar? How long does a planet-wide import take (for vector tiles) and how much RAM does it require?
As the default renderer for openstreetmap.org, Carto is currently an embarrassment for OpenStreetMap.
QGIS might be another client to test against. They’ve implemented OGC API read/write support. Plus, QGIS is great for mocking up a wide range of GIS user scenarios.
https://demo.baremaps.com/#12.91/32.06932/34.75969
Should be “תל אביב”, not “ביבא לת”. How do these issues even exists in 2023? Is a team building these renders not aware of RTL languages, or do they just not bother implementing it?
Have actually tried writing something that handles languages running in different directions? It might be 2023, but the libraries... aren't great...
As long as the core developpers of the new platform live and work on the US west coast, any issue non relevant to the US will be a second class citizen, mostly dealt with after the product is deemed stable.
The same way OpenAI operates in english first and other language systems will be improved "later".
It's not a jab on the devs, I realistically can't see any other approach. Just another angle where there's no free lunch and more investment is needed building systems that aren't US first if we care about non-US needs being met in a timely manner.
From my perspective, planetiler started as an effort to generate vector tiles from the OpenMapTile schema as fast as possible (pbf -> mvt). By contrast, Baremaps started as an effort to create a new schema and style from the ground up. In this regard, having a database (pbf -> db <- mvt) enables to live reload changes made in the configuration files. The database has a cost, but also comes with additional advantages (updates, dynamic data, on demand generation of tiles at zoom levels 16+, etc.).
That being said, I think the two projects overlap and I hope we will find opportunities to collaborate in the future. For instance, whereas PostgreSQL is still required in Baremaps, I recently ported a lot of the ST_ function of Postgis to Apache Calcite with the intent to execute SQL on fast memory mapped collection.
https://github.com/apache/calcite/blob/main/core/src/main/ja...
A planet wide import in Postgis currently takes about 4 hours with the COPY API (easy to parallelize) followed by about 12 hours of simplification in Postgis (not easy to parallelize). I will try to publish a detailed benchmark in the future.
Thanks also to the link for calcite. The import times with Postgis really sound impressive. (if you post benchmarks do not forget to include Xmx and physical available memory :) )
I'll take a brief look into all this - maybe something valueable we can learn for GraphHopper.
Can you explain what you mean with "live reload of configuration files"? I'm not that familiar with map tiles, but do you mean the configuration that e.g. house numbers should come for zoom levels 12-16 and no longer from 12-15 or something?