-
Notifications
You must be signed in to change notification settings - Fork 34
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
ID labels are not consistent in SVG files #35
Comments
@StephanSiemen thanks for reporting. Can you provide some examples so I can reproduce? |
Tom, Actually, I corrected most files already on in my branch of the cloned Thanks On 12 June 2015 at 13:41, Tom Kralidis [email protected] wrote:
|
Hi @StephanSiemen. The best approach here is to:
So something like: # fork repository on GitHub
git clone https://github.com/StephanSiemen/WorldWeatherSymbols.git
# copy earlier changes (wherever they are) into your fork
git commit -am 'fix ID labels (#35)'
git push origin master
# create New Pull request on GitHub |
Stephan, As Tom suggested, can you supply some examples please? There is only a partial mapping to the WMO codes, as some signs have alternates, or are determined by other means (such as Synop 8 groups!) Consequently, you will see Ids like 97, 97a, 97b, so it is not one-to-one. I agree unique Ids are required, but thought that I had supplied them. The intent is to use these to index into the populated WMO registries. Chris From: Tom Kralidis [mailto:[email protected]] @StephanSiemenhttps://github.com/StephanSiemen thanks for reporting. Can you provide some examples so I can reproduce? — |
@tomkralidis Stephan has now moved on from ECMWF, and I never saw a PR. So the question is, as the WMO registers do not seem fully populated, whether the IDs that were created have a good syntax for a URI environment, and how will WMO handle those weather symbols that have a many-to-one mapping onto the WMO weather codes. |
We would like to use the SVG symbols by a unique ID, but unfortunately some labels are wrongly labeled.
The text was updated successfully, but these errors were encountered: