Review differences: Android default style vs the web vector (MVT) style

Open
  • Is something wrong?
#2,234 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
javascript
Domain
frontend, web-dev

Research direction

Start with map/src/resources/mvt, which links to the MVT resources, and review mvt/default.mvt.json alongside the Android default map style to identify other objects Android draws that the web vector style omits. Use the pharmacy example at way 529024774 and the MVT tile details in the issue as a reference. Done means a verified list of differences and the corresponding missing web style rules are added.

Written by the indexing model from the issue text.

Description

Goal

A verified list of objects that OsmAnd for Android draws on the default map and the web vector map does not, then the missing rules added to the web style.

Background

  • Found while testing osmandapp/web#1953 (case W-TC-13): Pharmacie de l'Espérance (way 529024774, 47.60026, -0.83927) is not drawn on the web vector map at zoom 18–19; Android draws its icon.
  • The server sends it: https://maptile.osmand.net/vector/{z}/{x}/{y}.mvt, layer osmand, a polygon with amenity=pharmacy, building=retail, name, osm_id (z15–17).
  • The web style is mvt/default.mvt.json in osmandapp/OsmAnd-resources; in the web repo map/src/resources/mvt is a symlink to ~/osmand/resources/mvt. It has no layer for amenity=pharmacy, and building-names skips buildings with amenity, so neither the icon nor the name is shown. The sprite already has amenity_pharmacy.
  • Not filed: nothing in osmandapp for it; osmandapp/OsmAnd-Issues#3265 (style fine-tuning, closed) does not mention healthcare.
Dominant language
MDX
Stars
63
Forks
431
Avg merge
17h 10m
Merged PRs (30d)
124

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from osmandapp/web

All issues in osmandapp/web

Similar issues

More Web Dev issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.