As we've mentioned multiple times over the last months, the LWG decided
last year to consolidate all attribution guidance in to one document and
address some of the use cases that have become common over the last 7
years that previously had none. Particularly in the light of the
parallel
On Friday 09 August 2019, Richard Fairhurst wrote:
> > It does not in any way address the problem of second rate
> > attribution (i.e. someone else - usually the service provider of
> > the map service or the media outlet publishing the map) is being
> > attributed more prominently than OSM.
>
>
On Friday 09 August 2019, Jóhannes Birgir Jensson wrote:
> I think we move in different mapper communities as "mapping for the
> reward of being recognized by external data users" has never even
> been on my list, or of those mappers I know, of reasons for why we
> map.
Please don't twist my
On Fri, 9 Aug 2019 at 08:41, Simon Poole wrote:
> to consolidate all attribution guidance in to one document
Some thoughts:
> www.openstreetmap.org/copyright
openstreetmap.org/copyright (without "www") works, and should be
preferred (several occurrences).
> Our requested attribution is "©
Hi,
I wonder if we could perhaps get rid of the "Contributors" mention
altogether.
The term "OpenStreetMap Contributors" is the unwieldy; it just sounds
strange to say "this is a map made by OpenStreetMap contributors" when
what we really want to say is "this is OpenStreetMap". When translated
On Fri, Aug 9, 2019 at 7:35 AM Frederik Ramm wrote:
> Hi,
>
> I wonder if we could perhaps get rid of the "Contributors" mention
> altogether.
>
I agree, I've often felt that the OpenStreetMap Contributors was unwieldy.
If we agree to the change, I imagine that OpenStreetMap would need to be
I concur, this becomes long and unwieldy fast in my own language and to fully
capture it requires a full sentence, with a comma for clarity even.
Behind OpenStreetMap the brand we have contributors amongst others.
9. ágúst 2019 kl. 14:40, skrifaði "Frederik Ramm" :
> Hi,
>
> I wonder if we
SimonPoole wrote:
> the few things that are not nailed down belong to those that we
> would appreciate feedback on.
This is really good, and very much in accordance with both the text of the
ODbL and the long-standing precedents set by the osm.org/copyright page.
Thank you.
Two small wording
About the 50% exception. i recently had to be unpleasant with Fatmap
(their app and website https://fatmap.com/), after 2 months of zero
action from their side. Source
https://twitter.com/iamnunocaldeira/status/1136624467000602624 after my
message on the 3rd of August, they contacted me via
I am strongly against this in the current form because it addresses none
of the major issues about corporate attribution of OSM (or lack
thereof).
1) It does not in any way address the problem of second rate attribution
(i.e. someone else - usually the service provider of the map service or
Christoph Hormann wrote:
> It does not in any way address the problem of second rate attribution
> (i.e. someone else - usually the service provider of the map service
> or the media outlet publishing the map) is being attributed more
> prominently than OSM.
That is not something that the ODbL
I think we move in different mapper communities as "mapping for the reward of
being recognized by external data users" has never even been on my list, or of
those mappers I know, of reasons for why we map.
Of course everyones self-image is their own, so I don't know about your claim
of there
Hi Simon,
This guideline is a great piece of work, thanks a lot to all the participants.
Inevitably, this will be too much or not enough for anybody, however I find the
content reasonable and in line with what I understood from current written
expectations.
A few more mockups, notably for
Às 14:56 de 09/08/2019, Christoph Hormann escreveu:
On Friday 09 August 2019, Richard Fairhurst wrote:
It is a community guideline - a recommendation of the community on how
to work with OSM data to comply with the license. No data user has to
follow the guideline - the only binding document
Hi
Static Images.
"Static images should be generally attributed the same way as dynamic
images, " I agree & a way to enable users to easily add attribution
needs to be created. The Share>Image feature on the main page should
automatically image stamp the attribution into the corner. "images
Thank you for your work! I believe that clearly documenting our
expectations is a very important step towards solving the current
problems surrounding attribution. It will help well-intentioned data
users to avoid accidentally messing up OSM attribution, and it leaves
fewer excuses for the less
> Guidelines by the licensor
>
> On legal advice, *what a Licensor says carries weight with users of our
> data and, potentially, to a judge*. A court would make a final decision
> on the issue, however we hope these guidelines are helpful to *avoid *disputes
> arising in the first place and can
On Friday 09 August 2019, Dave F via talk wrote:
> Hi
>
> Static Images.
>
> "Static images should be generally attributed the same way as dynamic
> images, " I agree & a way to enable users to easily add attribution
> needs to be created. The Share>Image feature on the main page should
>
On Friday 09 August 2019, Kathleen Lu wrote:
> You are right that we hope to avoid disputes by setting out
> reasonable guidelines, but if OSMF sets out guidelines that are
> unreasonable and not tied to the language of the licence, then no
> one, either users of the data or judges, will listen to
* What's the guidance on scenarios where software does not ship with OSM
data, and does not display online maps, but e.g. allows downloading map
data for offline use? Would it be acceptable to make the license
information part of the download process, or is it still required that
attribution is
So you are saying that when we switched from CC to ODbL, the bellow
quote was not true?
Both licenses are “By Attribution” and “Share Alike”.
https://wiki.osmfoundation.org/wiki/Licence/Historic/We_Are_Changing_The_License#What_are_the_main_differences_between_the_old_and_the_new_license.3F
I agree, this would be more snappy and more international. It woulrd not be
necessary to translate the attribution for various languages. By shortening
the attribution, their would be less excuses to not attribute on the map.
Pierre
Le vendredi 9 août 2019 10 h 40 min 27 s UTC−4,
Where in CC-BY-SA's license does it say that attribution must be on top of
an image or that no interaction is allowed???
On Fri, Aug 9, 2019 at 10:17 AM Nuno Caldeira
wrote:
> So you are saying that when we switched from CC to ODbL, the bellow quote
> was not true?
>
> Both licenses are “By
I disagree that there is no harm. The credibility point goes both ways.
While no one could sue OSMF for recommending something that is not required
by the license, OSMF would lose the trust of data users, mappers, and any
adjudicative tribunals.
And it would be misleading and harmful to anyone who
sent from a phone
> On 9. Aug 2019, at 14:19, Richard Fairhurst wrote:
>
> But you can't start requiring that "the OpenStreetMap attribution needs to
> be at least on the same level of
> prominence and visibility as... other data providers, designers, service
> providers or publicists",
Where in CC-BY-SA's license does it say that attribution must be on
top of an image
As written on CC-BY-SA
*Attribution*.
If You Share the Licensed Material (including in modified form), You must:
retain the following if it is supplied by the Licensor with the
Licensed Material:
1.
On Friday 09 August 2019, Kathleen Lu wrote:
> I disagree that there is no harm. [...]
Not sure if you noticed but my argument was the inherent asymmetry of
the situation when creating a guideline with recommendations. If there
is harm like "hurt feelings" from erring on the side of caution in
On Friday 09 August 2019, Kathleen Lu wrote:
>
> "reasonably calculated" means "reasonable." [...]
I am sorry but this is completely distorting the ODbL.
"reasonably calculated to make any Person that uses, ... aware" means
that the calculation on what effect the specific form of attribution
Your complaint about LiveStream is that their attribution is
completely missing, not that it's behind a click. I agree that it's
missing and that it should be somewhere. It's not clear at all where
they are getting their data (the rendering looks like Leaflet). If
they are looking into it,
On Friday 09 August 2019, Richard Fairhurst wrote:
>
> These new guidelines say that, for 480px+ screens, hiding OSM
> attribution behind a click is not acceptable.
Unless "OpenStreetMap data accounts for a minority (less than 50%) part
of the visible map rendering" - which is the case for
On Friday 09 August 2019, Richard Fairhurst wrote:
>
> For better understanding, you claimed "this looks pretty much like
> being written by corporate representatives", and I pointed out that
> one of the items in point 2 that you object to was written by me in
> 2012, so not a corporate
Your complaint about LiveStream is that their attribution is completely
missing, not that it's behind a click. I agree that it's missing and that
it should be somewhere. It's not clear at all where they are getting their
data (the rendering looks like Leaflet). If they are looking into it, then
. Plus, if anyone went to court trying to enforce something that OSMF
recommended that was outside the licence, they would lose, and perhaps
be forced by the court to pay attorney's fees.
Maybe individual contributors might feel "scary" of the attorney fees,
but probably not these
On Fri, Aug 9, 2019 at 3:27 PM Nuno Caldeira
wrote:
> Your complaint about LiveStream is that their attribution is completely
> missing, not that it's behind a click. I agree that it's missing and that
> it should be somewhere. It's not clear at all where they are getting their
> data (the
Martin Koppenhoefer wrote:
If you look at Apple Maps, and for example zoomed into some place in Denmark,
there is an i-button which brings you to an overlay which has a TomTom logo and
a link „and others“
while in Denmark the data is from OpenStreetMap. IMHO this second rate
attribution
Christoph Hormann wrote:
> Just for understanding what second rate attribution is: For example
> the map on the bottom right of:
> https://www.zeit.de/politik/2019-07/strasse-von-hormus-bundesregierung-marinemission-usa-iran
> printing a prominent "Zeit Online" below the map (self attribution)
The OSM Foundation is trying to find out more about the OSM community/ies!
Forwarded Message
Subject: Survey on global and local communities in OpenStreetMap
Date: Wed, 7 Aug 2019 13:59:34 +0300
From: Dorothea Kazazi
To: t...@openstreetmap.org
Hello,
The following survey on
Hi Rob,
I'd be happy to
Cheers
Dan
Op do 8 aug. 2019 om 23:08 schreef Rob Nickerson :
>
> Hi all,
>
> I've been a bit slow to the solar mapping project but have now picked up the
> baton for outreach. If we can get some press lined up do we have any
> volunteers to speak with them?
>
>
Hej. Det är dessvärre inte så enkelt att man bara kan plocka data från
olika datakällor. Licensen på den öppna datan måste vara kompatibel med
OSMs licens (ODBL) vilket i praktikten innebär CC0 eller ODBL. I en del
fall har även data "skänkts" till OSM, men det innebär ju i praktiken
att den
Oui c'est vrai qu'il y a aussi cette situation faite avec JOSM. C'est le
cas sur les autres? Il me semble que ID refuse la fusion en cas de conflit
de clé.
Le ven. 9 août 2019 à 10:48, JB a écrit :
> Le 09/08/2019 à 09:59, Francois Gouget a écrit :
> > maxspeed=50;80
> Souvent le résultat du «
Hallo Nora,
a) Auf welche Art und Weise könnte man die vorliegenden Daten am
zeiteffizientesten UND im Sinne von OSM zielführendsten einarbeiten?
Import von shp-Dateien (??), manuelles Einarbeiten?
Manuell, da ein Import bestehende Daten doppeln würde.
b) Welches Browser-Format (zb JOSM?)
Might be interesting
Forwarded Message
Subject:International Day of the World's Indigenous Peoples
Date: Thu, 8 Aug 2019 22:31:07 + (UTC)
From: Suchith Anand via talk
Reply-To: Suchith Anand
To: Osm-talk
The International Day of the World’s
Le 09/08/2019 à 09:59, Francois Gouget a écrit :
maxspeed=50;80
Souvent le résultat du « merge » de deux highway avec des maxspeed
différents, rassemblés par défaut dans la clé finale avec un
point-virgule en séparateur.
___
Talk-fr mailing list
On Thu, 8 Aug 2019 at 23:06, Neil Matthews wrote:
> In light of some recent edits in South Gloucestershire -- is it ok to
> import unsurveyed footpaths based simply on rowmaps data?
Based on the licensing information at
http://www.rowmaps.com/datasets/SG/ my view would be "no". According
to
Potenciāli interesanti - jauno "attribution" noteikumu darba versija.
Noteiks, kā jānorāda autortiesības.
Neizdevās pārsūtīt normāli, skat. pielikumu.
Forwarded Message
Subject: [Osmf-talk] Attribution guideline status update
Date: Fri, 9 Aug 2019 09:41:25 +0200
From: Simon
On Thu, 8 Aug 2019, Jérôme Seigneuret wrote:
[...]
> vous pensez quoi de ça :
>
> note=#highwayspeedconflict + maxspeed=50;80 +
> source:maxspeed=FR:urban;FR:rural
maxspeed=50;80 Osmose n'aime pas : pas une valeur numérique.
Il y a déjà un certain nombre d'erreurs à cause de champs 50;90 dont
Hi Edwin, thanks a lot for that. Great to hear from you & Dominic that
there is energy for FOSS4G & SotM in the Pacific :)
One of the critical components for conference success is a group of
energetic people who will lead the way. At this stage we're looking for
those people, willing to do the
Hi,
I'm in agreement with Rob re:licensing. The good news is that lhe OS is now
fine with the OSM-compliant Open Government Licence (version 3), so if you
ask the council for an updated dataset they will be able to release the
data under the appropriate licence. [I was actually in the process of
Hallo Nora,
etwas Sorgen bereitet mir noch diese Aussage:
> Die shp-File selbst dürfen wir nur Projekt-Intern benutzen, also nicht an 3.
weitergeben.
Hier muss unbedingt geklärt werden, ob der Rechteinhaber der Dateien der Ableitung von Inhalten nach
OpenStreetMap zustimmt, in einem solchen
Le 08.08.19 à 17:06, Jérôme Seigneuret a écrit :
> Bref pour le moment je vais faire des notes:
j'ai n'ai pas compris quel problème exact tu essayes de résoudre
mais faire des notes pour remplacer une analyse QA me semble une
mauvaise idée.
autre exemple : ceux qui mettent des fixme=tel tag est
La plupart du temps ce sont des conflits de vitesses. L'autre possibilité
c'est des cas de vitesse et de position de voie en lien avec le modèle
lanes:*
Le ven. 9 août 2019 à 10:00, Francois Gouget a écrit :
> On Thu, 8 Aug 2019, Jérôme Seigneuret wrote:
> [...]
> > vous pensez quoi de ça :
> >
Hallo,
ich bin neu bei OSM und Teil eines Teams des Instituts IMobiS der
Universität Duisburg-Essen. Uns liegen Shape-Dateien zu den
Betriebswegen in der Emscher Region (entlang des Flusses Emscher,
Ruhrgebiet) vor, die wir gerne in OSM eintragen wollen. Für unsere
Zwecke brauchen wir nur die
Ok je veux bien pour l'histoire du maxspeed type. C'est juste une habitude
Ce que je souhaite faire c'est clairement identifier les conflits de
vitesse faute de signalisation clair. L'analyse QA ne te permettra pas
d'identifier les conflits d'où la double vitesse dans maxspeed.
En effet c'est une
Eine interessante, von vielen unterschaetzte, Methode um JOSM-Newcomer beim
Start zu helfen ist editing im screen-sharing Betrieb z.B. mit Skype.
Funktioniert unabhaengig von der geografischen Distanz. Bedingung ist
natuerlich eine gute Internet-Verbindung.
Volker (der zweite - ich sitze in
C'est un peu trop loin pour que je fasse un déplacement par là, mais en
croisant toutes les sources disponibles, dont le forum sarah, le
département, la site de la commune, je ne trouve absolument rien. Ca
reste un projet, c'est tout.
Je pense qu'il faut faire un/des revert
Stf
Le 09/08/2019
Le plus concret que j'ai trouvé, c'est un avis d'enquête pour
expropriations, qui courait jusqu'en mars 2019.
https://www.notre-territoire.com/enquete/111771
Le 09/08/2019 à 14:59, Stéphane Péneau a écrit :
C'est un peu trop loin pour que je fasse un déplacement par là, mais
en croisant toutes
Hello tous,
Je viens de terminer la traduction en FR des pages :
https://wiki.openstreetmap.org/wiki/Key:drinking_water
https://wiki.openstreetmap.org/wiki/FR:Espaces_de_noms
Si certains veulent faire une relecture, car mon prof de langue a encore
beaucoup à apprendre, il s'appelle G...gle
oh puis il à fait ça avec une tablette?
https://www.openstreetmap.org/changeset/72531797#map=18/47.27546/-1.78570
Le ven. 9 août 2019 à 15:07, Stéphane Péneau a
écrit :
> Le plus concret que j'ai trouvé, c'est un avis d'enquête pour
> expropriations, qui courait jusqu'en mars 2019.
>
Hello,
DeepL est de bien meilleur conseil que gg.
HTH.
--
deuzeffe
On 09/08/2019 15:24, gnrc69 via Talk-fr wrote:
Hello tous,
Je viens de terminer la traduction en FR des pages :
https://wiki.openstreetmap.org/wiki/Key:drinking_water
https://wiki.openstreetmap.org/wiki/FR:Espaces_de_noms
Mon avis correspond assez bien à ton résumé.
J'ajouterai qu'on n'utilise pas track pour :
La voie qui permet d'accéder à des habitations
La voie dans la parcelle privée qui permet au proprio d'accéder à son
garage derrière la maison
La voie principale qui permet d'accéder à l'entrée d'une
Hi Neil.
I contacted SG recently regarding as updated dataset under OGL v3. A
Nicola Chidley from SG said I should use their set on rowmaps. An IT
officer also said they were given OS copyright exemption in 2016.
As it's designated paths being added other tags as well as highway
should be
Höjdkurvorna finns om du byter till cykellagret. Dessa kurvor är hämtade från
en annan källa och finns inte i osm-databasen. Vad jag vet finns ingen aktiv
datamodell för höjdkurvor på osm, och data går därmed inte heller att importera
med någon form av etablerade taggar.
/Andreas
Skickat från
On Thu, Aug 08, 2019 at 11:05:44PM +0100, Neil Matthews wrote:
> In light of some recent edits in South Gloucestershire -- is it ok to
> import unsurveyed footpaths based simply on rowmaps data?
Apart from the licensing issue, many of these sorts of edits are simply
wrong. I had to correct
Und vor allem vorher klären, ob die Quellen OSM kompatibel sind.
Am 09.08.2019 um 11:27 schrieb chris66 via Talk-de:
> Hallo Nora,
>
>> a) Auf welche Art und Weise könnte man die vorliegenden Daten am
>> zeiteffizientesten UND im Sinne von OSM zielführendsten einarbeiten?
>> Import von
Bonjour
Si des géographiquement-proche (Saint-Étienne-de-Montluc, à l'ouest de
Nantes sur la D17)pouvait vérifier les travaux de cet utilisateur :
https://www.openstreetmap.org/user/Wood587
Ses contributions me semble plus que douteuses
Cordialement
--
David Crochet
こんにちは、奈良の石川です。
On Thursday, August 8, 2019, 4:06:25 PM GMT+9, ISHIKAWA Takayuki (Talk-ja 経由)
wrote:
>(2) 今回の議論に直接含まれてはいないのですが、そもそも「用例」という語がまずいと思います。
すみません、「ではどう表記すればよいか」という提案が抜け落ちておりました。「出典」「資料」「情報源」等のどれかでよいと思います。
一応解説します。例えば、F1 という地物には T1, T2, T3, …という tags があり、それぞれ R1a, R1b; R2a, R2b, R2c;
Hallo,
ich ergänze mal hier:
Am 09.08.2019 um 11:27 schrieb chris66 via Talk-de:
> Hallo Nora,
>
>> a) Auf welche Art und Weise könnte man die vorliegenden Daten am
>> zeiteffizientesten UND im Sinne von OSM zielführendsten einarbeiten?
>> Import von shp-Dateien (??), manuelles Einarbeiten?
>
Le 8 août 2019, marc marc a écrit :
> track à mes yeux est hors "réseau routier", c'est un chemin agricole,
> forestrier, agriculture, loisir (parc). c'est typiquement le chemin que
> vous ne prenez jamais en voiture malgré que la largeur le permet
Que vous ne prenez presque jamais parce qu'il
Le 08/08/2019 à 14:43, Jérôme Seigneuret a écrit :
@Stf
Pour le cas du chemin rural oui je garderai que la D56.
Je ne suis pas de ton avis. https://www.openstreetmap.org/way/112796056
me semble très bien en unclassified.
pour l'exemple demandé. J'ai encore du travail par ici.
There are certainly places where the rights-of-way as signed don't match what
appears on e.g. OS Landranger - I was in one south of York just a couple of
days ago. There in fact the OS data (including OS Opendata / older OS maps
which have been traced into OSM) doesn't match what's on the
Le 08/08/2019 à 15:53, pepilepi...@ovh.fr a écrit :
Le 08/08/2019 à 13:49, Stéphane Péneau a écrit :
Le gros problème de toute cette discussion, c'est qu'il n'y a pas
d'exemple, de lien vers un highway d'Osm.
Non.
LE gros problème, c'est que nous discutons entre français, avec nos
habitudes
C'est maintenant plus clair et officiel, avec une page de redirection et
une annonce :
https://www.itoworld.com/ito-map-announcement/
On Mon, 29 Jul 2019 at 13:09, Eric SIBERT wrote:
> Le 29/07/2019 à 10:45, Christian Quest a écrit :
> > HTTPS même 503 pour moi... le service ne semble plus
C'est très drole : ils ont inversé les liens :-)
- Mail original -
De: "althio"
À: "Discussions sur OSM en français"
Envoyé: Vendredi 9 Août 2019 14:15:37
Objet: Re: [OSM-talk-fr] Carte des limites de vitesseq
C'est maintenant plus clair et officiel, avec une page de redirection et
https://wiki.openstreetmap.org/wiki/Contributors#Public_Rights_of_Way_Data_from_local_councils
. While there's nothing listed there, it's definitely not ok to use
the data in OSM.
Rubbish.
Just because one person isn't aware of a fact, it doesn't make it untrue.
No one person has authority
Hallo,
morgen wird vielerorts
https://wiki.openstreetmap.org/wiki/OpenStreetMap_15th_Anniversary_Birthday_party
gefeiert.
Hier bei uns in Karlsruhe treffen wir uns um 10:00 auf einen Sekt im
Geofabrik-Büro, dann wollen wir mappen gehen, ab 16:00 gibt es dann
(aller Voraussicht nach)
sent from a phone
> On 9. Aug 2019, at 12:06, Martin Scholtes wrote:
>
> kann mittels access=no oder anderen Werten eine
> Zugangsbeschränkung verhängt werden.
besser ist private bei Wegen, die begangen werden können, aber nicht durch die
Allgemeinheit, Betriebswege sind meistens
Zdravo,
Ali kdo pozna tega (https://www.openstreetmap.org/user/kartog) "genija"?
Zgleda da je več ali manj naključno dvignil rang poti. Marsikje je
traktorske vlake, ki niso prevozne niti s terenskimi vozili,
klasificiral kot normalne ceste.
Mislim da bi bilo najbolje preprosto revertati
Le 09/08/2019 à 16:06, deuzeffe a écrit :
Hello,
DeepL est de bien meilleur conseil que gg.
HTH.
+1 je l'utilise quand j'ai des trous pour le wiki de josm
___
Talk-fr mailing list
Talk-fr@openstreetmap.org
こんにちはxyzxyz2です。
国土地理院地図（'https://cyberjapandata.gsi.go.jp/xyz/{std/pale}/{z}/{x}/{y}.pnd'
など）に顕著なずれも見られるようです。これに従って編集作業したと思われる道路が現在の OSM にも見られます（例えば、経緯度 132.8830 35.3861
付近）。
また、新聞報道でも、「関門トンネルも位置誤り国土地理院地図50メートルずれ」日本経済新聞 2019/8/2
したがって国土地理院地図だけではなく複数のソースを参考にして編集作業を加える必要がありそうです。
On Fri, 2 Aug 2019, Martin - CycleStreets wrote:
I've sent a follow-up e-mail to the OSMF Licensing Working Group, which
compiles all the various statements from Transport for London, and
includes various e-mails where these statements were originally made, so
that the LWG will hopefully be
Tack Andreas, det var bra att veta om höjdkurvorna. Där jag har tittat i
OSM har de 20 m mellanrum, i terrängkartan finns de med 5 m mellanrum
och de stämmer bättre med verkligheten på de ställen jag har tittat. Jag
vet inte varifrån höjdkurvorna i OSM kommer.
Riksantikvarieämbetets öppna
Le 09/08/2019 à 16:06, deuzeffe a écrit :
> Hello,
>
> DeepL est de bien meilleur conseil que gg.
+ 1 ! ! ! (https://www.deepl.com/translator)
JP
>
> HTH.
--
Si ma réponse n'a pas résolu ton problème, c'est que tu
Blaž Lorger je 9.8.2019 ob 18:34 napisal:
Zdravo,
Ali kdo pozna tega (https://www.openstreetmap.org/user/kartog) "genija"?
Zgleda da je več ali manj naključno dvignil rang poti. Marsikje je
traktorske vlake, ki niso prevozne niti s terenskimi vozili,
klasificiral kot normalne ceste.
Mislim
Hi Jeffrey,
I don't know much about nominatim technology, but `place=state` is wrong in
Japan. We don't use it for now.
See the addressing scheme in Japan.
https://wiki.openstreetmap.org/wiki/Japan_tagging
In this case
province=京都府
region=近畿地方
is right.
(Note: region=近畿地方 is not a part of
84 matches
Mail list logo
