map-boundary-editor 0.3.0 → 0.3.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -61,6 +61,7 @@ for visualization, review, or approval workflows.
61
61
  - Support for fixed, non-editable **reference boundaries**
62
62
  - Read-only mode for review or visualization use cases
63
63
  - Supports multiple editable boundaries (GeoJSON `FeatureCollection`)
64
+ - No vendor lock-in or API keys required
64
65
 
65
66
  ---
66
67
 
@@ -164,14 +165,12 @@ If editable boundaries are later loaded using `setGeoJSON`, the map will automat
164
165
 
165
166
  ---
166
167
 
167
- ### Optional: Geolocation Helper
168
+ ### Geolocation
168
169
 
169
- An optional geolocation helper is available to center the map on the user's current location.
170
+ Geolocation must be triggered explicitly from a user interaction due to browser permission requirements.
170
171
 
171
- This feature only affects the initial view and does not modify boundaries or output GeoJSON.
172
-
173
- ```html
174
- <map-boundary-editor use-geolocation></map-boundary-editor>
172
+ ```js
173
+ editor.enableGeolocation();
175
174
  ```
176
175
 
177
176
  ---
@@ -264,8 +263,8 @@ A demo is included in the repository to showcase:
264
263
  - Visual hierarchy between reference and user-defined areas
265
264
  - Readonly vs editable interaction modes
266
265
 
267
- The demo also serves as a reference implementation for integrating the component
268
- into real-world applications.
266
+ Live demo on StackBlitz:
267
+ https://stackblitz.com/github/heritechie/map-boundary-editor
269
268
 
270
269
  ---
271
270
 
@@ -275,6 +274,8 @@ into real-world applications.
275
274
  - v0.4: additional map engine adapters (MapLibre, Google Maps)
276
275
  - v1.0: stable API
277
276
 
277
+ The roadmap is intentionally conservative to keep the core API stable.
278
+
278
279
  ---
279
280
 
280
281
  ## Non-Goals
@@ -285,3 +286,5 @@ This project is intentionally not:
285
286
  - A GeoJSON validation library
286
287
  - A replacement for tools like geojson.io
287
288
  - A general-purpose map rendering framework
289
+
290
+ ---