cuhacking / atlas-editor Goto Github PK

When a feature's properties have been modified, the changes to those properties should be updated in-memory.
i.e. if you edit a property, and then select another feature, those changes should still be present when you select the original feature again.

• Persist changes to props in-memory
• Add "changes not saved" indicator when changes are present

When a feature is moused over, an outline of that feature should be highlighted.

This can be done using mapbox's "feature state" functionality, which allows the styling of a feature to be adjusted if a feature is selected. Alternatively (and necessary if we only want to show the outline), the feature that is being hovered over can be copied to a special line layer that is styled to look like an outline.

Now that we can view feature properties, we need to add the capability to edit the properties in those features. This will involve upgrades to the side panel UI, as well as additional logic to handle changes to those property values.

• #21
• #22
• #23

Currently the map's scrolling isn't very smooth. Enable smooth scroll in react-map-gl.

To better-support feature prop editing, we need to stylize the side panel.

This should include:

• Making the side panel a fixed width (optionally resizable)
• Add text input widgets for feature prop values (only text needs to be supported for now)
• Add style to the side panel, feature prop editor should look and feel like a "form"

When a user clicks on a feature on the map, its properties should be shown in the editor's side panel.

Subtasks:

• #7
• #8

(the display doesn't need to be fancy. Just a few rows of text for this task)

Once changes have been made to feature properties, we will need a way to save these changes back to the files that the features were imported from.

Since we treat a folder as a "project", and we import multiple files worth of features, we'll need to keep track of which object (in memory) came from which file, that way we can write the changes to the appropriate files.

When the editor is open nothing is displayed (on the map).

To display data, the user should have to open a folder (similar to how VSCode or other editors work). If that folder contains valid GeoJSON files (with a .json or .geojson extension) they should be loaded into the editor and displayed on the map using a Line layer.

As a list, this task should cover:

• #4
• #5
• #6

We can now click on features and view their properties in the side panel.

To enhance the user experience, we should add some visual indicators for when the user is interacting with the map.

• #18
• #19

In index.html, the meta tag still says boilerplate stuff like Web site created using create-react-app.

Let's change it to something 🌟atlas🌟 specific!

Imported data should be valid geojson. If non-geojson files are found, a warning should be displayed to the user with a list of the invalid files, but the editor should try to load all of the valid files that it found anyway.

https://github.com/cuhacking/atlas-editor/pull/13/files#diff-26ad4b834941d9b19ebf9db8082bd202aaf72ea0ddea85f5a8a0cb3c729cc6f2R47

https://github.com/cuhacking/atlas-editor/pull/13/files#diff-c2cc24bc9001b11b6add48a4cd8f893d5d6c6e4d1bd254158bd14ab997f552cdR8

https://github.com/cuhacking/atlas-editor/pull/13/files#diff-26ad4b834941d9b19ebf9db8082bd202aaf72ea0ddea85f5a8a0cb3c729cc6f2R6