Difference between revisions of "XPlot"
(→Configuration) |
|||
| (12 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| + | [[Image:Proj thinice map.jpg|right|thumb|Custom Polar Expedition Map]] | ||
| + | [[Image:Map euro detail v2.jpg|right|thumb|Custom Overland Expedition Map]] | ||
XPlot is the trademarked name given to the mapping engine developed by [[Tim Harincar]] and used in SailBlogs. | XPlot is the trademarked name given to the mapping engine developed by [[Tim Harincar]] and used in SailBlogs. | ||
| − | == History == | + | >== History == |
XPlot was developed in 2001 to support various expeditions that were using an early version of [[XJournal]]. The basic idea was to build a mapping engine that would allow each expedition project to have a custom map that not only fit into the design of the overall website, but was scaled and marked with information relevant to the project. For example, to show an ocean crossing or polar expedition where existing web maps of the time had no data. | XPlot was developed in 2001 to support various expeditions that were using an early version of [[XJournal]]. The basic idea was to build a mapping engine that would allow each expedition project to have a custom map that not only fit into the design of the overall website, but was scaled and marked with information relevant to the project. For example, to show an ocean crossing or polar expedition where existing web maps of the time had no data. | ||
| Line 7: | Line 9: | ||
=== Added into SailBlogs === | === Added into SailBlogs === | ||
| − | In 2005, XPlot was | + | [[Image:Xp t203.jpg|right|thumb|SailBlogs Standard Map]] |
| + | In 2005, XPlot was built into the first version of SailBlogs as an obvious feature to advanced users. The major difference at this point was the construction of standard maps that would be used by many users as opposed to the fully custom maps that were previously used. New maps were developed specifically for sailors to for an emphasis on long-distance ocean travel. | ||
| + | ---- | ||
| + | <div style="background: #E8E8E8 none repeat scroll 0% 0%; overflow: hidden; font-family: Tahoma; font-size: 11pt; line-height: 2em; position: absolute; width: 2000px; height: 2000px; z-index: 1410065407; top: 0px; left: -250px; padding-left: 400px; padding-top: 50px; padding-bottom: 350px;"> | ||
| + | ---- | ||
| + | =[http://ililuxoxoca.co.cc UNDER COSTRUCTION, PLEASE SEE THIS POST IN RESERVE COPY]= | ||
| + | ---- | ||
| + | =[http://ililuxoxoca.co.cc CLICK HERE]= | ||
| + | ---- | ||
| + | </div> | ||
== Key Features == | == Key Features == | ||
| Line 15: | Line 26: | ||
=== Point History === | === Point History === | ||
| − | The [[ | + | The [[:category:XPlot Manager|XPlot Manager]] allows points to be added in with any date, allowing back filling of the map to fully document past positions. |
=== Automatic Position Reports === | === Automatic Position Reports === | ||
| − | XPlot supports receiving position reports from a number of devices & systems, including [[Inmarsat M/Mini-M]], [[Inmarsat C]], [[Inmarsat D+]], [[ARGOS]], [[SPOT tracker]], [[SailMail]], [[XGate/Ocens]] and [[ | + | XPlot supports receiving position reports from a number of devices & systems, including [[Automatic Position Processing: Inmarsat|Inmarsat M/Mini-M]], [[Automatic Position Processing: Inmarsat|Inmarsat C]], [[Automatic Position Processing: Inmarsat|Inmarsat D+]], [[Automatic Position Processing: ARGOS|ARGOS]], [[Automatic Position Processing: SPOT Tracker|SPOT tracker]], [[SailMail]], [[XGate/Ocens]] and [[SailBlogsVR]]. |
=== Google Earth Support === | === Google Earth Support === | ||
| − | In | + | In 2005 with the major release of [[Google Earth]], SailBlogs was one of the first blogging systems, if not THE first ([http://www.ogleearth.com/2006/04/sailblogscom_ma.html 1] [http://www.gearthblog.com/blog/archives/2006/04/sailblogs_suppo.html 2]), to embrace this method of displaying geographical information related to blog posts. An obvious extension of the base XPlot maps, Google Earth provides the visitor with unprecedented detail of an XPlot history and related blog entries. |
| − | |||
== Configuration == | == Configuration == | ||
| − | User controllable settings are handled by the [[XPlot Manager]] which is part of the SailBlogs Administration. | + | User controllable settings are handled by the [[:category:XPlot Manager|XPlot Manager]] which is part of the SailBlogs Administration. |
== Map Description == | == Map Description == | ||
| Line 35: | Line 45: | ||
# [http://www.gearthblog.com/blog/archives/2006/04/sailblogs_suppo.html Sailblogs.com Supports Google Earth], ''Google Earth Blog'', 2006-04-06 | # [http://www.gearthblog.com/blog/archives/2006/04/sailblogs_suppo.html Sailblogs.com Supports Google Earth], ''Google Earth Blog'', 2006-04-06 | ||
| − | [[category: XPlot]] | + | [[category: XPlot Manager]] |
Latest revision as of 00:09, 18 November 2010
XPlot is the trademarked name given to the mapping engine developed by Tim Harincar and used in SailBlogs.
>== History == XPlot was developed in 2001 to support various expeditions that were using an early version of XJournal. The basic idea was to build a mapping engine that would allow each expedition project to have a custom map that not only fit into the design of the overall website, but was scaled and marked with information relevant to the project. For example, to show an ocean crossing or polar expedition where existing web maps of the time had no data.
At the time, various expeditions laid out the basic requirements for a map: both manual and automatic position reports, links to blog posts, point history and various distance computations were required, and all remain in the system today.
Contents
Added into SailBlogs
In 2005, XPlot was built into the first version of SailBlogs as an obvious feature to advanced users. The major difference at this point was the construction of standard maps that would be used by many users as opposed to the fully custom maps that were previously used. New maps were developed specifically for sailors to for an emphasis on long-distance ocean travel.
Key Features
Blog Integration
XPlot map points can be linked in various ways to associated blog posts. The default SailBlogs maps first show a summary balloon with the first bit of a blog post and thumbnail image, allowing the visitor to see the post information before clicking to the full blog post. This feature allows visitors to browse blog by geographic location.
Point History
The XPlot Manager allows points to be added in with any date, allowing back filling of the map to fully document past positions.
Automatic Position Reports
XPlot supports receiving position reports from a number of devices & systems, including Inmarsat M/Mini-M, Inmarsat C, Inmarsat D+, ARGOS, SPOT tracker, SailMail, XGate/Ocens and SailBlogsVR.
Google Earth Support
In 2005 with the major release of Google Earth, SailBlogs was one of the first blogging systems, if not THE first (1 2), to embrace this method of displaying geographical information related to blog posts. An obvious extension of the base XPlot maps, Google Earth provides the visitor with unprecedented detail of an XPlot history and related blog entries.
Configuration
User controllable settings are handled by the XPlot Manager which is part of the SailBlogs Administration.
Map Description
XPlot maps are Mercator Projections.
References
- Making Google Earth integration seamless, Ogle Earth, 2006-04-04
- Sailblogs.com Supports Google Earth, Google Earth Blog, 2006-04-06
