User Tools

Site Tools


manual:advanced:locus_api:geocaching_field_notes

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

manual:advanced:locus_api:geocaching_field_notes [2015/05/21 15:34] – created mstupkamanual:advanced:locus_api:geocaching_field_notes [2015/09/07 17:55] (current) mstupka
Line 1: Line 1:
 ====== Geocaching Field Notes ====== ====== Geocaching Field Notes ======
- 
-<WRAP box left>  
-  * Locus type: <html><b><a href="https://play.google.com/store/apps/details?id=menion.android.locus&amp;referrer=utm_source %3Ddocs%26utm_medium %3Dheader%26utm_content %3Dlocus_api_geoaching_field_notes" target="_blank">Free</a>/<a href="https://play.google.com/store/apps/details?id=menion.android.locus.pro&amp;referrer=utm_source %3Ddocs%26utm_medium %3Dheader%26utm_content %3Dlocus_api_geoaching_field_notes" target="_blank">Pro</a></b></html>, **3.2.0+** 
-  * Last updated manual: **3.2.0 / 13.7.2014** 
-</WRAP> 
  
 ===== Basic information ===== ===== Basic information =====
  
-Since version 3.2.0, Locus offer full access to user's field notes. For this access, is used system called [[http://developer.android.com/guide/topics/providers/content-providers.html|Content provider]]. +Since the version 3.2.0, Locus Map offers full access to user's field notes. For this access system called [[http://developer.android.com/guide/topics/providers/content-providers.html|Content provider]] is used
 You don't have to be too skilled with it. Most of required work is already done in Locus API and you may (and it's suggested) use already pre-prepared functions. You don't have to be too skilled with it. Most of required work is already done in Locus API and you may (and it's suggested) use already pre-prepared functions.
  
Line 28: Line 23:
 ==== Possibilities ==== ==== Possibilities ====
  
-Field notes are in Locus stored in SQLite databases, so all queries send over Locus API to content providermay be defined in probably well known way for you - same as a query to SQLite database.+Field notes in Locus are stored in SQLite databases, so all queries sent over Locus API to content provider may be defined in probably well known way for you - same as a query to SQLite database.
  
 **What is possible** **What is possible**
Line 34: Line 29:
   * GET, INSERT, UPDATE, DELETE queries on FieldNote images   * GET, INSERT, UPDATE, DELETE queries on FieldNote images
  
-To use basic featurescheck [[https://bitbucket.org/asamm/locus-api-android/src/6b45a152967b4ffd4d294b186f8bd249fc91ff0a/src/locus/api/android/features/geocaching/fieldNotes/FieldNotesHelper.java|FieldNotesHelper.java]] class.+To use basic features check [[https://bitbucket.org/asamm/locus-api-android/src/6b45a152967b4ffd4d294b186f8bd249fc91ff0a/src/locus/api/android/features/geocaching/fieldNotes/FieldNotesHelper.java|FieldNotesHelper.java]] class.
  
-__Here are three very important parts__+__Here are three very important parts:__
  
-  * Static classes that contains names of possible field notes columns. These are used in all specific requests. +  * Static classes that contain names of possible field notes columns. These are used in all specific requests. 
-  * Static helper functionsfor basic operations over content provider. You may write own functions if you require more specific requests of course+  * Static helper functions for basic operations over content provider. Of course you may write your own functions if you require more specific requests. 
-  * Static functions for some other tasks. For example request on log certain field notes over //Groundspeak Live API//.+  * Static functions for some other tasks. For example requests on "log certain field notes over //Groundspeak Live API//".
  
manual/advanced/locus_api/geocaching_field_notes.1432215279.txt.gz · Last modified: 2015/05/21 16:34 (external edit)