HashTrack and "Built-in" Layers about gm3

[theduckylittle]

I'd like to implement option 2.

[klassenjs]

+1 for Option 2. I like the flags approach, maybe with the option for more fine grained flags in the future.

[elil]

I agree with above, point 3. flexibility and consistency. Flexibility is very powerful and something that makes GeoMoose fairly unique. It is also something that complicates our testing and expands our corner cases and can lead to whack a mole. I'm not sure of the balance to strike. One complex way would be a mapbook validation tool that identifies conflicting mapbook configurations. But then we would need to write rules for valid mapbook configuration.

Also, #95, about hovering might more properly belong here.

[klassenjs]

Marking this a bug because it is easy to hurt yourself in the current state. I think this should be fixed before release.

[theduckylittle]

Two things:

1. My bad on the syntax, it should be:

 <param name="always-on" value="true"/>

2. I've now added parseBoolean as "true" coming in from the mapbook would bring in a string instead of an actual boolean value.

[klassenjs]

Update: conflicted with WMS parameters. Changed to use options instead of param so there no mapbook syntax at the moment.

[klassenjs]

@theduckylittle It's your issue to close.