-
Notifications
You must be signed in to change notification settings - Fork 4
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
Service owc #102
Service owc #102
Conversation
…raster and vector
return this.createLayerFromOffering(offering, resource, owc, targetProjection); | ||
const offerings = resource.properties?.offerings; | ||
if (offerings) { | ||
// TODO: allow Multiple offerings ??? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Currently we only support to use one Offering, so we do not create multiple Layers e.g. if there is a Resource with WMS and WFS offering.
Then we go in the order like: isWmsOffering | isWmtsOffering | isWfsOffering | isTMSOffering | offerings[0]
I think this should be extended later on to support multiple layers, e.g. a WMS and a WMTS.
@@ -700,35 +1089,39 @@ export class OwcJsonService { | |||
} | |||
} | |||
|
|||
/** | |||
* TODO: add more vendor params ?? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here it was requested to add more vendor params e.g. like cql_filter so the data can be filtered by configuration.
See ukis-frontend/project-zki-viewer/-/issues/93
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for this quest. Currently i put those directly in the request URL...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
quite much work behind this PR. Thanks a lot to @boeckMt for this! I have nothing aginst this PR. I have left couple of comments, please check them. It is up to you to consider them or not :)
* Update Layers.ts typo fix pupupFunktion --> pupupFunction (could be a breaking change in come apps) * update of map-ol.service.ts rename pupupFunktion to pupupFunction * Update CHANGELOG.md Renamed layer property pupupFunktion to pupupFunction * Update CHANGELOG.md * Update route-map.component.ts changed pupupFunktion to pupupFunction * Update map-ol.service.ts fixed typo pupupFunction to popupFunction * Update map-ol.service.ts fixed several typos pupup to popup * Update map-ol.service.spec.ts changed pupupFunktion to popupFunction * Update Layers.ts fixed type pupup to popup * Update route-map.component.ts fixed type pupup to popup * Update CHANGELOG.md
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
GlobalProgressComponent
.Issue Number: N/A
What is the new behavior?
closes Allow hidden/merged layers in LayerGroup/Layer #99
closes Use properties from OWS Context GeoJSON Standard #97
closes Remove owc-control #77
@dlr-eoc/core-ui: Missing output was added.
@dlr-eoc/layer-control: Legend images get shown in a new tab on click and resized if the are to large
@dlr-eoc/map-ol: Implemented new layers TMS, KML and fix GeoJSON from url.
@dlr-eoc/services-ogc: Implemented new layers TMS Raster and Vector, KML, XYZ, fix some OWC Parsing and better support for OWC writing
Does this PR introduce a breaking change?
BREAKING CHANGES
and see https://github.com/dlr-eoc/ukis-frontend-libraries/pull/102/files#diff-06572a96a58dc510037d5efa622f9bec8519bc1beab13c9f251e97e657a9d4ed
Other information
Is it part of one/more packages and which?