Backendless App Blueprints released in Version 6 let you get a jump on your development process by starting with a prebuilt app foundation.
In January of this year, we introduced spatial data functionality to Backendless Database. The purpose of this new data type was to replace the existing Geolocation features on the platform. On October 5th, 2020, this transition will be complete.
In January 2020, we introduced new spatial data types that will be replacing our existing geolocation features. This week, we released an update for our .NET SDK that will allow you to work with those new data types.
In this edition of Backendless Spotlight, we are going to look at a social platform designed to bring together individuals that suffer from epilepsy. Neurish is a U.S.-based company that has built a series of web apps – powered by a shared Backendless backend – to help those battling the disorder.
We are excited to announce a new release for the Backendless platform as we approach the release of Version 6.0. Available now, Release 5.7.0 includes two powerful new features: spatial data and console visibility controls. Read on to learn more.
Data objects in Backendless can be connected to related properties not only in other tables, but also with Geopoints. These relationships may be declared programmatically or using Backendless Console. In this post, we will review the process of declaring a Data-to-Geo relationship in a data table schema.
Geolocation is one of the most powerful features of Backendless. The geolocation service provides APIs for storing, searching and managing geolocation data. There are three main elements that the geolocation service operates on: geocategories, geopoints, and points metadata.
Backendless Geolocation allows you to map a location to a data object. This feature can lead to a lot of interesting opportunities. For example, consider a taxi booking service like Uber. You may have multiple cars/drivers available for hire as well as customers putting in pickup requests. Both drivers and customers may be represented by…
In another post, we described how to declare a relationship in a data table schema with a geopoint. Now that you know how to create a table column that contains one or more geopoints, we are going to show how to populate it with data.