Eyesis Panorama Database: Difference between revisions
Jump to navigation
Jump to search
OneArtPlease (talk | contribs) No edit summary |
OneArtPlease (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
==MySQL DB Structure== | ==MySQL DB Structure== | ||
Nodes Table: | |||
ID | ID | ||
Name | |||
Description | |||
Longitude | Longitude | ||
Latitude | Latitude | ||
| Line 10: | Line 13: | ||
Roll | Roll | ||
Panorama URL | Panorama URL | ||
Visibility3d - list of ranges [from,to] - which nodes are visible from the current one. from, to are both relative to the current node, so merging several segments should not break visibility (not so easy in the map that is not linear path, but we'll think of something - adding new nodes (importing KML) should not change the relative sequence of indices (kml "name" tag). | |||
Routes Table | |||
ID | |||
Name | |||
Description | |||
Nodes List | |||
==PHP Methods== | ==PHP Methods== | ||
Revision as of 17:47, 7 July 2011
MySQL DB Structure
Nodes Table:
ID Name Description Longitude Latitude Timestamp Altitude Heading Tilt Roll Panorama URL Visibility3d - list of ranges [from,to] - which nodes are visible from the current one. from, to are both relative to the current node, so merging several segments should not break visibility (not so easy in the map that is not linear path, but we'll think of something - adding new nodes (importing KML) should not change the relative sequence of indices (kml "name" tag).
Routes Table
ID Name Description Nodes List