QField | A simplified touch optimized interface for QGIS

by opengisch C++ Version: v2.8.2 License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(2)Vulnerabilities Install Support

kandi X-RAY | QField Summary

QField is a C++ library typically used in Quantum Computing applications. QField has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

A simplified touch optimized interface for QGIS. Perfect for field work on portable touch devices.

Support

Quality

Security

License

Reuse

Support

QField has a low active ecosystem.

It has 597 star(s) with 178 fork(s). There are 66 watchers for this library.

It had no major release in the last 12 months.

There are 210 open issues and 1093 have been closed. On average issues are closed in 141 days. There are 3 open pull requests and 0 closed requests.

It has a neutral sentiment in the developer community.

The latest version of QField is v2.8.2

Quality

QField has 0 bugs and 0 code smells.

Security

QField has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

QField code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

QField is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

QField releases are available to install and integrate.

It has 3085 lines of code, 67 functions and 58 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of QField

Get all kandi verified functions for this library.

QField Key Features

No Key Features are available at this moment for QField.

QField Examples and Code Snippets

No Code Snippets are available at this moment for QField.

Community Discussions

Trending Discussions on QField

Embedding files in an iOS app (C++/Qt/cmake)

Postgresql requests proxied by HTTP server

QUESTION

Embedding files in an iOS app (C++/Qt/cmake)

Asked 2020-Nov-29 at 16:50

In an iOS c++/Qt application, I need to ship a few files and to keep them in their directory structure.

For the Android version, we bundle a zip which we unzip on the target before creating the QApplication.

On iOS, it seems that CMake is not capable of bundling files in a tree: https://cmake.org/cmake/help/latest/prop_tgt/RESOURCE.html#prop_tgt:RESOURCE https://cmake.org/cmake/help/latest/prop_sf/MACOSX_PACKAGE_LOCATION.html

I am not sure if this is a limitation of cmake or if this is a global limitation on iOS. From the docs about iOS bundles:

It uses a relatively flat structure with few extraneous directories in an effort to save disk space and simplify access to the files.

What would be the preferred approach?

Is there a solution to ship the files from CMake directly?
If not, how can I achieve this so that they are available before the QApplication is created?

The xcode command

Thanks to @Cy-4AH, I added the folder in Xcode and could get the command to do this:

...

ANSWER

Answered 2020-Nov-27 at 20:56

So apparently the CMake method also works for directories.

Source https://stackoverflow.com/questions/64931610

QUESTION

Postgresql requests proxied by HTTP server

Asked 2020-Jul-08 at 15:20

I am using a mobile application that connects directly to the database instance (Postgres), as such, I have to keep the ports open for traffic that is generated from the internet (4G, mobile app).

This mobile app (QFIELD, mobile version of QGIS) has a direct connection to the database, this is the reason why the database is reachable from the internet on a public ip but this is a critical issue for the security of the data and the requests that can be sent to the database.

I would like to proxy the requests so that the database is only available to local machines and not open for connections directly.

The mobile appp would send the request to an HTTP url which would send the request to the local ip and port, this way I would avoid to have the database exposed on the internet.

Ideally, I would like to go from this app (which uses a postgres connection string to connect to the server) to an HTTP server that routes the request locally, as such:

APP connects to https://myproxy/postgres
Request is proxied to a local server

Can I do this with Apache2? Any ideas?

At the moment I cannot write a middleware that proxies requests from the APP to the local postgres.

...

ANSWER

Answered 2020-Jul-08 at 15:20

If your application is expecting to connect directly to a PostgreSQL database and you don't want to change that then you need to connect to something that "speaks" PostgreSQL's client protocol.

You can place a proxy such as pgbouncer or pgpool in front of it, but they aren't a guarantee of greater security just by themselves. This is the same problem as with any proxy - it is just forwarding requests and responses to your actual server so any vulnerability is still exposed.

What you can do is:

restrict the number of connections at the proxy point
restrict which users can connect non-locally to your PostgreSQL cluster
restrict where they can connect from to just your proxy
restrict those users permissions within the database(s)

That last point is particularly important - assume any user account your application can be used maliciously. Restrict the account to prevent mass updating or deleting of data. Also take special care to restrict access to other users' data.

If I was forced to allow access like this, I would want one PostgreSQL user account per actual user at the very least. In practice I wouldn't get to this point with a production application.

Source https://stackoverflow.com/questions/62790958

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install QField

You can download it from GitHub.

Support

QField is an open source project, licensed under the terms of the GPLv2 or later. This means that it is free to use and modify and will stay like that. We are very happy if this app helps you to get your job done or in whatever creative way you may use it. If you found it useful, we will be even happier if you could give something back. A couple of things you can do are.

Find more information at: