-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
137 changed files
with
510 additions
and
269 deletions.
There are no files selected for viewing
48 changes: 48 additions & 0 deletions
48
2024-10-25-announcing-open-street-map-and-3dstreet-integration.md
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,48 @@ | ||
--- | ||
title: "Announcing Open Street Map for 3DStreet Integration" | ||
description: Discover how 3DStreet is expanding its mapping capabilities with Open Street Map and GeoJSON integration, providing new options for areas without 3D tiles. | ||
authors: [kfarr] | ||
tags: [product update, open street map, geojson, mapping, open source] | ||
image: ./images/2024-10-25/open-street-map-integration-sf-city-hall.jpg | ||
--- | ||
|
||
High resolution 3D map tiles have become a popular choice for adding immersive local context to 3DStreet scenes. However, sometimes the most interesting places on Earth have the least availability of detailed 3D map tiles -- such as large parts of Africa and South America. Even for locations with detailed 3D tiles coverage, we've heard from users that sometimes the realism of the 3D tiles can distract from the focus of presenting proposed street projects. | ||
|
||
In these cases, our new integration with Open Street Map (OSM) offers new dimensions to our mapping capabilities. | ||
|
||
# PICTURE HERE WITH SAN FRANCISCO CITY HALL | ||
![Open Street Map Integration Screenshot of San Francisco City Hall](./images/2024-10-25/open-street-map-integration-sf-city-hall.jpg) | ||
<b><i>A screenshot of the new 3DStreet OSM integration showing San Francisco City Hall.</i></b> | ||
|
||
<!-- truncate --> | ||
|
||
## Introducing Open Street Map Integration | ||
|
||
3DStreet now offers integration with Open Street Map (OSM) as a new Geospatial Layer map source. This integration provides 2D political map ground tiles and 2.5D buildings through OSM GeoJSON buildings data. This feature is now available for all Geospatial Pro Plan users in addition to the existing map data providers Google Maps 3D Tiles and Mapbox 2D Satellite Maps. | ||
|
||
![Open Street Map Integration](./images/2024-10-25/open-street-map-geospatial-layer-ui.jpg) | ||
<b><i>Click Geospatial Layer > Map Source > osm3d to use the new OSM data source.</i></b> | ||
|
||
## The Advantage of Open Source Maps | ||
|
||
Integrating OSM with 3DStreet continues our commitment to open-source collaboration. A key advantage of the OSM approach is that it allows you to leverage the existing OSM community and resources, ensuring that the data remains up-to-date and accessible to all. The 3DStreet integration today is "read only" and relies on existing OSM data, but [users wishing to update map data can do so through a variety of tools from the OSM ecosystem](https://wiki.openstreetmap.org/wiki/Contribute_map_data). | ||
|
||
## More than just tiles - GeoJSON buildings | ||
|
||
In addition to Open Street Map 2D ground tiles, the new OSM integration provides basic building geometry through GeoJSON OSM data sources. The basic building footprints provide just enough context in most cases for locals to understand the location of a proposed project, while not distracting from the focus on the proposed project itself. | ||
|
||
This GeoJSON parser also opens the door to future integration of alternative geospatial data sources, although today this only supports closed polygons for buildings. | ||
|
||
## A-Frame Component for OSM Integration | ||
|
||
Similar to our other integrations, we've chosen to "build in the open" by contributing improvements to an existing A-Frame `OSM4VR` component designed by anonymous community member `ctrlw`. | ||
|
||
You can view the original A-Frame component by *ctrlw* here [https://github.com/ctrlw/osm4vr](https://github.com/ctrlw/osm4vr) and [check out the 3DStreet version here](https://github.com/3dstreet/osm4vr) which adds webpack support to better handle dependencies as well as custom features to allow for integration with the 3DStreet Editor app. Like all parts of 3DStreet, we welcome community contributions to this component and others. | ||
|
||
## What's Next? | ||
|
||
Looking ahead, we're excited about the potential to support custom tiles. In addition to the political map, we aim to move beyond this basic OSM implementation and support private servers and alternate tile types. Our ultimate goal is to allow users to specify which tile type they prefer, providing even greater flexibility and customization. | ||
|
||
Stay tuned for more updates as we continue to enhance 3DStreet's mapping capabilities and explore new ways to empower our users to reimagine public spaces. | ||
|
||
You can help us shape the future of the 3DStreet OSM integration by providing your feedback through [email](mailto:[email protected]), [GitHub issues](https://github.com/3dstreet/3dstreet/issues), or our public Discord server (link in footer). |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Binary file added
BIN
+129 KB
...images/open-street-map-geospatial-layer-ui-b4c17ae4a0e0a54f0f0db3036b20430e.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+405 KB
...s/open-street-map-integration-sf-city-hall-ff93419ac7bfad69485ea73d4bdb640a.jpg
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
2 changes: 1 addition & 1 deletion
2
assets/js/0afd36a3.dcee2bc3.js → assets/js/132139d8.f99de5f7.js
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Oops, something went wrong.