tice you will gain detail in actual use. There is probably a sweet
spot somewhere in the middle, enough detail to allow to differentiate
"important" differences while not adding too much detail overwhelming
anybody who wants to use the data.
Jochen
--
Jochen Topf joc...@remote.o
e coastline change in
> https://www.openstreetmap.org/changeset/126200089
Thanks. I have manually "unfrozen" the processing now. We'll probably
have some other bad edits that make it through this way, but at least
the big one is avoided.
Jochen
--
Jochen Topf joc...@remote.org https
ons of the ODbL between OSM/the
community vs. Facebook are involved. But you would not have a conflict
of interest over anything "beyond the ODbL". So by framing the issue
this way you argued yourself out of your conflict of interest problem in
this issue. Very clever!
[1] https://en.wik
rently available on
> https://osmdata.openstreetmap.de - so that mistakes do not lead to
> multi-week waits for new polygons? Right now the last update was 11/11/2020
> - ten days ago.
>
> Is there any way of getting updates more often than once a day in the
> best-case scenar
list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
Association - https://trufi-
> > association.org
> >
> > Ein Gag zu Hamsterkäufen: https://klopapier.mapdiscover.org id="-x-
> > evo-selection-end-marker">
> > ___
> > Talk-de mailing list
> > Talk-de@openstreetmap.org
> > https://lists
On Mon, May 20, 2019 at 10:23:07PM +0200, Florian Lohoff wrote:
> On Mon, May 20, 2019 at 09:32:25PM +0200, Jochen Topf wrote:
> > > besorgt - Problem ist das entgegen der Doku die durch
> > > das ST_Simplify doch kleiner werden und schneiden können. Muss man
> > &g
;smart"-Strategie benutzt, dann ist auch die
Grenze selbst garantiert drin. Vereinfachte Grenzen machen das Ganze
etwas schneller, aber nicht viel. Und dann musste Dich nicht mit Buffern
oder so rumärgern.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de
ich in dem Fall nicht, aber da kann man dem Osmium
> keinen Vorwurf machen.
Osmium kannste eh keinen Vorwurf machen, wenn dann Osmosis :-)
Florian: Warum nimmste nicht einfach Osmium, das ist auch noch
einfacher:
osmium tags-filter detmold-regbez-latest.osm.pbf a/boundary=administrative -
site (yet) and we are trying to gauge interest.
Some more background here:
https://blog.jochentopf.com/2019-03-07-the-new-osmdata-service.html
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing
finding and working with what we need now.
> Thank internet gods for the Internet Archive,
Not the gods but some good people who had a good idea. Let them do their
job and keep the history and lets do our job and keep the momentum in
the project instead of spending our time looking
nd. Except that I expect to find 10
useful pages, not 5. If the outdated pages were not there, who knows
what useful pages I might have found!
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailin
rst. Might
be okay for you and me because we have been around long enough to see
quickly what's interesting and what isn't. But if you are not familiar
with OSM this is daunting.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
__
SM itself, we allow anybody to delete anything there, too, and it seems
to work out mostly.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
/Name_finder
>
> --
> Per E-Mail kommuniziere ich bevorzugt GPG-verschlüsselt. (Mailinglisten
> ausgenommen)
> I prefer GPG encryption of emails. (does not apply on mailing lists)
>
> ___
> talk mailing list
> talk@op
deleting that
> file, osmosis would make a new one and the problem went away.
I guess its time to ditch Osmosis und switch to Osmium/PyOsmium for these
tasks...
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk
lk mailing list
> > talk@openstreetmap.org
> > https://lists.openstreetmap.org/listinfo/talk
> >
> https://munin.openstreetmap.org/problems.html#critical
>
> ___
> talk mailing list
> talk@openstreetmap.org
> https
Da gibts viele Möglichkeiten. Z.B. ein kleines PyOsmium-Skript. Oder Du
schreibst ein kleines Skript, was mit "osmium getid" die Ways
rausfriemelt, als OPL speichert und darin den Tag ändert und alles
wieder zusammensetzt. Ein bischen programmieren wirst Du aber schon
müssen.
Jochen
--
Joche
e always corner cases. But that's no reason to
discredit the rule.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
ht eher nicht z.B.), wie die beobachtete Nutzung durch Leute vor
Ort ist usw. Und ja, da macht man Dinge auch mal falsch. Aber das ist
okay, weil andere Mapper nach mir kommen und Dinge korrigieren können.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
cht
sicher bin.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de
lprogramm was bei libosmium dabei ist)
ergibt:
Length: 3069.67 km
Durch zwei geteilt sind das ca. 1535 km, was viel besser passt.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
Talk-de mailing lis
on the bottom right). I was looking through the "Addresses"
view because you mentioned something with "address nodes" trying to
figure out what you meant...
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
__
se.
> > * Query authors can easily search for it to see why they showed up in the
> > query result, and fix the original query
> >
> > The biggest problem is the tag name, any suggestions?
> >
> ___
> talk mailing list
> talk@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
ipolygons. But with the new-style multipolygons
interpretation, the tags from a collections of objects are *never*
aggregated into a larger whole.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
t
osmium getid planet.osm.pbf -r 1234 -o rel.osm.pbf
die Relation rausholen, die als Grenze dienen soll. Dann den Extract
machen:
osmium extract planet.osm.org -p rel.osm.pbf -o ausschnitt.osm.pbf
Eine Poly-Datei brauchste nimmer, osmium kann direkt die OSM-Datei mit
der Relation verwenden.
Joche
On Tue, Aug 29, 2017 at 03:54:44PM +0200, Christoph Hormann wrote:
> On Tuesday 29 August 2017, Jochen Topf wrote:
> >
> > > Would the number of visible problems in the map due to dropping
> > > broken geometries now, after the fixing effort, be low enough so
>
On Tue, Aug 29, 2017 at 12:10:47PM +0200, Christoph Hormann wrote:
> Date: Tue, 29 Aug 2017 12:10:47 +0200
> From: Christoph Hormann <o...@imagico.de>
> To: talk@openstreetmap.org
> Subject: Re: [OSM-talk] Multipolygon fixing effort done
>
> On Tuesday 29 August 2017, J
We have completed the 7-months effort to switch away from old-style
multipolygons and fix a lot of broken (multi)polygons. More about this
on my blog:
https://blog.jochentopf.com/2017-08-28-polygon-fixing-effort-concluded.html
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com
might
not see as similar enough to the OpenStreetMap trademark.
I am sure you have the best intentions of defending OSM against the big
bad conglomerates, but I think the best defense is having a large and
open community and eco-system, one where you don't have to ask for
permission before y
stand
you correctly that I can have a software with the name OpenStreetMap in
the title in a github repo and it doesn't fall under this policy?
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
community members have the same
restrictions on what they can actually do than the outside people have.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
have to get licenses and actually do, we are looking at at least
several hundreds of projects (There are nearly 3000 repositories on
Github that have "openstreetmap" in their name or description).
Can the OSMF even handle this?
Jochen
--
Jochen Topf joc...@remote.org https://www.joch
n if nobody really minds
them using this name) to make this stick. So just ignoring some
violations and fighting others isn't possible. Which opens the whole
question of whether the OSMF is organizationally and financially in a
position to actually do this fighting? If not, why have this policy?
denn hier? So wie ich das verstanden habe, sind es ja nur
ein paar POIs, die Du importieren willst, das sollte nicht wirklich sehr
aufwändig sein.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de
Neuimport durchlaufen lassen oder so. Das macht es viel
einfacher.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de
am Ende erreichen? Wenn das Ziel ist, rauszufinden,
wo es überall Änderungen bestimmter Art gegeben hast, dann reichen die
.osc-Dateien nicht als Datenquelle aus. Du kannst Dir mal
http://wiki.openstreetmap.org/wiki/Overpass_API/Augmented_Diffs
anschauen, vielleicht hilft Dir das weiter.
On Sat, Jul 01, 2017 at 09:52:48AM +0200, Jochen Topf wrote:
> > How difficult would it be to add this to OSM inspector? Not everybody has
> > Postgres running, and is able to use osm2pgsql. Yes, there is documentation,
> > but it requires some technical skills. Also, it would
n most cases this simply means that there should be no
tags on the ways at all.
Of course you should still check all cases against sat images. For
instance, sometimes the whole relation can be removed and just a simple
closed way be used if there are no inner w
On Fri, Jun 30, 2017 at 11:47:36PM +0200, Frank Steggink wrote:
> On 30-06-2017 21:21, Jochen Topf wrote:
> > On Fri, Jun 30, 2017 at 08:16:40PM +0200, Frank Steggink wrote:
> > > Maybe I'm not understanding it, but in the OSM inspector [1] I just see
> > >
he shortcut wasn't so short
after all, whining that you don't have the manpower to fix it. That
can't be the excuse.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
Talk-ca mailing list
Talk-ca@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-ca
of the data has to work around this or handle the
complaints.
* The Canadian community steps up and fixes the data, automatically or
manually.
* We ask the Data Working Group to remove the broken import.
Jochen
On Thu, Jun 22, 2017 at 11:38:15AM +0200, Jochen Topf wrote:
> Date: Thu, 22
Details
gibt es unter https://wiki.openstreetmap.org/wiki/Elbe-Labe-Meeting_2017
Wir laden alle OSMer ein, dabei zu sein. Da der Platz begrenzt ist,
ist eine Vorregistrierung erforderlich.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
://lists.openstreetmap.org/pipermail/talk/2017-June/078203.html
and this issue
https://github.com/osmlab/fixing-polygons-in-osm/issues/36 .
News of the effort are posted regularly to
https://github.com/osmlab/fixing-polygons-in-osm/issues/15 .
Jochen
--
Jochen Topf joc...@remote.org https
On Fri, Jun 16, 2017 at 11:04:27AM +0200, Christoph Hormann wrote:
> On Friday 16 June 2017, Jochen Topf wrote:
> >
> > Es gibt da eine Tendenz immer komplexere Dinge zu mappen, ohne dass
> > irgendwer diese Daten auch sinnvoll nutzt. Auf der einen Seite ist es
> > ja
chte. Siehe
http://docs.osmcode.org/osmium/latest/osmium-extract.html .
Normalerweise werden nur multipolygon-Relationen vervollständigt, aber
man kann auch sagen, dass das auch für die Grenzen gelten soll.
Jochen
--
Jochen Topf joc...@remote.org htt
werten, das ist schwierig und kann selbst bei kleinen
Änderungen erhebliche Auswirkungen haben. Da muss man schon viel genauer
hinsehen, was sinnvoll ist und was nicht.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
_
don't know yet, that they shouldn't do that, but
that's not a big problem.
So that part of the great (multi)polygon fixing effort is done. Huge
thanks to everybody involved! But there are still geometry errors to
fix.
Find more information here: http://area.jochentopf.com/
Jochen
--
Jochen Topf
fixing-polygons-in-osm/issues with specific
information about the OSM objects that are rendered incorrectly.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
Talk-us mailing list
Talk-us@openstre
can see on the map at http://area.jochentopf.com/map/index.html
most of the old-style multipolygons now left are from some large-scale
imports, including some in the US. We need your help in cleaning this
up! I you have any questions, don't hesitate to ask.
Jochen
--
Jochen Topf joc...@remote.org
On Sun, Mar 19, 2017 at 02:46:30PM +0100, Jochen Topf wrote:
> in my newest batch of Maproulette challenges, I have included a special
> challenge for Korea, because there were so many problems there.
>
> I encourage everbody to help:
> http://area.jochentopf.com/fixing.html#dup
On Mon, Mar 27, 2017 at 10:41:38AM +0200, Jochen Topf wrote:
> On Mon, Mar 27, 2017 at 03:56:43PM +1000, nwastra wrote:
> > I am unsure what is the preferred way or best practice to tag the source
> > for multipolygons.
> > I currently put the source on the relation with all
sense. We can not track every
source for every node, way, or relation or the parts of them for every
tiny change that somebody does. In the end most data will have multiple
sources and figuring out what came from what can only be done going
through the changeset tags, not by looking at the tags
On Mon, Mar 20, 2017 at 07:15:47AM +0100, Jochen Topf wrote:
> On Mon, Mar 20, 2017 at 06:27:05AM +0100, Andreas Vilén wrote:
> > It's not up to me to decide if this data is to be deleted or not. If
> > you want to do that, raise the question with each respective country's
> >
community on this topic and that the Swedish community had decided they
wanted to keep the data. So I thought this issue was settled.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing
ly related to
some kind of import. I have taken those out of the challenges I am
generating, because I wanted to contact the OSM community there first.
Anybody here who has connections to South Korea and/or knows about
what's going on there?
Jochen
--
Jochen Topf joc...@remote.
s just a subset of the old-style polygons.
Currently I am concentrating on actually broken polygons, the old-style
polygons are next and I will create challenges for them, too.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
_
On Sat, Mar 04, 2017 at 10:50:41AM +0100, Martin Koppenhoefer wrote:
> > On 4 Mar 2017, at 08:49, Jochen Topf <joc...@remote.org> wrote:
> >
> > Looking at the graphs on http://area.jochentopf.com/stats you can see
> > that the number of (multi)polygons is grow
com/osmlab/fixing-polygons-in-osm/issues/15
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
ngs
look then.
And maybe when there are less cases we can better see specific problems
creeping up that can be solved by improving editors etc.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing lis
lenges in the works that will cover all multipolygon problems.
This is just a matter of me rolling out those challenges a few at a time
so the community can concentrate on one problem before tackling the next
one.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31
k for
OSM. Not being able to report problems is frustrating to users. The
whole question of who decides what is spam and what isn't is a bit
besides the point here, isn't it? Obviously somebody is already handling
this as you mention and it works. But what would help is a
On Tue, Feb 21, 2017 at 07:44:18PM +0100, Sebastiaan Couwenberg wrote:
> On 02/21/2017 05:40 PM, Jochen Topf wrote:
> > Find all challenges and instructions here:
> > http://area.jochentopf.com/fixing.html
>
> My OCD complains about the typo before the challenge links, plea
On Wed, Feb 15, 2017 at 04:20:53PM +0100, Jochen Topf wrote:
> There are a lot of (multi)polygons in OSM that are broken in one way or
> another. And we have to fix them. While some of the broken ones appear
> on the map just fine, some don't appear and some mess up the map. And
> s
of a link to an example?
>
> I guess Florian ment geometries like this:
> http://www.openstreetmap.org/way/460032394
>
> There are indeed plenty of these in "less populated" areas,
> especially areas with round buildings...
Probably the result of some HOT mapping
aproulette2 .
I just opened an issue there to say that there is no contact info. :-)
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
l" polygons you
are talking about might not show up or show up wrong on the map because
of the errors they contain that the renderer is trying to fix and doing
so in the wrong way. We are doing all this to improve the accuracy of
the map!
Jochen
--
Jochen Topf joc...@remote.org
e different everywhere. I'd rather have
more specific challenges addressing exactly one problem, for instance
"Broken multipolygons of certain types of landcover data imported from
Corinne in Sweden". That is something I can extract from OSM data and
that I can explain to people how to fix aft
ew at
http://tools.geofabrik.de/osmi/?view=areas )
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
On Wed, Nov 09, 2016 at 07:09:05PM +0100, Jochen Topf wrote:
> I have opened an issue:
> https://github.com/gravitystorm/openstreetmap-carto/issues/2430
Thanks, nebulon42, for fixing this. Everybody encountering problems with
the icons can now simple re-import them into the wiki. There is n
It is here like with everything in OSM: There is a trend towards more
detail. If you have more detailed information, great. If not, it is
better than nothing.
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
t
works fine.
> any suggestions what might be going wrong, or other checkers i might use?
If the OSM Inspector says, the coastline is okay, it most likely is. The
coastline check is very picky. Sounds like a data problem in Osmand to
me.
Jochen
--
Jochen Topf joc...@remote.org ht
On Sun, Nov 06, 2016 at 03:44:56PM +0100, Jochen Topf wrote:
> On Sun, Nov 06, 2016 at 02:22:26PM +0100, nebulon42 wrote:
> > Both notations are correct and I have deliberately chosen the latter
> > one. The first one may be the right one for the problem you are tryi
ne.
Can you elaborate? What was your problem? Maybe we can find a solution
that works for everybody?
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.opens
. I am trying to do the
next step here, not change everything in one go.)
With this change the taglists can be made to look exactly like the old,
manually created ones (for instance on the MapFeatures page).
Jochen
--
Jochen Topf joc...@remote.org https://www.jochentopf.com/ +49-351-31778688
__
pretation of this
> data.
But it is the style that people use to check their edits. I just see
this as "giving people what they want". The current Map Feature page
shows that there are people who thought this was a good idea, otherwise
they wouldn't have gone through the consider
Hi!
User "Wuzzy" did a huge amount of work related to this discussion here:
http://www.openstreetmap.org/user/Wuzzy/diary/39580
https://wiki.openstreetmap.org/wiki/Standard_tile_layer/Key
Maybe we can use this somehow?
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf
o box,
the template that creates the info box is just a convenient place to put
this data). Then taginfo gets the data from there and puts them into the
list. This is the short-term solution that would allow us to have the
same Map Features page we already have, with a hugely reduced (but not
totall
aginfo should only be the helper here that makes it easier,
but it shouldn't decide what ends up on that list and what doesn't.
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@opens
Hi Matthijs,
On Mi, Sep 21, 2016 at 01:33:28 +0200, Matthijs Melissen wrote:
> On 1 September 2016 at 15:04, Jochen Topf <joc...@remote.org> wrote:
> > So, if somebody adds the rendering to the infobox (and tells me about it),
> > I'll pull that data from taginfo and can
nstreetmap.org/wiki/Geological
> > it seems to work well there.
>
> As there are some problems with the translations of the pages, this
> has now been reverted.
What are the problems with translations?
Jochen
--
Jochen Topf joc...@remote.org
well maintained. But looking
at it now, it looks quite good, especially for POIs.
So, if somebody adds the rendering to the infobox (and tells me about it),
I'll pull that data from taginfo and can put it in the taglist tables.
Jochen
--
Jochen Topf joc...@remote.org http://www.joche
h are currently broken.
This is now fixed. Images work again.
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
On Do, Sep 01, 2016 at 08:21:39 +0200, Matthijs Melissen wrote:
> On Thursday, 1 September 2016, Jochen Topf <joc...@remote.org> wrote:
>
> > On Do, Sep 01, 2016 at 12:42:10 +0200, Matthijs Melissen wrote:
> > > We have currently a Map Features p
every tag list in the wiki and replacing
it by the special syntax. The problem ist, as you say, the differing
descriptions and such, which need to be consolidated in the process.
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
__
sen "wir" die Wochennotiz,
weil wir darauf vertrauen, dass ihr das richtige auswählt.
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de
se to update the descriptions on the individual pages to not loose the
possibly better descriptions from the MapFeatures list.
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
address, just put the same address
on all buildings if they actually have the same address.
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
o this
> extraction for me?
http://data.openstreetmapdata.com/ireland-and-northern-ireland.osh.pbf
http://data.openstreetmapdata.com/great-britain.osh.pbf
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
talk maili
erhaupt nicht
nach OSM, weil es eine Spezialinformation ist, die sich "on the ground" nicht
verifizieren läßt. Aber ich werde mich jetzt auch nicht beschweren, wenn die
Eisenbahnmapper dafür einen besonderen Tag erfinden.
Jochen
--
Jochen Topf joc...@remote.org http://www.j
inwandfreie Aussage, dass sie damit zufrieden sind
auf http://www.openstreetmap.org/copyright in der Liste der Contributors
genannt zu werden und dass sich darin dann ihr Recht auf Namensnennung
erschöpft. Wenn Sie das unterschreiben, dann ist das okay, vorher nicht.
Jochen
--
Jochen Topf joc...@re
h mit osmosis extrahieren?
>
> Für Eure Hilfe herzlichen Dank.
>
> Heinz
>
>
>
> ___
> Talk-de mailing list
> Talk-de@openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk-de
--
Jochen Topf joc...@remote.org h
://taginfo.openstreetmap.org/
Mehr Details in meinem Blog unter
http://blog.jochentopf.com/2015-08-15-hacking-on-taginfo.html
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
Talk-de mailing list
Talk-de@openstreetmap.org
https
://blog.jochentopf.com/2015-08-15-hacking-on-taginfo.html
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk
etymology:wikidata like most of the name:something tags. It is hard enough
already to make sense of OSM tags...
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk@openstreetmap.org
https
a dam may have the same name, but have no use as a through
route?
This is more about the water flow than about being navigable by a ship.
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
talk mailing list
talk
gesagt ist das sogar das typische Verhalten.
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
___
Talk-de mailing list
Talk-de@openstreetmap.org
https://lists.openstreetmap.org/listinfo/talk-de
systemisches Problem nachweisen können, dann sollte man
das gemeinsam mit Mapbox lösen. Aber etwas mehr als zwei Tage später taucht
der nächste [...] auf, sollte es halt schon sein.
Jochen
--
Jochen Topf joc...@remote.org http://www.jochentopf.com/ +49-351-31778688
there are many names for London in different
languages, I don't think there are special Russian names for half a million
places on Earth. Chances are they are the result of automatic transliteration.
And results of automatic processes should not be mapped for obvious reasons.
Jochen
--
Jochen Topf
1 - 100 of 1030 matches
Mail list logo