WME Data Store (WDS) is a script for the Waze Map Editor that adds basic statistics (meagerly available for this initial release) and CSV export capability (available now) for some common data. The script requires Tampermonkey for Chrome or Greasemonkey for Firefox, and it is available here from GreasyFork: https://greasyfork.org/scripts/5322-wme-data-store
For anyone who is more comfortable dealing with spreadsheets, this makes it a little easier to spot anomalies such as city smudges, Places in need of address information, etc. Place and Segment exports include a permalink to the appropriate object while City exports include a permalink to the general vicinity.
Version 0.5.3 now adds a column to the Places CSV export for “PrimaryImageThumbnail”. If a Place has an image (approved or pending), there is now a link to the first image.
For version 0.5.5, I changed the “Approved” column to “PlaceApproved”, so the true/false there is whether the Place as a whole is approved. There are new columns for “ImageApproved”, "ImageUserName, “ImageUserRank”, and “ImageDateTime”. I noticed that sometimes where there is an image, the image username and rank are blank, and in those cases, they should be Private residential Places.
I don’t suppose you’d like to join us on the Toolbox development, eh?
We’ve had a “place list” on the todo list for quite some time… and it looks like you’ve figured out at least how to show a place list, if not also select and/or modify.
Version 0.6.1 cleans up the Primary Category export for Places so that it should match the same text you see in the editor. For example, “Gas Station” instead of “GAS_STATION”.
This release is a maintenance one but also removes the hover over the “Waze geek” icon.
Also, after having joined the WME Toolbox development team a few weeks ago and having the opportunity to contribute to that project, I’ve decided to sunset Waze Data Store going forward. After helping to bring the Place List to Toolbox as well as work on a few new, exciting features for that platform, I think that any potential features that I would have built into this script would likely end up in Toolbox anyway. I will leave the script up on GreasyFork for the time being, but if and when Toolbox has export capability, I’ll plan on taking it down.
