| 11 | | Documenting. |
| | 11 | |
| | 12 | Positioning |
| | 13 | |
| | 14 | Using the ossimplanet tcp listner and a python socket i'm configuring a gui to modify position and view parameters (roll, pith,heading) in ossimplanet. |
| | 15 | I'm planning to add different "position" type : |
| | 16 | |
| | 17 | 1 - Grass : read the grass region, extract the center in lon-lat wgs84 and sen it to ossimplanet, |
| | 18 | the region center will be the start point for the pan-action. |
| | 19 | i'm adding the capabilities to read data inside the current grass mapset and set the region according to : |
| | 20 | a) raster file |
| | 21 | b) vector file |
| | 22 | c) saved region |
| | 23 | |
| | 24 | 2 - Gps : read the position from a connected gps serial device, and use the gui to modify the view parameters. |
| | 25 | in these case the gps (NMEA) data will be saved in a postgis layer, the NMEA data will be displaied |
| | 26 | in a specific gui tab (in the gui will be added the ability to save a kml using a template |
| | 27 | (maybe html template using pyqt-webkit object so in addition will be possible to add an openlayer |
| | 28 | mapdisplay to display and interrogate the saved waypoints) |
| | 29 | |
| | 30 | 3 - Static Positioning : zomm to a point with know coordinates : |
| | 31 | a) simple insert manually a lon-lat values and zoom to it |
| | 32 | b) soom to a sepciphic place (i'm storing geonames cities data in a db) in a combobox |
| | 33 | i'll add a list with cities to zoom to. |
| | 34 | |
| | 35 | 4 - Joystic : The code will use pygame, it is an alternative pan-zooming mode, the joystick buttons will be cofigured |
| | 36 | to make action like save point in db or make query to loaded data. |
| | 37 | For now the relative code will be based on a simple "increase/decrease - latitude/longitude values" |
| | 38 | it will no andle rotation like a flight simulator. |
| | 39 | I'm tring to develop code based on quathernion math, the function to implement are relative simple ... |
| | 40 | but its usage is no easy beacouse it is not so intuitive |
| | 41 | |
| | 42 | Data managing : |
| | 43 | |
| | 44 | Using grass.py to read avaiable layer (image, elevation, vector) from the mapset, put a list for each type in a relative combobox, For each type will be possible to run on the relative layer the ossim executable application, img2rr to make preview, cmm, orthoigen to produce elevation data, ossim_height to retrieve msl data, and others. |
| | 45 | The ossim executable will run on grass data or external files. |
| | 46 | To load data for now i've no clue if it will be possible to load it dinamically (using tcp or modifing source), so i'm studing a way to add layers ... |
| | 47 | the more simple way seems to be : generate an ossim.session file using python from a list of "added" layers. |
| | 48 | For ogr vectors will be possible to add capabilities to customize its rendering using a kwl files, i'm tring that option to create a dialog to select colors, line's width, point's size etc .. (rasterizing vecor object will be an option, i'll add it too) |
| | 49 | |
| | 50 | Issue and question : |
| | 51 | where can i retrieve information on how to add a placemark using tcp |
| | 52 | |
| | 53 | |
