On 2012-09-19 05:36, Willi wrote:
I really don't like the attitude expressed by several people here in
response to this subject and which is already contained in the
subject
itself OSMF/DWG governance.
Governance. There's no governance. DWG is a group and everybody is
free to
join it. The
Pieren wrote:
The one who never made a mistake in JOSM can be the first to
throw a stone.
*waves*
cheers
Richard
--
View this message in context:
http://gis.19327.n5.nabble.com/Import-guidelines-OSMF-DWG-governance-tp5725810p5726047.html
Sent from the General Discussion mailing list
On 09/19/2012 01:58 AM, Marc Sibert wrote:
That's why we need of help of the machines... asta la vista, baby !
No, that is why you need more contributors. Preferably those who know
what is actually there in reality. Not people who only remotely map
stuff from secondary sources.
--
---
m.v.g.,
Lucas Nussbaum wrote:
Alternatively, if this was software development, what should probably be
done is:
1. commit the raw conversion for the vectorized cadastre, before the
cleanup
2. clean up and upload modified buildings after the cleanup
3. add roads, etc. and upload
With the growing
Pieren wrote:
Finally, he decided that the best
solution to clean-up the mess was to delete the previous buildings
dataset and import the new one. But again, his first intention was to
upload the delta only.
I will be the first to admit to being a little lax in adding comments to my
commits,
complaining about the quality of his imports.
The user was contacted, he didn't react as I understood. There for he
was short time blocked. That's a very fair and fine reaction from
the DWG. The user was not banned or something, just blocked for short
time to gain his attention.
And: why
Hi,
On 09/19/2012 12:38 AM, Christian Quest wrote:
For me a mandatory rule on which someone bases a block decision must be
something decided publicly and shared with the community, and clearly
published/announced... and none of these has taken place here.
Are you saying that we should have
guig...@free.fr wrote:
Please show me that I'm making jugement mistake, and show me that our
work, after beeing uncertain by licence, isn't threatened by
centralistic, autoritative, english only person who can set live or dead by
non community based decisions.
There is a lot of good support
2012/9/19 Richard Fairhurst rich...@systemed.net
Pieren wrote:
The one who never made a mistake in JOSM can be the first to
throw a stone.
*waves*
cheers
Richard
Richard !
As you're joining this topic, can you explain why you changed the
guidelines in the wiki to make the dedicated
2012/9/19 Frederik Ramm frede...@remote.org
Hi,
On 09/19/2012 12:38 AM, Christian Quest wrote:
For me a mandatory rule on which someone bases a block decision must be
something decided publicly and shared with the community, and clearly
published/announced... and none of these has taken
On Wed, Sep 19, 2012 at 9:37 AM, Frederik Ramm frede...@remote.org wrote:
Are you saying that we should have had a vote on the wiki, or what? Who
would have been eligible to vote? And are you at the same time saying that
changing a policy on the wiki is not clearly published?
To progress a
Christian Quest wrote:
As you're joining this topic, can you explain why you changed
the guidelines in the wiki to make the dedicated account a
requirement and not a recommendation anymore ?
As a few people have already said (Michael, Frederik, Simon etc.) this was
basically codifying
On 2012-09-19 12:04, Richard Fairhurst wrote:
It's also been observed, quite rightly, that the nuances of British
English
- which tends to gently suggest when other languages would say you
MUST!!!?!1 - are not easily appreciated by non-native speakers. We
had a
For this I always use the
On 19/09/2012 12:04, Richard Fairhurst wrote:
[..]
Thanks for the level-headed recapitulation - looks like we are moving
forward.
Firstly, the status of the import guidelines needs to become less ambiguous.
At present we have three largely overlapping policies ('Mechanical Edit
Policy',
Pieren wrote:
But let the local community decides when and who. And for that, we
need to contact people in their speaking language, not in English,
either through a local representative or e.g. standard messages
previously translated. Then check with the local community if or what
goes wrong
On 19/09/2012 12:17, Maarten Deen wrote:
On 2012-09-19 12:04, Richard Fairhurst wrote:
It's also been observed, quite rightly, that the nuances of British
English
- which tends to gently suggest when other languages would say you
MUST!!!?!1 - are not easily appreciated by non-native speakers.
On 19/09/12 at 12:17 +0200, Maarten Deen wrote:
On 2012-09-19 12:04, Richard Fairhurst wrote:
It's also been observed, quite rightly, that the nuances of
British English
- which tends to gently suggest when other languages would say you
MUST!!!?!1 - are not easily appreciated by non-native
2012/9/18 Jean-Marc Liotier j...@liotier.org:
On 09/18/2012 05:42 PM, Simon Poole wrote:
The French cadastre imports are, as you know, a rather controversial
subject. In my opinion it is a dataset that doesn't actually increase
the usefulness of the OSM dataset for most users (building
Martin Koppenhoefer wrote:
The French cadastre imports are, as you know, a rather controversial
subject. In my opinion it is a dataset that doesn't actually increase
the usefulness of the OSM dataset for most users (building outlines
without addresses just don't really help with anything)
2012/9/19 Jean-Marc Liotier j...@liotier.org:
the cadastre integration process represents such an amount of manual
processing that some of those who did it took understandable personal
offense that their work could be seen as just another botched mass import.
If their input can be taken into
On 19/09/2012 15:58, Martin Koppenhoefer wrote:
It seems that you generally apply the source-tag to the osm object
instead of the changeset comment, but I'd propose to do it the other
way round. There are already tens of millions of objects in the db
with related source-tags
2012/9/19 Pieren pier...@gmail.com:
The size of the whole French cadastre dataset is huge. We could upload
it in a single mass import with a bot using a seperate user account as
we did for the Corine Land Cover. We could follow 100% of the import
guidelines. Trust me, we have all the
Hi,
I've read the rather long thread Import guidelines OSMF/DWG governance and
I'd like to propose a change on the wiki page :
http://wiki.openstreetmap.org/wiki/Import/Guidelines
(you can also read and comment on my proposal change on the talk page if you
wish to keep this list trafic lower)
Le 19/09/2012 16:23, Martin Koppenhoefer a écrit :
2012/9/19 Pieren pier...@gmail.com:
The size of the whole French cadastre dataset is huge. We could upload
it in a single mass import with a bot using a seperate user account as
we did for the Corine Land Cover. We could follow 100% of the
I believe that dedicated accounts are generally better for imports
than using mixed ones which are also used for original data. This
really helps a lot in sorting data according to its intellectual
properties holders. The only exception I could possibly see is data
that doesn't come with strings
Martin Koppenhoefer wrote:
I believe that dedicated accounts are generally better for
imports than using mixed ones which are also used for
original data. This really helps a lot in sorting data
according to its intellectual properties holders.
Yes, absolutely.
The really obvious example
2012/9/19 Vincent Pottier vpott...@gmail.com:
Les données du cadastre ne peuvent former à elles seules les données
OSM. Ce qui interdit un import massif, direct et automatique
It means : You cannot make a map with only data from cadastre. You can only
mix them with other data.
Yes, and the
On Wed, Sep 19, 2012 at 5:41 PM, Richard Fairhurst rich...@systemed.net wrote:
I would caution against repeating the same mistake.
I thought that such issue is not possible anymore with ODbl.
Pieren
___
talk mailing list
talk@openstreetmap.org
Pieren wrote:
I thought that such issue is not possible anymore with ODbl.
No, the Contributor Terms simply say You are indicating that, as far as You
know, You have the right to authorize OSMF to use and distribute those
Contents under our current licence terms (1a).
If the licence changes to
On Wed, Sep 19, 2012 at 6:06 PM, Richard Fairhurst rich...@systemed.net wrote:
Pieren wrote:
If the licence changes to one which is incompatible with the import, OSMF
may remove Your contributions from the Project (1b)... and that rather
requires being able to identify what these incompatible
On 19/09/2012 17:26, Pieren wrote:
So, theoretically, we might have the same issue when tracing from Bing
for instance. Should we use a different account for Bing imagery
contributions as well, just in case we move later to a licence
incompatible with Bing ?
No, because tracing over Bing
2012/9/19 Pieren pier...@gmail.com:
So, theoretically, we might have the same issue when tracing from Bing
for instance.
The only obligation when creating data with the help of Bing aerial
imagery is that is has to be a non-commercial editor and that you have
to contribute back to
The really obvious example of this is the Polish UMP data, which was
licensed CC-BY-SA and could not be kept post-licence change. If dedicated
accounts had been used, removing this data would have been relatively easy;
in reality, it has been (and continues to be) a nightmare. :(
Although I
On Wed, Sep 19, 2012 at 12:06 PM, Richard Fairhurst
rich...@systemed.net wrote:
Pieren wrote:
I thought that such issue is not possible anymore with ODbl.
No, the Contributor Terms simply say You are indicating that, as far as You
know, You have the right to authorize OSMF to use and
On 19/09/12 at 16:24 +0200, sly (sylvain letuffe) wrote:
Hi,
I've read the rather long thread Import guidelines OSMF/DWG governance
and
^^
Note that the use of the term guidelines is problematic by itself.
Either they are *guidelines*,
On Sep 19, 2012, at 12:06 PM, Richard Fairhurst rich...@systemed.net wrote:
Pieren wrote:
I thought that such issue is not possible anymore with ODbl.
No, the Contributor Terms simply say You are indicating that, as far as You
know, You have the right to authorize OSMF to use and
On Wed, Sep 19, 2012 at 6:41 PM, Martin Koppenhoefer
dieterdre...@gmail.com wrote:
The only obligation when creating data with the help of Bing aerial
imagery is that is has to be a non-commercial editor and that you have
to contribute back to openstreetmaps.org
The only obligation to use
Richard Weait wrote:
So use a separate account for imports. And follow the other
guidelines as well. The guidelines make for a better OSM, even if it
is slightly less convenient.
I suppose if a mapper is ONLY using import data then they only need one account?
As long as it is flagged as
On Wed, Sep 19, 2012 at 6:51 PM, Richard Weait rich...@weait.com wrote:
requires being able to identify what these incompatible contributions are.
:
What has also happened, when cleaning up the inappropriate import, is
that the user mixed the import with their regular account.
I agree with
Before we go further with policy edits, perhaps we should make sure that
everyone understands the goals and that there is a consensus about
them... That will make the resulting rules or guidelines more acceptable.
Let's focus on the item that triggered the current debate : the
requirement for a
Have such schemes been proposed before ?
Not sure about that.
But this is logical and feasible _if_ all added/edited objects in a changeset
had/have the same source.
I can only say for sure about my own mapping: It would be almost always
impossible for me -- except when tracing in areas I've
On 20 September 2012 00:41, Richard Fairhurst rich...@systemed.net wrote:
Martin Koppenhoefer wrote:
I believe that dedicated accounts are generally better for
imports than using mixed ones which are also used for
original data. This really helps a lot in sorting data
according to its
On 19.09.2012 09:05, guig...@free.fr wrote:
Perhaps, because the user doesn't understand English
please use google translate or any other translating tool available on
the web or use a printed dictionary or ...
Best regards,
Michael.
___
On 19.09.2012 12:04, Richard Fairhurst wrote:
As a few people have already said
[...]
cheers
Richard
applause for this comment! And to clarify it already now: there is no
irony behind this statement.
Best regards,
Michael.
___
talk mailing list
th == Tom Hughes t...@compton.nu writes:
ecm account block. But historical information such as the number of
ecm blocks imposed per week are missing AFAICT (allows people to
ecm monitor for admin abuse).
th It should be pretty obvious from browsing the block list:
th
th
On 19.09.2012 11:22, Christian Quest wrote:
We're voting proposed tag scheme.
... or not. Frequently nowadays a new value or scheme is invented w/o
voting. No statement by myself whether I think this is good process or
not...
So these hard rules are coming from nowhere ? There's no process
Sending to imports@ and cc'ing talk@ as that's more widely read than the
wiki talk pages.
From: sly (sylvain letuffe) [mailto:li...@letuffe.org]
Subject: Re: [OSM-talk] Import guidelines proposal update
Or, to make it even clearer, can I commit my change to the wiki without
starting an edit
On Wed, Sep 19, 2012 at 1:57 PM, Jean-Marc Liotier j...@liotier.org wrote:
Before we go further with policy edits, perhaps we should make sure that
everyone understands the goals and that there is a consensus about
them... That will make the resulting rules or guidelines more acceptable.
Since
On 19.09.2012 17:03, Martin Koppenhoefer wrote:
I believe that dedicated accounts are generally better for imports
a very clear +1from my side.
Best regards,
Michael.
___
talk mailing list
talk@openstreetmap.org
On 19.09.2012 18:51, Richard Weait wrote:
More likely, and more often, what happens is that a well intentioned
mapper uses a source for which he believes he has permission.
Imports, then finds out that he didn't have (sufficient) permission
for the current license.
This has happened many times.
On 19.09.2012 18:42, sly (sylvain letuffe) wrote:
Although I agree we shouldn't forget the past to avoid repeating the same
mistakes but since every cases beeing different, I'm proposing to let local
communities decide what they think is good for them.
But only if it is not completely opposed to
rw == Richard Weait rich...@weait.com writes:
rw the facts at hand. A group of importers decided that they weren't
rw going to follow the guidelines. Then one failed to respond when
rw approached about a specific guideline. And now a group is upset to
rw find that their
Hi,
Le 19/09/2012 22:55, Richard Weait a écrit :
- Cadastre is not an import. Cadastre is an import. Could you do
the same thing if there were no Cadastre to import? No, you couldn't.
Cadastre is an import.
Cadastre is sometimes an import, sometimes not. Using the same data
source, you
On 19.09.2012 23:45, Vincent de Chateau-Thierry wrote:
The only criteria for removing French Cadastre data will be the value
of the source tag.
That's a bad idea: if someone for what ever reason just decides to
remove (or change) the source=cadastre tag of a object (and don't
change anything
On Wed, Sep 19, 2012 at 10:55 PM, Richard Weait rich...@weait.com wrote:
Since you[1] are trying to revise guidelines that are found to be
acceptable across the community
Could you provide evidences about this ? Since the vast majority of
the community does not care about import guidelines, I
On Wed, Sep 19, 2012 at 10:49 PM, Paul Norman penor...@mac.com wrote:
There definitely is not general agreement at this time that this passage
should be changed.
Could you please point out in archives (wiki or mailing list) where
the separate account became generaly agreed ? Or you can simply
Pieren pier...@gmail.com writes:
On Wed, Sep 19, 2012 at 10:55 PM, Richard Weait rich...@weait.com wrote:
Since you[1] are trying to revise guidelines that are found to be
acceptable across the community
Could you provide evidences about this ? Since the vast majority of
the community
- Original Message -
From: Lucas Nussbaum lu...@lucas-nussbaum.net
To: sly (sylvain letuffe) li...@letuffe.org
Cc: talk@openstreetmap.org
Sent: Wednesday, September 19, 2012 5:59 PM
Subject: Re: [OSM-talk] Import guidelines proposal update
On 19/09/12 at 16:24 +0200, sly (sylvain
On 9/19/2012 6:29 PM, Michael Kugelmann wrote:
Or to be more precise: you need to use a lot of effort and check all
versions of an object (this means: the whole planet) whether it once had
the source=cadastre tag. But thats a lot of work to do. Much (!) more
easy to identify all the object is if
From: Vincent de Chateau-Thierry [mailto:v...@laposte.net]
Subject: Re: [OSM-talk] Import guidelines proposal update
Hi,
Le 19/09/2012 22:55, Richard Weait a écrit :
- Cadastre is not an import. Cadastre is an import. Could you do
the same thing if there were no Cadastre to import?
Pieren writes:
Could you please point out in archives (wiki or mailing list) where
the separate account became generaly agreed ?
It's always been generally agreed upon as far as I know. You could
look at the wiki and see when the text was first edited to suggest a
separate account. I would do
On Wed, Sep 19, 2012 at 6:43 PM, Mike N nice...@att.net wrote:
On 9/19/2012 6:29 PM, Michael Kugelmann wrote:
Or to be more precise: you need to use a lot of effort and check all
versions of an object (this means: the whole planet) whether it once had
the source=cadastre tag. But thats a lot
En zouden die techneuten dat evt ook op het forum willen delen, of is dat
teveel gevraagd?
Zie http://forum.openstreetmap.org/viewtopic.php?pid=274222#p274222
ZMW schreef:
Is een een techneut die deze BAG data als transparant layer voor JOSM
beschikbaar kan stellen?
On Tuesday 18 September 2012 21:38:35 Wimmel wrote:
Mijn probleem was anders, namelijk twee verschillende soorten wegen,
gaan over hetzelfde stukje asfalt. De A18 (highway=motorway) en de
N317 (normaal highway=primary). Omdat de highway tag natuurlijk niet
aanpas, klopt de betekenis van de ref
On Tuesday 18 September 2012 21:38:35 Wimmel wrote:
Mijn probleem was anders, namelijk twee verschillende soorten wegen,
gaan over hetzelfde stukje asfalt. De A18 (highway=motorway) en de
N317 (normaal highway=primary). Omdat de highway tag natuurlijk niet
aanpas, klopt de betekenis van de ref
On 09/19/2012 04:35 PM, Ross Scanlon wrote:
They are not mini-roundabouts if you can not drive over them.
Look here:
http://wiki.openstreetmap.org/wiki/Tag:highway%3Dmini_roundabout
Also read the Australian Tagging Guidelines here:
FYI, Franc was kind enough to let me have a copy of his original Perl
import script. Email me if you want a copy. However, and I think Franc
would agree, I understand it has really been superceded by the
capabilities of ogr2osm. Emilie Laffray said to me in email, If it is
done properly
Hi all,
I want to draw attention to the correct tag for rest areas, namely
highway:rest_area
http://wiki.openstreetmap.org/wiki/Tag:highway%3Drest_area
Most I've seen have been tagged as amenity:parking and/or
tourism:camp_site. The camp_site tag is wildly misleading, as setting
up camp is
On 20/09/12 06:03, John Henderson wrote:
Hi all,
I want to draw attention to the correct tag for rest areas, namely
highway:rest_area
http://wiki.openstreetmap.org/wiki/Tag:highway%3Drest_area
Most I've seen have been tagged as amenity:parking and/or
tourism:camp_site. The camp_site
On 20/09/12 08:17, John Smith wrote:
The rest area to the south of Gympie allows camping for up to 48
hours or something like that, it's not the only one, but the one I
know off the top of my head.
I'm aware of a few of those free caravan/camping facilities, sometimes
provided by local
Unfortunately I've found that the ABS data that the data is not as good as
it ought to be. Many nodes that should be shared are not coincident and in
many cases a vertex node for one boundary has no corresponding node on the
straight through boundary. And in some cases the vertex node is not quite
something that will enable me to check my Garmin 62s' accuracy and give
the ability to align Bing when I find them on the ground providing that
they can be seen from Bing. Be great if they are in nice circles of
I doubt if you'll see them on bing as most survey points are way too small.
You'd
On 19/09/12 19:28, Michael James wrote:
On 09/19/2012 04:35 PM, Ross Scanlon wrote:
They are not mini-roundabouts if you can not drive over them.
Look here:
http://wiki.openstreetmap.org/wiki/Tag:highway%3Dmini_roundabout
Also read the Australian Tagging Guidelines here:
Arlindo e demais...
Geralmente fico só nos bizus na lista, mas não acho que seja o ideal
duplicar a informação, portanto, aqui vai uma sugestã:
Deixe que o IBGE se preocupe com o armazenamento dos dados por enquanto.
Abra o repositório no github e faça um link através da wiki do git. É menos
Criei o repositório no GitHub:
https://github.com/nighto/calibracao-mapas-ibge
Gerald (e demais), você pode colocar lá (ou me passar) os arquivos .cal
referente aos arquivos que você já fez?
[]s
2012/9/19 George Silva georger.si...@gmail.com
Arlindo e demais...
Geralmente fico só nos bizus
Hallo Tirkon,
*Wikimedia-Foundation* und *OSM-Foundation*
sind für mich /wesentlich/ eigenständige Organisationen.
Sie sollen m.E. nicht vermischt werden.
Und schon gar nicht nur deshalb, weil die OSMF (bisher - aber das ändert
sich ja gerade) wenig Inhalt, Prozess und Struktur zeigt.
Die
Hallo,
Am 18.09.2012 um 11:40 schrieb Lars Schimmer l.schim...@cgv.tugraz.at:
Dazu eine Anmerkung: das roof:levels tag ist ein wenig, hm, unschön.
Da das Gebäude (Keller, Kasten an sich) mit building:levels und
building:levels:underground getagt wird, aber das Dach plötzlich mit
roof:levels -
Moin ;-)
On 19.09.2012 08:45, Andreas Hubel wrote:
Am 18.09.2012 um 11:40 schrieb Lars Schimmer l.schim...@cgv.tugraz.at:
Dazu eine Anmerkung: das roof:levels tag ist ein wenig, hm, unschön.
Da das Gebäude (Keller, Kasten an sich) mit building:levels und
building:levels:underground getagt
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Moin!
Ich hader etwas mit einem geeignetem Tagging schema für Gebäude mit
Tiefgarage.
Situationen:
1. http://osm.org/go/0I5UUdblq-- das Gebäude mit Zielpunkt drinnen
Da ist unter der gesamten Fläche eine Tiefgarage, so auch gestern
eingetragen, mit
Hallo Ronnie,
Am Dienstag, 18. September 2012, 14:46:21 schrieb Ronnie Soak:
Das erste Proposal zum Thema extended conditions das mir (von den
Tücken der englischen Sprache mal abgesehen) intuitiv genug für den
Otto-Normalnutzer scheint und doch auch
verzwickte Fälle noch einigermaßen
Viel gravierender ist, dass das Schema für Mapper zumindest in den heutigen
Editoren eine Katastrophe ist, aber das scheint ja eher ein Randaspekt zu
sein.
Kannst du das genauer ausfuhren? Wo siehst du Probleme? Natürlich gibt
es momentan noch nichts in den Editoren. Es ist ja auch nur ein
Hallo,
Am 19.09.2012 09:58, schrieb Lars Schimmer:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Mein Plan: viele, viele building:part=yes für die einzelnen Höhen
eintragen, über alles ein building:parts=vertical.
Nur wie die Tiefgarage eintragen, und wie die Rasen/Pools im Innenhof
korrekt
On Wed, Sep 19, 2012 at 10:06:36AM +0200, Eckhart Wörner wrote:
Am Dienstag, 18. September 2012, 14:46:21 schrieb Ronnie Soak:
Das erste Proposal zum Thema extended conditions das mir (von den
Tücken der englischen Sprache mal abgesehen) intuitiv genug für den
Otto-Normalnutzer scheint und
Hallo Ronnie,
Am Mittwoch, 19. September 2012, 10:28:19 schrieb Ronnie Soak:
Viel gravierender ist, dass das Schema für Mapper zumindest in den heutigen
Editoren eine Katastrophe ist, aber das scheint ja eher ein Randaspekt zu
sein.
Kannst du das genauer ausfuhren? Wo siehst du Probleme?
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-19 10:31, Andreas Dommaschk wrote:
Hallo,
Am 19.09.2012 09:58, schrieb Lars Schimmer:
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1
Mein Plan: viele, viele building:part=yes für die einzelnen
Höhen eintragen, über alles ein
Hallo,
Lars Schimmer schrieb:
Der building:parts=* sollte ja nur die Hülle des gesamten Gebäudes
umfassen, um zu sagen: das ist ein Gebäude, welches horitzontal/vertikal
in kleinere Teilstücke aufgeteilt werden soll.
Die einzelnen Teilstücke sind dann mit building:part=yes gekennzeichnet.
Am 18.09.2012 21:26, schrieb Manuel Reimer:
Johannes Hüsing wrote:
Dann wäre es ja auch schon strittig, ob man operator=REWE mit beim
Supermarkt einträgt.
... oder gar name=REWE...
Ich frage mich hier, was das Markenrecht tatsächlich aussagt. Nennen und
niederschreiben wird man den Namen ja
Am 19.09.2012 10:46, schrieb Jochen Topf:
Diese Abstimmerei über ein Theoriegebäude bringt doch nix.
+1
Der GUI ist es doch letztlich nahezu egal, was sie in die Tags schreibt
und dem Auswerter ist es auch nahezu egal, was in dem Tag steht (es gibt
ein paar Einschränkungen, wie konstante
Hallo,
tumsi schrieb:
Ein etwas andere Frage, aber zu diesem Thema: Gibt es bereits ein
Vorlagen-Addon für JOSM für das 3D-Schema.
Ja gibt's :)
Schau mal in den Einstellungen unter den Objektvorlagen. Da gibt es die
3D properties von Kendzi (der Entwickler von Kendzi3D und auch ein
Hallo aighes,
Am Mittwoch, 19. September 2012, 11:28:37 schrieb aighes:
Der GUI ist es doch letztlich nahezu egal, was sie in die Tags schreibt
und dem Auswerter ist es auch nahezu egal, was in dem Tag steht (es gibt
ein paar Einschränkungen, wie konstante Keys). Egal wie simpel das
Schema
Okay, folgendes Beispiel (vereinfachtes Beispiel aus der Wirklichkeit): eine
Autobahnbrücke, auf der bei Nässe langsam (80) gefahren werden muss, die
Geschwindigkeit wird vor der Brücke schrittweise reduziert:
http://eckhart-woerner.de/~eckhart/conditional-restrictions.osm
Weil in der
Hallo Ronnie,
Am Mittwoch, 19. September 2012, 11:51:45 schrieb Ronnie Soak:
Okay, folgendes Beispiel (vereinfachtes Beispiel aus der Wirklichkeit):
eine Autobahnbrücke, auf der bei Nässe langsam (80) gefahren werden muss,
die Geschwindigkeit wird vor der Brücke schrittweise reduziert:
Am 19.09.2012 11:41, schrieb Eckhart Wörner:
Hallo aighes,
Am Mittwoch, 19. September 2012, 11:28:37 schrieb aighes:
Der GUI ist es doch letztlich nahezu egal, was sie in die Tags schreibt
und dem Auswerter ist es auch nahezu egal, was in dem Tag steht (es gibt
ein paar Einschränkungen, wie
Hi Eckhart, aighes
auf den Stücken vor und hinter der Brücke:
maxspeed:conditional = 100 @ (22:00 - 06:00)
Auf den bei Nässe reduzierten Stücken:
maxspeed:conditional = 100 @ (22:00 - 06:00); 80 @ (wet)
Die detailiertere Bedingung wird jeweils hinten angehägt. Es gilt bei
Nässe nach
Hallo,
ich arbeite jetzt ein paar Wochen an der Verbesserung der OSM Daten in
meiner Gegend. Jetzt plane ich mir ein GPS Gerät zuzulegen um selber
noch genauere Daten zu holen.
Da ich noch keine Erfahrung damit habe bin ich mir nicht sicher ob ich
mir ein Gerät wie z.B. Garmin eTrex oder
Am 19. September 2012 02:16 schrieb Tirkon tirko...@yahoo.de:
Georg Lösel georg.loe...@fossgis.de wrote:
Ein weiteres Projekt, das derzeit von der Wikimedia gefördert wird,
sind Luftaufnahmen, um Wikipedia Artikel besser illustrieren zu
können. Hier könnte man abklären, inwiefern so etwas auch
On 09/19/2012 01:12 PM, wwl wrote:
Zu was würdet Ihr mir Raten und wovon soll ich die Finger lassen?
Vorteile echter GPS Geräte: (hoffentlich) besserer Empfang und
genauere Ergebnisse, und vor allem längere Batterielebensdauer als
ein typisches Smartphone, optional barometrische Höhenmessung
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-19 13:12, wwl wrote:
Hallo, ich arbeite jetzt ein paar Wochen an der Verbesserung der
OSM Daten in meiner Gegend. Jetzt plane ich mir ein GPS Gerät
zuzulegen um selber noch genauere Daten zu holen. Da ich noch keine
Erfahrung damit habe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 2012-09-19 11:24, Peter Barth wrote:
Hallo,
Lars Schimmer schrieb:
Der building:parts=* sollte ja nur die Hülle des gesamten
Gebäudes umfassen, um zu sagen: das ist ein Gebäude, welches
horitzontal/vertikal in kleinere Teilstücke aufgeteilt
Hallo Christian,
Original-Nachricht
Betreff: [Talk-de] GPS Anfänger
Datum: Wed Sep 19 2012 13:12:05 GMT+0200
Von: wwl use...@schani.com
An: talk-de@openstreetmap.org
ich arbeite jetzt ein paar Wochen an der Verbesserung der OSM Daten in
meiner Gegend. Jetzt plane ich mir ein
1 - 100 von 282 matches
Mail list logo
