Order of map rendering in collections

Open
#2 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
php
Domain
frontend

Research direction

Start by locating how maps are rendered within collections and how map data is represented in the WordPress plugin. The issue proposes a priority attribute but does not specify its exact behavior or where it should be configured, so clarify those details before implementation. Done means collection maps render in priority order, with the town shape and circles displayed in the intended order.

Written by the indexing model from the issue text.

Description

enhancement good first issue

Hi Joe,

I have maps in a few collections and one of the map contain shape of the town. When I try to show collection with this shape of the town sometimes its covers other shapes from others maps. In my opinion it happens because of lack of priority attribute connected with map. Actually I workaround this behavior by removing map with shape of the town and adding new map because it seems that the newest added map is rendering as the first one when collection is rendering.

This page (from issue #1) show this problem perfectly - all circles are "under" shape of the town. I can't choose in which order maps are rendering. I can only use workaround described before.

The simplest method to resolve this problem is adding priority attribute to the maps and maps in collections should be render in order of these attributes.

Mirek

Dominant language
PHP
Stars
29
Forks
12
PR merge metrics
No merged PRs in 30d

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 OpenGIS/waymark-wp

All issues in OpenGIS/waymark-wp

Similar issues

More PHP issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.