Coder Social home page Coder Social logo

mapper-manual's People

Contributors

abbe98 avatar dg0yt avatar lpechacek avatar luzpaz avatar mitchellkrome avatar peterhoban avatar pkturner avatar puzzlepaint avatar sikmir avatar wanacode avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mapper-manual's Issues

task-based section in manual

Currently the manual is largely tool-based: there are pretty good references to all tools and what these do. However, what I feel is missing is descriptions like "how can I achieve x". For instance, I was unaware there is the duplicate tool and attempted to achieve a similar result with copy-paste. Earlier I have used other inefficient ways to achieve various results.

However, I don't see any obvious place where to add such information. True, there are a number of task-based entries (geo-referencing, tags and others). But what about creating a new section? We have "first steps", perhaps do something like "next steps", that would contain topics like "how to work with vegetation", "how to draw smooth lines", "how to use lidar data" and so on?

Other thoughts?

Suggestion: Gitbook

Have you considered Gitbook as a way to serve your manual? Would look like:

screen shot 2018-01-12 at 11 36 33 am

As a user I prefer its interface– it natively has:

  • Table of Contents
  • Search functionality
  • Epub/pdf/etc. auto-builds with each deploy (my dad recently printed the current manual, so there's a need there..)
  • More features if you want them? I quite like glossary support, for example.

As far as I can tell, a switch would keep your current features, including an in-browser editor that's pretty well featured (though I don't personally use it so can't fully vouch).

It's free for open source projects, & the project maintainers are responsive on Slack if support is needed. I maintain the Tessel Project (tessel.io) and we switched to Gitbook from a Jekyll-based solution because it was simpler and prettier in the GH view.

Conversion would be pretty simple– right now I'm using a not-really-converted version of your manual via:

git clone
book sm (autogenerate table of contents from file structure)
gitbook serve

which is where I pulled the screen shot from.

Autogen contents sidebar:

screen shot 2018-01-12 at 11 47 20 am

I'm currently using Gitbook for a few projects, if you want to poke around examples–

Let me know if this is of interest– I can commit a bit of time and don't think it takes much.

Instructions for translators

I planned to translate the manual into my native language, but I'm confused a little bit... I don't understand how to make it properly in order to not to break anything in online or offline documentation.
Could you provide instructions for translators like you have provided it for regular contributors?

O-Map Wiki (collaborative wiki project)

Luděk Krtička («Orienteering Mappers Int.» Facebook group staff) proposed reborn «O-wiki» (discontinued) wiki site as new «O-Map Wiki» for collecting info & docs about all aspects of orienteering mapping & orienteering software, including section about OpenOrienteering Mapper:

This is something I was talking about at ICOM in Prague: O-Map Wiki project. I would like to hear your opinion and suggestions. Also, I would like to invite you to make comments to the structure and content of the project proposal.

P.S.: I would took part in writing articles for «O-Map Wiki» on some aspects of OpenOrienteering Mapper usage.

REFERENCE

PDF version

Add possibility convert this manual to PDF document.

CRT files not working with OCAD file

Im trying to convert a map that started in OCAD to ISOM 2017 symbols. I have tried Symbols->Replace Symbol Set, then selecting the ISOM 2017 symbol set and loading the ISOM2000-ISOM2017.crt. This does not select all the symbols. I have also tried creating a OCD-ISOM2017.crt, and changing the Symbol Set ID, no luck.

Only thing I could get to work was first replacing the symbol set with with an ISOM2000, matched on number, then replacing that.

file attached with ocad
test_crt_ocad.zip
symbol set and a few random symbols

Undocumented restriction on types of geospatial data

The page pages/gdal.md suggests that all geospatial raster data can be used as templates. However, Mapper throws an error when trying to open data saved as GrayFloat32, which is a common internal format in GeoTIFFs representing data like height, slope etc. It appears that this data must first be saved in the GeoTIFF as RGB values, presumably a triplet of UInt8s (I'm guessing here). This restriction also occurs with other file extensions. This is an undocumented restriction on types of data that Mapper can load.

I have not encountered any restrictions on vector data. In particular, I can directly load the contour export from QGIS into Mapper.

I suggest updating the GDAL page to explain this (it would have saved me hours today). If it is appropriate to include, the instructions for exporting raster scalars from QGIS are: Calculate and make pretty your layer (e.g. of slope). Go to Layer->Save As. Change the Output mode to Rendered image. Input your file name and any other parameters. Click OK.

Mapper version: 0.9.4

Pie menu (chapter)

Need add some info (as chapter) about "pie menu", that came since OpenOrienteering Mapper v0.4, and how it work/look in different situations.

REFERENCES

Suggestion: How to add a text symbol to a map

Doesn´t have the english version of OOM but will try to translate my sugestion to the manual:

Use this if you don´t have a text icon in the Symbol Pane or if you want to add more text icons for other text-sizes or collours.

  1. Right click under the icons in the ?ymbol Pane (picture).
  2. Choose "New Symbol" then "Text" and a new window called "Symbol Preferenses show up.
  3. Under the first tab named "Text General", you fill in a number (for example 1) in the becomming icons number box. Fill in a name (for example "Headline".
  4. Click on the second tab "Text Preferences" and choose the size. Most important is to choosing a colour and if you forget this you can´t see any text.
  5. Click "OK" and a new icon showing the letter "A" is now seen in the Symbol Pane window.
  6. Choose the text icon you created and place it on the map and then type the text. A small window will open up in the maps left top corner, showing where the text will be positioned in relation to the marker you placed on the map before typing the text.

Excuse me for my bad english!

Autogenerated PDF manuals naming

Currently there are 3 versions of PDF manual:

For what reason you generate OpenOrienteering-Mapper-master-qt59_0.x.YYYYMMDD-Manual.pdf?

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.