Geo Data Upload content requirements

Data formats

When you send data in the right format, we can ingest the files easier. If you don’t send us a shapefile (.shp) or .csv with spatial attributes, there may be delays.

In order of preference, we support these files:

  • .shp
  • .csv: Make sure the data is separated by commas, with each column surrounded by quotes. Make sure there’s a header row and spatial attributes.
  • .kml/.kmz: Represent the data as SchemaData and SimpleFields (preferred) or ExtendedData. .kml/.kmz files must have  address fields.
Tips:
  • You may use AutoCAD or MapInfo TAB, but the above formats are recommended.
  • We don’t recommend you use GeoDatabase to store the data.

Important:

  • Use UTF-8 character encoding for vector attributes. We also accept UTF-16 and UTF-32.
  • No special character encodings
  • Files should be less than 2 GB.
  • For lookup tables, you can use .dbf or .csv files.
    • If you use a .csv file, separate the data by commas.
    • Surround each column by quotes to prevent issues with commas in names.
    • Make sure there’s a header row.
  • We recommend FGDC or other internationally recognized standard of formatted Metadata.
  • We don’t have standards on field types, field widths, or domains.
  • For questions on how to contribute your data via WMS or WFS, read Can Google just pull my organization's content from an OGC-compliant web service?.

Data format concepts

Throughout this specification, we refer to the following basic representations for fields that are shared between different types of data.

Format addresses

You can use addresses for points of interest and geocodes, plus a slight variant for streets. Address should have the following in separate columns:

Field

Description

Example

ST_NUM

Street Number 

125

ST_NAME

Street Name and Type (the words Street, Avenue, etc., can be abbreviated)

Powell St

NEIGHBH (optional)

Neighborhood Name 

Union Square

CITY

City Name

San Francisco

STATE

State (Two Letter Abbreviation)

CA

ZIP

5-digit zip code

94108 

CNT_NAME (optional)

County Name

San Francisco

CNT_FIPS (optional)

County FIPS 6-4 code (refer to Information Technology Laboratory)

06075

Geometry

We prefer multipolygons over polygons, rather than one feature with the same name, each with geometry. If a feature is composed of several polygons, use one multipolygon to represent them.

For polylines, give us clean geometry, with no:

  • Dangling lines
  • Undershoots
  • Overlapping lines or nearly overlapping lines
Notes:
  • If you have a park that is in two sections, include the park in one polygon. 
  • We accept Inner loops/donuts.
    • To exclude lakes from a park, or an island from a water feature.
  • Polygons should have correct windings, and they must not self-intersect.
    • Our preferred order is clockwise for both internal and external polygons.

Alternate names

The NAME field is the one that will show in our maps. But if people search for the alternate names, we can point them to the right location.

Names can be represented as follows:

Field

Description

Example

NAME

Most well-known Name

Alcatraz

ALT_NM_1

Alternate Name 1 (second most well known)

Alcatraz Island

ALT_NM_2

Alternate Name 2 (Third most well known)

Golden Gate Recreation Park (Alcatraz)

 

Properties of individual data types

Parks and protected areas

Parks and protected areas should have the following info:

  • We prefer polygon geometry over point geometry.
    • We recommend a scale better than 1:25,000.
  • Name of park/protected area (in a field called NAME, with alternates in ALT_NM_1, ALT_NM_2).
  • Optionally, parks should include an <anchor link> address <anchor link>.
  • An MTFCC field for the classification of the park. Include a data dictionary describing the types.
  • Under Documentation (stored in a field called MTFCC).
  • Optionally, you can add any data related to park operating hours, parking, or facilities. You can add the data in fields in the form of X_DESCRIPTION, such as X_USAGE, X_HOURS, X_PARKING.

MTFCC

Short description

Long description

K2180

Park

Open space; major category used alone when the minor category can’t be determined

K2185

Regional Park, Forest, or Recreation Area

A place or area set aside for recreation or preservation of a cultural or natural resource and under the administration of a regional government.

K2186

County Park, Forest, or Recreation Area

A place or area set aside for recreation or preservation of a cultural or natural resource and under the administration of a county government.

K2187

County Subdivision Park, Forest, or Recreation Area

A place or area set aside for recreation or preservation of a cultural or natural resource and under the administration of a minor civil division (town/township) government.

K2188

Incorporated Place Park, Forest, or Recreation Area

A place or area set aside for recreation or preservation of a cultural or natural resource and under the administration of a municipal government.

K2189

Private Park, Forest, or Recreation Area

A privately owned place or area set aside for recreation or preservation of a cultural or natural resource.

K2190

Other Park, Forest, or Recreation Area (quasi-public, independent park, commission)

A place or area set aside for recreation or preservation of a cultural or natural resource and under the administration of some other type of government or agency such as an independent park authority or commission.

Points of interest (POIs)

You must upload POIs in .csv format. Encode the .csv to UTF-8.

This is especially important for non-English characters. We recommend you create the .csv file from OpenOffice or Google Drive (Docs or Sheets).

Microsoft Excel usually saves .csv files differently, based on the operating system of the machine. For this reason, we recommend you save .csv files with the use of other programs that will ensure the file is set to the right encoding.
Use quotes
Some CSV fields include text strings. If the text string includes any reserved characters, such as a comma or a quotation mark, enclose the character string with double quotation marks ("). To include double quotes in the string, use two double quotes ("").
 

For example:

  • "This text string, for example, includes commas (,)."
  • "This text string includes double quotes: ""example text."""
Read more about comma-separated values.
File format

.csv field

Required

Description

Example

address

required

Has the full formatted address, including all available details (street number, street name, town/city, state/province/region, country, and postal code).

"1281 University Ave., Palo Alto, CA 94301 U.S.A."

category

optional

Has the business category to which the business belongs.

Restaurant

id

optional

Has the unique case-sensitive English alphanumeric ID identifying a business listing on your site. The length should not exceed 248 characters.

12345aBc

latitude

optional

Has the latitude that corresponds to the location of the listing.

37.455809

longitude

optional

Has the longitude that corresponds to the location of the listing.

-122.149710

phone

optional

Has the main phone number of the business (including country code e.g. +86).

+1(650)555-1212

name

required

Has the business name for a particular listing.

Maggic Pizza

website

optional

Has the URL for the official website of the business. Make sure your URLs begin with "http://" and include your domain name.

http://www.magicpizza.com/

Below is the content of a .csv file that has only one row:

Name, Latitude, Longitude, Address, Phone, Website, id

Empire State Building,40.7484,-73.9857,"20 W 34th St,New York,NY 10011", +1(212)736-3100,https://www.esbnyc.com/, ABC123
 

Building footprints

The following apply to building footprints:

Address points

  • Include full address information.
  • Don’t include invalid geocoded points (like no latitude/longitude values).
  • The geocode should link to the segment it belongs to using the unique id.
  • Address points should be placed closest to the most natural access point
    • For example, if a house is on the corner of a major roadway and a local road, make sure the geocode point is closer to the main entryway.
  • Standardize the format.
    • All the addresses in an area should be in a consistent format.
    • For example, one house in an area shouldn’t be 1-A and another one 2B. The format should be 1A and 2B.

New roads and bicycle and pedestrian paths

We accept two specific types of network data: new roads, and bicycle and pedestrian paths.

  • Use a segment-based representation: a segment is part of a road between two intersections. We can’t accept roads that have multiple intersections hanging off them.
  • The street format is similar in many ways to the address format, except for the different street number format.
  • All address ranges should be specified relative to the geometry.
    • For example, the right side is to the right of the path from the start of the segment to the end of the segment.
The following fields are useful for roads and bike and pedestrian paths. Fields marked as "optional for BP" aren’t necessary for bike and pedestrian paths:

Field

Description

Example

ID

A unique and stable identifier for the road segment

Any alphanumeric string (e.g. "14232514")

AR_RT_FR (optional for BP)

Starting address on the right-hand side, relative to geometry

42

AR_RT_TO (optional for BP)

Ending address on the right-hand side, relative to geometry

58

AR_LT_FR (optional for BP)

Starting address on the left-hand side, relative to geometry

41

AR_LT_TO (optional for BP)

Ending address on the left-hand side, relative to geometry

57

ST_NAME

Street Name and Type (the words Street, Avenue can be abbreviated)

Powell St

ST_NM_A1 (optional)

Alternative Name 1

U.S. 101

ST_NM_A2 (optional)

Alternative Name 2

 

NEIGHBH (optional)

Neighborhood Name 

Union Square

CITY

City Name

San Francisco

STATE

State (Two Letter Abbreviation)

CA

ZIP (optional for BP)

5-digit zip code

94108 

CNT_NAME (optional)

County Name

San Francisco

CNT_FIPS (optional)

County code (refer to Information Technology Laboratory)

06075

ONEWAY (optional for BP)

One-wayness - relative to the direction of geometry

"None", "To-From", and "From-To"

PRIORITY (optional for BP)

We would consider the following levels: interstate, federal/state highway, expressway, minor arterial, local, not intended for public traffic.

minor arterial

LANES (optional)

Number of lanes

2

SURFACE (optional)

Road Surface

Paved or Unpaved

SPEED_LM (optional)

Speed limit in MPH

55

AVG_SP (optional)

Average Speed

25 

CAR (optional)

Cars are allowed on this segment?

Allowed, Small vehicles only (mopeds), None, Disallowed

PEDEST (optional)

Whether the segment allows bikes, and if so, what type it is

One of: Trail, Walkway, Mall, Sidewalk, Wide Shoulder, None, Disallowed

BIKE (optional)

Whether the segment allows bikes, and if so, what type it is

One of: Trail, Bike Lane, Wide Shoulder, Recommended, None, Disallowed

SEPARATED (optional)

Whether the road is separated by a barrier in the middle

Y/N

TURN_R (optional)

Turn Restrictions (below you’ll find the exact format)

Freeform text

ELEVATION (optional)

If the road is elevated, or a bridge or a tunnel

One of: bridge, tunnel, overpass, underpass

We’re experimenting with the process of turn restrictions as freeform text to make it easier for people to submit data as turn restriction formats can be complicated.

Below is a model format that would typically be delivered as a .csv file or a .dbf file:

 

Field

Description

Example

FROM_ID

The ID (find the id column above of a road segment) of the segment where the turn restriction starts

14232514

FROM_END

The end of the segment the turn restriction applies to relative to its geometry. 

Either "FROM" or "TO"

TO_ID

The ID (find the id column of a road segment) of the segment where the turn restriction ends 

14232599

TO_END

The end of the segment the turn restriction applies to relative to its geometry

Either "FROM" or "TO"

MODE

The mode of transportation the limitation applies to. 

Either "ALL", "PEDESTRIAN", "CAR", "TRUCK", "BUS" or "NON-HOV"

START_TM

The start time of the turn restriction, in 24-hour notation. Leave this and END_TM blank for permanent restriction

06:00

END_TM

The end time of the turn restriction, in 24-hour notation. Leave this and START_TM blank for permanent restriction

10:00

TYPE

Type of turn restriction  

Either "NO LEFT TURN", "NO RIGHT TURN" or "NO U-TURN" 

 

Was this helpful?
How can we improve it?