[docs] Change OM (referring to Organic Maps) to CoMaps

Signed-off-by: Filip Czaplicki <git@starsep.com>
This commit is contained in:
Filip Czaplicki
2025-07-20 16:32:09 +02:00
parent cdaf34bde2
commit 6cfdeadf87
4 changed files with 7 additions and 7 deletions

View File

@@ -72,7 +72,7 @@ This test-case should work with the same behavior regardless of
- Tap on location button - "To continue, turn on device..." dialog - Tap on location button - "To continue, turn on device..." dialog
should re-appear again. should re-appear again.
5. OM location dialog (negative case) 5. CoMaps location dialog (negative case)
- Use non-Google flavor or disable Google Play Location in the app settings; - Use non-Google flavor or disable Google Play Location in the app settings;
- Disable Wi-Fi, disable Cellular Data, disable Location; - Disable Wi-Fi, disable Cellular Data, disable Location;

View File

@@ -71,7 +71,7 @@ TRANSIT_URL: file:///home/result_json_dir
Run generator tool [as usual](../tools/python/maps_generator) with this ini config. After it is done you'll have mwms with transit section in experimental GTFS format. Run generator tool [as usual](../tools/python/maps_generator) with this ini config. After it is done you'll have mwms with transit section in experimental GTFS format.
:checkered_flag: Use the resulting mwms in your app. Enjoy the experimental public transport in Organic Maps! :checkered_flag: Use the resulting mwms in your app. Enjoy the experimental public transport in CoMaps!
## If you have questions ## If you have questions

View File

@@ -30,7 +30,7 @@ There are some other files not mentioned here.
### Map features / classificator ### Map features / classificator
- `mapcss-mapping.csv` - mapping between OSM tags and OM types. - `mapcss-mapping.csv` - mapping between OSM tags and CoMaps types.
- `replaced_tags.txt` - merging similar OSM tags. - `replaced_tags.txt` - merging similar OSM tags.
- `mixed_tags.txt` - pedestrian streets of high popularity. - `mixed_tags.txt` - pedestrian streets of high popularity.
@@ -38,7 +38,7 @@ There are some other files not mentioned here.
- `config.xsd` - XML schema for `editor.config`. - `config.xsd` - XML schema for `editor.config`.
Automatically generated: Automatically generated:
- `classificator.txt` - hierarchical list of all OM types. - `classificator.txt` - hierarchical list of all CoMaps types.
- `types.txt` - `types.txt`
### Styles and icons ### Styles and icons

View File

@@ -56,7 +56,7 @@ Icons are stored in [`data/styles/default/light/symbols/`](../data/styles/defaul
## How to add a new icon ## How to add a new icon
1. Add an svg icon to `data/styles/default/light/symbols/` (and to `dark` too) 1. Add an svg icon to `data/styles/default/light/symbols/` (and to `dark` too)
preferably look for icons in [collections OM uses already](../data/copyright.html#icons) preferably look for icons in [collections CoMaps uses already](../data/copyright.html#icons)
2. Add icon rendering/visibility rules into `data/styles/default/include/Icons.mapcss` and to "navigation style" `data/styles/vehicle/include/Icons.mapcss` 2. Add icon rendering/visibility rules into `data/styles/default/include/Icons.mapcss` and to "navigation style" `data/styles/vehicle/include/Icons.mapcss`
3. Run `tools/unix/generate_symbols.sh` to add new icons into skin files 3. Run `tools/unix/generate_symbols.sh` to add new icons into skin files
4. Run `tools/unix/generate_drules.sh` to generate drawing rules for the new icons 4. Run `tools/unix/generate_drules.sh` to generate drawing rules for the new icons
@@ -64,7 +64,7 @@ preferably look for icons in [collections OM uses already](../data/copyright.htm
## How to add a new map feature / POI type ## How to add a new map feature / POI type
1. Add it into `data/mapcss-mapping.csv` (or better replace existing `deprecated` line) to make OM import it from OSM 1. Add it into `data/mapcss-mapping.csv` (or better replace existing `deprecated` line) to make CoMaps import it from OSM
2. If necessary merge similar tags in via `data/replaced_tags.txt` 2. If necessary merge similar tags in via `data/replaced_tags.txt`
3. Define a priority for the new feature type in e.g. [`priorities_4_overlays.prio.txt`](../data/styles/default/include/priorities_4_overlays.prio.txt) and/or other priorities files 3. Define a priority for the new feature type in e.g. [`priorities_4_overlays.prio.txt`](../data/styles/default/include/priorities_4_overlays.prio.txt) and/or other priorities files
4. Add a new icon (see [above](#how-to-add-a-new-icon)) and/or other styling (area, line..) 4. Add a new icon (see [above](#how-to-add-a-new-icon)) and/or other styling (area, line..)
@@ -105,7 +105,7 @@ A whole map needs to be [regenerated](MAPS.md) for the changes to take effect if
## Technical details ## Technical details
Map style files syntax is based on [MapCSS/0.2](https://wiki.openstreetmap.org/wiki/MapCSS/0.2), Map style files syntax is based on [MapCSS/0.2](https://wiki.openstreetmap.org/wiki/MapCSS/0.2),
though the specification is not supported in full and there are OM-specific extensions to it. though the specification is not supported in full and there are CoMaps-specific extensions to it.
The `tools/unix/generate_drules.sh` script uses a customized version of [Kothic](https://codeberg.org/comaps/kothic) The `tools/unix/generate_drules.sh` script uses a customized version of [Kothic](https://codeberg.org/comaps/kothic)
stylesheet processor to compile MapCSS files into binary drawing rules files `data/drules_proto*.bin`. stylesheet processor to compile MapCSS files into binary drawing rules files `data/drules_proto*.bin`.