### Introduction
Localization package provides tools for multilateration and triangulation in `2D`,`3D` and on `earth surface`.
The current model of the earth, supported by the package, is called `Earth1`.
Earth1 models the earth as an ideal sphere having radius of 6378.1 kilometers.
### Installation
The package has been tested with python2.7 and python3.6. Use pip to install the package:
```
pip install localization
```
### Usage
Typical usage of the package is:
```python
import localization as lx
```
To initilaize new localization Project use:
```python
P=lx.Project(mode=<mode>,solver=<solver>)
```
Currently three modes are supported:
- 2D
- 3D
- Earth1
Also three solvers can be used:
- LSE for least square error
- LSE_GC for least square error with geometric constraints. Geometric constraints force the solutions to be in the intersection areas of all multilateration circles.
- CCA for centroid method, i.e., the solution will be the centroid of the intersection area. If no common intersection area exist, the area with maximum overlap is used.
To add anchors to the project use:
```python
P.add_anchor(<name>,<loc>)
```
where name denote user provided label of the anchor and <loc> is the location of the anchor provided in tuple, e.g., (120,60).
To add target use:
```python
t,label=P.add_target()
```
t is the target object and label is the package provided label for the target.
Distance measurements must be added to target object like:
```python
t.add_measure(<anchore_lable>,<measured_distance>)
```
Finally running P.solve() will locate all targets. You can access the estimated location of the target t by t.loc.
t.loc is a point object. Point object `B` has `x`,`y`,`z` coordinates available by `B.x`, `B.y`, `B.z` respectively.
Here is a sample use of the package for three anchors and one target scenario:
```python
import localization as lx
P=lx.Project(mode='2D',solver='LSE')
P.add_anchor('anchore_A',(0,100))
P.add_anchor('anchore_B',(100,100))
P.add_anchor('anchore_C',(100,0))
t,label=P.add_target()
t.add_measure('anchore_A',50)
t.add_measure('anchore_B',50)
t.add_measure('anchore_C',50)
P.solve()
# Then the target location is:
print(t.loc)
```
---
contact: __kamal.shadi85@gmail.com__
Metadata
Release files for Localization 0.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| Localization-0.1.7.tar.gz | 12.4 kB | Without provenance | Details for Localization-0.1.7.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| Localization-0.1.7-py3-none-any.whl | Python 3 | none | any | Details for Localization-0.1.7-py3-none-any.whl |
Total release size: 28.7 kB
Release files / Localization-0.1.7.tar.gz
| Download URL | Localization-0.1.7.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ddf8db1c1235ceea8e9515facea66a056454f707fdd4ff054a3ce4596d44aa8c
|
|
BLAKE2b-256 checksum How to use checksums |
8273a8153fe113dd7523a22f67f6a9def0de56a1a95593606585d71b9e017698
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/38.4.0 requests-toolbelt/0.8.0 tqdm/4.22.0 CPython/2.7.14
|
Release files / Localization-0.1.7-py3-none-any.whl
| Download URL | Localization-0.1.7-py3-none-any.whl |
|---|---|
| Size | 16.3 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
fc72e24bd18cfe4b4afea348fb08056732e096886c043e4b6353fecebfd7e34c
|
|
BLAKE2b-256 checksum How to use checksums |
8d7eb1323bfade87d5ca5e61f083e44124f0b24cf7a557b23a4496c0811387f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/38.4.0 requests-toolbelt/0.8.0 tqdm/4.22.0 CPython/2.7.14
|
Security for Localization 0.1.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.