Geo Data Upload Content Requirements

How to Format and Structure Your Data

Sending data using the file types, schema, format and templates we provide in this section will ease the processing. Preprocessing data outside of these requirements will cause delays.

File Types for GDU

.SHP (Shapefile): Submit required file extensions (at least the .shp, .shx, .dbf, and .prj) in a .zip file (zipped file)

.CSV (Comma Separated Value): Submit data separated by commas, with each column surrounded by quotes.  Header row and spatial attributes (latitude & longitude coordinates) are required.

.KML/.KMZ (Keyhole Markup Language): Represent the data as SchemaData and SimpleFields (preferred) or ExtendedData. .kml/.kmz files must have address fields.  KML/KMZ files can be made with Google Earth - To see more information on this, click this link

.PDF (Portable Document Format): Include location information (latitude and longitudinal coordinates), names, addresses, and pictures if necessary to accurately represent the features that should be updated. Please note that Political features should not be sent as PDFs.

Important to Note:

  • We don’t accept Geodatabase, AutoCAD file, MrSID or MapInfo TAB.  Most software has an option to convert to SHP or CVS so you can export into an accepted format. 
  • GDU can only accept map data in raw, unaltered form, and cannot accept data via WMS or WFS or other OGC-compliant web services.
  • There are no file size limits

 

Data Format Concepts

For specific Data Type field/attribute requirements and options, please review the respective Data Type sections. Here are fields/attributes requirements applicable to all Data Types:

  • Table attributes cannot contain special character encodings; We accept UTF-8, UTF-16, and UTF-32.
  • For lookup tables, you can use .dbf or .csv files
    • If you use a .csv file, separate the data by commas. Limit commas in other fields
    • Surround each column by quotes to prevent issues with commas in names
    • Make sure there’s a header row
  • We don’t have standards on field types, field widths, or domains
  • We recommend FGDC or other internationally recognized standard of formatted Metadata

Geometry

Please provide clean geometry with:

  • No Dangling lines
  • No Undershoots
  • No Overlapping lines or nearly overlapping lines
  • No Polylines
  • No Overlapping polygons 
  • Features with the same name or containing the same feature represented by a single polygon rather than multiple polygons.
  • We accept Inner loops/donuts
    • E.g., 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

Acceptable Data Types 

Below is a list of data types we take on this site. 

  • Political administrative areas and water boundaries
  • Points of Interest (POIs) including business and services 
  • Address Points/Geocodes
  • Road network updates, including:
    • Road-related travel restrictions (e.g., checkpoints, border restrictions) 
    • New and existing road changes (e.g., geometry, names, directionality) 
    • Bike and pedestrian paths 
  • Other map updates, including:
    • New Housing Developments (road centerline, geocoded addresses, sales office POI)
    • Compounds (building or grounds outlines)
    • Parks (green spaces)
    • Overhead imagery

If the data type you would like to submit to Google is not listed here, please visit Get on Google.

 

Data Type Detailed Properties

Political Boundaries

Basic Requirements:

  • Name of Political Feature (English and local language preferred)
  • Polygon indicating bounds of the political feature
    • Boundaries extend out to the water if coastal 
    • If a river is the boundary, features should snap to one another
    • Mindful of other country boundaries - please align with bordering countries
    • Ensure the Data ‘tiles’ with no gaps or overlaps/sliver segments 
  • Type column indicating administrative area, postal code, or border feature
    • Multiple feature types separated by Admin layer or Type (example below)

What Classifies as a Political Feature:

  • Postal Codes
    • Postal Prefix and Suffix
    • Post Towns
  • Administrative Areas (state, province, county)
  • Municipal features (cities and subdistricts)
  • Neighborhood Boundaries
  • Colloquial Areas (Bay Area, Acadiana, etc.)
  • School Districts 
  • Reservations (Tribal Areas)

Important to Note:

  • All political uploads will be reviewed by political operators, no guarantee of edits is made.
  • Authoritative providers (governments) are the only sources considered through this site for Political features. 
  • Polygons are preferred to point features but we also accept point features for Municipal features or smaller. 
  • We accept shapefiles and .KML/.KMZ.  PDFs are NOT accepted for political features.

Political Fields/Attribute Requirements:

FIELD REQUIRED DESCRIPTION EXAMPLE
NAME REQUIRED Official Name of the Feature Seattle
TYPE REQUIRED Administrative Level City

 

 

Points of Interest (POIs)

To describe POIs, please use guidance and definitions included here. Please upload it as .csv file only. 
 
 
FIELD REQUIRED DESCRIPTION EXAMPLE
Name REQUIRED Contains the business name for a particular listing. Empire State Building
Category REQUIRED Contains the business category to which the business belongs.
(i.e. hospital, medical_lab)
historical landmark
Latitude REQUIRED Contains the latitude that corresponds to the location of the listing. 40.7484
Longitude REQUIRED Contains the longitude that corresponds to the location of the listing. -73.9857
Full_Address PREFERRED Contains the full formatted address, including all available details (street number, street name, town/city, state/province/region, country and postal code). 20 W 34th St, Suite 201, New York, NY 10011
Street_Number PREFERRED

Parsed out address

20
Street_Name PREFERRED West 34th Street
Apartment PREFERRED Suite 201
City_Locality PREFERRED New York
State_Province PREFERRED NY
Postal_Code PREFERRED 10011
Phone PREFERRED Contains the main phone number of the business (including country code e.g. +86). (212) 736-3100
Website OPTIONAL Contains the URL for the official website of the business. Please make sure your URLs begin with "http://" and include your domain name. https://www.esbnyc.com/
Monday OPTIONAL

Please check this link for more information on how to format business hours: 

Preferred Business Hours Format

09:00-17:00
Tuesday OPTIONAL 09:00-17:00
Wednesday OPTIONAL 09:00-17:00
Thursday OPTIONAL 09:00-17:00
Friday OPTIONAL 09:00-17:00
Saturday OPTIONAL 09:00-17:00
Sunday OPTIONAL 09:00-17:00
Unique_ID PREFERRED NY_001
 
 
 
 
To keep users informed during the COVID-19 pandemic, we accept the additional attributes below for POIs, with a focus on storefront businesses including retail shops and restaurants (full definitions in the provided template)
 
Additional POI attributes accepted:
  • Existence - status of an establishment's operations (open, temporary closed or permanently closed)
  • serves_dine_in - customers are allowed / not allowed to eat inside 
  • has_takeout - a place allows / doesn't allow patrons to purchase and takeaway food
  • has_curbside_pickup - customers can / cannot place an order by the curb
  • has_delivery - a place offers / doesn't offer delivery to customers
  • has_in_store_pickup - a place allows / doesn't allow online orders to be picked up in store
  • has_no_contact_delivery - a place offers / doesn't offer delivery at the customer's door without face-to-face interaction
  • has_in_store_shopping - a place allows / doesn't allow customers to go inside the shop
 
To claim a business POI please visit Google My Business.
 

Address Points (Geocodes)

  • Include full address information required for a valid address (street number, street name, administrative areas, postal codes) or we may be unable to process your request for updates
  • Expand abbreviations in street names
  • Center address points on the property or house structure they represent
  • 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.

Important to Note:

  • If the address updates you are providing reflect associated postal code or city boundary changes, please also submit the updated postal or city polygon as a political upload

Address Fields/Attributes List:

The following fields are listed as either Required or Optional for Geocode Addresses.  This format also applies for address fields in Points of Interest or Roads datasets:

Field

Required

Description

Example

ST_NUM

Required

Street Number 

125

APT_NUM

Optional

Apartment Number

#101

BLDG_NAME

Optional

Building Name

BLDG D

ST_NAME

Required

Street Name and Type 

(Street, Avenue, etc., can be abbreviated but expansion of abbreviations is preferred)

Powell St

NEIGHBH 

Optional

Neighborhood Name 

Union Square

CITY

Required

City Name

San Francisco

STATE

Required

State (Two Letter Abbreviation)

CA

ZIP

Required

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)

06075f5

 

New Roads and Bicycle and Pedestrian Paths

  • Road and bike/pedestrian path data is preferred as a shapefile or .KML/.KMZ
  • 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 detailed above,  except for the different street number format.
  • Specify all address ranges 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.
  • See separate section below for TRAVEL ROAD RESTRICTIONS

Important to Note:

  • Please specify in the description if you are updating a previous upload. Subsequent uploads of the same network should only contain geometry and attributes of any updated information

Roads, Bikes, and Pedestrian Fields/Attributes List.

The following fields are useful for roads and bike and pedestrian paths. "Required" is specific to Feature Type:

Field

Required

Description

Example

ID

Optional

A unique and stable identifier for the road segment

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

ST_NAME

Preferred 

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

RT 101

NEIGHBH 

Optional

Neighborhood Name 

Union Square

CITY

Preferred

City Name

San Francisco

STATE

Preferred 

State (Two Letter Abbreviation)

CA

ZIP 

Preferred 

5-digit zip code

94108 

CNT_NAME 

Optional

County Name

San Francisco

AR_RT_FR 

Optional

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

2

AR_RT_TO 

Optional

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

98

AR_LT_FR 

Optional

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

1

AR_LT_TO 

Optional

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

99

SURFACE 

Optional

Road Surface

Paved or Unpaved

SPEED_LM 

Optional

Speed limit in MPH or KPH

55

CAR 

Required for Road Datasets

Cars are allowed on this segment

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

PEDEST 

Required for Pedestrian Walkway Datasets

Segment traffic restricted to pedestrian access

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

BIKE 

Required for Bicycle Datasets

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

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

SEPARATED 

Optional

The road segment 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

Travel Restrictions for Checkpoints, Road Closures, Border and Road Restrictions

If uploading tabular data for checkpoints, road closures, road restrictions, border restriction, please use of this Travel Restrictions guidance below.

  • Include as much detail as possible in the provided format. Ensure that your attribute table has the equivalent fields to the template
  • Please note that other formats can be accepted: PDFs, shapefile, public URL, detailed screenshots.

Travel Restrictions Fields/Attributes List: 

If uploading shapefile or .KML/.KMZ, include required and optional fields/attributes of the Roads, Bikes, and Pedestrian Fields/Attributes List and additionally include the following required fields/attributes.

 

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" 

 

Transit

Please note that Google has a Transit website for real time feed data. Through GDU, you can add:

Stops/Stations (Bus Stops)

  • Geometry - point or polygon features
  • Name of transit station or transit stop
  • Latitude and Longitude coordinates of the stop
  • Route or Line type  (Not Transit Lines)
  • Agency
  • Address
  • Stop Schedule

Footprints

  • Geometry - polygons of footprints, buildings, or bus bay structures
  • Station name
  • Lat/long
  • Agency
  • Route type

Stops/Stations Fields/Attributes List:

The following fields are listed as either Required or Optional.

Field

Required

Description

Example

STOP_NAME

Required

Name of station or stop

42 ST

LAT

Required

Latitude coordinates of the stop 

40.752619

LONG

Required

Longitude coordinates of the stop

-73.977268

ROUTE_TYPE

Required

Type of vehicle services 

Train

AGENCY

Required

Entity that owns or operates transit system

ITO

ST_NUM

Optional

Street Number 

89

ST_NAME

Required for train, subway stations, or transit hubs

Street Name and Type 

(Street, Avenue, etc., can be abbreviated but expansion of abbreviations is preferred)

E 42nd ST

NEIGHBH 

Optional

Neighborhood Name 

Midtown Manhattan

CITY

Required

City Name

New York

STATE

Required

State (Two Letter Abbreviation)

NY

ZIP

Required

5-digit zip code

10017

CNT_NAME 

Optional

County name

Manhattan

STOP_TIMES

Optional

Times that transit feature will stop at this location

1:00, 1:30, 2:00, 2:30

Important to Note:

  • Modeling of stations, station buildings or bus bays - Upload each station as an individual polygon or point rather than a single polygon as a network
  • If you would like to become a Transit Partner please follow this link for more details.

Transit Footprints Fields/Attributes List:

The following fields are listed as either Required or Optional.

Field

Required

Description

Example

STATION_NAME

Required

Name of station

Zurich HB

LAT

Required

Latitude coordinates of the stop 

40.76255 

LONG

Required

Longitude coordinates of the stop

-74.000969

AGENCY

Required

Entity that owns or operates transit system

ITO

ROUTE_TYPE

Optional

Type of vehicle services 

Train

New Housing Development

  • Shapefiles are preferred. We can work with other data types (platt maps) but there will be delays in processing any data that is not in shapefiles.

  • Road centerlines with street names (see roads and addresses section for more info).

  • Address points in the center of the structures or parcels they occupy. Street number and street name are required, but include all address components if possible (see roads and addresses section for more info).

  • Public opening date should be included. This is the month and year that public routing through the housing development will be made available
  • Community sales office names must be included in the POI shapefiles attribute table
  • Parcels are accepted but not actively added to the map
  • You can upload one zip file that includes all road centerlines, addresses, boundaries, and parcels. We can process these as a package.

Building Footprints, Property Boundaries and Parcels

  • Polygon of building or grounds extent
  • Name of building or grounds (if applicable)
  • APN or unique identifying number (parcels only)
  • Full address information
  • Should include the category (residential, business)

Parks and Protected Areas

Parks and protected areas should have the following info:

  • Polygon geometry of park boundaries is preferred over point geometry. We recommend a scale better than 1:25,000.
  • If you have a park that is in two sections, include the park in one polygon
  • Name of park or protected area (in a field called NAME, with alternates in ALT_NM_1, ALT_NM_2).
  • A field for the classification of the park with an MTFCC column (Type). Use the latest MTFCC park code provided from the US Census MAF/TIGER Feature Class Code Definitions.  Include a data dictionary describing the types. 
  • Optionally, parks can include an address,  park operating hours, parking, or facilities. Add the data in fields in the form of X_DESCRIPTION, such as X_USAGE, X_HOURS, X_PARKING.

Overhead Imagery

We can accept your overhead imagery if it is top-down (we are not accepting oblique or 3D) and in the following format:

  • Basic Description of Data
    • Location of Imagery
    • Date of Capture
    • Method of Capture (Satellite, Airplane, Balloon, Drone, etc)
    • Projection
  • Data must be orthorectified
  • File Format:  GeoTIFF, JP2000
Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue