Skip to content

Develop test harness #4

@CloudNiner

Description

@CloudNiner

I'm...not sure what this looks like yet.

We'll need an osmx database set to a sequence number and an osm change file that has relevant changes within the extent of the osmx database. Not a problem if we test on the whole world, but that database would be huge. and it would be nice to replace the osmx database with the base version after each test so we can repeatedly use the same change file for consistency. Holding two copies of the osmx db for the whole world would require a 2TB drive.

All that to say, think about this more before pointing and addressing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions