This is in progress, and taking forever (I about 10,000 ways in all).
Apparently uploading large changesets with JOSM takes a long time. Not
sure if it's JOSM or the server. Worse, I started to upload some changes
(using 1000 size chunks as JOSM couldn't handle it all at once), but it
took
On Wed, Aug 4, 2010 at 1:46 PM, Alan Mintz alan_mintz+...@earthlink.net wrote:
I've written perl scripts in the past, but these ad-hoc changes I've done as
follows:
[snip]
Thanks - this worked perfectly. I've uploaded
http://www.openstreetmap.org/browse/changeset/5406539.
It's the API not JOSM. You have to be patient.
On 5 Aug 2010, at 24:40 , Kevin Atkinson wrote:
This is in progress, and taking forever (I about 10,000 ways in all).
Apparently uploading large changesets with JOSM takes a long time. Not sure
if it's JOSM or the server. Worse, I
I'm afraid we've veered way off topic here.
There were three topics and I'd like to close one of them (or spin it
off) and discuss the other two.
Topic 3 (the unimportant one):
Periods are AFAIK, valid in OSM. We don't care about the underlying
implementation, whether it's Postgres or Mongo or
On Thu, Aug 5, 2010 at 1:19 PM, Serge Wroclawski emac...@gmail.com wrote:
[ ... ]
What do people think of a something like A friendly guide to bots and
imports?
I like it. Let's start.
Required reading:
http://www.asklater.com/matt/wordpress/2009/09/imports-and-the-community/
Hi,
Richard Weait wrote:
Required reading:
http://www.asklater.com/matt/wordpress/2009/09/imports-and-the-community/
http://www.asklater.com/matt/wordpress/2009/09/imports-and-the-community-ii/
I also like The Pottery Club:
One thing I'm wondering about: how useful is a small piece of a future
larger import? For example, there's the National Hydrography Dataset,
import of which is apparently being coordinated on the wiki. I've
imported individual lakes and swamps from it, as well as all of those
in small areas (such
On Thu, Aug 5, 2010 at 1:27 PM, Nathan Edgars II nerou...@gmail.com wrote:
One thing I'm wondering about: how useful is a small piece of a future
larger import? For example, there's the National Hydrography Dataset,
import of which is apparently being coordinated on the wiki. I've
imported
On Thu, Aug 5, 2010 at 2:38 PM, Ian Dees ian.d...@gmail.com wrote:
I think the NHD import is a good example of a well-intentioned importer
(me) gone wrong. I had initially planned to import the whole darn thing in
one swoop, but various technical and life challenges came up before I could
get
On Thu, Aug 5, 2010 at 1:47 PM, Nathan Edgars II nerou...@gmail.com wrote:
On Thu, Aug 5, 2010 at 2:38 PM, Ian Dees ian.d...@gmail.com wrote:
I think the NHD import is a good example of a well-intentioned importer
(me) gone wrong. I had initially planned to import the whole darn thing
in
On Sat, Jan 8, 2000 at 3:20 PM, Katie Filbert filbe...@gmail.com wrote:
The difference with NHD is that we are leaving conversion to osm format for
the local mapper / importer. Since OSM US has server space, maybe that's
good use of it to host converted data ready for import.
I like this...
On Sat, Jan 8, 2000 at 4:20 PM, Katie Filbert filbe...@gmail.com wrote:
Bad imports are bad for the osm. High quality data carefully imported is
helpful. If such high quality data is available for us that is as good or
better than what we can do ourselves, then it's fine not to reinvent the
On Thu, Aug 05, 2010 at 01:38:36PM -0500, Ian Dees wrote:
I think the NHD import is a good example of a well-intentioned importer
(me) gone wrong. I had initially planned to import the whole darn thing in
one swoop, but various technical and life challenges came up before I could
get it
Katie,
your computer thinks it is the year 2000. I see you sent that from
your iPhone. Maybe you had your fingers on the wrong spot so it didn't
get a time signal.
Katie Filbert wrote:
Bad imports are bad for the osm. High quality data carefully imported
is helpful.
Not
On Thu, Aug 05, 2010 at 10:38:47PM +0200, Frederik Ramm wrote:
Katie,
your computer thinks it is the year 2000. I see you sent that from
your iPhone. Maybe you had your fingers on the wrong spot so it didn't
get a time signal.
Not only that, all of your messages (katie) are being
At 2010-08-05 11:52, Ian Dees wrote:
...
It isn't any different. I had made the (bad) decision at the time to
import over any existing data because in the several hundred places I
spot-checked, NHD was vastly superior in resolution (and probably quality).
By import over, do you mean to add
On Thu, Aug 5, 2010 at 4:43 PM, Alan Mintz
alan_mintz+...@earthlink.netalan_mintz%2b...@earthlink.net
wrote:
At 2010-08-05 11:52, Ian Dees wrote:
...
It isn't any different. I had made the (bad) decision at the time to
import over any existing data because in the several hundred places I
I have to say that after importing a large amount of NHD data (most of NC
and MN) that it is of varying quality, as was the preexisting water related
data already on the server. In general, I agree with Ian that it is higher
quality (both resolution and accuracy) than the preexisting data that
BTW: In case you missed it I already did the initial upload. But there is
always room to fix things up.
On Thu, 5 Aug 2010, Serge Wroclawski wrote:
Is this proposed mass-change something good for Salt Lake City. That
is does it fit in with the way locals name the streets. This seemed to
get
On Thu, Aug 5, 2010 at 6:10 PM, James U jumba...@gmail.com wrote:
I have to say that after importing a large amount of NHD data (most of NC
and MN) that it is of varying quality, as was the preexisting water related
data already on the server. In general, I agree with Ian that it is higher
So the upload went well, there is still a lot that can be done but this a
good first start.
I am going to fix up the script so that it can run repeatably on the same
area to allow it to further be refined.
Maybe I make the source available, but it only really should be used in
areas that
Some guides aimed at focused scripts which address a particular problem in
a well defined area would be useful, as most of the guide is aimed at
automatic fixup bots and large scale imports. For example a note in big
bold letters that large uploads take a long time will be very helpful.
Hi,
On 5 August 2010 21:46, Richard Weait rich...@weait.com wrote:
On Sat, Jan 8, 2000 at 4:20 PM, Katie Filbert filbe...@gmail.com wrote:
Leaving imports to local mappers is good. They are best able to assess the
quality of the data for that area an care about quality of their local map
the web page may be found here:
https://docs.google.com/document/pub?id=1YTf9-iUKivwvAOEN6VpkGRyDDrABMIsMAFtiF5ehBz0
OSM US Chapter Call August 5th, 2010
Attendees
Kate Chapman, Serge Wroclawski, Richard Welty, Thea Clay, Steven Johnson
Approval of Minutes
July 22nd, 2010
24 matches
Mail list logo
