2011/5/19 Federico Cozzi f.co...@gmail.com:
ma direi che il namespace si può già usare.
certo. si poteva già usare prima ;-)
Mi piacerebbe che qualcuno esperto di JOSM / Potlatch 2 mi aiutasse ad
aggiungerlo ai preset. Cioè bisognerebbe editare i preset per
shop=bicycle in modo da gestire queste specificazioni aggiuntive. Chi
mi dà una mano?
per JOSM lo faceva in passato sempre Christoph Eckert (
c...@christeck.de ). PL2 non lo so. In realtà non è difficile, se ti
prendi il file dei preset attuali lo capisci quasi subitò come
funziona.
penso (non sono sicuro) che il file da modificare è quello:
http://josm.openstreetmap.de/svn/trunk/data/defaultpresets.xml
(se te lo mettono dentro e non dicono che devi fare un optional preset).
Al inizio del file è anche spiegato come funziona e una riferenza a
questa pagina:
http://josm.openstreetmap.de/wiki/TaggingPresets.
ciao
Martin
qui le spiegazioni:
!--
item:
name: the text to display
icon: the icon to display
- relative to the icon path
- URL's are also supported to allow remote icons (are cached locally)
type: the data types - way,node,relation,closedway (separated by comma)
link: link to the relating map features website
label: simple static text label
text: the text to display
key: fixed key/value pair to be set
key: key to set
value: value to set
text: text box
key: key to set
text: fixed label to display
default: default string to display
delete_if_empty: true/false
use_last_as_default: true/false
combo: combo box, with multiple choices and possible to enter free form text
key: key to set
text: fixed label to display
values: comma separated list of values
display_values: comma separated list of values to be displayed instead of the
database values, order and number must be equal to values
short_description: comma separated list of texts to be displayed below each
display_value. (Only if it is not possible to describe
the entry in 2-3 words.) Instead of comma
separeted list, you can
also write it in the following form:
short_descriptionfirst description/short_description
...
short_descriptionlast description/short_description
default: default string to display
delete_if_empty: true/false
use_last_as_default: true/false
multiselect: list of values from which zero or more can be selected
key: key to set
text: fixed label to display
delimiter: character that separates values (default: semicolon) - this
will also be used to separate selected values in the tag.
values: delimiter-separated list of values (delimiter can be escaped
with backslash)
display_values: delimiter-separated list of values to be displayed
instead of the
database values, order and number must be equal to values
short_description: delimiter-separated list of texts to be displayed
below each
display_value. (Only if it is not possible to describe
the entry in 2-3 words.) Instead of a separated
list, you can
also write it in the following form:
short_descriptionfirst description/short_description
...
short_descriptionlast description/short_description
default: default string to display
delete_if_empty: true/false
use_last_as_default: true/false
check: checkbox
key: key to set
text: fixed label to display
default: ticked on/off
delete_if_empty: true/false
value_on: the value to set when checked (default is yes)
value_off: the value to set when unchecked (default is 'no')
role: type to specify possible roles in relations
key: the role name used in relation
text: fixed label to display
requisite: optional or required (default is optional)
count: how often can the role occur (if not given unlimited number is assumed)
type: the data types - way,node,relation,closedway (separated by comma)
For external files the presets should have following elements:
- author the author of the preset
- version a version number of some sort (e.g. creation date)
- description what is your preset meant to be
- shortdescription very short description
- link a link to a helpful website (optional)
- The fields description, shortdescription and link may also be
localized (e.g. de.link)
See also http://josm.openstreetmap.de/wiki/TaggingPresets.
The fields name, text, display_values may also be localized
(e.g. de.name).
When translations of equal words but different meanings may conflict,
a translation
context should be specified. Use name_context, text_context or
values_context
for this. The context should be a meaningful short description to help
translators.
In JOSM internally all name, text and display_values are translated when
no specific translation has
