jolavb / sno_demo Goto Github PK

Possibilities:

• select a trail and then drop hydrants associated with it. This is probably a good first step and easy from what we have now.
• drop hydrants independently and associate with trail by circling them or simlilar
• drop hydrants independently and have them associate with the closest trail by coordinates; manually prompt for conflicts (hydrants at overlapping trails, etc)

Add buttons that import from KLM into state, and exports state into KLM (probably have the option of exporting trails and hydrants separately, similar to how its structured now).

Make it rotate.

If a user deletes a trail with hydrants, the orphaned hydrant's style doesn't match newly added unaccociated hydrants.

Hydrants shouldn't live inside trails, just be associated with them.

This is definitely low priority, but I've noticed the font and button sizes are significantly different on your comp versus mine. Namely, they're much bigger on mine. Not a huge deal, but I think it actually makes for a significantly worse experience when editing on something like a normal laptop screen because I'm getting much less actual map space on the screen. Not sure if it's a difference in browser defaults, or something else.

Should see if we can make these more uniform maybe. Browserstack is a good tool for this if we take the time to do it.

Add pressure temp and flow zones.

Hydrants are rendering as trails in some cases (Canyons Hydrants KML file)

Map currently doesn't render when zoomed in too far

Add instructions on how to use tool somewhere (i.e to rotate map-> shift + option + drag)

Per discussion: switch between "hydrant mode" and "trail mode", without them being interdependent like they are now. Auto-associating hydrants and import/export are separate buttons and processes.

When Multiple polygons make up a single trail, the user should be able to delete one of them.

Self explanatory

Make hydrant data editable (elevation, coords, and name for sure, maybe also attach a gun?)

Probably either a popup or something extending out from whatever menu they click on to select the hydrant.

After KLM's are working, look at GeoJSON and csv/xlsx exports.

I'm not sure this is REALLY a requirement, something simpler like just automatically starting in the current location might be fine, since this is supposedly going to take place on site, but look at it and decide the best way. Having them input some coordinates to start wouldn't be the end of the world if there isn't an easy-to-use API we can just integrate with.