You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The GeoServer tutorial has some hard coded paths to GeoServer that make it hard to follow if you are using a different Geoserver configuration than that prescribed by the tutorial. It would be easy to make it more generic and just get the paths from the geoserver_engine.
The text was updated successfully, but these errors were encountered:
But we'd first have to add a base_url attribute to the geoserver engine.
The only concern I have with this approach is that it implies that the URI needs to match the engine URL, which it does not. It just has to be a unique ID in URL form. This isn't a bad approach though and the nuance could be explained in a note box.
The GeoServer tutorial has some hard coded paths to GeoServer that make it hard to follow if you are using a different Geoserver configuration than that prescribed by the tutorial. It would be easy to make it more generic and just get the paths from the geoserver_engine.
The text was updated successfully, but these errors were encountered: