MapColonies / MapColonies/image-exporter-client
Imagery - Vector - Geo-packaging export tool
@seganom is already working on this.
Since Aug 17, 2020.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- PR merge metrics
- No merged PRs in 30d
Description
### Background
GeoPackage is an OGC standard data package that can store different kinds of spatial data types such as points, poly-line, and polygon. We can save multiple layers into a single GeoPackage (.gpkg) file.
### Server side
- The system shall set the spatial reference systems for the packaged data. The spatial reference value should be configured.
- The system shall package feature data ( including geo and metadata) and raster (tiled) data.
- The GeoPackage data table will be indexed by the x, y, z fields.
- The system shall limit the geo region size to configurable param, default value shall be 100km by 100km
- The system shall clear packages older that configurable param, default 7 days
- The system shall export package to a shared folder set by configurable parms
~~- The system shall enable the user to download to a local folder.~~
### The export tool UI shall have the following features
1. Map section to display the Best layer.
1.1. At the map status bar display mouse position in WGS84 coordinates
2. Basic drawing tool to select the region to be exported (packaged)
2.1. Rectangle tool
2.2 Top Left coordinate, Button right coordinate
3. Folder selection section.
3.1. An option to select a mapped shared folder ~~or local folder~~
3.1.1. If shared folder was selected display copy to clipboard the folder location
3.2. Create folder on the shared folder ~~or local folder~~
3.3 Package name text box.
3.4 Progress bar
4. Send request ~~or cancel~~ buttons.
5. Estimated file size label.
6. UI should support RTL (hebrew)
(TBD - do we need to export vector data?, TBD file size limit)
For OSM check --> https://github.com/hotosm/osm-export-tool-python
----------
### Load Test
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.