Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update geodetic_control xslt and related xml in geoserver in delivery #6

Open
mraross opened this issue Apr 10, 2017 · 8 comments
Open
Assignees

Comments

@mraross
Copy link
Contributor

mraross commented Apr 10, 2017

Changed filename convention for xslt and related xml file to use underscore instead of dash. Please copy updated geodetic control xslt and xml files from dbc-kml-apps/geoserver/geodetic_control to geodetic control datasource in geoserver

@webgismd
Copy link
Collaborator

I have updated geoserver in delivery with this files. However, to set up a jenkins job for XSLTs, I would like to have all the xml and xslts in one directory.. ie /geoserver/transform/.x rather than dbc-kml-apps/geoserver/geodetic_control/geodetic.x*

@mraross
Copy link
Contributor Author

mraross commented Apr 12, 2017

What about slds and ftl templates? I would like slds to be named and predefined so developers only have to reference them by name and not have to include their full definition on every request. Don't slds and ftl templates have to be in the appropriate data source directories of geoserver?

@webgismd
Copy link
Collaborator

I would suggest this structure:
/geoserver/ftls/.ftl
/geoserver/slds/
.sld

we have equivalent directories in SVN for this too..(as part of the geoserver build scripts)

@mraross
Copy link
Contributor Author

mraross commented Apr 12, 2017

So if description.ftl templates for all data sources reside in a single directory, how do we distinguish them? I thought geoserver expects them to have an unqualified name and be in the correct subdirectory of the data source as in:
geoserver/data_source/ds1/description.ftl
geoserver/data_source/ds2/description.ftl

@webgismd
Copy link
Collaborator

you are correct it could be structure like this in github:
\WHSE_BASEMAPPING\WHSE_BASEMAPPING.BC_MAJOR_WATERSHEDS\description.ftl

or <schema><object>\description.ftl

@mraross
Copy link
Contributor Author

mraross commented Apr 12, 2017

Ok, should the same structure apply to named SLDs? transforms?

@webgismd
Copy link
Collaborator

no SLDs and Transforms have one folder only each and aren't divided in this way.

data\styles*
data\wfs\transform*

@mraross
Copy link
Contributor Author

mraross commented Apr 12, 2017

Ah, ok.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants