| Name | holonote JSON |
| Version |
0.1.0
JSON |
| download |
| home_page | None |
| Summary | Annotate your data |
| upload_time | 2023-11-15 11:07:03 |
| maintainer | None |
| docs_url | None |
| author | None |
| requires_python | >=3.9 |
| license | Copyright (c) 2023, HoloViz team (holoviz.org).
All rights reserved.
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are
met:
* Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the
distribution.
* Neither the name of the copyright holder nor the names of any
contributors may be used to endorse or promote products derived
from this software without specific prior written permission.
THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
"AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. |
| keywords |
annotation
holoviews
tools
|
| VCS |
|
| bugtrack_url |
|
| requirements |
No requirements were recorded.
|
| Travis-CI |
No Travis.
|
| coveralls test coverage |
No coveralls.
|
# `holonote`
The `holonote` library offers tools to create, edit and persist
annotated regions for [HoloViews](https://holoviews.org/).
An annotated region marks a region-of-interest that is overlaid on top
of the visual representation of a HoloViews element. Such a region has a
unique identifier as well as additional domain-specific information
associated with it. What `holonote` offers is a flexible way to
interactively work with these visual regions as well as tools to add,
update and delete whatever domain-specific information you want to
associate with them.
There are two primary components currently offered by `holonote`:
1. `Annotators`: These classes offer the ability to interactively define
regions, add associated domain-specific information and then persist
this information to a database. You can interactively add, delete and
update these annotation regions as well as their associated
domain-specific data.
2. `Editors`: These tools are designed to let you interactively
manipulate and edit the visual regions themselves. These regions are in
fact HoloViews elements which means you can use these editors as
generic edit tools for the corresponding HoloViews elements.
By default, annotators automatically persist any annotations you create
to a local SQLite database file. This is a very convenient way to get
started with your annotation task, allowing you to immediate begin the
process of collecting useful information.
For production usage where you are investing significant resources
authoring annotations, it is advisable that you define a custom
connector to a more appropriate database system. You can also use
connectors to load annotations from existing databases of annotation
data.
**Do not use the SQLite connector when deploying to production. It is
intended for use only during local development. It is not designed to
be particularly efficient, stable, or secure.**
## Terminology
There are two particularly important pieces of terminology that are used
throughout this library to be aware of:
1. *Regions*: These denote the visual regions-of-interest with a final
visual representation as a HoloViews element. These may be one or two
dimensional, may have different visual representations for the same data
(e.g. a point marker or a crosshair to mark a point in 2D space) and
have different types:
- *Points*: A single value of interest in an N-dimensional space. For
instance, on a time axis, this corresponds to a moment in time
which may be represented visually as a vertical line. On an image,
this can ve visually represented with a crosshair.
- *Ranges*: A range is an axis-aligned span between a start and end
point. For instance, along a time axis, this corresponds to a time interval and
on an image, this corresponds to a 2D box.
2. *Fields*: These are the domain-specific component of the annotation
data, containing information that is not to be visualized by
`holonote`. These are defined by the user or application and can have
arbitrary types and contents. A complete set of fields together with one
or more regions constitutes an annotation.
Raw data
{
"_id": null,
"home_page": null,
"name": "holonote",
"maintainer": null,
"docs_url": null,
"requires_python": ">=3.9",
"maintainer_email": null,
"keywords": "annotation,holoviews,tools",
"author": null,
"author_email": null,
"download_url": "https://files.pythonhosted.org/packages/a2/2b/b9265d7d90ab3e50411e20b5fd3f3241542ba6ee9ac6a4b5d8f5b63aa430/holonote-0.1.0.tar.gz",
"platform": null,
"description": "# `holonote`\n\nThe `holonote` library offers tools to create, edit and persist\nannotated regions for [HoloViews](https://holoviews.org/).\n\n\n\nAn annotated region marks a region-of-interest that is overlaid on top\nof the visual representation of a HoloViews element. Such a region has a\nunique identifier as well as additional domain-specific information\nassociated with it. What `holonote` offers is a flexible way to\ninteractively work with these visual regions as well as tools to add,\nupdate and delete whatever domain-specific information you want to\nassociate with them.\n\nThere are two primary components currently offered by `holonote`:\n\n1. `Annotators`: These classes offer the ability to interactively define\nregions, add associated domain-specific information and then persist\nthis information to a database. You can interactively add, delete and\nupdate these annotation regions as well as their associated\ndomain-specific data.\n\n2. `Editors`: These tools are designed to let you interactively\nmanipulate and edit the visual regions themselves. These regions are in\nfact HoloViews elements which means you can use these editors as\ngeneric edit tools for the corresponding HoloViews elements.\n\nBy default, annotators automatically persist any annotations you create\nto a local SQLite database file. This is a very convenient way to get\nstarted with your annotation task, allowing you to immediate begin the\nprocess of collecting useful information.\n\nFor production usage where you are investing significant resources\nauthoring annotations, it is advisable that you define a custom\nconnector to a more appropriate database system. You can also use\nconnectors to load annotations from existing databases of annotation\ndata.\n\n**Do not use the SQLite connector when deploying to production. It is\n intended for use only during local development. It is not designed to\n be particularly efficient, stable, or secure.**\n\n## Terminology\n\nThere are two particularly important pieces of terminology that are used\nthroughout this library to be aware of:\n\n1. *Regions*: These denote the visual regions-of-interest with a final\nvisual representation as a HoloViews element. These may be one or two\ndimensional, may have different visual representations for the same data\n(e.g. a point marker or a crosshair to mark a point in 2D space) and\nhave different types:\n\n - *Points*: A single value of interest in an N-dimensional space. For\n instance, on a time axis, this corresponds to a moment in time\n which may be represented visually as a vertical line. On an image,\n this can ve visually represented with a crosshair.\n - *Ranges*: A range is an axis-aligned span between a start and end\n point. For instance, along a time axis, this corresponds to a time interval and\n on an image, this corresponds to a 2D box.\n\n2. *Fields*: These are the domain-specific component of the annotation\ndata, containing information that is not to be visualized by\n`holonote`. These are defined by the user or application and can have\narbitrary types and contents. A complete set of fields together with one\nor more regions constitutes an annotation.\n",
"bugtrack_url": null,
"license": "Copyright (c) 2023, HoloViz team (holoviz.org).\n All rights reserved.\n \n Redistribution and use in source and binary forms, with or without\n modification, are permitted provided that the following conditions are\n met:\n \n * Redistributions of source code must retain the above copyright\n notice, this list of conditions and the following disclaimer.\n \n * Redistributions in binary form must reproduce the above copyright\n notice, this list of conditions and the following disclaimer in the\n documentation and/or other materials provided with the\n distribution.\n \n * Neither the name of the copyright holder nor the names of any\n contributors may be used to endorse or promote products derived\n from this software without specific prior written permission.\n \n THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS\n \"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT\n LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR\n A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT\n OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,\n SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT\n LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,\n DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY\n THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT\n (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE\n OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.",
"summary": "Annotate your data",
"version": "0.1.0",
"project_urls": null,
"split_keywords": [
"annotation",
"holoviews",
"tools"
],
"urls": [
{
"comment_text": null,
"digests": {
"blake2b_256": "fc962a9eb7d7c71e3bb10592671f991032381bf6a805a5042c4e483ea51307ae",
"md5": "d4114f94ffd508e826d9b9230048dad1",
"sha256": "2036b3568c7d19653e1861030957a97b222f6478d34bcb7d33ed8d77ab6cff16"
},
"downloads": -1,
"filename": "holonote-0.1.0-py3-none-any.whl",
"has_sig": false,
"md5_digest": "d4114f94ffd508e826d9b9230048dad1",
"packagetype": "bdist_wheel",
"python_version": "py3",
"requires_python": ">=3.9",
"size": 40018,
"upload_time": "2023-11-15T11:07:05",
"upload_time_iso_8601": "2023-11-15T11:07:05.231246Z",
"url": "https://files.pythonhosted.org/packages/fc/96/2a9eb7d7c71e3bb10592671f991032381bf6a805a5042c4e483ea51307ae/holonote-0.1.0-py3-none-any.whl",
"yanked": false,
"yanked_reason": null
},
{
"comment_text": null,
"digests": {
"blake2b_256": "a22bb9265d7d90ab3e50411e20b5fd3f3241542ba6ee9ac6a4b5d8f5b63aa430",
"md5": "c140e4fdc78e46f491691d445ce58705",
"sha256": "7adc3d749f1483a5b29b14c619da7fcd88eea4037f1a5c66868eaf18dea3c2ce"
},
"downloads": -1,
"filename": "holonote-0.1.0.tar.gz",
"has_sig": false,
"md5_digest": "c140e4fdc78e46f491691d445ce58705",
"packagetype": "sdist",
"python_version": "source",
"requires_python": ">=3.9",
"size": 2230391,
"upload_time": "2023-11-15T11:07:03",
"upload_time_iso_8601": "2023-11-15T11:07:03.438180Z",
"url": "https://files.pythonhosted.org/packages/a2/2b/b9265d7d90ab3e50411e20b5fd3f3241542ba6ee9ac6a4b5d8f5b63aa430/holonote-0.1.0.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2023-11-15 11:07:03",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "holonote"
}
