Thread: [Pymag-devel] Unable to render Polygons
Status: Alpha
Brought to you by:
lhj
Menu
▾
▴
pymag-devel
|
From: Ingo H. <in...@ni...> - 2009-05-06 15:34:43
|
Hi! It's me again... And again with some problems :) At the moment I am trying to generate a more complete osmmagrules.xml which should render nice maps for my eXplorist 500. The problem is that I get only roads and tracks, but I'm unable to render polygons. So I get no nice landscape ;) Is there a problem with that? If not I would be very pleased if someone can give me an example: A small osm extract with an XML file and probably also the result *.imi would do it. Probably it's only a lack of documentation ;) Thanks and best regards, Ingo |
|
From: henrik j. <hen...@gm...> - 2009-05-11 13:02:33
|
Hi Ingo, Strange problem. There are plenty of polygon rules in the default rule file like parks and buildings. And they work fine on my explorist. Do you get any polygons with the default rule file? If you like you can send the osm-file and rule file that doesn't work for you and I'll have a look. Best regards, Henrik 2009/5/6 Ingo Hornberger <in...@ni...>: > Hi! > > It's me again... And again with some problems :) > > At the moment I am trying to generate a more complete osmmagrules.xml > which should render nice maps for my eXplorist 500. The problem is > that I get only roads and tracks, but I'm unable to render polygons. > So I get no nice landscape ;) > > Is there a problem with that? If not I would be very pleased if > someone can give me an example: > A small osm extract with an XML file and probably also the result > *.imi would do it. > > Probably it's only a lack of documentation ;) > > Thanks and best regards, > Ingo > > ------------------------------------------------------------------------------ > The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your > production scanning environment may not be a perfect world - but thanks to > Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 > Series Scanner you'll get full speed at 300 dpi even with all image > processing features enabled. http://p.sf.net/sfu/kodak-com > _______________________________________________ > Pymag-devel mailing list > Pym...@li... > https://lists.sourceforge.net/lists/listinfo/pymag-devel > |
|
From: Ingo H. <lab...@go...> - 2009-05-13 17:25:58
Attachments:
bremen.imi
bremen.osm.bz2
|
Hi Henrik, I tried it again with the current trunk and assured that I had no locally changed files. But sadly with the same result. For a test I tried to render bremen.osm, because it is the smallest of our states in germany ;) I attached you both files. I created it with the following command: ./osmmag.py -v -n "bremen" -r data/osmmagrules.xml -o bremen.imi bremen.osm And just to make it clear: I "sourced" the "setup.sh" into my environment before: . setup.sh Best regards, Ingo 2009/5/11 henrik johansson <hen...@gm...>: > Hi Ingo, > > Strange problem. There are plenty of polygon rules in the default rule > file like parks and buildings. And they work fine on my explorist. > > Do you get any polygons with the default rule file? > > If you like you can send the osm-file and rule file that doesn't work > for you and I'll have a look. > > Best regards, > > Henrik > > 2009/5/6 Ingo Hornberger <in...@ni...>: >> Hi! >> >> It's me again... And again with some problems :) >> >> At the moment I am trying to generate a more complete osmmagrules.xml >> which should render nice maps for my eXplorist 500. The problem is >> that I get only roads and tracks, but I'm unable to render polygons. >> So I get no nice landscape ;) >> >> Is there a problem with that? If not I would be very pleased if >> someone can give me an example: >> A small osm extract with an XML file and probably also the result >> *.imi would do it. >> >> Probably it's only a lack of documentation ;) >> >> Thanks and best regards, >> Ingo >> >> ------------------------------------------------------------------------------ >> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your >> production scanning environment may not be a perfect world - but thanks to >> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 >> Series Scanner you'll get full speed at 300 dpi even with all image >> processing features enabled. http://p.sf.net/sfu/kodak-com >> _______________________________________________ >> Pymag-devel mailing list >> Pym...@li... >> https://lists.sourceforge.net/lists/listinfo/pymag-devel >> > |
|
From: henrik j. <hen...@gm...> - 2009-05-19 05:43:52
|
Hi Ingo, I tried the files and I have the same problem and I have found the bug in CellElement.py when a polygon is created and it checks if it's a closed polygon or not. Sadly, Mapsend Lite crashes when I zoom around when I have the Parks rule active. With parks commented out in the rule file it works fine though. I haven't yet been able to track down the offending park. Regards, Henrik On 13/05/2009, Ingo Hornberger <lab...@go...> wrote: > Hi Henrik, > > I tried it again with the current trunk and assured that I had no > locally changed files. But sadly with the same result. > > For a test I tried to render bremen.osm, because it is the smallest of > our states in germany ;) > > I attached you both files. I created it with the following command: > > ./osmmag.py -v -n "bremen" -r data/osmmagrules.xml -o bremen.imi bremen.osm > > And just to make it clear: I "sourced" the "setup.sh" into my > environment before: > . setup.sh > > Best regards, > Ingo > > 2009/5/11 henrik johansson <hen...@gm...>: >> Hi Ingo, >> >> Strange problem. There are plenty of polygon rules in the default rule >> file like parks and buildings. And they work fine on my explorist. >> >> Do you get any polygons with the default rule file? >> >> If you like you can send the osm-file and rule file that doesn't work >> for you and I'll have a look. >> >> Best regards, >> >> Henrik >> >> 2009/5/6 Ingo Hornberger <in...@ni...>: >>> Hi! >>> >>> It's me again... And again with some problems :) >>> >>> At the moment I am trying to generate a more complete osmmagrules.xml >>> which should render nice maps for my eXplorist 500. The problem is >>> that I get only roads and tracks, but I'm unable to render polygons. >>> So I get no nice landscape ;) >>> >>> Is there a problem with that? If not I would be very pleased if >>> someone can give me an example: >>> A small osm extract with an XML file and probably also the result >>> *.imi would do it. >>> >>> Probably it's only a lack of documentation ;) >>> >>> Thanks and best regards, >>> Ingo >>> >>> ------------------------------------------------------------------------------ >>> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your >>> production scanning environment may not be a perfect world - but thanks >>> to >>> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK >>> i700 >>> Series Scanner you'll get full speed at 300 dpi even with all image >>> processing features enabled. http://p.sf.net/sfu/kodak-com >>> _______________________________________________ >>> Pymag-devel mailing list >>> Pym...@li... >>> https://lists.sourceforge.net/lists/listinfo/pymag-devel >>> >> > |
|
From: <jo...@fe...> - 2009-05-20 04:04:13
|
Thanks Henrik, I just saw your changes are in svn already. Looking forward to getting polygons working again! Regards, Josh Quoting henrik johansson <hen...@gm...>: > Hi Ingo, > > I tried the files and I have the same problem and I have found the bug > in CellElement.py when a polygon is created and it checks if it's a > closed polygon or not. > > Sadly, Mapsend Lite crashes when I zoom around when I have the Parks > rule active. With parks commented out in the rule file it works fine > though. I haven't yet been able to track down the offending park. > > Regards, > > Henrik > > On 13/05/2009, Ingo Hornberger <lab...@go...> wrote: >> Hi Henrik, >> >> I tried it again with the current trunk and assured that I had no >> locally changed files. But sadly with the same result. >> >> For a test I tried to render bremen.osm, because it is the smallest of >> our states in germany ;) >> >> I attached you both files. I created it with the following command: >> >> ./osmmag.py -v -n "bremen" -r data/osmmagrules.xml -o bremen.imi bremen.osm >> >> And just to make it clear: I "sourced" the "setup.sh" into my >> environment before: >> . setup.sh >> >> Best regards, >> Ingo >> >> 2009/5/11 henrik johansson <hen...@gm...>: >>> Hi Ingo, >>> >>> Strange problem. There are plenty of polygon rules in the default rule >>> file like parks and buildings. And they work fine on my explorist. >>> >>> Do you get any polygons with the default rule file? >>> >>> If you like you can send the osm-file and rule file that doesn't work >>> for you and I'll have a look. >>> >>> Best regards, >>> >>> Henrik >>> >>> 2009/5/6 Ingo Hornberger <in...@ni...>: >>>> Hi! >>>> >>>> It's me again... And again with some problems :) >>>> >>>> At the moment I am trying to generate a more complete osmmagrules.xml >>>> which should render nice maps for my eXplorist 500. The problem is >>>> that I get only roads and tracks, but I'm unable to render polygons. >>>> So I get no nice landscape ;) >>>> >>>> Is there a problem with that? If not I would be very pleased if >>>> someone can give me an example: >>>> A small osm extract with an XML file and probably also the result >>>> *.imi would do it. >>>> >>>> Probably it's only a lack of documentation ;) >>>> >>>> Thanks and best regards, >>>> Ingo >>>> >>>> ------------------------------------------------------------------------------ >>>> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your >>>> production scanning environment may not be a perfect world - but thanks >>>> to >>>> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK >>>> i700 >>>> Series Scanner you'll get full speed at 300 dpi even with all image >>>> processing features enabled. http://p.sf.net/sfu/kodak-com >>>> _______________________________________________ >>>> Pymag-devel mailing list >>>> Pym...@li... >>>> https://lists.sourceforge.net/lists/listinfo/pymag-devel >>>> >>> >> > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Pymag-devel mailing list > Pym...@li... > https://lists.sourceforge.net/lists/listinfo/pymag-devel > |
|
From: <jo...@fe...> - 2009-05-19 10:50:01
|
I've just tried the latest code from svn, with mixed results. Some of
my maps have polygons rendering again, but others that warn about
Improper polygons now crash Mapsend/Vantagepoint.
Some of the warnings I can understand - polygons with only 2 points,
or polygons that are 'open', but one example I saw has me confused...
I got this warning one one tonight -
WARNING Improper polygon found: [(144.844255, -38.373168800000002),
(144.8432851, -38.373168800000002), (144.844255, -38.373168800000002)]
That shows a polygon with 3 points, and two of them have the same
coordinates? That should be a valid polygon unless I'm missing
something.
The nodes/way relating to that error are:
<node id="172752298" timestamp="2009-02-25T17:02:53Z"
lat="-38.3731688" lon="144.844255"/>
<node id="172751478" timestamp="2009-02-25T17:02:53Z"
lat="-38.3731688" lon="144.8432851"/>
<way id="16711763" timestamp="2009-02-25T17:02:53Z">
<nd ref="172752298"/>
<nd ref="172751478"/>
<nd ref="172752298"/>
<tag k="created_by" v="Potlatch 0.5d"/>
<tag k="leisure" v="park"/>
</way>
Regards,
Josh
|
|
From: Josh <jo...@fe...> - 2009-05-19 11:06:45
|
Oops, I had another think about that, and realised a 3 pointed closed polygon is actually more like a straight line ;) Is it possible to just discard bad polygons, seeing as they don't render anyway, and just break the map? Josh Quoting jo...@fe...: > I've just tried the latest code from svn, with mixed results. Some of > my maps have polygons rendering again, but others that warn about > Improper polygons now crash Mapsend/Vantagepoint. > > Some of the warnings I can understand - polygons with only 2 points, > or polygons that are 'open', but one example I saw has me confused... > > I got this warning one one tonight - > WARNING Improper polygon found: [(144.844255, -38.373168800000002), > (144.8432851, -38.373168800000002), (144.844255, -38.373168800000002)] > That shows a polygon with 3 points, and two of them have the same > coordinates? That should be a valid polygon unless I'm missing > something. > > The nodes/way relating to that error are: > > <node id="172752298" timestamp="2009-02-25T17:02:53Z" > lat="-38.3731688" lon="144.844255"/> > <node id="172751478" timestamp="2009-02-25T17:02:53Z" > lat="-38.3731688" lon="144.8432851"/> > > <way id="16711763" timestamp="2009-02-25T17:02:53Z"> > <nd ref="172752298"/> > <nd ref="172751478"/> > <nd ref="172752298"/> > <tag k="created_by" v="Potlatch 0.5d"/> > <tag k="leisure" v="park"/> > </way> > > > Regards, > Josh > > > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Pymag-devel mailing list > Pym...@li... > https://lists.sourceforge.net/lists/listinfo/pymag-devel > |
|
From: henrik j. <hen...@gm...> - 2009-05-19 12:44:46
|
Actually they are discarded, they thing is that those warnings are not from those that make Mapsend crash. I still haven't been able to find out those that cause the problem. In Ingo's example from Bremen I know that there are only polygons from parks that cause problems. Far from all parks though because I can see most of them and they look correct. Maybe the easiest way is to make a osm file with only those parks and then try to find the bad ones. /Henrik On 19/05/2009, Josh <jo...@fe...> wrote: > Oops, I had another think about that, and realised a 3 pointed closed > polygon is actually more like a straight line ;) > > Is it possible to just discard bad polygons, seeing as they don't > render anyway, and just break the map? > > Josh > > > > Quoting jo...@fe...: > >> I've just tried the latest code from svn, with mixed results. Some of >> my maps have polygons rendering again, but others that warn about >> Improper polygons now crash Mapsend/Vantagepoint. >> >> Some of the warnings I can understand - polygons with only 2 points, >> or polygons that are 'open', but one example I saw has me confused... >> >> I got this warning one one tonight - >> WARNING Improper polygon found: [(144.844255, -38.373168800000002), >> (144.8432851, -38.373168800000002), (144.844255, -38.373168800000002)] >> That shows a polygon with 3 points, and two of them have the same >> coordinates? That should be a valid polygon unless I'm missing >> something. >> >> The nodes/way relating to that error are: >> >> <node id="172752298" timestamp="2009-02-25T17:02:53Z" >> lat="-38.3731688" lon="144.844255"/> >> <node id="172751478" timestamp="2009-02-25T17:02:53Z" >> lat="-38.3731688" lon="144.8432851"/> >> >> <way id="16711763" timestamp="2009-02-25T17:02:53Z"> >> <nd ref="172752298"/> >> <nd ref="172751478"/> >> <nd ref="172752298"/> >> <tag k="created_by" v="Potlatch 0.5d"/> >> <tag k="leisure" v="park"/> >> </way> >> >> >> Regards, >> Josh >> >> >> >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables >> unlimited royalty-free distribution of the report engine >> for externally facing server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Pymag-devel mailing list >> Pym...@li... >> https://lists.sourceforge.net/lists/listinfo/pymag-devel >> > > > > > ------------------------------------------------------------------------------ > Crystal Reports - New Free Runtime and 30 Day Trial > Check out the new simplified licensing option that enables > unlimited royalty-free distribution of the report engine > for externally facing server and web deployment. > http://p.sf.net/sfu/businessobjects > _______________________________________________ > Pymag-devel mailing list > Pym...@li... > https://lists.sourceforge.net/lists/listinfo/pymag-devel > |
|
From: henrik j. <hen...@gm...> - 2009-05-20 07:46:31
|
I found the problem. If the first vertex of the polygon is the same as the lower right corner of the bounding box it's of type 3. In the Bremen data set there was one polygon of type 3 which crashed MapsendLite. I have now disabled generation of type 3 polygons (they will still be generated but of another type) so it should work now. But I still don't know why type 3 makes it crash. /Henrik On 19/05/2009, henrik johansson <hen...@gm...> wrote: > Actually they are discarded, they thing is that those warnings are not > from those that make Mapsend crash. I still haven't been able to find > out those that cause the problem. In Ingo's example from Bremen I know > that there are only polygons from parks that cause problems. Far from > all parks though because I can see most of them and they look correct. > > Maybe the easiest way is to make a osm file with only those parks and > then try to find the bad ones. > > /Henrik > > On 19/05/2009, Josh <jo...@fe...> wrote: >> Oops, I had another think about that, and realised a 3 pointed closed >> polygon is actually more like a straight line ;) >> >> Is it possible to just discard bad polygons, seeing as they don't >> render anyway, and just break the map? >> >> Josh >> >> >> >> Quoting jo...@fe...: >> >>> I've just tried the latest code from svn, with mixed results. Some of >>> my maps have polygons rendering again, but others that warn about >>> Improper polygons now crash Mapsend/Vantagepoint. >>> >>> Some of the warnings I can understand - polygons with only 2 points, >>> or polygons that are 'open', but one example I saw has me confused... >>> >>> I got this warning one one tonight - >>> WARNING Improper polygon found: [(144.844255, -38.373168800000002), >>> (144.8432851, -38.373168800000002), (144.844255, -38.373168800000002)] >>> That shows a polygon with 3 points, and two of them have the same >>> coordinates? That should be a valid polygon unless I'm missing >>> something. >>> >>> The nodes/way relating to that error are: >>> >>> <node id="172752298" timestamp="2009-02-25T17:02:53Z" >>> lat="-38.3731688" lon="144.844255"/> >>> <node id="172751478" timestamp="2009-02-25T17:02:53Z" >>> lat="-38.3731688" lon="144.8432851"/> >>> >>> <way id="16711763" timestamp="2009-02-25T17:02:53Z"> >>> <nd ref="172752298"/> >>> <nd ref="172751478"/> >>> <nd ref="172752298"/> >>> <tag k="created_by" v="Potlatch 0.5d"/> >>> <tag k="leisure" v="park"/> >>> </way> >>> >>> >>> Regards, >>> Josh >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Crystal Reports - New Free Runtime and 30 Day Trial >>> Check out the new simplified licensing option that enables >>> unlimited royalty-free distribution of the report engine >>> for externally facing server and web deployment. >>> http://p.sf.net/sfu/businessobjects >>> _______________________________________________ >>> Pymag-devel mailing list >>> Pym...@li... >>> https://lists.sourceforge.net/lists/listinfo/pymag-devel >>> >> >> >> >> >> ------------------------------------------------------------------------------ >> Crystal Reports - New Free Runtime and 30 Day Trial >> Check out the new simplified licensing option that enables >> unlimited royalty-free distribution of the report engine >> for externally facing server and web deployment. >> http://p.sf.net/sfu/businessobjects >> _______________________________________________ >> Pymag-devel mailing list >> Pym...@li... >> https://lists.sourceforge.net/lists/listinfo/pymag-devel >> > |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X