User:Mstr/Sandbox/Tutorials
This sandbox is used to coordinate and discuss OpenGeoFiction tutorials. Not all proposals are accomplished yet, thus they should be taken with caution!
Many useful tutorials and other community-related discussions are provided here:
OGF:Automated tables and lists
see main page: OGF:Automated tables and lists
OGF:Wiki cleanup
see main page: OGF:Wiki cleanup
OGF:Using vector graphics
requires the ImportVec-plugin for JOSM
see also
OGF:Transferring lost country to "preserved" territory
A short documentation (so far only proposal!) how to transfer a lost country to a "preserved" territory
- a general decision has to be made if a former (now lost) country deserves a "preserved" status since
- a) its role (culture, economy, foreign relations) is important for the region
- b) there is significant high-quality mapping which deserves preservation
- the preserved area should be restricted/condensed to a minimum (no preservation of white map)
- if parts of the country's territory are blanked neighbors should be contacted to synchronize changes (e.g. common infrastructure projects...)
- mapping at characteristic places should be preserved, e.g. a town in a river bend which perfectly fits there (and nowhere else)
- the wiki content of a "preserved" country should be reduced to the most relevant parts
- a) the country page (modified if the country's size is reduced)
- b) important other pages if there is significant content and if they are important for the community
- c) further content should be moved to the country page (to keep the number of pages small)
- other pages belonging to this country (check the user's wiki contributions -> only page creations) should be blanked and marked for deletion (also links to these pages should be checked and modified!), for further details see OGF:Wiki cleanup
- a "preserved" country is community/admin owned, but administered by one user who's interested in preserving the country, this includes
- no massive changes regarding the mapping and style
- no massive changes regadring the role of the former country
- removing unrealistic objects
- small changes (e.g. placing/modifying embassies, relations, ...) are still possible
OGF:Provide links to map
Providing positions on the map
Each and every wiki article can only be as good as the corresponding objects on the map. To make it more easy for other users to judge about the quality of information (e.g. to prevent overwikification) but also to explore excellent examples of mapping (e.g. as a guidance how something can be mapped) each wiki page must provide links to all map positions related to the article. There are many possibilities what can be linked and different techniques how this can be done.
What to link
- geographic places like countries, states, cities, by using coordinates, nodes or boundary relations
- natural sights, monuments, ... by using coordinates or nodes
- companies by providing a link to the headquarters and, depending on the type of company, to all other relevant places which are related to the company, e.g. for
- manufacturing companies provide links to the factories
- retailers provide links to all stores
- transportation companies provide links to infrastructure they possess (or use) like stations, routes, maintenance facilities, ...
- sport clubs by providing links to sport venues and training grounds
How to link
Linking a map position always requires the coordinates (latitude and longitude, make sure that you don't mix them up) and often the zoom level. There are different ways to provide link(s):
- A single map position can be directly linked by using
https://opengeofiction.net/#map=ZOOM-LEVEL/LATITUDE/LONGITUDE
.
- Instead of using the link there are nice templates available, e.g. the MER-coordinates template (with many options)
{{MER-coordinates | zoom = 17 | latitude = 47.13913 | longitude = 131.35221 }}
47.13913 N, 131.35221 E
- If one wants to link many places at once (shops, ...) one can either use tables, multimaps or an overpass querry. The first two options represent the data at the wiki page. Besides the map position, tables can include more information about the place. On the other hand, multimaps visualize the spatial distribution of places, but usually do not show any information without clicking on places.
- Positions can be manually added to tables by using single map links. A nice alternative (especially if the data changes in the future) is to create tables which are automatically filled up by data from the map. This can either be based on a relation (you have to add the places to a relation) or an overpass querry. To make programming more simple you can use the MER-autoTable template which shows data requested by a relation or the overpas querry (with several search attributes).
- Positions can be manually added to multimaps by using single markers as described here. Similar to tables, this can be done automatically by using a relation and specifying a layer as, e.g., it is done for the Gobeletplain coffeehouse chain.
- Use the opq template to visualize all locations by using several search attributes in the overpass surface, e.g.
{{MER-overpquery | name = Gobeletplain Cafés | search1 = brand/Gobeletplain | area = Federal States of Archanta}}- providing the opq to all
Gobeletplain Cafés in the Federal States or {{MER-overpquery | name = Gobeletplain Cafés | search1 = brand/Gobeletplain}}- providing the opq to all Gobeletplain Cafés worldwide.
- link via node/line number or relations, e.g. for countries
- center position which should be linked, carefully chose zoom level (depends on screen size)
- special position links fpr airports to make it possible to create flight routes
- precision of coordinates?
The OGF count template enables to embed real-time data from the map in the wiki. A prominent example where this feature is useful is to get a reasonable number of inhabitants in a specific area.
OGF:Displaying flight routes in the wiki
using the Airlines routes template
International/List of airports
| marker=Template:WAAT-marker | line=Template:WAAT-airline routes ~Color=#001E97 ~Weight=1 ~Opacity=0.8
Template:WAAT-airline routes Template:WAAT-marker
| line={{WAAT-airline routes | route = DIA/STI }} ~Color=#001E97 ~Weight=1 ~Opacity=0.8
| marker={{WAAT-marker | STC | [[Stanncatt]]<br>{{Mergany}} | [[Stanncatt#Airport|International Airport Stanncatt]] | Marker25 panulethan.png }}
OGF:Working with categories
Due to the fact that my country Mergany is an industrial country, I permanently reorganize the industrial sector, e.g. the categories and lists:
- Companies by industry, e.g.
- Category:Aircraft engine manufacturer
- Category:Aircraft manufacturer
- Category:Airlines (plural form due to historic reasons)
- Category:Auto parts supplier
- Category:Automobile manufacturer
- Category:Beer brewing company
- Category:Beverage company
- Category:Broadcasting company
- Category:Building materials company
- Category:Bus manufacturer
- Category:Ceramics manufacturer
- Category:Chemical company
- Category:Construction company
- Category:Cycle manufacturer
- Category:Defence company
- Category:Electrical engineering company
- Category:Electronics company
- Category:Engineering company
- Category:Firearm manufacturer
- Category:Furniture company
- Category:Home appliance manufacturer
- Category:Internet company
- Category:Locomotive manufacturer
- Category:Motor vehicle manufacturer
- Category:Musical instrument maker
- Category:Oil and gas company
- Category:Pharmaceutical company
- Category:Printing company
- Category:Restaurant chain
- Category:Retailing company
- Category:Rolling stock manufacturer
- Category:Shipbuilding company
- Category:Sporting goods manufacturer
- Category:Telecommunication company
- Category:Tobacco company
- Category:Tool manufacturing company
- Category:Tractor manufacturer
- Category:Watch manufacturing company
OGF:Railway route relations
| § Important technical notes to users |
| Please note, that this concept is in a very early stage. |
Critical issues to discuss
- relations must start/end at some point between junctions
- - multiple relations on one track
- + equal length of relations improve clarity
- alternative: split at junctions: one relations per track, but many short relations at junctions and crossover
- trains/companies/networks are relations including (only!) other relations
- - parent relations don't show up on the map?
- + more easy to manage the parent relation
- + more easy to modify infrastructure, only handle track section relation(s), not a large number of company/train etc. relations
Creating railway sub- and super-relations
- sub-relations are logical parts of a railway line, containing (only one way from north-to-south or east-to-west of) a route from a start to an end point (imagine two stations)
- super-relations are specific trains (might use several sub-relations), networks, companies, state railway relations
Why to use relations for routes on railway tracks?
In collaborative projects (including international collaboration) each participant should be able to set up trains/train companies. Of course, everybody is able to modify existing tracks according to their needs, but after several (uncoordinated) edits mapped railways will end up in a mess. Thus it should be on behalf of every user to map railways in such a way that everybody is able to "use" them without making edits.
While e.g. the "owner" of a track can be directly attached to the object on the map (i.e. the way which says "railway=rail") there might be different operators/users on such a track. In addition, ways might be split where properties change (at bridges/tunnels/switches/...). Collecting all ways from one destination to another destination in a relation would be much easier to use and can be used without modifications if is set up appropriately.
In order to make routes easily accessible for other railway companies (without changing the map) relations can be used to gather together all tracks on a route.
- Such relations are tagged as type = route + route = tracks.
- Relations include tracks from one "node" to another "node".
- "Nodes" are points between junctions or state borders.
- In case of multiple tracks only north to south or east to west are assembled in a relation.
- Relations end at state borders.
How to create railway routes?
Example
|
Loading map... When parsing the passed parameters had the following errors:
Service name "OGF" not found in the list of available services (leaflet, google, yandex, wikimedia). Used default service "Leaflet" Unknown parameter: "layers" Unknown parameter: "overlays" Unknown parameter: "overlaydef" |
| Railway routes in Oakley | 
| |
|---|---|---|
| ref | name | Map |
| 13-21 | OKBA-OKRG | map
|
| 13-22 | OKBA-OKRF | map
|
| 13-23 | OKBC-OKBA | map
|
| 13-12 | OKBB-OKBA | map
|
| 13-02 | OKA-OKRD | map
|
| 13-03 | OKRA-OKF | map
|
| 13-04 | OKF-OKRC | map
|
| 13-13 | OKF-OKBB | map
|
| 13-11 | OKBB-OKRC | map
|
| 13-14 | OKBB-OKBC | map
|
| 13-24 | OKHD-OKBC | map
|
| 13 | Railway tracks in Oakley | map
|
| Railway nodes in Oakley |
| |
|---|---|---|
| ref | name | Map |