Skip to content

Enable <map-layer> inline or remote static features #1034

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Draft
wants to merge 22 commits into
base: main
Choose a base branch
from

Conversation

prushforth
Copy link
Member

First stab at getting rid of processFeatures / _mapmlvectors approach

Several test failures related to feature indexing and perhaps other stuff

Peter Rushforth and others added 15 commits August 1, 2025 14:49
First stab at getting rid of processFeatures / _mapmlvectors approach

Several test failures related to feature indexing and perhaps other stuff
  map-extent, -tile, -feature to determine zIndex positioning in parent
  based on how Leaflet layers are created and shared among sibling
  elements in a sequence
Add red/green/blue-tile.png
Add setZIndex function to MapFeatureLayer, MapTileLayer, copied from
MapExtentLayer.
Update MapFeatureLayer, MapExtentLayer, MapTileLayer initialize 
constructors to set the zIndex if there's an option present for it
Adapt calculatePosition to working within either shadow root or light DOM
Un-break and de-flake tests as possible
Clean up map-feature connectedCallback (remove unused bind)
context, i.e. as child of a <map-layer>, the container for the MapFeatureLayer
or the MapTileLayer should be removed from the layer rendered dom;
includes basic tests of this for both types of static content.

Update ToDo file, index.html to remind me to fix problems with 
TemplatedFeaturesOrTilesLayer
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant