Trends and insights from our IT experts

Just think of the number of objects that Google Maps has to store to support everything we do while using the application - all the buildings in the world, all the roads, rivers, terrain information, traffic… On the other hand, users will often expect instant or close to instant responsiveness of the application while moving on the map and zooming in and out. So, how do we accomplish that?

Imagine a scenario. You are working on a new complex feature. Your team releases to production every two weeks, but to complete the feature, you need more than that. You can always create a feature branch and postpone merging to the main branch until everything is done, but this brings some risks. There is another approach you can use: a technique called feature flags.

In this article, we will put together some of the basic spatial data types and operations while leveraging PostGIS to build something that resembles a real-world application that can be useful for our daily lives. The focus will be on the database layer of the application, as that’s where most of the GIS magic happens, but we will ultimately build a full-stack application featuring PostGIS database, Java Spring Boot back-end, and HTML/JavaScript front-end.

From adding numbers to translating sentences, it’s all just simple operations on binary data. “But how is it even possible to operate on textual data?” Good question! Let’s find out.

If you are a web developer who wants to achieve faster time to market for new products and features, cut (almost eliminate) time to provision and manage infrastructure, minimize downtime and security risks, along with costs - this is the place for you.

In this article, we will cover some basics of PostGIS and what it can do, along with some tips and tricks that can be used to simplify solutions or improve performance. In short - PostGIS is a Postgres extension that adds support for storing and manipulating spatial data types.