-
Notifications
You must be signed in to change notification settings - Fork 59
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
Adding WFS-T editing to GeoMoose #620
Conversation
0ca74fd
to
ddf26e6
Compare
1cc047b
to
ea80452
Compare
src/gm3/components/map/index.js
Outdated
let queryFeature = util.featureToJson(evt.feature); | ||
const mapProjection = this.map.getView().getProjection(); | ||
|
||
if (querySource.config['buffer-point']) { |
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.
@klassenjs and @brentfraser - Thoughts on this pattern for querying points/lines layers?
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.
8205fb5
to
6129c35
Compare
29acd5f
to
48d7bee
Compare
Issue: Delete -> click on empty area (e.g. no polygon) shows "Remove ..." dialog (and clicking Okay shows error in console). No dialog should be shown. |
Issue: Should the edit (and other?) tools be hidden when layer is turned off/disabled/not shown? Currently the legend is not shown in that case. |
Issue: If the editable layer is accessed through the "Favourites" tab, no "Edit feature properties" dialog is shown. |
Issue: Map tools (zoom in/out, end drawing buttons) obscure menu drop down choices. Change menu text from "Zoom to Full Extent" to "Full Extent", This move the other menu items slightly to the left. Start a feature edit, then click search and observe how the menu options are obscured by the Map tools. |
Issue: When the WFS-T server is TinyOWS, and an attempt is made to edit properties on a features property values when they are all null, the fetch in wfs.js:171 fails:
because The fix is to test for null, and make the value an object:
or something similar. GeoServer appears to include a "boundedBy" property by default, but TinyOWS does not. |
48d7bee
to
8d38682
Compare
Fixed. Wrapped the entire block in the feature-length check.
This really isn't an "issue" we could hide the tools. My initial thought is to keep them visible since they indicate the capabilities of the layer before it's turned on.
Moved the Modals' definition to the map from the catalogs.
Added a safer mixin to prevent errors. |
Currently I put the editable layers in a separate group to indicate which are editable since that ability is so important to the user. |
@theduckylittle The latest commits are awesome! I've tested my "Issues" and all the bugs are fixed. As for the issue/opinion of "hide edit tools", having a clean looking catalog/layer list is important (as is having an understandable UI). One solution is to have an edit icon at the same level of the "refresh" and "metadata" icons on the layer name: and while we're at it, move the "Toggle legend visibility" icon up there too. |
I'm willing to open up the discussion on this. There are good/bad reasons for this and I'm willing to talk about them but not in this already monster sized pull request. |
@theduckylittle A discussion on the layer controls would be great! |
@klassenjs - I believe this is ready for code review. @brentfraser has done a very thorough job of testing the functionality. I suspect any more bugs will be corner cases are minor oversights that can be handled in a follow up PR. Commits can/will be squashed appropriately after review. I suspect it's okay for docs to come in as a separate PR. I think Brent has those in the works. |
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.
Also, it might be worth bumping the version in package.json before the merge. No way this is a precursor to 3.7.1. Not sure if we want to call this 3.8 or 4.0.
Drawing and markup->Draw Point Actually seem to get locked in scroll at end of drawing any feature on Drawing and Markup (with mouse button up) Associated with the following in the console
|
The CSS changes are mostly subtle but it looks way nicer and feels more intuitive than before. |
I'm still working on a Geoserver install. |
1075283
to
b92747f
Compare
1. Fix bug with joining "?" urls - Adds new util function to centralize cleanup logic. - Fixes vector map-source issue when there are trailing question marks. 2. Add built-in fixed editing layer. 3. Convert map controls to new react components 4. add keybindings for edit operations
…for point layer query
1. Add affordances to selected tools in the catalog. 2. Add signifiers to selected services in the toolbar.
b92747f
to
8797a83
Compare
Big honking MR to add WFS-T editing capabilities to GeoMoose.