WebGL-powered map analytics for BigQuery and Snowflake. Lightweight alternative to CARTO and Foursquare Studio for data scientists, analysts and engineers.
Empower teamwork with our new editing and refresh features for shared reports. Now, every user can refresh data with a simple click, ensuring everyone has the latest insights at their fingertips. Plus, grant editing access to trusted colleagues to foster a truly collaborative environment.
Thanks to @Tsovak contribution you now can configure Dekart to query PostgreSQL! PostgreSQL, when paired with the PostGIS extension, becomes an incredibly powerful database for managing and querying geospatial data due to its ability to efficiently store, index, and perform complex spatial queries.
Dekart now introduces dedicated space, which allows you to seamlessly configure and manage connections, streamlining your workflow and enhancing your data interaction experience.
No Google Service account required any more!
This feature allows Dekart to authorize users via Google OAuth 2.0 and pass user-specific tokens to access BigQuery and Cloud Storage. No more need for a universal service account or setting GOOGLE_APPLICATION_CREDENTIALS
! Plus, all tokens are stored only in your browser memory, offering an additional layer of security.
Required User Permissions:
Note: This feature is currently only supported for BigQuery and Cloud Storage data sources.
How to enable?
Set these environment variables to get started:
DEKART_REQUIRE_GOOGLE_OAUTH=1
DEKART_GOOGLE_OAUTH_CLIENT_ID=Your-Client-ID
DEKART_GOOGLE_OAUTH_CLIENT_SECRET=Your-Client-Secret
Now Dekart users can create Data Connections directly through the UI, stepping away from the single configuration approach facilitated by environment variables. Coupled with the recently implemented pass-through authentication, this upgrade empowers users and admins with unparalleled control over the data stored and cached.
Currently, only BigQuery supported DEKART_DATASOURCE=BQ
.
To enable the feature, leave empty DEKART_BIGQUERY_PROJECT_ID=
and/or DEKART_CLOUD_STORAGE_BUCKET=
The following images have been updated: dekartxyz/dekart:0.14.1
, dekartxyz/dekart:0.14
, dekartxyz/dekart:latest
Upgrade from previous versions
Now you can rename dataset tabs. Before they had automatic names assigned like Query 1
, Query 2
. Dataset layer in visualization panel will also pick up the new name.
Added a mechanism to configure extra OAuth scopes for BigQuery. Extra OAuth scopes can be supplied via the DEKART_GCP_EXTRA_OAUTH_SCOPES
environment variable as a comma-delimited list. (#122).
This allows querying a BigQuery table backed by a Google Sheet residing in Google Drive. In this case, it is necessary to set DEKART_GCP_EXTRA_OAUTH_SCOPES=https://www.googleapis.com/auth/drive
.
This feature is the first contribution made by @hnicke 🚀
Added the ability for users to export their maps as HTML, images and data (#106). This can also be useful for printing maps or exporting to PDF. Thank you, @pooriaPoorsarvi, for the support and contribution!
Added the ability to specify an AWS Athena workgroup via an environment variable. This gives you the option to segment your query execution history for better governance, management, and isolation of queries (#102). Thank you, @seanlane, for the contribution.
Added an option to configure Postgres using a connection string (#97). It allows specifying sslmode
and use Dekart with wider range of managed Postgres services. Thank you, @christippett, for the contribution.
Additionally to the existing CSV format, you can now also upload GeoJSON files to be used as datasets for your visualizations. As per the previous release, files are stored in the same storage as the SQL query cache. Both Amazon S3 and Google Cloud Storage are supported.
As a step towards better collaboration within an organization, we now introduce the feature allowing to make your own reports discoverable to other users. When sharing a report, you will allow other users of the same organization/website domain to see it in Shared Reports
with only view access. Simply uncheck this setting and your report will not be visible anymore.
While this feature enhances discoverability, you can still see reports of other users from your organization if they share their link with you directly.
You can now resize the query editor, allowing each user to define how big they want the map/editor for certain use cases. Simply drag the bar left and right to find your perfect configuration!
With the upgrade to the latest version of kepler.gl, you can now leverage their Copy Geometry
feature to extract the coordinates of vertices from a manually drawn polygon on the map. Simply paste in the query editor and there you go!
As we all love data, Dekart appends some anonymized statistics to the referrer of external links related to the usage of the tool.
You have full control on if you allow this or not. Simply configure the variable DEKART_DISABLE_USAGE_STATS
in your deployment environment.
See details in user experience configuration
You can now upload enable file upload by setting DEKART_ALLOW_FILE_UPLOAD=1
in environment variables. Once enabled, you can upload .csv
files to Dekart backend and add them to your report. Files are stored in the same storage as SQL query cache. Both Amazon S3 and Google Cloud Storage are supported.
New environment configuration DEKART_CORS_ORIGIN=
is strongly recommended to secure your deployment from CORS attacks. CORS attack allow 3rd party to delete, edit and run queries on behalf of the user visiting malicious web page.
Now, you can configure user authorization in Dekart when using Amazon Load Balancer to host Dekart
You can configure Amazon Load Balancer to authenticate users via Amazon Cognito. Dekart parses x-amzn-oidc-data
header, validates the JWT token and extracts claims containing user email. When you configure DEKART_REQUIRE_AMAZON_OIDC
option, users will be authorized user to:
Links: