Real time 3D map using WebGL

Thanks Cactusbone!

Suggestion:
use for building=garage without height=* as default height=3 meter
use for building=greenhouse without height=* as default height=4.5 meter

We’re already using mapping tables for height generation :

50 → 75 meters for [‘tower’, ‘skyscraper’]
10 → 20 meters for [‘apartments’, ‘dormitory’, ‘hospital’, ‘hotel’, ‘commercial’, ‘industrial’, ‘warehouse’, ‘church’, ‘cathedral’, ‘civic’, ‘public’, ‘barn’, ‘hangar’]
3 → 4 meters for [‘roof’, ‘canopy’, ‘cabin’, ‘shed’, ‘hut’, ‘garage’, ‘garages’]
7 → 10 meters for other values

Greenhouse automatically uses glass material on both walls and roofs

I know :wink:

I did it already 2008 for 3D model of Hamburg: http://www.hamburg.de/contentblob/407336/data/3-d-stadtmodell.pdf
I introduced the term “Level of detail”. In LOD 1 is the representation of buildings only by use of building outline and estimated height depend on use.
I defined also the table with heights for different building uses based on realistic values for heght.

OSM definition allows very detailed and more realistic height estimation. I give you simply my experience.

Btw:
Realistic LOD 2 from Hamburg - http://www.maxon.net/uploads/pics/02_02.jpg

It works now. :slight_smile:

  1. Following polygon are not rendered:
    http://www.openstreetmap.org/way/278201017
    http://www.openstreetmap.org/way/168324687

What´s the reason?

  1. This city: http://www.openstreetmap.org/#map=15/51.2200/18.5714 is an experiment area with some young users from the geodesy gymnasium Wielun.
    Is it possible to render this area in shorter time periods? Also as a kind of experiment for You.
    In the psychological point of view is it difficult to motivate young people during such actions when the results are visible after 24 hours.

Hi Marek,

both ways are not valid in JOSM (self intersecting polygons) i fixed them a few minutes ago.

Thanks a lot cmif4! Still the same small mistakes :wink:

Dear f4 friends, please look here:
http://demo.f4map.com/#lat=51.2174803&lon=18.5735399&zoom=21&camera.theta=63.908&camera.phi=54.032
http://www.openstreetmap.org/way/249686837
http://www.openstreetmap.org/way/249686821

What is the reason for?

@marek: adding tags just to crash f4map is still kind of tagging for the renderer :stuck_out_tongue:


Initializing translations with locale en api.js:1
Shader precision:
precision highp float;
precision lowp int;
 api.js:1
Connecting to watcher index.js:1
event.returnValue is deprecated. Please use the standard event.preventDefault() instead.
Translations initialized successfully for locale en api.js:1
Connected to watcher index.js:1
[GSFN.Widget.Shell.initialize] loader.js?_=1399143003066:1
[GSFN.Widget.initialize] 5379 -- jquery version: 1.6.4 loader.js?_=1399143003066:1
roof shape not handled skillion  
Object
building:colour: "#c1bfb3"
building:part: "yes"
errors: Array[1]
f4roof: "skillion "
height: "8"
osm_id: "278768335"
parentBuilding: "polygon#278768331"
parentBuildingOsmId: "278768331"
querytype: "polygon"
roof:colour: "#6c8174"
roof:height: "0.5"
roof:shape: "skillion "
way: Object
way_area: 41.1732
z_order: 0
__proto__: Object
 api.js:1
Uncaught TypeError: Cannot read property 'name' of undefined api.js:1
XHR finished loading: GET "http://osmsync.f4map.com/state.json". api.js:1


(above link, using ubuntu 14.04 with chromium)

@marek: looks like there is a space too much in 'skillion ’

btw, bug reports are also welcome for the other webgl map http://opensciencemap.org/s3db/#scale=19&rot=101&tilt=52&lat=51.217&lon=18.573

@cmif: How about using your “Watcher” to catch unhandled exceptions and send them to some CrashLytics server?

j3d,thank you!
The progress of opensciecemap is really impressive! I didn´t realize that.
Let´s discuss monday about bug reports and pushing of your project.

Best regards,
Marek

Edit:
how to zoom in/ zoom out
how to rotate the map

?

What´s wrong here:

http://demo.f4map.com/#lat=51.2223190&lon=18.5715905&zoom=20&camera.theta=66.879&camera.phi=-144.088
http://www.openstreetmap.org/way/278530381

Over,
Marek

How to add low-resolution phototextures (1 pixel=20cm) to the buildings? I collect in the next time some streets in Wielun.
Idea: I add link to the the corner edge which is beginning of building outline. Phototexture is “valid” along straight way to the next corner point with change of direction with more than 10°.

Marek, view controls in vtm are the usual scroll-wheel to zoom and right click for tilt/rotate. Though on mac input handling needs some work. Last time I tried, scrolling was over-sensitive and the right mouse button was somehow missing :slight_smile:

Great, thanks j3d!
Let´s talk next days.

Best regards,
Marek

I didnt read the first eleven pages of this topic, but I am already really impressed!

Water: is floating - very nice!

Shadows: they change in relation to the location and time, right? So they are in the right place when you look at the 3D version. 2D version: shadows in the south means sun in the north. That does not happen.

Elevation: there is no ground elevation, so my town looks nice but flat. I wonder how one could integrate elevation data.

Very very nice, I will keep this on my favourites list!

An open line with “area=yes”… What does it mean ?

I’ll have a look at this building, the walls are extruded correctly but something skip the roof triangulation.

[Edit: once again it was a self intersecting polygon, i fixed it in OpenStreeMap]

@j3d: thank you for your reports we’ll have a look as soon as possible

@Guido: We’re glad you appreciate our work. Regarding elevations you can activate it from the graphic options in the top right menu but it is still a work in progress.

Thank You cmif4.
Incremental update mechanism works well.
Good job.

We are evaluating some solutions to catch user errors early, but for now we have higher priorities.

Unfortunately the service works again with speed of 48 h.
unreliable :expressionless:

It looks nice but it is not really “real time”.