Betrachte 13 Beiträge - 1 bis 13 (von insgesamt 13)
  • Autor
    Beiträge
  • #34990

    DanyRider
    Teilnehmer

    In my area (near Cannes south of France), all guideposts have an identification number, and this number is reported on the official topo maps of the French Geographic Institute (IGN). Example here n°251 :


    This is really useful and I would like to reproduce this in OAM.
    Currently, in the „Elevate theme“, guideposts symbols appear at zoom level 16 and name+ele caption at zoom 17.
    My objective is to replace the elevation with the reference number, and set the min zoom levels at 15.
    In the OSM database, the identification numbers of these guideposts are (most of the time) stored with the tag „ref“

    
    <tag k='tourism' v='information' />
    <tag k='information' v='guidepost' />
    <tag k='name' v='Col de Roua' />
    <tag k='ref' v='251' />
    

    So I have modified guidepost rendering lines as follows, in the Elevate.xml file :

    
    <rule e="any" k="information" v="guidepost" zoom-min="15">
      <symbol id="s_guidepost" src="file:ele_res/s_guidepost.svg" symbol-scaling="size" symbol-height="16" symbol-width="16" />
      <rule e="any" k="*" v="*" zoom-min="15">
        <caption k="name" symbol-id="s_guidepost" position="above" font-size="10" font-style="bold" fill="#734A08" stroke="#E5FFFFFF" stroke-width="2" />
        <caption k="ref" priority="-5" symbol-id="s_guidepost" position="below" font-size="10" font-style="bold" fill="#734A08" stroke="#E5FFFFFF" stroke-width="2" />
      </rule>
    </rule>
    

    Unfortunately, the tag „ref“ seems not to be recognized by mapsforge and is not rendered, and the guideposts symbols & name appear at zoom 16, not 15 as specified.
    Finally, I understood that the min zoom level is forced at 16 during map creation in the tagmapping-urban.xml file :
    <osm-tag key="information" value="guidepost" zoom-appear="16"/>

    So I have 2 questions :
    1) Could you please set the zoom-appear at 15 in tagmapping file for future updates of OAM maps (at least southern France and western Alps) ?
    2) Is there a way to transfer the „ref“ tag to mapsforge maps ?

    Thank you

    Regards
    Daniel

    • Dieses Thema wurde vor vor 3 Monaten, 3 Wochen von  DanyRider bearbeitet.
    • Dieses Thema wurde vor vor 3 Monaten, 3 Wochen von  DanyRider bearbeitet.
    #34998
    ChristianK
    ChristianK
    Verwalter

    Hi Daniel,

    From my side this node is included in the preprozessed osm file used for feeding the mapwriter.
    REF is included for _every_ object in MapsForge

    
    	<node id="5884561926" lat="44.02565" lon="6.8651207" version="1" timestamp="1970-01-01T00:59:59Z" changeset="1">
    		<tag k="ref" v="250"/>
    		<tag k="name" v="Col de Roua"/>
    		<tag k="hiking" v="yes"/>
    		<tag k="tourism" v="information"/>
    		<tag k="information" v="guidepost"/>
    	</node>
    
    

    As for zoom-appear:
    It would be possible to include the guideposts fromn ZL15 on
    IF
    @tobias modifies the Ellevate that guideposts with REF are rendered at 15, all others at 16.

    Reason: There are so many guidepost, a growing issue with most Tags in OSM.

    1 Teilnehmer(n) gefällt dieser Beitrag
    #35005
    Tobias
    Tobias
    Moderator

    REF is included for _every_ object in MapsForge

    AFAIK in maps up to V4 only for ways, and ELE for POIs. REF has to be tag-transformed to e.g. addr:housenumber.
    I have to check again if it makes sense to render guideposts earlier (even with refs), it might get pretty crowded. But maybe it makes sense to include those with the waymarks layer?

    Developer of Elevate mapstyle

    2 users thanked author for this post.
    #35024

    DanyRider
    Teilnehmer

    Thank you for your answers.
    @tobias, if my understanding is correct, your proposal is to tag-transform the tag ref = „nnn“ to the tag rwn_ref=“n“
    and on the final map, the reference will appear as a „hike_node“, like these :

    Well, to me this seems to be a good approach … this feature can be activated/deactivated with the „hiking routes“ in the RenderTheme menu.
    Just for information, the guidepost references in my region have the following format :
    1 to 4 numbers optionality followed by 1 letter a to e. This should be mached by following regexp :
    ^[0-9]{1,4}[a-eA-E]?
    Thank you for your great work :-) You have by far the best looking and most comprehensive of all OSM maps !

    Regards
    Daniel

    • Diese Antwort wurde vor vor 3 Monaten, 3 Wochen von  DanyRider bearbeitet.
    #35039
    Tobias
    Tobias
    Moderator

    if my understanding is correct, your proposal is to tag-transform the tag ref = “nnn” to the tag rwn_ref=”n”

    No, I just thought it might be a good idea to show these guideposts with refs (transformed to addr:streetnumber) only on lower zoom levels, if waymarks are activated in the mapstyle options.

    Developer of Elevate mapstyle

    #35041

    DanyRider
    Teilnehmer

    Yes it makes sense … seems to be a good idea.
    It’s up to you to decide if you want to implement this modification.
    Thank you.

    Regards
    Daniel

    #35096
    ChristianK
    ChristianK
    Verwalter

    Done, will be included in next update = end of next week.

    tourist=Information, information=guidepost are now included from ZL15

    
    	<translation>
    		<name>information=guidepost ref2addr</name>
    		<description>mapsforge doesnt address "ref" on NODES so ref is transformed to "addr:housenumber"</description>
    		<match mode="and" type="node">
    			<tag k="information" v="guidepost"/>
    			<tag k="ref" match_id="gpost_ref" v="(^[A-Z,a-z,0-9]{1,5})"/>
    		</match>
    		<output>
    			<copy-all/>
    			<tag k="addr:housenumber" from_match="gpost_ref" v="{1}"/>
    		</output>
    	</translation>	
    
    
    #35109
    ChristianK
    ChristianK
    Verwalter

    Well…..

    Tested the transform rule and found _lots_ of refs like this:

    
    <node id="618578607" version="1" timestamp="1970-01-01T00:00:01Z" changeset="1" lat="28.6035736" lon="-17.8586639">
        <tag k="ref" v="PR LP 14 / SL EP 103"/>
        <tag k="name" v="PR LP 14.1 / SL LP  103"/>
        <tag k="tourism" v="information"/>
        <tag k="information" v="guidepost"/>
      </node>
    

    And in most cases the value in ref tag is the ref of the route where the guideposts are situated and not the number of the guidepost.
    I’m shure that rendering the few correct tagged refs will be sunk in this ocean of garbage, sorry.

    • Diese Antwort wurde vor vor 3 Monaten, 3 Wochen von ChristianK ChristianK bearbeitet.
    • Diese Antwort wurde vor vor 3 Monaten, 3 Wochen von ChristianK ChristianK bearbeitet.
    • Diese Antwort wurde vor vor 3 Monaten, 3 Wochen von ChristianK ChristianK bearbeitet.
    #35117
    Tobias
    Tobias
    Moderator

    I’m shure that rendering the few correct tagged refs will be sunk in this ocean of garbage, sorry.

    So you won’t add this?

    Developer of Elevate mapstyle

    #35146

    DanyRider
    Teilnehmer

    Hi,
    If we focus on refs with strictly this format (^[0-9]{1,3}[a-eA-E]?) the situation will be much more clear.
    I have extracted all guideposts with ref=“^[0-9]{1,3}[a-eA-E]?“ from Geofabrik OSM databases of France, Italy and Alps. There are exactly 3682 guideposts with such refs, and 2086 of them are concentrated in my small region of Alpes-Maritimes :

    So if you tag-transform these refs to addr:housenumber only for maps of Southern France & Western Alps, I think that these correct tagged refs will not be sunk in an ocean of garbage :-)

    I have created a small map with guideposts references rendered at zoom level 15. Hereunder a focus on an area with a high concentration of guide posts : to me it is not really crowded …

    So min zoom level 15 should be acceptable.

    Tell me if this approach seems acceptable for you.
    Thanks

    Regards
    Daniel

    #35175
    ChristianK
    ChristianK
    Verwalter

    So you won’t add this?

    Lets see what happens.
    I added the rule from my posting obove

    #35377

    DanyRider
    Teilnehmer

    Hi,
    I have downloaded the latest OAM map, and thanks to a small modification of the RenderTheme xml file, the guideposts references are now displayed at ZL 15 & 16.

    		<rule e="any" k="information" v="guidepost" zoom-min="15">
    			<symbol id="s_guidepost" src="file:ele_res/s_guidepost.svg" symbol-scaling="size" symbol-height="16" symbol-width="16" />
    			<rule e="any" k="*" v="*" zoom-min="15" zoom-max="16">
    				<caption k="addr:housenumber" symbol-id="s_guidepost" display="always" position="above" font-size="11" font-style="bold" fill="#ffff00" stroke="#E5000000" stroke-width="2" />
    			</rule>
    			<rule e="any" k="*" v="*" zoom-min="17">
    				<caption k="name" symbol-id="s_guidepost" position="above" font-size="10" font-style="bold" fill="#734A08" stroke="#E5FFFFFF" stroke-width="2" />
    				<caption k="ele" priority="-5" symbol-id="s_guidepost" position="below" font-size="10" font-style="bold" fill="#734A08" stroke="#E5FFFFFF" stroke-width="2" />
    			</rule>
        </rule>

    null

    Thank you very much, this will be useful in my region!

    Regards
    Daniel

    3 users thanked author for this post.
    #37464
    Tobias
    Tobias
    Moderator

    if my understanding is correct, your proposal is to tag-transform the tag ref = “nnn” to the tag rwn_ref=”n”

    No, I just thought it might be a good idea to show these guideposts with refs (transformed to addr:streetnumber) only on lower zoom levels, if waymarks are activated in the mapstyle options.

    I added this in the latest Elevate version 4.4.1

    Developer of Elevate mapstyle

    2 users thanked author for this post.
Betrachte 13 Beiträge - 1 bis 13 (von insgesamt 13)

Sie müssen angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.