Multiple values in isced:level

Multiple values in isced:level

Hi!

I would like to know how to indicate that a school offers several educational levels. I've been seeing the isced: level tag, which is that I think to use, but I have a question about how to separate multiple values.

I have looked in taginfo and approximately in 15000 cases the semicolon (;) is used, in 3000 the comma (,) and in 1000 cases the hyphen (-). It would seem therefore that the general criteria is to use the semicolon.

It really is that? Is there no risk of causing errors when converting data to another format?

Another option that I had valued, and of which I have not found use, is to add the level in the label itself, thus being:

Re: Multiple values in isced:level

I have looked in taginfo and approximately in 15000 cases the semicolon (;) is used, in 3000 the comma (,) and in 1000 cases the hyphen (-). It would seem therefore that the general criteria is to use the semicolon.

I would like to know how to indicate that a school offers several educational levels. I've been seeing the isced: level tag, which is that I think to use, but I have a question about how to separate multiple values.

I have looked in taginfo and approximately in 15000 cases the semicolon (;) is used, in 3000 the comma (,) and in 1000 cases the hyphen (-). It would seem therefore that the general criteria is to use the semicolon.

It really is that? Is there no risk of causing errors when converting data to another format?

Another option that I had valued, and of which I have not found use, is to add the level in the label itself, thus being:

I would like to know how to indicate that a school offers several educational levels. I've been seeing the isced: level tag, which is that I think to use, but I have a question about how to separate multiple values.

I have looked in taginfo and approximately in 15000 cases the semicolon (;) is used, in 3000 the comma (,) and in 1000 cases the hyphen (-). It would seem therefore that the general criteria is to use the semicolon.

It really is that? Is there no risk of causing errors when converting data to another format?

Another option that I had valued, and of which I have not found use, is to add the level in the label itself, thus being:

Re: Multiple values in isced:level

> On 4. Aug 2019, at 14:14, Andrew Harvey <[hidden email]> wrote:
>
> It could be cultural but I've always understood that the hyphen (-), ie. 1-3 would mean it covers 1, 2 and 3, while if you say 1;3 or 1,3 then it would cover 1 and 3 only, excluding two 2.

This is also my general understanding although there are situations where the meaning can differ, e.g. housenumber = 1-3 can mean either 1;2;3 or 1;3 (depending on the local numbering scheme for this road).

Re: Multiple values in isced:level

This is also my general understanding although there are situations where the meaning can differ, e.g. housenumber = 1-3 can mean either 1;2;3 or 1;3 (depending on the local numbering scheme for this road).

There are several different views on this. Mine would be 1-3 means 1;2;3 and 1,3 means 1;3. Oh,

and 1,2,3 is an alternative to 1-3 but more cumbersome. However, this is OSM where a foolish

Re: Multiple values in isced:level

sent from a phone

> On 4. Aug 2019, at 16:58, Paul Allen <[hidden email]> wrote:
>
> There are several different views on this. Mine would be 1-3 means 1;2;3 and 1,3 means 1;3. Oh,
> and 1,2,3 is an alternative to 1-3 but more cumbersome. However, this is OSM where a foolish
> consistency is never the hobgoblin of our little minds.

if these were housenumbers, what about 1/3 ?

There might also be 1/1, 1/2 and 1/4, etc., or it could mean 1;3 (1 and 3). The latter is quite common in Italy, where every door or gate gets its number, but I have also seen the former, where a housenumber has been split into several housenumbers.

Re: Multiple values in isced:level

I have looked in taginfo and approximately in 15000
cases the semicolon (;) is used, in 3000 the comma (,)
and in 1000 cases the hyphen (-). It would seem
therefore that the general criteria is to use the
semicolon.

The page does not represent community consensus, it is an
intermediate state of an old edit war.

That it doesn't make sense should be clear from a) the fact that
there are a lot of attribute tags that use semi-colons separated
values without any issues, b) that in the mean time we have a lot
of tags that use far more complicated structured values which work
just fine and nobody writes pamphlets with lots of bold and
capital letters claiming that they can't possibly work.

If there should have been a conclusion from the discussion, it
should have been that use of lists in a specific tag should be
documented, including what the semantics are.

Simon

One thing that page doesn't explicitly mention is that
the semi-colon is a problem in URLs because

it can be a valid, meaningful character in some URLs.

It really is that? Is
there no risk of causing errors when converting data to
another format?

See link above.

Another option that I had valued, and of which I have
not found use, is to add the level in the label itself,
thus being:

Re: Multiple values in isced:level

so, after reading the different opinions, I understand that I can use the semicolon (;) or boolean values (yes/no), and both systems would be correct, is it? And, in any case, it should be documented in the wiki.

And I understand too, that it was a war of editions about the use of semicolon like a value separator, so my question is now that if the current version of the page it's ok or not, because I'd like complete its translation into Spanish.

Re: Multiple values in isced:level

I'll still be using a range with a -. so 0-2 to mean from 0 to 2 inclusive. I've used it all over my state for schools together with the grades key. To me it's a lot clearer and simpler than the semicolon or multiple yes/no values.

so, after reading the different opinions, I understand that I can use the semicolon (;) or boolean values (yes/no), and both systems would be correct, is it? And, in any case, it should be documented in the wiki.

And I understand too, that it was a war of editions about the use of semicolon like a value separator, so my question is now that if the current version of the page it's ok or not, because I'd like complete its translation into Spanish.

Re: Multiple values in isced:level

I'll still be using a range with a -. so 0-2 to mean from 0 to 2 inclusive. I've used it all over my state for schools together with the grades key. To me it's a lot clearer and simpler than the semicolon or multiple yes/no values.

so, after reading the different opinions, I understand that I can use the semicolon (;) or boolean values (yes/no), and both systems would be correct, is it? And, in any case, it should be documented in the wiki.

And I understand too, that it was a war of editions about the use of semicolon like a value separator, so my question is now that if the current version of the page it's ok or not, because I'd like complete its translation into Spanish.

End of the day, it's easy for a computer to read "0-2" and "0 to 2" and "0,1,2" and "0;1;2" as all the same, so really mappers should be able to use what makes the most sense for them or what's less error prone and simpler, as they all should be easily interpreted by the downstream data consumer.

I'll still be using a range with a -. so 0-2 to mean from 0 to 2 inclusive. I've used it all over my state for schools together with the grades key. To me it's a lot clearer and simpler than the semicolon or multiple yes/no values.

so, after reading the different opinions, I understand that I can use the semicolon (;) or boolean values (yes/no), and both systems would be correct, is it? And, in any case, it should be documented in the wiki.

And I understand too, that it was a war of editions about the use of semicolon like a value separator, so my question is now that if the current version of the page it's ok or not, because I'd like complete its translation into Spanish.