Tagged: ,

Viewing 15 posts - 106 through 120 (of 262 total)
  • Author
    Posts
  • #34186

    mbe57
    Participant

    Mhh… indeed :-)
    Do you have some stats how many Locus download versus others OAM handles?
    If that number is significant, which I would expect, then I would offer two distinct data packages:
    – Locus
    [name]_oam.osm.map
    [name]_oam.osm.db
    – others
    [name]_oam.map
    [name]_oam.poi
    Cheers
    Michael
    PS: [name]_oam.map and [name]_oam.osm.map are identical except for their names, hence only ONE production per map.

    #34188

    cebewee
    Participant

    This would be an option if the storage can be afforded. Another option would be using _oam.osm.map for all applications.

    Unfortunately, locus-actions seem to not support renaming files.

    2 users thanked author for this post.
    #34190

    mbe57
    Participant

    That would mean:

    [name]_oam.osm.map
    [name]_oam.osm.db
    [name]_oam.osm.poi

    Nice, I think!

    1 user thanked author for this post.
    #34193

    mictie
    Participant

    Sounds good!

    #34227
    ChristianK
    ChristianK
    Keymaster

    The pois work fine on Locus.

    HOWEVER: I will have to work through the poi-mapping cause there are numerous pois with no real value in the files just bloating the PoiDB up to uselessness
    Like hundreds of guideposts tagged as touris_information, countless old walls tagged a ruins, viewpoints whereever one took a selfie, amenity parkings wherever someone can stop a car – aso.

    I will drop a lot of Pois down to a number really usefull for hiker/cyclists
    This will mean another tag-transform/osmfilter, time consuming, process bevore starting the poi-writer.

    4 users thanked author for this post.
    #34229
    Tobias
    Tobias
    Moderator

    I will have to work through the poi-mapping

    I thought about this before as there are also POIs in the maps which aren’t in the POI database.
    More POIs in the database than in the maps are alright for e.g. OruxMaps, as only those that are searched for are shown in the maps.

    Developer of Elevate mapstyle

    #34388
    ChristianK
    ChristianK
    Keymaster

    All maps with both Mapsforge/Locus POIs are online now.
    Naming is

    [name]_oam.osm.map
    [name]_oam.osm.db
    [name]_oam.osm.poi

    Zip files are named as [name].zip – to prevent confusion ;-)
    Both POI files are are included in the map.zip file.
    Well, the extra poi.zip is’nt necessary any longer, I will remove this download option in some weeks.

    Locus Poi files for Germany/Europe are new with filtering.
    For all other regions Locus-pois are the ones from March-update and converted w/o filtering.

    Why both POI files are included ?
    Well, we – the freaks – spend hours and hours with maping and developing tools and we know what we are doing.
    However, the usual user don’t have time/resources to go into the depth of making/using VectorMaps
    these poeple want to navigate with their backpacks on or riding their cyles and simply enjoy outdoor without getting lost.
    So – KISS is the way to go for me.
    So – both files are included, and yes – this eats bandwidth but this is not an issue in urban areas with modern G4 structure while in more remote areas the poi files are small so its neither an issue there.

    The pois in the poi-files are not the same than on the maps.
    WHY?? : For me it makes no sense to include Viewpoints, Peaks, Ruins without Names/Descriptions
    every little Parking, etc.
    Its fine in the map but NOT in the poi file where people search for Points and a huge, useless result_set is returned.
    Basicly its a problem of “overmapping” in the OSM Database.
    In the area where I life there literally EVERY Parking lot where a car can be squeezed in is mapped.
    Every viewpoint where someone took a selfy. At Dürnstein every broken down wall is mapped as a seperate “Ruin”.
    in short – without filtering this is a lot of useless information.

    As usual: everything may be discussed here.

    9 users thanked author for this post.
    #34390

    mictie
    Participant

    Great! Working!
    Thank you so much for your hard work!
    BTW: what is the ‘filtering’ you mentioned?

    #34392
    ChristianK
    ChristianK
    Keymaster

    Filtering means that not all pois from the OSM database are included in the OAM pois.

    Here are the rules:
    (*.noname, no_*, *private* – Tag/Values are NOT included in the POI database)

    
    
    <?xml version="1.0"?>
    <translations>
    
    	<translation>
    		<name>remove unec. Tags</name>
    		<description>remove values from to reduce effects of "common value bug" in mapsforge and confusing information in POIs-DB</description>
    		<match mode="or">
    			<tag k="oneway" v="no"/>
    			<tag k="one" v="no"/>
    			<tag k="bridge" v="no"/>
    			<tag k="tunnel" v="no"/>
    			<tag k="noexit" v=".*"/>	
    			<tag k="access" v="yes"/>
    			<tag k="building" v="no"/>
    			<tag k="ladder" v="no"/>			
    			<tag k="lockable" v="no"/>	
    			<tag k="lockable" v="yes"/>	
    			<tag k="raised" v="no"/>
    			<tag k="raised" v="yes"/>		
    			<tag k="fixme|FIXME" v=".*"/>
    			<tag k="source" v=".*"/>
    			<tag k="source(:.*)" v=".*"/>
    			<tag k="width" v=".*"/>
    			<tag k="smoothness" v=".*"/>
    			<tag k="created_by" v=".*"/>
    			<tag k="wikipedia" v=".*"/>
    			<tag k="wikidata" v=".*"/>
    			<tag k="official_name" v=".*"/>
    			<tag k="alt_name" v=".*"/>
    			<tag k="alt_name(:.*)" v=".*"/>			
    			<tag k="note(.*)" v=".*"/>
    			<tag k="is_in" v=".*"/>
    			<tag k="is_in(:.*)" v=".*"/>
    			<tag k="gnis(:.*)" v=".*"/>
    			<tag k="ideewfs(:.*)" v=".*"/>			
    			<tag k="gns(:.*)" v=".*"/>
    			<tag k="ngbe(:.*)" v=".*"/>	
    			<tag k="iemv(:.*)" v=".*"/>		
    			<tag k="naptan(:.*)" v=".*"/>
    			<tag k="NaPTANAreaCode" v=".*"/>
    			<tag k="ele(:.*)" v=".*"/>	
    			<tag k="seamark(:.*)" v=".*"/>		
    			<tag k="munro" v="no"/>
    			<tag k="roof(:.*)" v=".*"/>
    			<tag k="old_(.*)" v=".*"/>					
    			<!--tag k="opengeodb(:lat|:lon)" v=".*" /-->
    			<tag k="uic_(.*)" v=".*" />
    			<tag k="uic(:.*)" v=".*" />
    		</match>
    		<output>
    			<copy-unmatched/>
    		</output>
    	</translation>	
    
    	<translation>
    		<name>noname historic</name>
    		<description>only viewpoints, peaks, volcanos, etc with name or description or url survive in POI</description>
    		<match>
    				<tag k="historic" v="castle|memorial|monument|ruins|wayside_cross|wayside_shrine|boundary_stone"/>
    				<notag k="name|description" v=".*"/>
    		</match>
    		<output>
    			<copy-all/>
    			<tag k="historic" v="historic_noname"/>
    		</output>
    	</translation>
    
    	<translation>
    		<name>noname tourism</name>
    		<description>only viewpoints, peaks, volcanos, etc with name or description or url survive in POI</description>
    		<match>
    				<tag k="tourism" v="viewpoint|attraction"/>
    				<notag k="name|description" v=".*"/>
    		</match>
    		<output>
    			<copy-all/>
    			<tag k="tourism" v="tourism_noname"/>
    		</output>
    	</translation>
    	
    	<translation>
    		<name>noname place</name>
    		<description>only viewpoints, peaks, volcanos, etc with name or description or url survive in POI</description>
    		<match>
    				<tag k="place" v=".*"/>
    				<notag k="name|description" v=".*"/>
    		</match>
    		<output>
    			<copy-all/>
    			<tag k="place" v="place_noname"/>
    		</output>
    	</translation>	
    	
    	<translation>
    		<name>noname natural</name>
    		<description>only viewpoints, peaks, volcanos, etc with name or description or url survive in POI</description>
    		<match>
    				<tag k="natural" v="peak|volcano|spring"/>
    				<notag k="name|description" v=".*"/>
    		</match>
    		<output>
    			<copy-all/>
    			<tag k="natural" v="natural_noname"/>
    		</output>
    	</translation>
    	
    	<translation>
    		<name>noname amenity</name>
    		<description>only viewpoints, peaks, volcanos, etc with name or description or url survive in POI</description>
    		<match>
    				<tag k="amenity" v="parking"/>
    				<notag k="name|description|operator|access|ref" v=".*"/>
    		</match>
    		<output>
    			<copy-all/>
    			<tag k="amenity" v="no_parking"/>
    		</output>
    	</translation>	
    
    	
    	<translation>
    		<name>private amenity</name>
    		<description>only viewpoints, peaks, volcanos, etc with name or description or url survive in POI</description>
    		<match>
    				<tag k="amenity" v="parking"/>
    				<tag k="access" v="private|no"/>
    		</match>
    		<output>
    			<copy-all/>
    			<tag k="amenity" v="parking_private"/>
    		</output>
    	</translation>	
    	
    </translations>
    
    
    #34394
    ChristianK
    ChristianK
    Keymaster

    BTW:

    Hi Community: Please test the Locus poi DB with the new LoPoi Beta-Function:
    IMO the Python converter_script works like charm, even with the BetaLoPois
    IT’S INCREDIBLE, amazing !!

    https://docs.locusmap.eu/doku.php?id=de:manual:user_guide:points:locus_maps_pois
    https://docs.locusmap.eu/doku.php?id=manual:user_guide:points:locus_maps_pois

    Please try to find bugs and report it – thanks

    1 user thanked author for this post.
    #34396

    mictie
    Participant

    Ok, understand! Thank you!

    • This reply was modified 6 months ago by  mictie.
    #34399
    ChristianK
    ChristianK
    Keymaster

    @cebewee

    Which tag/value would you need in the poi database to get the Link to OSM running in Locus
    eg
    osm_id=[ID][way|node]

    or a ready made link like
    osm_id_link=https://www.openstreetmap.org/node/6880636128

    ??

    Edit: Next version of the pois will include this tag/value:
    osm_id_link=https://www.openstreetmap.org/[node|way]/[osm_ID]
    Perl script is running fast and every modification|addition is possible

    • This reply was modified 6 months ago by ChristianK ChristianK.
    2 users thanked author for this post.
    #34426

    vsa
    Participant

    Add to Locus db POI for this tag, please:
    building=bunker
    military=bunker

    #34428

    Lmu
    Participant

    Nice work, thank you!
    I started trying one map with POIs today. First tests are going fine.

    It’s not a bug, but there are some categories in original LoMaps that are interesting when doing some bicycle trips but which are missing here. If possible it would be nice to add them:
    – campsites (tourism=camp_site and eventually tourism=caravan_site)
    – bicycling shops (shop=bicycle but If remember correctly original LoMaps gather also other sport shops in the same category)

    #34439
    ChristianK
    ChristianK
    Keymaster

    – campsites (tourism=camp_site and eventually tourism=caravan_site)
    – bicycling shops (shop=bicycle but If remember correctly original LoMaps gather also

    Thats a bug….
    Looking deeper into the poi converter I found there is a serious problem with the interface between OAM-poi-mapping LoPoi structure we have to sort out.

    Thanks for bringing this to my attention.

    Best regards
    Christian

Viewing 15 posts - 106 through 120 (of 262 total)

You must be logged in to reply to this topic.