Changeset 4578 for trunk/packages

Timestamp:

Jul 27, 2014, 2:00:08 PM (10 years ago)

Author:

ldelgass

Message:

protocol doc update

File:

• trunk/packages/vizservers/geovis/geovis_protocol.txt (modified) (3 diffs)

trunk/packages/vizservers/geovis/geovis_protocol.txt

@@ -90 +90 @@
 
 screen bgcolor <r> <g> <b>
+screen coords <x> <y> <z> <?srs?> <?verticalDatum?>
+       Transate map coordinates to screen/mouse coordinates.
+       <x>,<y>,<z> - Map coordinates.  If srs not given, these are in the map's 
+       coordinate system.
+       <srs> - Optional horizontal srs init string for coordinate system of 
+       x,y,z
+       <verticalDatum> - Optional vertical srs init string for coordinate system
+       of x,y,z
 screen size <width> <height>
 
@@ -106 +114 @@
 == Map Commands ==
 
-map coords <x> <y>
-    Translate screen/mouse coordinates into map coordinates
+map coords <x> <y> <?srs?> <?verticalDatum?>
+    Translate screen/mouse coordinates into map coordinates.
+    <x>,<y> - Screen/mouse coordinates
+    <srs> - Optional horizontal srs init string for coordinate system to return
+    <verticalDatum> - Optional vertical srs init string for coordinate system to
+    return
 
 map grid <bool> <?type?>
@@ -195 +207 @@
 nv>image -type image -bytes <nbytes>
   <binary RGB data>
-nv>map coords <x> <y> <z> <?mouseX?> <?mouseY?>
-   Reply to query of map coordinates.  If reply is to a request with mouse
-   coordinates, the mouse coordinates are included.
+nv>map coords <mapX> <mapY> <mapZ> <screenX> <screenY> <?srs?> <?verticalDatum?>
+   Reply to query of map coordinates from screen coordinates.  srs of the map
+   coordinates may be included if not in map's native coordinate system
 nv>map coords invalid <mouseX> <mouseY>
    Reply indicating an off-map click/query
+nv>screen coords <screenX> <screenY> <screenZ> <mapX> <mapY> <mapZ>
+   Reply to query of screen coordinates from map coordinates
+nv>screen coords invalid <mapX> <mapY> <mapZ>
+   Reply indicating requested point is out of the view frustum
 nv>ok -token <seqnum>
    Reply indicated commands through <seqnum> (numbered beginning at 1) have been