ogcmetoceandwg / worldweathersymbols Goto Github PK
View Code? Open in Web Editor NEWA complete set of WMO weather symbols in SVG with full metadata.
Home Page: https://github.com/OGCMetOceanDWG/WorldWeatherSymbols
License: Other
A complete set of WMO weather symbols in SVG with full metadata.
Home Page: https://github.com/OGCMetOceanDWG/WorldWeatherSymbols
License: Other
Currently, SVG files are not pretty printed in the codebase. We have discussed that this may be valuable.
I've added pretty print utility by running
$ ./scripts/wws_manage.sh pp # needs svgpp command, install with apt-get install libbatik-java
which will pretty print all .svg
files in the codebase.
@chris-little, @iedwards: if we want this for all files in the codebase, I can run a one time process and commit/push. Subsequent workflows by committers would then include running this command before pushing changed files (even though the script pretty prints all files, git will only detect changed files as staged for commit).
Comments?
Hi, I think the calm wind symbol might be wrong. Everywhere I looked, this symbol is a complete empty cercle. Currently, the symbol in this repos is a broken cercle, not complete:
ddff_WindArrows/WeatherSymbol_WMO_WindArrowCalm_00.svg
Can this issue be confirmed, and if so, then fixed? Thanks -- Alex
Remove unnecessary precision?
Here's a suggestion. If you agree that it's a good idea, I can implement.
The idea is to add readme.md files in each of the symbols directories, such as CH_CloudHigh, and display in the readme itself the symbols of the associated directory. This can be done by leveraging RawGit.com.
Benefit: users would be able to see all symbols of a directory at once while browsing the GitHub repos instead of having to click all svg symbol individually to find out what they look like. Cheers -- Alex
Hello...
It appears that the intent of PR #39 was to update the license version to CC BY 4.0, however it looks like only the protocol in the URLs was changed from http
to https
. The license referenced in the SVG symbols is still CC-BY-3.0.
Remove unnecessary transformations?
Example: https://github.com/OGCMetOceanDWG/WorldWeatherSymbols/blob/master/symbols/Ft_Fronts/WeatherSymbol_WMO_Front_Cold_frontolysis.svg?short_path=959a6e4#L27 has a dc:identifier
of http://codes.wmo.int/306/1152/4b
These codes should resolve on http://codes.wmo.int proper (currently 404).
I think the following code in wws_manage.sh needs to be updated for case = readmes:
cat <<END
Usage: `basename $0` <png>
png: generate PNG versions of symbols
END
Right?
Is it worth adding scripts to convert these svgs to
When symbolizing the compound value of wind speed and wind direction, to choose which wind arrow symbol to be used, we use the following approach:
In our case we use MapServer and have data driven symbol selection based on our observed properties of wind speed / wind direction.
The wind arrow type symbols, by default, have an orientation which needs to be rotated if used as part of automated systems per above. As a result, part of our automated build process has to rotate the symbols accordingly (i.e. rotate all 'north' images 90 degrees CW, rotate all 'south' 90 degrees CCW).
Should we have these rotated to 0 degrees in the codebase by default?
The list of wind arrow symbols can be found with find . -type f -name "*.svg"|grep -i arrow
or find . -type f -name "*.svg"|grep -i wind
@chris-little: there may be reasons for having the wind arrow images oriented this way by default, in which case feel free to mark this invalid. Else we can rotate them as default orientation.
Tagging a version as 1.0 is a sign of maturity and will certainly attract more users and organizations to start using those symbols in their projects. Currently, we have some ideas identified in the TODO.txt file, but we don't currently have milestones or target requirements for eventually tagging a version 1.0.
My suggestion would be to create and discuss what improvements and changes should Version 1.0 of the WorldWeatherSymbols have. Without a clear path forward and a list of potential improvements, we won't reach maturity as quickly as we could. Thoughts / comments? Thanks -- Alex
We would like to use the SVG symbols by a unique ID, but unfortunately some labels are wrongly labeled.
There is no implicit namespace declaration for http://www.w3.org/2000/svg within the svg documents. This causes unbound namespace prefix/URI errors.
Currently, there's no indication anywhere about WWS's associated license, right? That's missing and should be added.
Thanks! -- Alex
(cc @alexandreleroux)
@chris-little @iedwards should we introduce version tags as part of WorldWeatherSymbols? This would help in cutting releases of the repository as well as the pre-generated PNGs.
I would suggest the semver approach, but I'm good with whatever approach works for you, and keep consistent.
Remove unnecessary deep grouping? I suggest each symbol is in a single group, rather than each in its own SVG?
What about providing pre-generated PNGs to users? Or a link to such a repository?
I know we can generate the PNGs with the included script, but the process is out of reach to lots of casual users. As an example, on MacOSX, installing Inskcape is not enough, you need XQuartz too, and still then, you may end up with missing libraries to run the script and need to run a 'make' (at least, this was the case on my MacOSX 10.8.5 system) - this is asking way too much to potential users of the WorldWeatherSymbols. Let's make WorldWeatherSymbols more accessible to all by providing pre-generated PNGs? Thanks -- Alex
Provide a different resolution, such as 100x100 or 20x20, or with optional styles encoded, or significant extra symbols added.
Looks like we have defaults of:
stroke:#000000
fill:#000000
Add a utility which allows the user to specify a hex, rgb, or color to update an SVG.
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.