alexwohlbruck's Comments
| Changeset | When | Comment |
|---|---|---|
| 164605054 | 9 months ago | too many nodes fighting for one spot i imagine aha |
| 164605054 | 9 months ago | lmao i'm gonna group these racks into one object, we will use capacity tag to indicate number of bikes that can fit |
| 163921373 | 9 months ago | I've visited the location and found no signage or wayfinding that suggests Brownstone Law to exist here. Suite 110, described as the office's location, is a UPS store and extends from both sides of the building. I am removing this POI |
| 163921373 | 9 months ago | I am reverting this change as the business info tags were placed on the inner building part instead of a separate node. Will replace the POI with it's own node and tags |
| 164261766 | 9 months ago | RIP |
| 140828953 | about 1 year ago | Correct me if I'm wrong, but isn't this road regarded as "boulevard"? |
| 155486367 | over 1 year ago | This change includes a node that has been moved incorrectly, I will correct this |
| 150897449 | over 1 year ago | I have actually made an app for that!
It is better to group up racks that are close together that you might consider a "clump". This will reduce clutter on the map and is easier for data queries. Then use the capacity tag to specify how many bikes can fit there. I usually mark the center of the row of stands for the node marker. You can however use an "area" way to draw the boundary of the bike parking area. Only a few are tagged this way but it is valid. |
| 151432356 | over 1 year ago | I have reverted this changeset as I have previously mapped the newly opened Sullenberger Aviation Museum which is located here, using the 2024 Mecklenberg nearmap imagery |
| 150897449 | over 1 year ago | Please be sure to add "amenity=bicycle_parking" tag to any bike racks you add to the map. This is important metadata to surface in apps which consume this information |
| 146574071 | over 1 year ago | Hi, I have removed a couple of these cycle paths you added in this changeset. For roads with painted cycle shoulders, we use tags on the road to indicate them. Dedicated cycle paths will get their own ways. |
| 138995709 | over 1 year ago | Btw, the height on buildings is *meters*, not feet. I am converting some of these but keep this in mind in the future. Many buildings in Charlotte have been tagged incorrectly |
| 149147525 | over 1 year ago | This business sells shipping supplies such as boxes, packing supplies, and envelopes. They are also an authorized ship center for UPS, Fedex, DHL, USPS. How would you consider tagging this place? |
| 147075651 | almost 2 years ago | ahhh sick, way to go man. got some work to do! |
| 147075651 | almost 2 years ago | how did you get 24 imagery ? |
| 146343982 | almost 2 years ago | I had added those and then removed them in a second edit since they seemed to clutter the map and aren't useful to the public or for navigation. I can update these as private, but should I do them along the entire shoreline? |
| 143592990 | about 2 years ago | Users can still enter the capacity manually if they see fit. I should make it clear what the computed capacity will be. |
| 143592990 | about 2 years ago | Should it be something included permanently? I can do that easily, this is the original question asked by the user and the capacity is computed automatically depending on the rack type. Users can also opt to enter capacity manually. |
| 143592990 | about 2 years ago | It does mark the number of individual "racks", but I did add this as a metadata field in my app, forgot to remove in the payload request so some of these elements still have the tag. You can remove if you like, it's not needed. |
| 143786086 | about 2 years ago | I had updated my app from a simple "capacity" field to a more intuitive input that asked, for example "How many stands?", then the capacity will be calculated based on that answer. The altCapacity is that value. I had forgotten to delete that field from the payload data, so it snuck in to a couple of my edits. I will remove. |