Re: [osmosis-dev] [OSM-dev] Problem in rake db:migrate with postgre
Hi Brett, http://git.openstreetmap.org/?p=rails.git;a=blob;f=db/migrate/051_add_status_to_user.rb;h=cc8a2f23848af8ffaf86dc6f5bb65cb42597d2d3;hb=180228b7e36224fefd5540306d7fb77799d4b827 It's now a status column rather than active and visible. Shaun On 12 Jun 2010, at 17:30, Brett Henderson wrote: > The Osmosis error message seems to indicate that the "active" column on the > users table no longer exists. I haven't checked the recent migrations to > figure out exactly what has changed. > > Currently when populating a datatabase, Osmosis creates any required users > and makes them active (active = 1 I think). If active no longer exists, the > replacement column will need to be populated with an equivalent value. > > Brett > > On Fri, Jun 11, 2010 at 6:43 PM, M Naveed Akram wrote: > Brett: the issue is still there in the latest build of osmosis.. > can u please guide a little if i want to resolve it > > > On Mon, Jun 7, 2010 at 12:44 PM, M Naveed Akram wrote: > can anyone tell me that to which schema migration version number the new > osmosis works fine > > > On Sun, Jun 6, 2010 at 7:35 AM, Brett Henderson wrote: > On Fri, Jun 4, 2010 at 10:38 PM, Ævar Arnfjörð Bjarmason > wrote: > On Fri, Jun 4, 2010 at 09:40, M Naveed Akram wrote: > > thanks to all > > UTF8 issue resolved. > > but now its osmosis > > Last I checked osmosis hadn't been fixed to work with the latest > schema changes in the rails port, I run the Debian osmosis version, > but it wasn't fixed in trunk either (at least the newest user group > thing). > > Maybe that's what's going on, I just use an older version of the rails > port for my importing purposes. > > Due to the way osmosis does imports it's fairly susceptible to > breaking like this due to relatively small schema changes. > > I wasn't aware of the breakage until now. The database I use for unit tests > is ancient. I won't get to this for a while, but if anybody else wants to > take a look I'd appreciate it muchly. > > Brett > > > > > -- > Regards > M Naveed Akram > http://www.google.com/profiles/cmnajs > > > > > -- > Regards > M Naveed Akram > http://www.google.com/profiles/cmnajs > > > ___ > osmosis-dev mailing list > osmosis-dev@openstreetmap.org > http://lists.openstreetmap.org/listinfo/osmosis-dev ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [osmosis-dev] Error Importing data to mysql using osmosis 35
On Fri, Jun 11, 2010 at 4:40 PM, M Naveed Akram wrote:
> hi,
> i am unabel to write-apidb form osm file to mysql.
>
> my mysql schema version is 25(25 migrations)
> and i am getting the following problem
>
> Caused by:
> com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationExceptions:
> Cannot add or update a child ros: a foreign key constraing fails
> ('osm_database'.'changeset_tags', CONSTRAINT 'changeset_tags_ibfk_1' FOREIGN
> KEY ('id') REFERENCE 'changesets' ('id'))
>
Do you have to use MySQL? I no longer test on MySQL, and only use
PostgreSQL. MySQL might still work, but I'd rather not invest too much time
in supporting it.
However the error message you're getting seems a bit strange. It seems like
a changeset_tags is being added or modified to point to a non-existent
changesets row. That shouldn't happen. Is your database empty prior to the
import? Even that may not explain it though ...
___
osmosis-dev mailing list
osmosis-dev@openstreetmap.org
http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [osmosis-dev] [OSM-dev] Problem in rake db:migrate with postgre
The Osmosis error message seems to indicate that the "active" column on the users table no longer exists. I haven't checked the recent migrations to figure out exactly what has changed. Currently when populating a datatabase, Osmosis creates any required users and makes them active (active = 1 I think). If active no longer exists, the replacement column will need to be populated with an equivalent value. Brett On Fri, Jun 11, 2010 at 6:43 PM, M Naveed Akram wrote: > Brett: the issue is still there in the latest build of osmosis.. > can u please guide a little if i want to resolve it > > > On Mon, Jun 7, 2010 at 12:44 PM, M Naveed Akram wrote: > >> can anyone tell me that to which schema migration version number the new >> osmosis works fine >> >> >> On Sun, Jun 6, 2010 at 7:35 AM, Brett Henderson wrote: >> >>> On Fri, Jun 4, 2010 at 10:38 PM, Ævar Arnfjörð Bjarmason < >>> ava...@gmail.com> wrote: >>> On Fri, Jun 4, 2010 at 09:40, M Naveed Akram wrote: > thanks to all > UTF8 issue resolved. > but now its osmosis Last I checked osmosis hadn't been fixed to work with the latest schema changes in the rails port, I run the Debian osmosis version, but it wasn't fixed in trunk either (at least the newest user group thing). Maybe that's what's going on, I just use an older version of the rails port for my importing purposes. Due to the way osmosis does imports it's fairly susceptible to breaking like this due to relatively small schema changes. >>> >>> I wasn't aware of the breakage until now. The database I use for unit >>> tests is ancient. I won't get to this for a while, but if anybody else >>> wants to take a look I'd appreciate it muchly. >>> >>> Brett >>> >>> >> >> >> -- >> Regards >> M Naveed Akram >> http://www.google.com/profiles/cmnajs >> >> > > > -- > Regards > M Naveed Akram > http://www.google.com/profiles/cmnajs > > ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [osmosis-dev] bounding-box does not support data provided by default pipe
That helped. Am 12.06.2010 um 13:41 schrieb Frederik Ramm: > Hi, > > Oliver Schrenk wrote: >>> bzcat $(MAPS.OSM)/planet-080611.osm.bz2 | $(TOOLS.OSMOSIS) >>> --read-xml-0.5 enableDateParsing=no file=/dev/stdin --bounding-box >>> top=$(TOP) left=$(LEFT) bottom=$(BOTTOM) right=$(RIGHT) --write-xml >>> file=080611.osm > > Perhaps throw in a --migrate just before the --bounding-box! > > Bye > Frederik > > -- > Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [osmosis-dev] bounding-box does not support data provided by default pipe
Hi, Oliver Schrenk wrote: >> bzcat $(MAPS.OSM)/planet-080611.osm.bz2 | $(TOOLS.OSMOSIS) >> --read-xml-0.5 enableDateParsing=no file=/dev/stdin --bounding-box >> top=$(TOP) left=$(LEFT) bottom=$(BOTTOM) right=$(RIGHT) --write-xml >> file=080611.osm Perhaps throw in a --migrate just before the --bounding-box! Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [osmosis-dev] bounding-box does not support data provided by default pipe
Thanks. I'm using the perl script to extract data from the old maps. I still get the same error message when reading from ftp://ftp5.gwdg.de/pub/misc/openstreetmap/planet.openstreetmap.org/planet-080611.osm.bz2 though The map is definitely 0.5 http://www.openstreetmap.org/api/0.5"; /> ... I use --read-xml-0.5 with 0.35.1 > bzcat $(MAPS.OSM)/planet-080611.osm.bz2 | $(TOOLS.OSMOSIS) --read-xml-0.5 > enableDateParsing=no file=/dev/stdin --bounding-box top=$(TOP) left=$(LEFT) > bottom=$(BOTTOM) right=$(RIGHT) --write-xml file=080611.osm Am 12.06.2010 um 10:35 schrieb Frederik Ramm: > Hi, > > Oliver Schrenk wrote: >> Has 0.3 been deprecated/removed? Can I use an older version for extracting >> bb from 0.3 maps? What's the case for 0.4 maps? > > 0.3 and 0.4 are basically the same and can be processed with the same > software. Osmosis never supported either, it starts at 0.5. There is a tool > in SVN which converts from 0.4 (and therefore also 0.3) to 0.5 > (applications/utils/conv05). However that will probably not run on the whole > planet file, or take too long; you will have to use > applications/utils/osm-extract/planetosm-excerpt-area.pl to cut out an area > from the old file. That perl script either supports 0.4 in its current form, > or maybe you'll have to check out an older version from SVN. > > Bye > Frederik > > -- > Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
Re: [osmosis-dev] bounding-box does not support data provided by default pipe
Hi, Oliver Schrenk wrote: > Has 0.3 been deprecated/removed? Can I use an older version for extracting bb > from 0.3 maps? What's the case for 0.4 maps? 0.3 and 0.4 are basically the same and can be processed with the same software. Osmosis never supported either, it starts at 0.5. There is a tool in SVN which converts from 0.4 (and therefore also 0.3) to 0.5 (applications/utils/conv05). However that will probably not run on the whole planet file, or take too long; you will have to use applications/utils/osm-extract/planetosm-excerpt-area.pl to cut out an area from the old file. That perl script either supports 0.4 in its current form, or maybe you'll have to check out an older version from SVN. Bye Frederik -- Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33" ___ osmosis-dev mailing list osmosis-dev@openstreetmap.org http://lists.openstreetmap.org/listinfo/osmosis-dev
