-
Notifications
You must be signed in to change notification settings - Fork 4
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
-xsl flag does not work as intended #21
Comments
@noaaroland @karlmsmith is it possible to verify that the ncISO standalone is working as expected? |
Yes, it works, but the instructions were wrong. I updated the README.md and verified the behavior using the latest jar file release (2.3.7). |
Thanks for checking @noaaroland but in our case with v.2.3.7 -xsl tag does not actually read the custom XSL. It doesn't generate any error messages but also does not seem read the custom style sheet. I can point to an empty file or a bogus filename it doesn't matter. No errors generated, custom XSL not applied.... EDIT: it was v2.3.7 not v2.3. Corrected above. |
What is stopping you from using the latest version? |
Verify the files are in place...
Try running with a non-existent file name...
Look at the XSL to see what was changed from the default...
Verify the _META.xml file contains the modifications per the new XLS...
|
I reopened this until we get it sorted out, but I'm not going to investigate the behavior of other versions if I know the current release works. |
Thank you so much for looking into this @noaaroland. I was using the most recent version v2.3.7, corrected the typo in my previous post. I do not get this part when I run the same command with you:
Here's my screenshot:
Could something (like a file or a path to a library) be hardcoded in the script? Would Java software or version matter? |
Do you have a directory called 'xsl' in D:\Documents\DATA_RELEASE\ISOcompare\standalone_ISO? |
I have successfully run it under Linux with: (base) schweitzer@GREEN:~/nciso$ java -version and Windows PowerShell with: PS C:\Users\schweitzer\Documents\nciso> java -version So if you don't have at least Java 8 installed that is the last suggestion I can offer, because I cannot reproduce the error. |
I am on Windows PowerShell with OpenJDK Temurin. Could that be the problem? I will look into it...
|
...and interesting! that seems to make a change!!! |
Fixed in 2.3.8. |
thanks for your help on this. I am working with zdefne at usgs. i am finding that the java version is critical. **********> on our Linux system we have But i get an error **********> on my windows system i have So i works on the WINDOWS but not on Linux. |
Hi @noaaroland, Now I get errors that complain about "as=string" tags in the XSL. It looks like this is an issue with XSLT1.0 but not with XSLT2.0 (see here for more info). Was the XSLT version downgraded from 2.0 to 1.0 sometime in the past? I see a similar discussion here: Unidata/threddsIso#19 (comment) |
Yes, the XSLT processor did change. I'm trying to move away from old unsupported packages. I put up a new jar as a beta which uses Saxon which supports XSLT 2 and 3. Try it and let me know please. |
Thank you @noaaroland! This seems to work. It creates an _ISO.xml which is based on the original XSL, and a _META.xml which is based on the modified XSL (as expected). In the previous versions _META.xml always came out empty. I can now go back to throwing wrenches at it!!! 🐵🛠 What is the source of original ISO style sheet used to create the _ISO.xml by the way? |
Thanks for letting me know. All of the XSL and the Java code originates from work done by @dneufeldcu and colleagues. I am just the caretaker. I made 2.3.9 official. |
I am trying to do this on my desktop with the -custom and -xsl the flags:
but I get this error:
ncISO is trying to locate the style sheet here:
I tried with placing the XSL in the same folder and with/without the folder name in the command line but no luck.
This works without the flags and the custom XSL. Also ncISO-2.3.5 throws this error but ncISO-2.3.7 completely ignores the flag and uses the default style sheet therefore no errors generated...
The text was updated successfully, but these errors were encountered: