-
Notifications
You must be signed in to change notification settings - Fork 20
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
Upload QML (Issue 3433) #3435
Upload QML (Issue 3433) #3435
Conversation
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.
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.
Not much has changed regarding #3431
Only now when I add the layer "bioregion_pilots" from the data catalogue as WFS, all layers disappear from the map 😱
Yes, getcolor was added back in ol-ext just in the latest ol-ext version.
Dicd you npm ci?
…On Mon, 10 Oct 2022, 23:34 jmacura, ***@***.***> wrote:
***@***.**** requested changes on this pull request.
[image: image]
<https://user-images.githubusercontent.com/5598693/194948223-640a657e-5433-4e6a-bf2e-6aa2217fad3f.png>
This is now in the console, when I start the test-app. I believe it was
not there before...
—
Reply to this email directly, view it on GitHub
<#3435 (review)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AADAR6QLZJJUM6EA4EU6UWTWCR4V3ANCNFSM6AAAAAARBG7DGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Good point. My apologies. I have updated the comments above. |
Right, I actually only fixed it when uploading the SLD to style pannel. Not for loading the layer from |
@jmacura could you retest please? |
Sure, will test it later today. |
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.
And... We can't. There is an issue opened in the geostyler/geostyler-qgis-parser library about it: geostyler/geostyler-qgis-parser#259 From the code in https://github.com/geostyler/geostyler-qgis-parser/blob/ae5203392377d2342ef04a50766eedcdfe5990ec/src/QGISStyleParser.ts#L143 it is quite obvious, that the "fieldName" attribute of the "text-style" element in QML gets misinterpreted as
FTR. Changing the label formatting expression from Hence I think this PR is an acceptable fix of #3431 . |
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.
Would you mind changing the last commit message to something better than "squash", @raitisbe ? 🙏 🙂
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.
e36f0f7
to
a9f2e74
Compare
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.
We can also implement the upload of QML along with new vector layer later on.
ed6b5f8
to
f318385
Compare
I did it in this PR, but It had so many changes I'm not sure I haven't broken something... Especially on the upload to Layman side. I think we will need to have some e2e test for this |
Aye. That is what I was afraid of. Actually I started to implement it after our telco today, but then I have realised I am lost, as I do not know the consequences on the Layman side so I have thrown my changes away. |
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.
Description
Support upload of QML in style panel and create a walkaround for invalid WellKnownName problem when parsing qml with geostyler-qml-parser.
Related issues or pull requests
#3433
#3431
Pull request type
Please check the type of change your PR introduces:
Do you introduce a breaking change?
Checklist
npm test
locally)