opensavannah / savmaps Goto Github PK

Because we wanted to have the logo in place of the Title, we used basic HTML markup to insert the logo. Initially, this was causing the Page Title itself then to be displayed as unrendered HTML markup.

I've fixed this by editing map.js to set a manual value for the page title.

Need a solid list of columns that are needed to run sav maps to refactor the spreadsheet

When trying to view only one or two of the taxonomies, it gets tedious having to uncheck the rest first. We should add a select/deselect all function.

At the event, the map kept breaking inexplicably. The reason is that users were entering new data but hadn't yet geocoded it yet.

Workaround temporarily

Instead of editing the main workbook itself, make your own copy and edit it, making sure that every single row/entry has valid lat/long columns. Then copy the entirety directly back into main workbook. This is akin somewhat to GitHub's forking process.

.map-title, .img, #points-legend, .ladder....

To free up screen real-estate

Should include an emergency modal...

Not for use with life-threatening emergencies

If you are experiencing an emergency, call 9-11

...or something to that effect

How do we include hotlines and other non-physical resources in a visual resource directory?

Rape Crisis Center , for example.

I think we should limit access to people who are logged into google at least. Ideally, people would request access and then be allowed in. Is there good reason to allow anonymous changes?

Before we get too bogged down in the mud with submission forms and security concerns, could @egomadking lead the way in being the gatekeeper of the current workbook?

There's still a . lot of data from SavBook that hasn't been brought into SavMaps in any fashion, staging or otherwise. We can figure out the submission part better later. But let's get in there what we have available now.

I'll help some but it needs to be coordinated.

So it looks like @egomadking presumably made a best effort attempt to solve this by categorizing the entries' colors with the corresponding hex code values for the legend...

... problem is, the code can't read hex values (insane, I know, right?). Instead, it uses the following list of colors, because they're best suited for colorblind-friendliness:

So, I've sorted the entries alphabetically A-Z, and am changing the hex code values out for the closest one I can find in the legend.