Abstract:
The subject matter of this specification can be implemented in, among other things, a computer-implemented method for accessing map tiles. The method includes receiving a first request from a computing device for a portion of a map. The portion of the map includes combined map tiles that are a combination of corresponding ones of first map tiles from a first type of map and second map tiles from a second type of map. The method further includes providing first tile version identifiers and second tile version identifiers to the computing device in response to receiving the first request. The method further includes providing instructions to the computing device for using the first tile version identifiers and the second tile version identifiers to request the combined map tiles.
Abstract:
A map data server may provide metadata about available indoor map data that accompanies map data for drawing a base map. For example, map data may include vector data for drawing a footprint of a building, and the metadata may include information about the physical properties of the building (e.g., an indication of how many floors the building has and if detailed map data is available for the indicated floors, etc.). A mapping application running on the client can use this metadata to display an interface that allows a user to select floors or otherwise interact with the floor data. Further, the metadata accompanying map data can include a bounding box, or a bounding polygon, for one or more floors. The mapping application can use these bounding shapes to properly reposition the viewport as map data for a new floor is being loaded, for example.
Abstract:
The subject matter of this specification can be implemented in, among other things, a computer-implemented method for managing updates to map tiles. The method includes receiving an update to a feature in geospatial information that describes a map. The map is represented by multiple tiles. The method further includes rerendering at least one tile from the tiles based on the update to generate an individual rerendered instance of the tile. The method further includes generating a tile version identifier that uniquely identifies the individual rerendered instance of the tile. The method further includes storing the tile version identifier and an association between the tile version identifier and the individual rerendered instance of the tile. The method further includes providing, to a computing device, the tile version identifier and instructions for using the tile version identifier to send a request for the individual rerendered instance of the tile.
Abstract:
A map data server may provide map data to a client device by generating a description of a geographic area that includes outdoor map features including a multi-story building. The multi-story building includes a “default” floor. The map data server may also provide data to the client device to graphically represent the indoor features of the default floor in the description of the geographic area. The indoor map features may be annotated to allow the client device to selectively activate or deactivate the display of the indoor map features.
Abstract:
A map data server may provide metadata about available indoor map data that accompanies map data for drawing a base map. For example, map data may include vector data for drawing a footprint of a building, and the metadata may include information about the physical properties of the building (e.g., an indication of how many floors the building has and if detailed map data is available for the indicated floors, etc.). A mapping application running on the client can use this metadata to display an interface that allows a user to select floors or otherwise interact with the floor data. Further, the metadata accompanying map data can include a bounding box, or a bounding polygon, for one or more floors. The mapping application can use these bounding shapes to properly reposition the viewport as map data for a new floor is being loaded, for example.