The plugin enables three distinct sets of functionality:
- Easy linking of Canalplan places, canals etc into your blog posts.
- Back Linking from Canalplan Gazetteer entries to corresponding posts in your blog.
- “Cruise” blogging from a route imported from CanalPlan.
I plan to cover each of these areas of functionality in separate blog posts along with one covering the various customisation options the plugin supports. In this post I plan to basically cover some of what the plugin can do in general, and if you think bits of this sound familiar its because I’ve “borrowed” bits from previous posts on the subject.
Canalplan Locations – linking and Micro maps
WordPress makes adding links to a post quite easy but to add links to places in Canalplan you’d need to keep getting the urls from Canalplan and posting them into new links. This might be OK for one or two posts but what if you want to actually put a lot of Canalplan places into a blog post.. it would become a complete and utter pain. So the Canalplan Plugin makes this a complete doddle by adding a new input to the Edit Post screen which allows you to find a Canalplan location and insert a link into your post simply by typing a few letters and clicking on a button. You can insert places as either links to Canalplan Gazetteer entries such as :
[[CP:Market Drayton|tnj9]] which presents a link Market Drayton
or you can do it as “micro map”
[[CPGM:Market Drayton|tnj9]] which renders a little Googlemap of the location:
There are a couple of additional options which can be manually inserted to override the defaults which are set on the Plugin page. These options allow you to change some of the map parameters. For example
[[CPGM:Market Drayton|tnj9|height=400,width=300,type=t]] produces a larger map that the normal map and I’ve changed the map type to “t” (terrain) :
Of course for those of you who want to show somewhere off the canal system – well you can do that too!
Here is somewhere I used to work :
which was produced using the following code:
If you hover over the pin in the map you’ll see it contains the text that is shown in the tag, and I suspect you might have already worked out that if you change the text in the first part of the Canalplan tag that it changes the text used in the link/map – so:
[[CP:Market Drayton (Newcastle Road)|tnj9]] would make the following link Market Drayton (Newcastle Road)
So that’s single places dealt with but Canalplan AC also has complete canals in it… so it would be good if the plugin allowed you to basically do what we can do with single locations but with whole canals wouldn’t it? Well it can:
Canalplan Waterways – linking and Maps
Say you’re writing a blog post about the Leeds and Liverpool canal, specifically the Main Line – Wigan to Leeds, and you’d like to link to the Canalplan gazetteer entry for the canal. You could do it by creating a link containing the following url : http://www.canalplan.eu/cgi-bin/waterway.cgi?id=779v
Or you could use the Canalplan linker and again by typing a few letters (to pick the right canal) and a click and your post ends up with [[CPW:Leeds and Liverpool Canal (Main Line - Wigan to Leeds)|71jn]] which creates a nice link for you: Leeds and Liverpool Canal (Main Line - Wigan to Leeds)
But rather than link out to a map wouldn’t it be even better to have a map in your blog post?
[[CPGMW:Leeds and Liverpool Canal (Main Line - Wigan to Leeds) |71jn|type=h]] produces a nice map in your post:
Or how about the Shropshire Union Canal (Llangollen Canal - Main Line)
The two examples above show single parts of a Canal which is how CanalPlan stores its canals. But what if you want to show an entire canal? You don’t need to try to patch together bits, we do that for you.
So here’s the complete Leeds and Liverpool Canal :
Or how about the sprawling mess that is the Shropshire Union Canal ?
These last few examples show customisation to the default map with different colours and differing thickness for the line used to draw the canal.
These link and map codes are the basis of most of the functionality of the plugin. In the next post I’ll cover how we actually embed these short codes into a blog post.