Announcement

Collapse
No announcement yet.

Openstreet or garmin maps integration

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Openstreet or garmin maps integration

    Hi there, i have bee looking around this info a litle while, but i havent managed to get it working...have some one got any working integration betwen world wind java and open street maps!?

    Any help would be great!

  • #2
    This help?

    http://www.earthissquare.com/2009/02...er-for-wwjava/


    Earth is Square blog

    PUBLIC NOTICE AS REQUIRED BY LAW: Any use of this forum post, in any manner whatsoever, will increase the amount of disorder in the universe. Although no liability is implied herein, the consumer is warned that this process will ultimately lead to the heat death of the universe.

    Comment


    • #3
      There are already two versions of an OSM layer in the SDK - see layers.Earth.OpenStreetMapLayer and experimental.layers.Mercator.examples.OS MMapnikLayer
      My World Wind Java Blog & WW.net Plugins page

      Comment


      • #4
        OpenStreetMap Integration

        Originally posted by camicase82 View Post
        Hi there, i have bee looking around this info a litle while, but i havent managed to get it working...have some one got any working integration betwen world wind java and open street maps!?

        Any help would be great!
        The layers that come with WWJ work very well (OpenStreetMapLayer, OSMMapnikTransparentLayer). However, if you want to stand up OSM on a standalone LAN and/or you want to tune the layers that appear in the OSM tiles, it isn't too hard to put together an OSM tile server that works well with WWJ.

        Basic steps (not WWJ unique):
        - Find a server (or configure a VM) with a spare 100-200 Gb of space.
        - Download OSM data for area of interest, or entire world
        - Load OSM data into PostgreSQL, build Mapnik server using instructions at: http://wiki.openstreetmap.org/wiki/Mapnik
        - Install TileCache w/ mod_python
        Configuring for WWJ:
        - After generating osm.xml file, change overall projection to EPSG:4326 (1)
        - Set background to transparent (1)
        - Turn off layers you don't want (e.g., text labels, solid filled areas, coastal boundaries, ...) (2)
        - Add layer definition to tilecache.cfg (3)
        - Create xml file for WWJ that defines the layer (4)

        (1) After generating the osm.xml file for Mapnik, you will probably want to copy it (call it osm-thin.xml) and make changes. The most important change is at the top of the file to turn it into a long-lat format rather than Mercator, and give it a transparent background (if desired):
        <Map bgcolor="transparent" srs="+proj=longlat +datum=WGS84">


        (2) The standard OSM tile has a lot of filled polygons that can obscure underlying imagery. It will also have text information that duplicates placename data. You may want less information - to get there just turn off layers in osm-thin.xml. One example that is limited to just streets and little else involves turning off: world, coast-poly, builtup, leisure, sports-grounds, water-areas, buildings, placenames, text, text-poly, and area-text.

        (3) A layer definition for TileCache that works with OSM/Mapnik (assuming you have changed to longlat from Merc) looks like this:
        # OpenStreetMap - transparent background, no text
        [osm_thin]
        type=Mapnik
        mapfile=/maps/osm/osm-thin.xml
        Size=512,512
        extension=png
        metaTile=true
        Note that tiles are defined as 512x512 here. This results in slower loading tiles than the 256x256 of the standard OSM server. For OpenLayers this works great. However, WorldWind layers look much nicer at the higher resolution. If you look at the gov.nasa.worldwind.layers.Mercator.examp les.OSMMapnikTransparentLayer, you will see quite a bit of aliasing due to the reduced (256x256) resolution.

        The metaTile directive helps keep labels from coming out oddly, but also negatively impacts performance in generating tiles.

        (4) A WWJ configuration file that pulls the tiles, OSMOverlayerLayer.xml looks like this:
        <?xml version="1.0" encoding="UTF-8"?>
        <!--OpenStreetMap Layer: no labels or filled areas, transparent background -->
        <Layer version="1" layerType="TiledImageLayer">
        <DisplayName>OpenStreetMap Overlay</DisplayName>
        <Service serviceName="WWTileService">
        <URL>http://osmserver.mydomain.org/tilecache/tilecache.py</URL>
        </Service>
        <RetrievePropertiesFromService>true</RetrievePropertiesFromService>
        <DatasetName>osm_thin</DatasetName>
        <DataCacheName>Earth/OSM-Tiles</DataCacheName>
        <ImageFormat>image/png</ImageFormat>
        <AvailableImageFormats>
        <ImageFormat>image/png</ImageFormat>
        <ImageFormat>image/dds</ImageFormat>
        </AvailableImageFormats>
        <FormatSuffix>.png</FormatSuffix>
        <NumLevels count="19" numEmpty="0"/>
        <TileOrigin>
        <LatLon units="degrees" latitude="-90" longitude="-180"/>
        </TileOrigin>
        <LevelZeroTileDelta>
        <LatLon units="degrees" latitude="180" longitude="180"/>
        </LevelZeroTileDelta>
        <TileSize>
        <Dimension width="512" height="512"/>
        </TileSize>
        <Sector>
        <SouthWest>
        <LatLon units="degrees" latitude="-90" longitude="-180"/>
        </SouthWest>
        <NorthEast>
        <LatLon units="degrees" latitude="90" longitude="180"/>
        </NorthEast>
        </Sector>
        <UseTransparentTextures>true</UseTransparentTextures>
        <RetrievalTimeouts>
        <ReadTimeout>
        <Time units="milliseconds" value="30000"/>
        </ReadTimeout>
        </RetrievalTimeouts>
        </Layer>

        Note that you have to replace osmserver.mydomain.org with wherever you stood up your OSM/TileCache server. Add the file reference to your worldwind.layers.xml.

        Note that TileCache can serve up the same tiles using WMS in addition to using the tile naming convention (T/X/Y).

        Xander

        Comment


        • #5
          Thanks a loot guys!!!! u been a great help!!!!

          Comment


          • #6
            @Xander : nice tuto ! this should be in the wiki !
            http://gplus.to/BrunoSpy
            http://www.ohloh.net/p/videso3d

            Comment


            • #7
              Why would you use OpenStreetMap if there is Google Maps?

              There is no extreme answer with respect to which one is better. These two have the same number of similitudes as contrasts. They depend on various essentials, yet they unravel a similar fundamental human need to know "WHERE". The key distinction between these two mapping situations is an insightful "Open" versus "Shut" approach with how the information is gathered and dispersed.

              OpenStreetMap was conceived in 2004 in the UK, when guide information sources were constrained by private and administrative players. They were costly and exceedingly prohibitive which made them available just by huge organizations. The thought behind OSM was to take care of this issue by utilizing a Wikipedia-like model and make a free, editable guide of the world tried altogether by the intentional endeavors of online masses. The convenience and the requirement for open guide information sources was high to the point that today OSM has over 2.2 million enlisted clients who are hand making a nitty gritty guide of the whole world.

              Free Garmin Map Update Download 2019

              This publicly supporting methodology has been recognized by Google which additionally went to clients so as to improve its maps. In 2008, the organization presented Google Map Maker, which utilized a comparable methodology and interface to the OSM so as to assemble neighborhood information from individuals willing to contribute where guide information was difficult to buy.

              The principle distinction between these two administrations is that each alter you make to OSM is claimed by you and the network, while each change you make to Google Maps… will be possessed by Google.

              The OSM people group is the thing that makes the undertaking so exceptional. A great many volunteers from all around the world are refreshing the guide as their reality changes around them. Each update is promptly unmistakable to every single other client and is form controlled. There are no corporate guide cycle discharges, endorsements and KPIs that are run of the mill to huge associations.

              Comment

              Working...
              X