The analyses you can do in mySidewalk are enhanced by integrating your own data. Some examples of layers you may want to upload include project areas, economic districts, transit corridors, emergency service points, and more!
There are several different file types that you can use to upload your own spatial data. All uploaded files can be points, lines, or polygons (no rasters). Each layer must contain 5000 or fewer features. You can upload as many layers as you want in a zipped file, including different layer types, so long as the total file size is less than 50MB.
The different formats are listed below along with a brief description of how to prepare each type:
1. Esri Shapefile: A shapefile consists of several individual files all with the same name but different file extensions.
Each shapefile must include the file extensions .shp and .prj. We recommend including the other file extensions too.
Multiple shapefiles can be included in the same zipped folder
Any m-values or z-values will be ignored
2. Esri File Geodatabase (.gdb – must be zipped): A File Geodatabase can contain several point, line, and polygon feature classes. By uploading one zipped file geodatabase, all of the contained feature classes are uploaded at once.
ArcGIS file geodatabase versions 9.x and 10.x are supported
Since a file geodatabase is a folder containing data, you will need to zip the file geodatabase to upload it
Only the point, line, polygon feature classes will upload. No rasters, annotations, or relational tables
3. Keyhole Markup Language (.kml)
You can upload .kml files that mix points, lines, and polygons
During the upload process, a .kml file that contains a mix of points, lines, and polygons will be split into three. A separate layer for the points, the lines, and the polygons will appear in the app.
The .kmz extension will not work, as it is a zipped (compressed) version of a .kml. To use it, simply unzip (extract) the .kmz file and upload the uncompressed .kml
4. Geography Markup Language (.gml)
Uploaded .gml files can be a mix of points, lines, and polygons. During the upload process, a .gml file that contains a mix of points, lines, and polygons will be split into three. A separate layer for the points, the lines, and the polygons will appear in the app.
5. GeoJSON (.json or .geojson)
Uploaded geojson files can be a mix of points, lines, and polygons.
During the upload process, a layer that contains a mix of points, lines, and polygons will be split into three. A separate layer for the points, the lines, and the polygons will appear in the app.
The default projection for geojson is WGS84. If the coordinate reference system (crs) either doesn't exist or it contains unrecognizable text, it will default to WGS84
6. Comma Separated Values / Comma delimited (.csv)
The first row of your .csv should be the column headers
The .csv table needs to have two geography columns, one for the longitude and one for the latitude.
The latitude and longitude must be in separate columns
We suggest to give the longitude and latitude columns common names like the examples below. Otherwise, the upload process will attempt to determine which columns contain the coordinates, which may result in the columns not being found or the wrong columns chosen
point_x, point_y
longitude, latitude
x, y
long, lat
lon, lat
lng, lat
The coordinates must be in World Geodetic System 1984 (WGS84) reference system
The coordinates must be in decimal degree format. Example: 37.624843, -122.381905 (with each value in a separate column)
Do not include text like N/North/Northing or E/East/Easting in the latitude and longitude columns
Latitude must be between -90 and 90
Longitude must be between -180 and 180
Correct Examples:
Incorrect Examples:
Need additional assistance? Please message us on chat and let us know that you are having trouble uploading your file—we're happy to jump in and help!
The mySidewalk platform supports many common GIS geometry types for user data upload. Below is a list of the types we support, as well as a list of the types we currently do not support.
Supported Geometries:
wkbPoint
wkbLineString
wkbPolygon
wkbMultiPoint
wkbMultiLineString
wkbMultiPolygon
wkbPoint25D
wkbLineString25D
wkbPolygon25D
wkbMultiPoint25D
wkbMultiLineString25D
wkbMultiPolygon25D
wkbPointM
wkbLineStringM
wkbPolygonM
wkbMultiPointM
wkbMultiLineStringM
wkbMultiPolygonM
Unsupported Geometries:
wkbUnknown
wkbGeometryCollection
wkbCircularString
wkbCompoundCurve
wkbCurvePolygon
wkbMultiCurve
wkbMultiSurface
wkbCurve
wkbSurface
wkbPolyhedralSurface
wkbTIN
wkbTriangle
wkbNone
wkbLinearRing
wkbCircularStringZ
wkbCompoundCurveZ
wkbCurvePolygonZ
wkbMultiCurveZ
wkbMultiSurfaceZ
wkbCurveZ
wkbSurfaceZ
wkbPolyhedralSurfaceZ
wkbTINZ
wkbTriangleZ
wkbGeometryCollectionM
wkbCircularStringM
wkbCompoundCurveM
wkbCurvePolygonM
wkbMultiCurveM
wkbMultiSurfaceM
wkbCurveM
wkbSurfaceM
wkbPolyhedralSurfaceM
wkbTINM
wkbTriangleM
wkbPointZM
wkbLineStringZM
wkbPolygonZM
wkbMultiPointZM
wkbMultiLineStringZM
wkbMultiPolygonZM
wkbGeometryCollectionZM
wkbCircularStringZM
wkbCompoundCurveZM
wkbCurvePolygonZM
wkbMultiCurveZM
wkbMultiSurfaceZM
wkbCurveZM
wkbSurfaceZM
wkbPolyhedralSurfaceZM
wkbTINZM
wkbTriangleZM
wkbGeometryCollection25D
See a type of geometry you would like us to support for layer upload? Please message us on chat and let us know which type would be helpful to you!