You’ve imported a new symbol set to an existing map, converted various symbols and then realise some of those symbols are not showing up on the map. Or maybe you have imported an existing map to meld with a new or adjacent map and have the same issue.
It is likely that the colours for those symbols are below every colour in the original symbol set. If there are many new symbols and/or many existing symbols, it can be time consuming to move colours up the table. But all is not lost.
Fixing the colour table sequence
Take a copy of your map for safety. Select all the new symbols, right click and Delete. File | Import the new symbol set as an empty OCAD file and select the option to place colours at top of colour table. After import, all the symbols on the map are re-engaged with the new symbol set and should now be visible.
Getting it right first time
For a clean run, simply File | Import the new symbol set as an empty OCAD file and select the option to place colours at top of colour table. If you are melding an existing map file then File | Import that file and select the option to place colours at top of colour table.
This function is on the OCAD AG wish list to include in Map | Load colours & symbols from… That will negate the need to have an empty map file when you simply wish to import new symbols.
If, like me, you draw a lot of suburban streets to their correct size (see www.organisedgrime.com.au/families.php) you will find that OCAD autojoins rather aggressively because it takes into account the width of the symbol when deciding the autojoin threshold.
Drawn offset – now joined!
So if you have autojoin on (I like it) and are zoomed all the way in (32x) to precisely draw a road which is 10 metres wide, OCAD will autojoin that road to any other similar road which is within 10 metres, which is 32mm on the screen! When drawing with the bezier/curve tool it will even bend the road to make it join.
This makes drawing roads that join at a roundabout very arduous as you have to correct all of the autojoins – not only their location but their angle. Even worse, the autojoin occurs when you finish drawing the object – so if you have panned as you draw the road, the autojoin at the beginning will happen out of sight.
Junction becomes an overpass?*!
Another example is a wide symbol (bike path with exaggerated width) stopping either side of a narrower symbol (narrow road) – the second bike path will always autojoin across the road to the first one.
This is obviously a bug but I have not been able to persuade the OCAD people to agree.
Ah, a solution of sorts
They have added a feature to OCAD 11 in response to my nagging: if you hold down the Shift key as you finish drawing an object, it will suppress autojoin. Note that different drawing tools finish drawing in different ways. The bezier/curve tool requires a right-click.
Shift is not the most obvious choice of key to suppress autojoin; if you hold down Shift when you start drawing a line it will force an autojoin and merge to any neighbouring similar object.
The great value Startereditions for your occasional mappers. Standardfor your power mappers. Free Viewerfor anyone who needs to check out maps.
Starterdoes lack many functions of Standard. However, many are likely infrequently, if ever, used by occasional mappers. Some key ones to consider are;
Large or highly detailed maps will be outside the limit of 10,000 map objects
Circle/ellipses and rectangular lines are commonly used drawing tools not available in Starter. Both can be effected in slower ways
Layout layer not available. Allows positioning of raster (.jpg etc) logos, advertisements etc
GPX import (often used for GPS files) and Open Street Map (OSM) are amongst imports not available
Exporting an OCAD Internet Map is not available.
Clubs that can afford to improve productivity for their not infrequent volunteer mappers could buy Standardfor them as well as for their power mappers.
If Shape and OSM import or export required then Professionalis needed. Similarly for creating OCAD Internet maps. Professionaloffers advanced productivity functions but in my reckoning, only orienteering professional mappers would likely notice those functions, let alone use them.
A few clubs
Any mapper preparing base maps frequently from GIS data (e.g. Shape files) and/or Open Street Map (OSM) extensively, will gain significant productivity from Professional. That could also be true if extensive import/export capabilities are required.
Productivity aside, if specialist requirements are uncertain over the next 2-3 years then perhaps stick to Standardknowing that an upgrade to Professionalis always available.
I have found OCAD 11 (and 10) to be noticeably more productive than OCAD 9 and earlier.
OCAD 8 ‘club‘ license
The good news for OCAD 8 users is that you have every reason for updating and none for sticking to OCAD 8 (perhaps apart from cost). A few mappers mentioned OCAD 8’s ‘club’ license as a reason for sticking with OCAD 8. It isn’t a reason for sticking to OCAD 8 as OCAD 8 is a single PC license as with every OCAD version. (The license can be read in the OCAD 8 folder). The belief possibly came about when OCAD 9 introduced online activation. But that is simply a licence management method.
An excellent brief description can be found on this CSIRO web page.
An interesting experience of use of LIDAR in orienteering mapping was recently posted on the NZ MapTalk’s Mapping forum, pages 38-39. The linkis in the sidebar on this page but more directly, head to Selwyn’s post of 7 June on the topic of Base map contours.
In that post he mentions work by RouteGadget’s developer on automating orienteering map production from LIDAR sources. For those interested in LIDAR potential, this is well worth a visit. Find it on the RouteGadget Facebook page. (You might have to be a Facebook member to view).
A 2005 article LIDAR Basemaps Come of Age by Greg Lennon of Quantico Orienteering Club, USA. The image upper right is from that article.