Coming from an IT background where version control and the like is exceptionally important, I was interested to know how clubs manage their maps. The sort of things I was interested in were:
Presumably clubs have a single repository for the maps. Is this just the map coordinator's PC, and they effectively check-out and check-in maps to their repository, or are clubs doing something more sophisticated?
How do clubs coordinate the update of maps? Is it a set process, or is it more hand-to-mouth where the planner makes changes just before the event?
Do clubs limit the people who can update a master map? If so, how do you incorporate updates from the planner / controller of an event into the master map? If the planner does their own changes, does anyone verify these?
How do clubs "hold" the map? Just the map, or map with title, key, scale etc, or some other way? We are currently using OCAD 9 - I think it was one of the last versions before OCAD implemented a stricter licensing system. I believe that later versions have features that allow the map and layout features to be separated in the same OCAD file.
However, it seems to me that holding just the map makes more sense, e.g. if the mapped area is bigger than you would normally use at any one event, or you want to produce competitor maps at different scales. The downside being that you would need to create the layout objects for each event.
Are clubs generally using OCAD (if so what version?) or are any successfully using Open Orienteering Mapper (if so are you worried about continued support?)?
Does either product have any features that support version control? Do either of them "track" changes?
Are clubs using OCAD course setting software, or an external course setting program, such as Purple Pen? Is this a standard in the club, or is the planner free to choose whichever app they like?
Thanks in advance
Managing Maps
Moderators: [nope] cartel, team nopesport
7 posts
• Page 1 of 1
Re: Managing Maps
Coming from an IT background, I had the same concerns when I started planning for my club...
OpenOrienteeringMapper's native formats are XML and they include line breaks. It is not too hard to look at diffs between different versions of the fie and see what has changed. So you can add a point feature such as a tree and it is a single new line in the file. If there were an HTML5 OpenOrienteeringMapper renderer, it would be quite nice to be able to view map diffs between different revisions as you may with source code.
Similarly, PurplePen's format is XML and, again, it's a very clear schema.
I've yet to convince all the club mappers to move over to OpenOrienteeringMapper and feature-wise it is a bit lacking. While it does read and write up to OCAD 12, there will always be the potential for loss of data when converting between file formats (in particular, I've found the georeferencing to be a washout).At the moment this means we tend to still be using OCAD as a file format, so the best I can do is insist that I act as a gatekeeper for the master copies and insist on getting copies of the maps and planning files after events. Version control is based on a strict file naming convention. I would much prefer putting XML files in a proper version control system though.
We tend to work from larger master maps (without borders, keys, etc.) particularly for urban areas and use partial maps and overlays for the borders/keys for event maps. Of course, this does mean that if the planner wants to make changes, they can get lost unless they have access to the master map.
OpenOrienteeringMapper's native formats are XML and they include line breaks. It is not too hard to look at diffs between different versions of the fie and see what has changed. So you can add a point feature such as a tree and it is a single new line in the file. If there were an HTML5 OpenOrienteeringMapper renderer, it would be quite nice to be able to view map diffs between different revisions as you may with source code.
Similarly, PurplePen's format is XML and, again, it's a very clear schema.
I've yet to convince all the club mappers to move over to OpenOrienteeringMapper and feature-wise it is a bit lacking. While it does read and write up to OCAD 12, there will always be the potential for loss of data when converting between file formats (in particular, I've found the georeferencing to be a washout).At the moment this means we tend to still be using OCAD as a file format, so the best I can do is insist that I act as a gatekeeper for the master copies and insist on getting copies of the maps and planning files after events. Version control is based on a strict file naming convention. I would much prefer putting XML files in a proper version control system though.
We tend to work from larger master maps (without borders, keys, etc.) particularly for urban areas and use partial maps and overlays for the borders/keys for event maps. Of course, this does mean that if the planner wants to make changes, they can get lost unless they have access to the master map.
- sborrill
- off string
- Posts: 45
- Joined: Tue Oct 09, 2018 6:40 pm
Re: Managing Maps
Having open access to club map files in an open data format (eg OOM) is a recipe for multiple versions and chaos...
* Have a club store of maps online that planners can access (eg Google drive). Limit responsibility for maintaining this store to as few people as possible.
* Have a naming convention eg area name then date of last revision.
* Make sure cartographic changes happen through one or, at most, very few people. A bit bureaucratic but far safer and more likely to work long-term than a free-for-all.
* Make sure there are multiple copies of the map on several computers - just in case any one store fails...
* Have a club store of maps online that planners can access (eg Google drive). Limit responsibility for maintaining this store to as few people as possible.
* Have a naming convention eg area name then date of last revision.
* Make sure cartographic changes happen through one or, at most, very few people. A bit bureaucratic but far safer and more likely to work long-term than a free-for-all.
* Make sure there are multiple copies of the map on several computers - just in case any one store fails...
- Big Jon
- guru
- Posts: 1895
- Joined: Tue Nov 14, 2006 11:59 am
- Location: Dess
Re: Managing Maps
Thank you both.
Is this with OOM or when you convert between OCAD and OOK format?
Is there any particular reason that you would like everyone to use OOM?
Some other questions that have come to mind:
On georeferencing, do clubs use GB National Grid? It would seem to make sense to do so, as most of the reference data in the UK, such as LIDAR is produced to this projection. One of our maps has been updated to use UTM Zone 31 N, but I can't understand why this has been done? Also, if I wanted to convert it to GB National Grid, will OCD convert it, if I import the map into a new map file that has been setup to use GB National Grid.
Do clubs store their master maps with a 0 degree variation, and then rotate the for a particular event?
sborrill wrote: I've found the georeferencing to be a washout
Is this with OOM or when you convert between OCAD and OOK format?
sborrill wrote:I've yet to convince all the club mappers to move over to OpenOrienteeringMapper
Is there any particular reason that you would like everyone to use OOM?
Some other questions that have come to mind:
On georeferencing, do clubs use GB National Grid? It would seem to make sense to do so, as most of the reference data in the UK, such as LIDAR is produced to this projection. One of our maps has been updated to use UTM Zone 31 N, but I can't understand why this has been done? Also, if I wanted to convert it to GB National Grid, will OCD convert it, if I import the map into a new map file that has been setup to use GB National Grid.
Do clubs store their master maps with a 0 degree variation, and then rotate the for a particular event?
- enoquy
- string
- Posts: 5
- Joined: Fri Nov 13, 2020 8:34 pm
Re: Managing Maps
In an ideal world:
1. A central repository backed up to the Cloud and that back up proven to work.
2. Only mapping coordinator has access to the repository and issues map files to planners. Access to Cloud version available to someone else in case of emergency.
3. Mappers submit new/revised maps to coordinator to store.
3. No problem with a mix of OCAD versions/OOM, up to the mapper concerned. Avoid changing between formats.
4. Once a file has been shared with planner or mapper that file is frozen, any changes made to that file to be saved with a new version/date in the file name.
5. Cut down extracts for events fine, but any changes identified are made to the master file first and new extract created.
6. Purple Pen (or Condes) for planning. Planner can't change map accidentally. And probably easier to use for planning than OCAD.
M.
1. A central repository backed up to the Cloud and that back up proven to work.
2. Only mapping coordinator has access to the repository and issues map files to planners. Access to Cloud version available to someone else in case of emergency.
3. Mappers submit new/revised maps to coordinator to store.
3. No problem with a mix of OCAD versions/OOM, up to the mapper concerned. Avoid changing between formats.
4. Once a file has been shared with planner or mapper that file is frozen, any changes made to that file to be saved with a new version/date in the file name.
5. Cut down extracts for events fine, but any changes identified are made to the master file first and new extract created.
6. Purple Pen (or Condes) for planning. Planner can't change map accidentally. And probably easier to use for planning than OCAD.
M.
- MJG
- white
- Posts: 66
- Joined: Wed Sep 05, 2012 8:25 am
Re: Managing Maps
6. isn't really an issue. If you use OCAD to plan you are only editing the overprint. The map file is a separate background image just like with condes or purple pen so there is no risk of inadvertently changing the map.
- pete.owens
- diehard
- Posts: 750
- Joined: Tue Jan 15, 2008 12:25 am
Re: Managing Maps
Big Jon wrote:Having open access to club map files in an open data format (eg OOM) is a recipe for multiple versions and chaos...
I think the main issue is the "open access" part rather than the "open data format". Fully agree that you need a system of close control over who / when / how maps are being updated. Clubs need an experienced "mapping coordinator" who manages the process, and who understands how the maps are put together; it is much more than just a librarian role.
OCAD is great for professional mappers, and perhaps for amateurs making maps regularly (say 1 to 2 a year). But the subscription / licence management model adds a layer of complexity that isn't justified for occasional use: say a planner making updates only once every 3 years - particularly in more active clubs where 2-3 events might be at the map update / planning stage simultaneously. So I see OOM as being the long-term future for most amateur mappers / planners; it will probably only continuously improve.
What might help both OCAD/OOM (if they don't already have it?) is a layering system whereby an event planner can make temporary modifications on a top "layer", without accidentally destroying the underlying map. Then one or more such top layers can be reviewed by a more experienced mapper - for consistency, and compliance with ISOM/ISSOM - when the map is next properly updated.
Similarly, who wants to subscribe and then repeatedly transfer OCAD Course Setter licences around a club when everyone - including event controllers - can simply have a copy of Purple Pen? The latter has now evolved to a level where it can do almost anything required.
- Snail
- diehard
- Posts: 706
- Joined: Wed Nov 30, 2005 8:37 pm
7 posts
• Page 1 of 1
Who is online
Users browsing this forum: oo_wrong_way and 147 guests