Comments (3)
So, thanks for this @justb4. One general question: Is this all about "divide and conquer", so that we separate the mapLayers
from the application config? Or is the main motivation the preparation of embedding remote endpoints as you described for OGC REST API an OpenAPI Feature? Are there any other advantages?
What bothers me is the fact that you can declare single layers directly in the app-config's mapLayers
and inject others by a defining this special layer type. This might be confusing somehow, IMHO. But maybe I oversee something here.
from wegue.
@chrismayer : thanks for reaction. The requirement came from a real-world project where Vector data is managed within a CMS and unlocked via HTTP endpoints each providing a single GeoJSON Feature Collection. The "Collection of Collections" (like Capabilities) is defined in a single endpoint that returns an array of Wegue Layer JSON definitions. Now one could argue that it would be better to use an OGC standard like WFS or better OGC API Features ("WFS3"), but then you would also have define/manage Styles, icons and other resources within the Wegue frontend app, in a somehow generic fashion (as users can add new Layers/icons in CMS). Now all these can be managed in the CMS.
The other use-case is a local "LayerList" JSON file as static
resource. This could help with app managers to separate the main config from a Layer list, having that list maybe created via other tools/transformations. One example I saw in the Wegue FOSSGIS 2020 presentation is the "QGIS2Wegue QGIS Plugin" by @JakobMiksch . Maybe it can be useful there.
The mechanism within Wegue (need async fetching/axios), getting layer-list can be factored out later to support OGC Capabilities endpoints for WMS, WFS and WFS3, and why not ;-) ArcGIS Online endpoints...Did something similar in the past with GeoExt/GXP/Heron, even generate a LayerTree. Big issue was with WFS how to deal with Layer styling...
from wegue.
Thanks for the clarification @justb4. Makes things much clearer. From my side we can introduce a dynamic layer configuration. Since it is backwards compatible no existing configs have to be changed. I'll have a look at your PR #113
from wegue.
Related Issues (20)
- cog geotiff support on wegue HOT 2
- Need to access service worker file as /sw.js HOT 3
- Hook to toggle sidebar visibility programmatically HOT 2
- Vector layer - access members of object under properties HOT 5
- Manage TileGrids in LayerFactory instead of MapComponent HOT 1
- Enforce Vuetify ESLint rules. HOT 4
- Streamline console logging behavior.
- Optimize bundle size
- Upgrade to latest OpenLayers HOT 1
- Upgrade to Vue 2 and Vuetify 2 LTS HOT 1
- package-lock.json messed up since merge of #335 HOT 1
- Upgrade to Vue 3 HOT 3
- Upgrade to Vuetify 3 HOT 2
- Access to layer inside HoverTooltip HOT 4
- OL layer properties are no longer reactive HOT 5
- Document global app properties
- Transition to new ESLint configuration
- Use new code formatting approach since ESLint deprecated all formatting rules
- Do not assign to Vue.prototype in unit tests
- Clarify revert before "Add a custom module" in workshop
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from wegue.