We're sorry but this page doesn't work properly without JavaScript enabled. Please enable it to continue.
Feedback

Baremaps studio: dynamic vector tiles map rendering

00:00

Formal Metadata

Title
Baremaps studio: dynamic vector tiles map rendering
Title of Series
Number of Parts
351
Author
License
CC Attribution 3.0 Unported:
You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor.
Identifiers
Publisher
Release Date
Language
Production Year2022

Content Metadata

Subject Area
Genre
Abstract
Baremaps is a blazing fast vector tile server which makes your life easier regarding the publication of OSM data: import, generation and cloud storage. But Baremaps also shines and differentiates from solutions like pg_tileserv in the way you can customize your tileset and merge custom datasets. Based on this advantage, we turn Baremaps out to be a vector tiles studio api, allowing the user to easily customize the content of the vector tiles. We adopted the OGC api specification for tileset, layers and styles. Baremaps offers various entry points to manage the datasets and serve them as vector tiles. As an exemple, you can dynamically import different kinds of data sources (geojson, SHP, database) to the server which will expose them as datasets, then you can use any kind of dataset within the same tileset. You can also bring value to your data by doing aggregations (spatial, attribute, hexbin) or computation. It leverages the power of postgis functions and vector tiles specification into one solution. You can attach a style for your dataset and baremaps will serve both Mapbox style file and Vector tiles stream to render the map the way you expect. To illustrate this concept, we will showcase a studio UI which literally provides a tool to quickly create valuable maps and publish them to the web. Baremaps Studio is the solution to handle dynamic rendering and styling of your vector datas.
Keywords
Open sourceMean value theoremService (economics)Server (computing)DisintegrationCache (computing)Streaming mediaPower (physics)Mean value theoremFunction (mathematics)Content (media)Software developerType theoryVector spaceWeb 2.0Level (video gaming)MappingCASE <Informatik>Query languageData integrityPrototypeMathematical singularityRepresentational state transferModule (mathematics)Zoom lensParallel portElectronic visual displayServer (computing)TessellationTesselationElectronic mailing listComputer animation
Computer fileComputing platformSource codeLevel (video gaming)Set (mathematics)Computer fileData storage deviceComputer animation
Scanning tunneling microscopeData typeText editorCircleRadiusVector spaceTable (information)TesselationPoint (geometry)Streaming mediaMappingDot productType theoryComputer animation
Text editorCircleRadiusIntegerAttribute grammarLattice (order)MoistureVector spaceLattice (order)MappingStreaming mediaType theoryCodeComputer animation
Attribute grammarLattice (order)PolygonMappingClient (computing)CountingContent (media)Type theoryVector spaceFlow separationFunctional (mathematics)Point (geometry)Server (computing)TessellationSet (mathematics)Computer animation
BuildingCombinational logicMappingComputer animation
MappingCuboidLevel (video gaming)Attribute grammarComputer animation
Mean value theoremStreaming mediaStreaming mediaVector spaceLevel (video gaming)Point (geometry)PolygonType theoryCuboidWeb 2.0Computer animation
Demo (music)Web 2.0Presentation of a group2 (number)Streaming mediaComputer animation
Open sourceXML
Transcript: English(auto-generated)
Go ahead. Okay. So, I'm Florent Garvin. I'm working at Camp2Camp as a research and development lead. And I'm going to talk about Bear Maps Studio, which is a new way to build your map and publish your map based on vector types. So, it's based on Bear Maps, which is yet another MVT server, but it has the singularity
to be a full package MVT server with OSM data integration pipeline, facilities to cache the output in S3 or buckets. There is a Maputnik which is integrating, so everything is made to ease the publication of your own vector types stream with your own style.
Yes. One thing is the typeset definition. It's the way Bear Maps display and the content of the vector types. So, for each layers, you have different queries depending on zoom level, and it's directly SQL queries.
So, actually, in the end, it aggregates all these queries, parallelize them, and give the content of the vector types. So, from this, we wanted to leverage the power of PostGIS to be able to construct and to define the content, complex content inside or within our vector types. So, on top of that, we added a module called the Studio with an OGC API compliance for tiles, styles,
and tilesets. So, there is a REST API to control these tilesets and the styles. What does it mean? It means we are able from the web to create, yes, to elaborate the content of our MVTs.
A use case to illustrate that, the car accident in Brittany. So, here, we develop a prototype studio to use the API. So, you can add and connect to a data source. So, here, I have my car accident as a geosystem file.
So, actually, when I push it, it push the datasets and ingest that into PostGIS. Then the dataset is present in my local storage, and I can load it in my map. When I load the dataset in my map, actually, it uploads the typeset definition, and it adds a select star from the table which has been created.
Then, bare maps gives these dots as points as in the vector type stream. You also have a usual edition of the style, so nothing fancy there, but you can change the style of your points, do data-driven styles, and so on.
So, here, what happen is that there is the data inside of the PostGIS and bare maps. Provide the data within a vector type stream. Now, because there is PostGIS behind that, it's just a select star, but we can see there is a department code inside of the dataset.
So, we can do spatial join. And here, from the same dataset, the bare maps in the vector types does not contain point, but contain polygon with the aggregation and the count of accident per department. Because there is PostGIS, you can do spatial joins,
you can use PostGIS function like xbin, and everything you want to value the content of your data. So, here, everything is done on the server, and nothing is done on the client. You can have several datasets per tileset, of course, and you can combine OSM data with your own data,
because bare maps allow you to integrate easily OSM dataset. So, it's based on bare maps, bare maps studio. All the requests are done with PostGIS, and we embrace the ecosystem of my box with the tileset and the styles. This is the example of the automatic joins
which are made when you push your tileset, so attributes and spatial. The style is very easy, using my box style to do choropleth. And in the end, it's just one stream of vector types that can contain points, aggregation, polygons, xbin, whatever, and one my box style,
et voila, you have your map published on the web. For the last second, okay, so it's finished. If you check out the presentation, you can find a video with more examples. And that's it. Thank you.