This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
manual:about:add_new_content [2015/05/21 16:13] – mstupka | manual:about:add_new_content [2018/01/04 10:53] (current) – [Additional information for Locus Store] voldapet | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== New Content |
---- | ---- | ||
- | ===== Basic information | + | ==== Basic information ==== |
- | Locus Store can be simple | + | Locus Store can be simply |
+ | ===== Possible models of map distribution ===== | ||
- | ===== We need to know ===== | + | The way of map sales in Locus Store depends on the data distribution options of their provider. |
+ | ==== Publisher provides map via web map server | ||
- | === Provider information | + | In case the map data are available at a web server of the provider in a form of map tiles we offer three different models in Locus Store. |
- | * **Name** of provider | + | === Offline packages |
- | * **Provider icon** - best is semi-transparent 64x64px PNG image | + | |
- | === Item information === | + | This model offers map data in a form of offline (map) packages. Locus Store contains definitions of areas of particular offline maps (like paper map crops). When the user purchases an area, Locus downloads all needed tiles for defined area. The package |
- | * **Form of data** - in which form can be your data distributed? | + | |
- | * **The name** of item | + | We are also able to prepare packages in advance and store packages on our server. Prepared packages on our side can decrease load on your map server and it reduces possibility of some network issue like incorrectly downloaded tiles, temporary map server issues, etc. |
- | * **Icon** for item - can be similar as provider icon. Again best is semi-transparent 64x64px PNG format | + | === Online browsing and offline downloads === |
- | * **Images** - suggest to prepare at least 3 images (PNG format) or screenshots that better describe | + | |
- | * **HTML description** - that describe what data are provided | + | Users can view the map online for free but offline downloading |
- | * **Countries or region** - area which is covered by item (in case of map) or definition of country where item can be used (parameter | + | |
- | * **Usage** - For what purpose | + | === Subscription for using maps online and offline === |
- | * **GeoJson of item area** (optional) - similar | + | |
- | * Data itself and decision where data will be stored. | + | Both online and offline access to map data is charged. The user must pay monthly/ |
- | * **Our storage** – we use Google Cloud Storage or Amazon S3 service. | + | ==== Publisher can provide maps as raster files ==== |
- | | + | |
- | + | It is possible | |
- | ==== How users can purchase the data ==== | + | |
- | All items in Locus store can be purchased for internal virtual currency | + | We accept any geo-referenced raster format that is supported by GDAL utilities. |
+ | ===== Security ===== | ||
+ | |||
+ | We are able to prepare a security mechanism (for all described models) that prevents abuse of your data. Because its details can be quite specific, feel free to [[mailto: | ||
+ | |||
+ | ===== How can users purchase the data? ===== | ||
+ | All items in Locus Store can be purchased for our internal virtual currency LoCoins. Users can get LoCoins for real money via Google in app billing (we’re planning to add support for PayPal payments, etc.). | ||
The purchase itself can be performed in three different ways: | The purchase itself can be performed in three different ways: | ||
- | * **Pay for one package** – it’s like e-commerce system. | + | * **Pay for one package** – it’s like e-commerce system. |
- | * **Subscription** – useful for using some services. | + | * **Subscription** – useful for some services. |
- | * **Pay as you go** – Locus use this method for downloading specific | + | * **Pay as you go** – LocusMap uses this method for downloading specific |
- | ==== Security | + | ===== Additional information for Locus Store ===== |
- | Basically it depends on how much time and work you want to put into security. Because it could be quite specific feel free to ask us. | + | |
- | ==== Contact | + | === Provider information |
- | Please feel free to contact us with any question about Locus store on [[support.locus@asamm.com]] | + | * **Name** of the provider |
- | We can prepare individual model to fit your data or requirements. | + | * **Provider icon** - best is a semi-transparent 64x64px PNG image |
+ | |||
+ | === Item information | ||
+ | * **Form of data** - what form can your data be distributed in? In form of a file/ | ||
+ | * **Name** of the item | ||
+ | * **Icon** of the item - can be similar as the provider icon. Again, best is a semi-transparent 256x256px PNG format | ||
+ | * **Images** - prepare at least 3 images (PNG format) or screenshots that describe the data the best. Recommended resolution is about 1280 x 720 px (optional). | ||
+ | * **Description** - what kind of data is provided | ||
+ | * **Countries or region** - definition of the area covered by the item (in case of maps) or of the country where the item can be used (optional parameter) | ||
+ | * **Usage** - what is the purpose of the data usage? Are the data useful for hiking, cycling, sailing | ||
+ | * **GeoJson of the item area** similar to the region parameter. In case the map covers some specific area we are able to show coverage on map and the user can select the item for purchase directly on map. Simplified GeoJson about 50 - 100 points is preferred. | ||