Re: [sumo-user] OSM tags used by polyconvert (UNCLASSIFIED)

[Daniel K. <d.k...@go...>]

Hello Dawne,

yes, it was my fault. I only added the "polygon"-type to the nodes, not to
the edges. This is now fixed (rev 8890), I hope the also added tests prove
it correctly.

I also added a boolean option to POLYCONVERT which lets use the value from a
"name"-atribute as you requested. You have to set the option --osm.use-name.
Then the value of "name" will be used, if given, otherwise still the id.

You know, POLYCONVERT patches are not that complicated. Did you investigate
the recent (0.12) simulation version? Any comments/problems that occured?

sincerely,
Daniel


2010/7/15 Deaver, Dawne CIV USA AMC <daw...@us...>

> Classification: UNCLASSIFIED
> Caveats: NONE
>
> Daniel,
>
> Thanks so much for your response.  This is a big help.
>
> I downloaded the "nightly build" and ran the polyconvert on my existing
> OSM database (the example in my original post), but it did not import my
> polygons.  I'm not sure how to tell if this is rev 8882.
>
> Secondly, I did go back and alter some of my tags to use
> boundary.overpass and defined the rendering in a typemap as you
> suggested and this works wonderfully.
>
> Now, for a related question/request:
>
> Would it be difficult to also import and print out the tag k="name"
> v="whatever"?
>
> I noticed that the typemap seems to override any "name" field.  Also I
> noticed that guisim labels the polygon using "id" not the "name" field
> as defined in the typemap.  It would be much more useful if the name was
> the actual name defined in OSM, and if that was the label used in
> guisim.  I am trying to keep track of unique intersections that obscure
> the view of vehicle in order to properly visualize the traffic from the
> air.
>
> I realize this is a new feature request, so if it's too much trouble,
> please let me know, or possibly suggest to me the section of source code
> that I might modify myself.
>
> Thanks again!
> -Dawne
>
> -----Original Message-----
> From: Daniel Krajzewicz [mailto:d.k...@go...]
> Sent: Thursday, July 15, 2010 2:36 AM
> To: Deaver, Dawne CIV USA AMC
> Cc: sum...@li...
> Subject: Re: [sumo-user] OSM tags used by polyconvert (UNCLASSIFIED)
>
> Hello Dawne!
>
> I think the problem is that a polygon must have one of the following
> keys:
> waterway, aeroway, aerialway, power, man_made, building, leisure,
> amenity, shop, tourism, historic, landuse, natural, military, boundary,
> or sport
>
> That's the way how polyconvert determines whether it is something that
> can be displayed as a polygon.
>
> I changed this yesterday, also allowing "polygon". To give it a style
> (definition how it shall be rendered) you probably have to add something
> like the following to your typemap (you have seen typemaps already?):
>
>    <polytype id="polygon.overpass" name="overpass" color=".2,.9,.2"
> layer="-10"/>
>
> It is available since yesterday in the SVN, revision 8882.
> You can also add a tag to your OSM definition, then you could also use
> the release version of polyconvert. I suppose you'd have to add for
> example:
>   <tag k="boundary" v="overpass"/>
>
> sincerely,
> Daniel
>
>
>
>
> 2010/7/12 Deaver, Dawne CIV USA AMC <daw...@us...>
>
>
>        Classification: UNCLASSIFIED
>        Caveats: NONE
>
>
>
>        We would like to import polygons from an OpenStreetMap (OSM)
> network
>        that has been edited using the Java OpenStreetMap editor.  In
> JOSM, I
>        have drawn polygons to mark areas where there are overpasses
> that
>        obscure an edge below it and I wish to import these polygons
> using
>        Sumo's polyconvert code.  We have tagged these new polygons
> using a
>        customized JOSM pre-set to define certain attributes.  (I wanted
> to
>        create my own pre-set so that our new polygons can never be
> mistaken or
>        confused with polygons that may have already existed in the OSM
>        database.)  So in the OSM file, my polygons appear as:
>
>
>
>         <way id="-974" action="modify" timestamp="2010-07-08T13:25:07Z"
>        visible="true">
>
>           <nd ref="-752"/>
>
>           <nd ref="-750"/>
>
>           <nd ref="-753"/>
>
>           <nd ref="-755"/>
>
>           <nd ref="-752"/>
>
>           <tag k="polygon" v="overpass"/>
>
>           <tag k="name" v="p0045"/>
>
>           <tag k="class" v="polygon"/>
>
>         </way>
>
>
>
>        The problem is that my polygons were not imported using
> polyconvert, so
>        I am assuming I have not set the tags properly.  I have looked a
> bit at
>        examples of polygons that do get imported and also have looked
> at the
>        source code for polyconvert, but I have not been able to
> discover how I
>        should set my tags in order for polyconvert to recognize and
> import my
>        polygons.  I can easily change my pre-set definition to apply
> more
>        appropriate tags.
>
>
>
>        Any help or advice is appreciated.
>
>
>
>        Many thanks,
>
>        -Dawne
>
>        Classification: UNCLASSIFIED
>        Caveats: NONE
>
>
>
> ------------------------------------------------------------------------
> ------
>        This SF.net email is sponsored by Sprint
>        What will you do first with EVO, the first 4G phone?
>        Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
> <blockedhttp://p.sf.net/sfu/sprint-com-first>
>         _______________________________________________
>        sumo-user mailing list
>        sum...@li...
>        https://lists.sourceforge.net/lists/listinfo/sumo-user
> <blockedhttps://lists.sourceforge.net/lists/listinfo/sumo-user>
>
>
>
> Classification: UNCLASSIFIED
> Caveats: NONE
>
>
>