Difference between revisions of "Location"

From AMTech WikiDocs
Jump to: navigation, search
Line 2: Line 2:
 
*[https://en.wikipedia.org/wiki/Well-known_text Well-known text]
 
*[https://en.wikipedia.org/wiki/Well-known_text Well-known text]
 
*observations and things have a location property
 
*observations and things have a location property
**this property can be used to execute observer geo-spatial criteria  (See [[Observers|Observers]])  
+
**this property can be used to define observer geo-spatial criteria  (See [[Observers|Observers]])  
 
**allows a geo-representation of the things  
 
**allows a geo-representation of the things  
 
<syntaxhighlight lang="jsonld">
 
<syntaxhighlight lang="jsonld">
Line 14: Line 14:
 
}
 
}
 
</syntaxhighlight>
 
</syntaxhighlight>
 +
 +
The value of this field consist on a stringified json object containing a mandatory field "wkt" defining the geometry, and two optional fields "sContext" (holding only "geo" as value to indicate that the wkt is written in geospatial context coordinates) and "hash" containing the [https://en.wikipedia.org/wiki/Geohash geohash] corresponding to the bounding rectangle of the given wkt. The field "hash" is computed internally so any value entered is ignored by the application.
 +
 +
  Note: It is important to escape the quotation marks (") with \"

Revision as of 11:07, 26 April 2016

location supported property is represented using Well-known text (wkt) format

  • Well-known text
  • observations and things have a location property
    • this property can be used to define observer geo-spatial criteria (See Observers)
    • allows a geo-representation of the things
{
    ...
    "location": "{
                    \"sContext\" : \"geo\", 
                    \"wkt\" : \"POINT(-99.16297853 19.42359932)\"
                 }",
    ...
}

The value of this field consist on a stringified json object containing a mandatory field "wkt" defining the geometry, and two optional fields "sContext" (holding only "geo" as value to indicate that the wkt is written in geospatial context coordinates) and "hash" containing the geohash corresponding to the bounding rectangle of the given wkt. The field "hash" is computed internally so any value entered is ignored by the application.

 Note: It is important to escape the quotation marks (") with \"