@opengis/partsmap 0.0.43 → 0.0.45

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (4) hide show
  1. package/README.md +56 -64
  2. package/dist/PartsMap.js +3087 -3102
  3. package/dist/PartsMap.umd.cjs +37 -37
  4. package/package.json +3 -3
package/README.md CHANGED
@@ -1,92 +1,84 @@
1
- # partsmap
1
+ ![alt text](https://cdn.softpro.ua/data/npm/partsmap/opengis-partsmap.png)
2
2
 
3
+ [![NPM version](https://img.shields.io/npm/v/@opengis/partsmap?style=plain)](https://www.npmjs.com/package/@opengis/partsmap)
4
+ [![NPM last update](https://img.shields.io/npm/last-update/@opengis/partsmap?style=plain)]()
5
+ [![NPM downloads](https://img.shields.io/npm/dw/@opengis/partsmap?style=plain)]()
6
+ [![js-standard-style](https://img.shields.io/badge/code%20style-standard-brightgreen.svg?style=plain)](http://standardjs.com/)
3
7
 
8
+ Partsmap is part table, part map.
4
9
 
5
- ## Getting started
10
+ ### Why Partsmap?
6
11
 
7
- To make it easy for you to get started with GitLab, here's a list of recommended next steps.
12
+ - **Spatial representation of data:** Combining both interfaces on single page allows for instant data visualization.
13
+ - **Base Theme:** A clean and practical design inspired by Preline.
14
+ - **Base maps:** Possibility to add any map tiles.
15
+ - **Smooth transitions:** Zoom in and out between objects with fluid animations.
16
+ - **Color attributes:** Use CLS to define and differentiate data visually.
17
+ - **Server Side Rendering** - Ensures quick and responsive content delivery.
8
18
 
9
- Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
19
+ ### Features
10
20
 
11
- ## Add your files
21
+ - Filter and search
22
+ - Detailed data cards
23
+ - Attribute based styling
24
+ - Print and share
25
+ - Data history
26
+ - SSR
12
27
 
13
- - [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
14
- - [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
28
+ ---
15
29
 
16
- ```
17
- cd existing_repo
18
- git remote add origin https://git.softpro.ua/npm/partsmap.git
19
- git branch -M main
20
- git push -uf origin main
21
- ```
22
-
23
- ## Integrate with your tools
24
-
25
- - [ ] [Set up project integrations](https://git.softpro.ua/npm/partsmap/-/settings/integrations)
26
-
27
- ## Collaborate with your team
30
+ ### Install
28
31
 
29
- - [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
30
- - [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
31
- - [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
32
- - [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
33
- - [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
34
-
35
- ## Test and Deploy
36
-
37
- Use the built-in continuous integration in GitLab.
32
+ ```bash
33
+ npm i @opengis/partsmap
34
+ ```
38
35
 
39
- - [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
40
- - [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing(SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
41
- - [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
42
- - [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
43
- - [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
36
+ ### Usage
44
37
 
45
- ***
46
38
 
47
- # Editing this README
39
+ ```ts
40
+ import PartsMap from '@opengis/partsmap';
41
+ import '@opengis/partsmap/dist/style.css';
42
+ PartsMap.install(app);
43
+ ```
48
44
 
49
- When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thank you to [makeareadme.com](https://www.makeareadme.com/) for this template.
45
+ ---
50
46
 
51
- ## Suggestions for a good README
52
- Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
47
+ ### Documentation
53
48
 
54
- ## Name
55
- Choose a self-explaining name for your project.
49
+ For a detailed understanding of `partsmap`, its features, and how to use them, refer to our [Documentation](https://apidocs.softpro.ua/partsmap/).
56
50
 
57
- ## Description
58
- Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
51
+ ---
59
52
 
60
- ## Badges
61
- On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
53
+ ### Technology stack
62
54
 
63
- ## Visuals
64
- Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
55
+ <a href="https://vuejs.org/" target="_blank">
56
+ <img src="https://img.shields.io/badge/Vue%20js-323330?style=for-the-badge&logo=vuedotjs&logoColor=4FC08D" /></a>
65
57
 
66
- ## Installation
67
- Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
58
+ <a href="https://maplibre.org/" target="_blank">
59
+ <img src="https://img.shields.io/badge/Maplibre-323330?style=for-the-badge&logo=maplibre&logoColor=87b2f0" /></a>
68
60
 
69
- ## Usage
70
- Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
61
+ ---
71
62
 
72
- ## Support
73
- Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
63
+ ### Contribute
74
64
 
75
- ## Roadmap
76
- If you have ideas for releases in the future, it is a good idea to list them in the README.
65
+ Feel free to contact us through our website [SOFTPRO.UA](https://softpro.ua) or email <info@softpro.ua>
77
66
 
78
- ## Contributing
79
- State if you are open to contributions and what your requirements are for accepting them.
67
+ - Report bugs
68
+ - Share your ideas
69
+ - Ask questions
80
70
 
81
- For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
71
+ ### Follow Us
82
72
 
83
- You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
73
+ [Official site](https://softpro.ua)
84
74
 
85
- ## Authors and acknowledgment
86
- Show your appreciation to those who have contributed to the project.
75
+ <p>
76
+ <a href="https://www.instagram.com/gissoftpro/" target="_blank"><img src="https://cdn.softpro.ua/data/npm/instagram.png" alt="Softpro Instagram" title="oftpro Instagram"></a>&nbsp;&nbsp;
77
+ <a href="https://www.facebook.com/gissoftpro" target="_blank"><img src="https://cdn.softpro.ua/data/npm/facebook.png" alt="Softpro Facebook" title="Softpro Facebook"></a>&nbsp;&nbsp;
78
+ <a href="https://t.me/softprogis" target="_blank"><img src="https://cdn.softpro.ua/data/npm/telegram.png" alt="Softpro Telegram" title="Softpro Telegram"></a>&nbsp;&nbsp;
79
+ <a href="https://www.linkedin.com/in/softpro-ukraine-a8876b282/recent-activity/all/" target="_blank"><img src="https://cdn.softpro.ua/data/npm/social/linkedin.png" alt="Softpro Linkedin" title="Softpro LinkedIn"></a>&nbsp;&nbsp;
80
+ </p>
87
81
 
88
- ## License
89
- For open source projects, say how it is licensed.
82
+ ### License
90
83
 
91
- ## Project status
92
- If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
84
+ Copyright © SOFTPRO. All rights reserved.