Live data from Hacker News

Apache Baremaps: online maps toolkit

baremaps.apache.org

41–46 of 46 posts

Re: Apache Baremaps: online maps toolkit

#41
post #34

Really cool! Any thought to Baremaps as an OGC API data provider for something like Pygeoapi? https://docs.pygeoapi.io/en/stable/plugins.html

We recently attended the OGC/Apache Code Sprint at Camptocamp and improved our experimental support for Collection, Conformance, Tiles and Styles. In the future I would also like to expose the attributes and geometries of the database with the Feature API. We havn't yet tested our implementations with an external client and Pygeoapi would demonstrate interoperability very well.

Re: Apache Baremaps: online maps toolkit

#42
post #7
post #5

This is a great addition to the space. Do you plan to fill the gap left by mapbox for the open source community? 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.

Yes, there is clearly a need for a go-to solution. MapLibre and Cesium are doing a great job with their open-source renderers. Baremaps complements this by providing open infrastructure components, such as a data pipeline and a vector tile server. For instance, another missing piece in this space is an open-source IP to location solution. Our current prototype is rudimentary but demonstrates that this gap can be fill…

I see you also use some minor code from planetiler :)

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?

Re: Apache Baremaps: online maps toolkit

#44
post #7

Earlier quoted context omitted.

Yes, there is clearly a need for a go-to solution. MapLibre and Cesium are doing a great job with their open-source renderers. Baremaps complements this by providing open infrastructure components, such as a data pipeline and a vector tile server. For instance, another missing piece in this space is an open-source IP to location solution. Our current prototype is rudimentary but demonstrates that this gap can be fill…

I see you also use some minor code from planetiler :) 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?

Yes, planetiler rocks and the memory mapped collections enabled us to remove our dependency to rocksdb ;)

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 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.

Re: Apache Baremaps: online maps toolkit

#45
post #34

Really cool! Any thought to Baremaps as an OGC API data provider for something like Pygeoapi? https://docs.pygeoapi.io/en/stable/plugins.html

We recently attended the OGC/Apache Code Sprint at Camptocamp and improved our experimental support for Collection, Conformance, Tiles and Styles. In the future I would also like to expose the attributes and geometries of the database with the Feature API. We havn't yet tested our implementations with an external client and Pygeoapi would demonstrate interoperability very well.

Really cool!

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.

Re: Apache Baremaps: online maps toolkit

#46

Earlier quoted context omitted.

I see you also use some minor code from planetiler :) 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?

Yes, planetiler rocks and the memory mapped collections enabled us to remove our dependency to rocksdb ;) 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 That being said, I think the two…

This sounds really interesting. (unfortunately I did not notice earlier that you replied)

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?

Post reply on HN