When you create a map using Map Designer, you'll get a short URL (e.g. https://wrld.mp/5816a80) which you can share with your users or embed in your website. The link will also open in WRLD App if you're on a mobile device. The Map Designer tutorial video walks you through sharing your maps in more detail.
You can also build your own apps using our SDKs for web, mobile, and AR/VR.
All of your custom Points-of-Interest are only available to users accessing the map through your Mapscene (short link) or your own app. You can publish your indoor maps to our public maps but you don't have to. It's also possible to lock your indoor map so only users of your app can enter it.
We don't have coverage of the whole world yet. You can see our current coverage and register a vote for new areas here. If you need a specific area such as a city or district added sooner for your project, contact us for a quote.
We build our 3D maps from a range of data sources. It's possible that your building wasn't present when we imported the data (especially if it's a new development), and sometimes the source data is patchy. Our team can add individual buildings to the map for you, starting at $300 for a basic procedural building or more for detailed hand-built 3D models - contact us for a quote.
Yes, but only if you're developing an app with our Unity SDK. We are considering adding this capability to our other SDKs soon.
It's possible to add items of furniture from our library of assets to your indoor maps using our Assets Tool and these will appear in your map automatically.
It's not possible for users to add their own 3D models into the map, but our team can create custom 'landmark' models of buildings and add them to the map for you. If you have your own 3D model, we can use that as a starting point. Our pricing covers both interior and exterior but we can do exterior-only if required.
Yes, we have a building services team who can create accurate and realistic maps of indoor and outdoor spaces. Pricing varies depending on the size and complexity of the building and the level of detail required.
Yes, we take on a range of customer projects and have built web, mobile and kiosk apps for a range of uses. Please get in touch to discuss your requirements.
Currently the WRLD platform is only available in English.
The theme tab in our Map Designer tool allows you to select a theme for your map. The Map Designer tutorial video walks you through the process of customising your maps in more detail.
You can customise the weather, seasons and time-of-day using our mapping SDKs.
Points of Interest (POIs) are added to your map via the Places Designer Tool. The Places Designer tutorial video walks you through the process of creating Points of Interest and adding them to your map in more detail.
You can use your own images in the POI cards but you must host them yourself, outside of WRLD. You can also host custom POI card HTML views.
A series of 3 video tutorials walk you through the process of using our Map Upload tool in conjunction with Open Source QGIS software. A detailed, step-by-step tutorial can be followed here.
If you don't have the time to do it yourself - don't worry, our WRLD building service can do the heavy lifting for you if required.
If you just want to create the indoor map and don't need the exterior of the building to show on the map, you can create a building outline manually and upload it to our Indoor Maps REST API to create your indoor map. Follow these tutorial steps to get started.
If you want a building added to the map, let us know.
There are several options available to you:
No, WRLD does not currently support Linux.
No, we do not currently support Unreal Engine, and it isn't in our roadmap for the foreseeable future. For gaming and VR applications, we recommend using our Unity SDK.
Yes, but we recommend our native SDKs for a slicker mobile experience. We have published a React Native examples to show how to use wrld.js in a React Native app.
Instead of using the Map Design tools to manage your map content, you can create and modify content using our REST APIs. These are particularly useful for automating updates such as keeping POI data in sync with an external data source.
A manifest (Coverage Tree Manifest) can be thought of as a list of resources which a WRLD app is allowed to access. By default, WRLD apps use our Public Global manifest which contains all of our public map data, as well as indoor maps which have been published by our users. Custom manifest files may be selected by specifying a URL which the WRLD app loads when it starts up (for example, the coverageTreeManifest parameter in wrld.js).
Every time you build a new version of an indoor map, a preview manifest is created (you can find it in the "Review Your Indoor Map" drawer in the Indoor Map Tool). This contains the new version of the indoor map, plus all of the public map content. If you have only a single indoor map, you can just use this manifest in your app instead of publishing your indoor map.
We can produce custom manifests on request for customers, for example if you wish to have multiple private indoor maps in the same manifest, or if you have paid for access to licensed resources such as the Middle East map data.
You might also see the Environment Themes Manifest - this is used to specify the appearance of the map. You can find out more about them here.
A Morton key is simply the address of a particular location on the earth's surface. They look like a string of digits e.g. 202233232221330 is in central London, UK. The longer the key, the smaller the area it refers to. You can read more about why we use Morton Keys and how they work in this blog post.
A Mapscene is a customised map created by the WRLD Map Designer tool. It has a unique ID (e.g. 5816a80) and when the mapscene is loaded by WRLD App the app will position the map at the correct location, set the theme and loads a custom manifest if specified. A mapscene has its own so you can allow it access to specific indoor maps, and link it to POI sets created in Places Designer so they can be searched.
An API Key is a unique identifier consisting of 32 hexadecimal digits e.g. c0c84f6e1e3cbf110fc6cc49aa301772 which belongs to a specific WRLD app - either a Mapscene or an app built using the WRLD SDKs. The API Key is used to control permissions (such as what indoor maps, POI sets, or routes an app can access), and to track and report usage of the app by WRLD.
A Developer Token is a unique identifier consisting of 64 hexadecimal digits e.g. 28935ef3dc2bc08799fb3feab33db1838c0c84f6e1e3cbf110fc6cc49aa30177 which belongs to a specific WRLD account. It can be used with our REST APIs to create, delete and modify resources such as Indoor Maps and POIs so should be kept private by the owner.
Back in 2017 we rebranded, changing the name of the company from eeGeo to WRLD. You might still find the old name in a few places, especially in the source code of our developer tools. Don't worry - it's still us!