WME Data Store (WDS) is a script for the Waze Map Editor that adds basic statistics (not yet available) and CSV export capability (available) for some common data. The script requires Tampermonkey for Chrome or Greasemonkey for Firefox, and it is available here from GreasyFork
User Interface
- After installing the script, load WME. WDS is not triggered until after the user pans or zooms the map, which populates most of the objects that WDS uses. At that point, you should see the Waze "Geek" icon as well as export links in the lower left corner of the map next to the Google icon.
- WDS also offers basic translation support, which relies upon WME's translations. Changing the language in WME should also change the export labels to correspond with the selected language. Everything else will appear in English.
Statistics
- Basic statistics for the current view appear when the user hovers over the Waze "Geek" icon.
- More is planned for future releases, and suggestions for analysis are welcome.
Exporting Data
- WDS currently supports CSV export capability for a variety of objects. The data depends upon the same zoom level used for selecting or viewing these objects in WME. For example, most segments will only appear in an export if the user is at a zoom level between 4 and 10, Point Places will only export at a zoom between 5 and 10, etc.
- NOTE: Because the exports involve comma delimited files, any commas(,) in names or other text are replaced with a period(.). For example, "Historic Fort Wayne, Detroit" would export as "Historic Fort Wayne. Detroit".
- CSV (comma delimited) files are not natively handled in an application like Microsoft Excel. If using Excel, you will more than likely need to use the "Text Import Wizard" and manually specify that you are using a Delimited File on window 1 of 3 and Comma on window 2 of 3. If the CSV opens in Excel and everything is in column A, and commas are present, go to the Data tab and select "Text to Columns" to reach the Text Import Wizard.
- Current Column List
- Cities
- CountryID
- Country
- StateID
- State
- CityID
- CityName
- CityEnglishName
- IsEmpty
- Permalink
- Places
- PlaceID
- PlaceName
- Brand
- Lock
- PrimaryCategory
- Type
- PublicOrPrivate
- Approved (status of true or false)
- Description (limited to first 100 characters)
- ImageCount (number of images pending or approved)
- UpdateRequestCount (number of pending approvals)
- CountryName
- StateName
- CityName
- StreetName
- HouseNumber
- CreateDateTime
- CreatedByName
- CreatedByRank
- UpdateDateTime
- UpdatedByName
- UpdatedByRank
- Permalink
- Segments
- SegmentID
- CountryName
- StateName
- CityName
- PrimaryStreetName
- RoadType
- RoadTypeName
- FwdToll
- ReverseToll
- FwdDirection
- ReverseDirection
- Elevation
- Rank
- LengthInMeters
- CreatedByName
- CreatedByRank
- UpdateDateTime
- UpdatedByName
- UpdatedByRank
- Permalink
Troubleshooting
- Exports have headers but no data, or data is from a previous map area
- You may not be at the correct zoom level for properly exporting data, or the map may not have finished loading all of the objects prior to clicking on the export. WDS relies upon zoom *end* and move *end* events, which means that it will not execute until the map finishes a pan or zoom and reloads data. This may take a few seconds. Also, cities are tied to street names, so it is necessary to at least wait for the road layer to load.
Known Issues
- Nothing refreshes when you use the search bar to change locations. You need to first pan the map for new data to display/export.
- Refreshing on a zoom is sometimes unreliable. Panning is much more reliable.
- Much of the data export is "raw" (i.e. Place categories of "STADIUM_ARENA"). The initial releases will be about getting functionality correct.