Skip to content
This repository has been archived by the owner on Nov 8, 2018. It is now read-only.

Request: Custom file names for custom metro extract requests #166

Open
IndyHurt opened this issue Jul 14, 2016 · 1 comment
Open

Request: Custom file names for custom metro extract requests #166

IndyHurt opened this issue Jul 14, 2016 · 1 comment
Labels

Comments

@IndyHurt
Copy link
Contributor

The file name of my first custom metro extract is ex_Gy4qNDDaADes7swaFXr33Wc4JwTVL.osm.pbf

It would be helpful to have a custom file name that uses the name of the area I searched for i.e. Trinidad-and-Tobago.osm.pbf

Even better might be the place name followed by a date that reflects the date of the date of the planet file used to obtain my custom metro extract - i.e. Trinidad-and-Tobago_20160714.osm.pbf

@migurski
Copy link
Contributor

@sleepylemur / @heffergm it’d be interesting to provide for a (non-unique) name in the ODES service, so that download URLs could be reformatted without losing the long unique identifier:

https://s3.amazonaws.com/mapzen.odes/{guid}/{name}.osm2pgsql-shapefiles.zip

This should have no effect on S3 keys, but may provide a better download experience. The names could be based on WoF as they are now, and need not be returned in the API.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

2 participants