masmap.org open source maps

Mapping at Masmap goes through a 7-step cycle. If you miss any step in this cycle, a conflict can occur, especially when two mappers work on the same map tile. Steps 1. SVN Update Working Trunk Folder 2. SVN Get Lock Working Map Tile 3. Edit Working Map Tile 4. Verify Working Map Tile 5. Save Working Map Tile 6. SVN Commit Working Tile 7. Enter a comprehensive log 1. SVN Update Working Folder Before you begin mapping, always perform an SVN Update on your working trunk folder to get the latest tiles from Masmap's Subversion Server. These tiles are the updated maps drawn by other mappers. Perform this on or in your working trunk folder: Right click > SVN Update. What was meant earlier by "constant communication" between the mappers doesn't actually imply you have to inform other mappers actively of where you want to map. You can actually gauge what other mappers are doing in two ways: (a) Looking at the SVN Log The SVN Log (Right click on or in Working Folder > TortoiseSVN > Show Log) shows 100 recent commit revisions and gives you a rough idea of who has been working on which tile recently. If the time and date is quite recent, it would be best to avoid the recently committed tile. SVN Log - Who is working on what recently (b) Check the repository for modifications To check the repository for modifications, right click on or in your working folder and choose TortoiseSVN > Check for modifications then click on the Check Repository button. This lists the currently locked tiles by mappers, if any. Locked tiles cannot be mapped by anyone except the locker until he commits and releases the lock. Check repository for modifications 2. SVN Get Lock Working Map Tile Before you can begin mapping, perform an SVN Get Lock on the tile of your choosing. Right click on tile > SVN Get Lock. In Windows Explorer, confirm that your locked tile has a green checkmark icon overlay and NOT a grey one. How to differentiate a locked tile Some versions of Windows or Tortoisesvn have a padlock icon overlay over the locked map tile: 3. Edit Working Tile You may now edit your working tile with GPSmapedit, rest assured that no one else will be mapping on it at the same time. Lock is King. 4. Verify Working Map Tile Before saving your tile it is prudent to run Verify Map and fix any errors that appear. Tools Menu > Verify Map. You can skip this step if you wish to continue mapping but want to intermittently commit your changes to the subversion server and save the Verify Map step till last. Tile edited5. Save Working Map Tile Save your working tile in GPSmapedit. Once your tile is saved, Windows Explorer will show a red exlamation mark icon overlay on your working tile. This means that your tile has changed from the last SVN Update and needs to be committed to the server for others to view your work of art. 6. SVN Commit Working Tile Right click on your edited working tile to choose SVN Commit. Enter a detailed log of your edits and click OK. Lastly, you will be asked for your username and password. If you plan to continue mapping immediately after your commit, check Keep Lock to prevent others from locking the tile just after you commit. You may skip the SVN Update step in this instance as you have the latest tile update. 7. Enter a comprehensive log It would be good to tell others what you did to the map and its exact location in coordinates. If you mapped with the help of a contributor's tracklog credit their names in brackets, even if the contributor is you. Mapping Cycle for Beginners Additional Notes 1. Decorum dictates that you shouldn't lock a tile for reservation purposes if you plan to edit the map at a later time as that would deprive other mappers of the opportunity to map. Commit Failed 2. In the event that you see a commit error, such as the above, this indicates that you have missed one of the earlier two steps: SVN Update or SVN Lock, or both. Email a senior mapper for help in resolving this error. DO NOT continue mapping as this will make the situation worse. Comment on this article